<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_02_25_0548259</id>
	<title><em>Quake 3</em> For Android</title>
	<author>Soulskill</author>
	<datestamp>1267127580000</datestamp>
	<htmltext>An anonymous reader writes <i>"Over the last two months I <a href="http://code.google.com/p/kwaak3/">ported <em>Quake 3</em> to Android as a hobby project</a>. It only took a few days to get the game working. More time was spent on tweaking the game experience. Right now the game runs at 25fps on a Motorola Milestone/Droid. 'Normally when you compile C/C++ code using the Android NDK, the compiler targets a generic ARMv5 CPU which uses software floating-point. Without any optimizations and audio <em>Quake 3</em> runs at 22fps. Since <em>Quake 3</em> uses a lot of floating-point calculations, I tried a better C-compiler (GCC 4.4.0 from Android GIT) which supports modern CPUs and Neon SIMD instructions. <em>Quake 3</em> optimized for Cortex-A8 with Neon is about 15\% faster without audio and 35\% with audio compared to the generic ARMv5 build. Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support, so sin/cos/log/.. take advantage of the FPU.''</i></htmltext>
<tokenext>An anonymous reader writes " Over the last two months I ported Quake 3 to Android as a hobby project .
It only took a few days to get the game working .
More time was spent on tweaking the game experience .
Right now the game runs at 25fps on a Motorola Milestone/Droid .
'Normally when you compile C/C + + code using the Android NDK , the compiler targets a generic ARMv5 CPU which uses software floating-point .
Without any optimizations and audio Quake 3 runs at 22fps .
Since Quake 3 uses a lot of floating-point calculations , I tried a better C-compiler ( GCC 4.4.0 from Android GIT ) which supports modern CPUs and Neon SIMD instructions .
Quake 3 optimized for Cortex-A8 with Neon is about 15 \ % faster without audio and 35 \ % with audio compared to the generic ARMv5 build .
Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support , so sin/cos/log/.. take advantage of the FPU .
''</tokentext>
<sentencetext>An anonymous reader writes "Over the last two months I ported Quake 3 to Android as a hobby project.
It only took a few days to get the game working.
More time was spent on tweaking the game experience.
Right now the game runs at 25fps on a Motorola Milestone/Droid.
'Normally when you compile C/C++ code using the Android NDK, the compiler targets a generic ARMv5 CPU which uses software floating-point.
Without any optimizations and audio Quake 3 runs at 22fps.
Since Quake 3 uses a lot of floating-point calculations, I tried a better C-compiler (GCC 4.4.0 from Android GIT) which supports modern CPUs and Neon SIMD instructions.
Quake 3 optimized for Cortex-A8 with Neon is about 15\% faster without audio and 35\% with audio compared to the generic ARMv5 build.
Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support, so sin/cos/log/.. take advantage of the FPU.
''</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600</id>
	<title>Hmmm.</title>
	<author>Anonymous</author>
	<datestamp>1267088640000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>Dunno why TFA didn't include it, but there is <a href="http://www.youtube.com/watch?v=q9Xaz7ECI4M&amp;feature=player\_embedded" title="youtube.com" rel="nofollow">video</a> [youtube.com].</p></htmltext>
<tokenext>Dunno why TFA did n't include it , but there is video [ youtube.com ] .</tokentext>
<sentencetext>Dunno why TFA didn't include it, but there is video [youtube.com].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950</id>
	<title>Are libraries even involved</title>
	<author>Anonymous</author>
	<datestamp>1267093680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm not familiar with ARM architecture, but this bit still sounds suspicious to me:</p><p><div class="quote"><p>Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support, so sin/cos/log/.. take advantage of the FPU.''"</p></div><p>On x86 at least, no C compiler worth its salt would even generate a call to a library function for something like sin or cos - why bother with all the overhead of a call, if ultimately it's a single instruction in the FPU?</p><p>Now, one trick there is that it actually depends on compiler settings - whether you specify "precise" floating-point mode (which is fully standard conformant), or "fast" mode. Only the latter seem to produce an inlined implementation of sin &amp; cos. Are you sure you're compiling with -ffast-math?</p></div>
	</htmltext>
<tokenext>I 'm not familiar with ARM architecture , but this bit still sounds suspicious to me : Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support , so sin/cos/log/.. take advantage of the FPU .
' ' " On x86 at least , no C compiler worth its salt would even generate a call to a library function for something like sin or cos - why bother with all the overhead of a call , if ultimately it 's a single instruction in the FPU ? Now , one trick there is that it actually depends on compiler settings - whether you specify " precise " floating-point mode ( which is fully standard conformant ) , or " fast " mode .
Only the latter seem to produce an inlined implementation of sin &amp; cos. Are you sure you 're compiling with -ffast-math ?</tokentext>
<sentencetext>I'm not familiar with ARM architecture, but this bit still sounds suspicious to me:Most likely the performance improvement compared to the ARMv5 build is not that big because the system libraries of the Milestone have been compiled with FPU support, so sin/cos/log/.. take advantage of the FPU.
''"On x86 at least, no C compiler worth its salt would even generate a call to a library function for something like sin or cos - why bother with all the overhead of a call, if ultimately it's a single instruction in the FPU?Now, one trick there is that it actually depends on compiler settings - whether you specify "precise" floating-point mode (which is fully standard conformant), or "fast" mode.
Only the latter seem to produce an inlined implementation of sin &amp; cos. Are you sure you're compiling with -ffast-math?
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271218</id>
	<title>modg up</title>
	<author>Anonymous</author>
	<datestamp>1267108200000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>eto be about doing</htmltext>
<tokenext>eto be about doing</tokentext>
<sentencetext>eto be about doing</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269808</id>
	<title>Just another note:</title>
	<author>Anonymous</author>
	<datestamp>1267091340000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>In the story it doesn't say that it runs the best on the Phone it's developed: The Milestone/Droid.<br>Also it doesn't say that it does not run on android 1.5 and that it again runs the best on android 2.0 and upwards.</p></htmltext>
<tokenext>In the story it does n't say that it runs the best on the Phone it 's developed : The Milestone/Droid.Also it does n't say that it does not run on android 1.5 and that it again runs the best on android 2.0 and upwards .</tokentext>
<sentencetext>In the story it doesn't say that it runs the best on the Phone it's developed: The Milestone/Droid.Also it doesn't say that it does not run on android 1.5 and that it again runs the best on android 2.0 and upwards.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270954</id>
	<title>Re:DUDE You're incredible</title>
	<author>cpricejones</author>
	<datestamp>1267106100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How about Crisis?</htmltext>
<tokenext>How about Crisis ?</tokentext>
<sentencetext>How about Crisis?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270266</id>
	<title>Re:Hmmm.</title>
	<author>Anonymous</author>
	<datestamp>1267097460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Maybe the video wasn't included because it is gawdawful?  85\% of screen real estate occupied by background and two hands; long, long wait before game-play starts, no closeup of control inputs.</htmltext>
<tokenext>Maybe the video was n't included because it is gawdawful ?
85 \ % of screen real estate occupied by background and two hands ; long , long wait before game-play starts , no closeup of control inputs .</tokentext>
<sentencetext>Maybe the video wasn't included because it is gawdawful?
85\% of screen real estate occupied by background and two hands; long, long wait before game-play starts, no closeup of control inputs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270324</id>
	<title>See yesterday's NS</title>
	<author>Anonymous</author>
	<datestamp>1267098360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Or a <a href="http://www.newscientist.com/article/dn18558-magnet-magic-puts-phone-control-in-the-air.html?DCMP=OTC-rss&amp;nsref=online-news" title="newscientist.com" rel="nofollow">magnet-powered natural gesture interface</a> [newscientist.com].</p></htmltext>
<tokenext>Or a magnet-powered natural gesture interface [ newscientist.com ] .</tokentext>
<sentencetext>Or a magnet-powered natural gesture interface [newscientist.com].</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269780</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270242</id>
	<title>Re:Are libraries even involved</title>
	<author>quadrox</author>
	<datestamp>1267097220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I believe most (older?) versions of ARM come without a FPU. Presumably the ARM processor on the Droid/Milestone is one of those that do have a FPU and thus can take advantage of it.</p><p>That's what I've been told, not sure whether it's correct.</p></htmltext>
<tokenext>I believe most ( older ?
) versions of ARM come without a FPU .
Presumably the ARM processor on the Droid/Milestone is one of those that do have a FPU and thus can take advantage of it.That 's what I 've been told , not sure whether it 's correct .</tokentext>
<sentencetext>I believe most (older?
) versions of ARM come without a FPU.
Presumably the ARM processor on the Droid/Milestone is one of those that do have a FPU and thus can take advantage of it.That's what I've been told, not sure whether it's correct.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270158</id>
	<title>Look carefully now slashdot... This is news!</title>
	<author>Anonymous</author>
	<datestamp>1267096200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>for a change</p></htmltext>
<tokenext>for a change</tokentext>
<sentencetext>for a change</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269778</id>
	<title>Re:Not impressed</title>
	<author>Grey Ninja</author>
	<datestamp>1267091040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I highly doubt that Unreal 3 would run better than the Quake 3 engine.  Modern does not equal better.  Most of the things that newer engines do better are somewhat worthless on a cell phone.  You want simplicity and speed on a cell phone, not abstraction and flexibility.  I would think that the Quake 3 engine would knock the pants off of Unreal 3.</htmltext>
<tokenext>I highly doubt that Unreal 3 would run better than the Quake 3 engine .
Modern does not equal better .
Most of the things that newer engines do better are somewhat worthless on a cell phone .
You want simplicity and speed on a cell phone , not abstraction and flexibility .
I would think that the Quake 3 engine would knock the pants off of Unreal 3 .</tokentext>
<sentencetext>I highly doubt that Unreal 3 would run better than the Quake 3 engine.
Modern does not equal better.
Most of the things that newer engines do better are somewhat worthless on a cell phone.
You want simplicity and speed on a cell phone, not abstraction and flexibility.
I would think that the Quake 3 engine would knock the pants off of Unreal 3.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269654</id>
	<title>Kudos!</title>
	<author>Anonymous</author>
	<datestamp>1267089420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Really! This is one of the main reasons I love open source, things like this and others would be imposible/difficult with the iPhone OS.</p></htmltext>
<tokenext>Really !
This is one of the main reasons I love open source , things like this and others would be imposible/difficult with the iPhone OS .</tokentext>
<sentencetext>Really!
This is one of the main reasons I love open source, things like this and others would be imposible/difficult with the iPhone OS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270350</id>
	<title>Re:Are libraries even involved</title>
	<author>Thunderbird2k</author>
	<datestamp>1267098840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yes I'm compiling kwaak3 using -ffast-math but in all cases it uses libm. It is only a hypothesis on why perhaps a generic soft-float build is not that much slower than a floating-point optimized build. You would expect that a soft-float version is a lot slower because quake3 uses floats for most of its math.</htmltext>
<tokenext>Yes I 'm compiling kwaak3 using -ffast-math but in all cases it uses libm .
It is only a hypothesis on why perhaps a generic soft-float build is not that much slower than a floating-point optimized build .
You would expect that a soft-float version is a lot slower because quake3 uses floats for most of its math .</tokentext>
<sentencetext>Yes I'm compiling kwaak3 using -ffast-math but in all cases it uses libm.
It is only a hypothesis on why perhaps a generic soft-float build is not that much slower than a floating-point optimized build.
You would expect that a soft-float version is a lot slower because quake3 uses floats for most of its math.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272920</id>
	<title>Re:How about integers instead of floating point?</title>
	<author>-kyz</author>
	<datestamp>1267117920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Because integers don't hold enough precision to be useful in modern graphics.</p><p>Believe it or not, they <b>are</b> currently useful for simply shaded/textured objects on phone-sized screens. You can use fixed point 16:16 numbers for that.</p><p>But they start being a hindrance after that because of the limited precision, and the amount of work you have to do to bring values back in line when doing multiplies or divides. You're generally wasting your time if the device you're targeting has a hardware FPU.</p><p>You can see for yourself what it looks like when you try and use fixed point values for 3D calculations. Get a Playstation (i.e. Playstation 1) emulator and run a game at 1024x768 or higher. You'll now see all the vertexes pop whenever you move about, even though they're meant to be static.</p><p>It's because the PS1 hardware used fixed point values throughout, and while the programmers were careful to make sure they wouldn't pop 1 pixel on a 320x256 screen, they didn't check what happened when you had a larger screen size.</p></htmltext>
<tokenext>Because integers do n't hold enough precision to be useful in modern graphics.Believe it or not , they are currently useful for simply shaded/textured objects on phone-sized screens .
You can use fixed point 16 : 16 numbers for that.But they start being a hindrance after that because of the limited precision , and the amount of work you have to do to bring values back in line when doing multiplies or divides .
You 're generally wasting your time if the device you 're targeting has a hardware FPU.You can see for yourself what it looks like when you try and use fixed point values for 3D calculations .
Get a Playstation ( i.e .
Playstation 1 ) emulator and run a game at 1024x768 or higher .
You 'll now see all the vertexes pop whenever you move about , even though they 're meant to be static.It 's because the PS1 hardware used fixed point values throughout , and while the programmers were careful to make sure they would n't pop 1 pixel on a 320x256 screen , they did n't check what happened when you had a larger screen size .</tokentext>
<sentencetext>Because integers don't hold enough precision to be useful in modern graphics.Believe it or not, they are currently useful for simply shaded/textured objects on phone-sized screens.
You can use fixed point 16:16 numbers for that.But they start being a hindrance after that because of the limited precision, and the amount of work you have to do to bring values back in line when doing multiplies or divides.
You're generally wasting your time if the device you're targeting has a hardware FPU.You can see for yourself what it looks like when you try and use fixed point values for 3D calculations.
Get a Playstation (i.e.
Playstation 1) emulator and run a game at 1024x768 or higher.
You'll now see all the vertexes pop whenever you move about, even though they're meant to be static.It's because the PS1 hardware used fixed point values throughout, and while the programmers were careful to make sure they wouldn't pop 1 pixel on a 320x256 screen, they didn't check what happened when you had a larger screen size.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270008</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784</id>
	<title>What about the N900?</title>
	<author>anomnomnomymous</author>
	<datestamp>1267091160000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>The N900 has also recently received a port of IOQuake3: Have a look at their <a href="http://ioquake3.org/" title="ioquake3.org">site</a> [ioquake3.org] for more details.<br> <br>
If you're looking for a very nice (open) phone, I'd go with the N900. No, I'm not from Nokia, just a -very- satisfied customer.</htmltext>
<tokenext>The N900 has also recently received a port of IOQuake3 : Have a look at their site [ ioquake3.org ] for more details .
If you 're looking for a very nice ( open ) phone , I 'd go with the N900 .
No , I 'm not from Nokia , just a -very- satisfied customer .</tokentext>
<sentencetext>The N900 has also recently received a port of IOQuake3: Have a look at their site [ioquake3.org] for more details.
If you're looking for a very nice (open) phone, I'd go with the N900.
No, I'm not from Nokia, just a -very- satisfied customer.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31275236</id>
	<title>So when it's the Android, it's news?</title>
	<author>Hurricane78</author>
	<datestamp>1267126020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I&rsquo;m sorry, but not only does the N900 run <a href="http://nokia-n900.com/quake-3-arena-on-the-nokia-n900-including-multiplayer-mode/" title="nokia-n900.com">Quake 3 (and very smoothly)</a> [nokia-n900.com]. No, it also runs <a href="http://dailymobile.se/2010/02/09/windows-95-running-on-the-nokia-n900/" title="dailymobile.se">Windows 95</a> [dailymobile.se] and <a href="http://thenokiablog.com/2010/01/31/mac-os-x-nokia-n900/" title="thenokiablog.com">MacOS X</a> [thenokiablog.com]!</p><p>But I haven&rsquo;t seen news for this on<nobr> <wbr></nobr>/.</p><p>Funny that this could never ever happen with iPhone (locked down), so we&rsquo;re at least safe from that.<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>I    m sorry , but not only does the N900 run Quake 3 ( and very smoothly ) [ nokia-n900.com ] .
No , it also runs Windows 95 [ dailymobile.se ] and MacOS X [ thenokiablog.com ] ! But I haven    t seen news for this on /.Funny that this could never ever happen with iPhone ( locked down ) , so we    re at least safe from that .
; )</tokentext>
<sentencetext>I’m sorry, but not only does the N900 run Quake 3 (and very smoothly) [nokia-n900.com].
No, it also runs Windows 95 [dailymobile.se] and MacOS X [thenokiablog.com]!But I haven’t seen news for this on /.Funny that this could never ever happen with iPhone (locked down), so we’re at least safe from that.
;)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269774</id>
	<title>lets do video</title>
	<author>Teque5</author>
	<datestamp>1267091040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>here is the conspicuously missing video: <a href="http://www.youtube.com/watch?v=q9Xaz7ECI4M" title="youtube.com" rel="nofollow">http://www.youtube.com/watch?v=q9Xaz7ECI4M</a> [youtube.com]</htmltext>
<tokenext>here is the conspicuously missing video : http : //www.youtube.com/watch ? v = q9Xaz7ECI4M [ youtube.com ]</tokentext>
<sentencetext>here is the conspicuously missing video: http://www.youtube.com/watch?v=q9Xaz7ECI4M [youtube.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270648</id>
	<title>What about the classics?</title>
	<author>jonr</author>
	<datestamp>1267103040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>To heck with Quake. How about all those old 16 bit strategy games that are like made for cellphones? CIV series? MOO? StarCraft? MoM? Where are they?</p></htmltext>
<tokenext>To heck with Quake .
How about all those old 16 bit strategy games that are like made for cellphones ?
CIV series ?
MOO ? StarCraft ?
MoM ? Where are they ?</tokentext>
<sentencetext>To heck with Quake.
How about all those old 16 bit strategy games that are like made for cellphones?
CIV series?
MOO? StarCraft?
MoM? Where are they?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628</id>
	<title>Running Demos</title>
	<author>get quad</author>
	<datestamp>1267089000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've been unable to get any demos to work which were recorded on the 1.32c exe, obviously because this is based off ioq3. If anyone cares to record or get vanilla demos for showcase purposes I'm all ears. OSP/mods appears to run, but being able to play match demos to show off gameplay would be the BOMB.

Also, id software should REALLY take notice here and release a spectator-only client for QuakeLive which runs on Adroid<nobr> <wbr></nobr>;-)</htmltext>
<tokenext>I 've been unable to get any demos to work which were recorded on the 1.32c exe , obviously because this is based off ioq3 .
If anyone cares to record or get vanilla demos for showcase purposes I 'm all ears .
OSP/mods appears to run , but being able to play match demos to show off gameplay would be the BOMB .
Also , id software should REALLY take notice here and release a spectator-only client for QuakeLive which runs on Adroid ; - )</tokentext>
<sentencetext>I've been unable to get any demos to work which were recorded on the 1.32c exe, obviously because this is based off ioq3.
If anyone cares to record or get vanilla demos for showcase purposes I'm all ears.
OSP/mods appears to run, but being able to play match demos to show off gameplay would be the BOMB.
Also, id software should REALLY take notice here and release a spectator-only client for QuakeLive which runs on Adroid ;-)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272144</id>
	<title>time for RA3</title>
	<author>pak9rabid</author>
	<datestamp>1267113780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The next logical step, of course, is RA3 =D</htmltext>
<tokenext>The next logical step , of course , is RA3 = D</tokentext>
<sentencetext>The next logical step, of course, is RA3 =D</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270750</id>
	<title>Re:Good job</title>
	<author>TheRaven64</author>
	<datestamp>1267103880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>There are two big differences between the MIPS32 you'll find in the A320 and, basically, any recent ARM SoC.  One is that the last two or three generations of ARM chips have hardware FPUs, while the A320's CPU does not.  If you're running Debian, then the A320 will be painfully slow, because the default Debian install for it was configured for hard float, meaning that every floating point instruction (including loads and stores to the FPU registers) raises an invalid instruction interrupt.  This is then caught by the kernel, which inspects the old program counter, decodes the instruction (in software) and emulates it.  This means FPU-intensive code runs at about 1\% of the speed of a hardware implementation.  Recompiling with softfloat support (which changes the calling conventions, so you need to recompile everything from libc up) makes it a lot faster.</p><p>
The other big difference is that recent ARM SoCs all come with a GPU.  The latest generation all support OpenGL ES 2.0, so you get a fully programmable pipeline (shaders and so forth), while the older ones have ES 1, which supports only the fixed-function pipeline.  Even the old ES 1 GPUs are faster and more capable than anything on the market when Q3 was released.  </p><p>
In short, the A320 is a pretty useless machine.  It's massively underpowered even by handheld standards (the Nokia 770 will be faster in most uses).  The newer cheap MIPS-based use the Loongson 2F, which is a 64-bit superscalar MIPS III implementation (still little endian), and two FPUs, but a lot of them still don't come with a GPU, so you're looking at software rendering only.  They're more than powerful enough for Quake 2, but Quake 3 required OpenGL hardware, so they'll probably struggle a lot.</p></htmltext>
<tokenext>There are two big differences between the MIPS32 you 'll find in the A320 and , basically , any recent ARM SoC .
One is that the last two or three generations of ARM chips have hardware FPUs , while the A320 's CPU does not .
If you 're running Debian , then the A320 will be painfully slow , because the default Debian install for it was configured for hard float , meaning that every floating point instruction ( including loads and stores to the FPU registers ) raises an invalid instruction interrupt .
This is then caught by the kernel , which inspects the old program counter , decodes the instruction ( in software ) and emulates it .
This means FPU-intensive code runs at about 1 \ % of the speed of a hardware implementation .
Recompiling with softfloat support ( which changes the calling conventions , so you need to recompile everything from libc up ) makes it a lot faster .
The other big difference is that recent ARM SoCs all come with a GPU .
The latest generation all support OpenGL ES 2.0 , so you get a fully programmable pipeline ( shaders and so forth ) , while the older ones have ES 1 , which supports only the fixed-function pipeline .
Even the old ES 1 GPUs are faster and more capable than anything on the market when Q3 was released .
In short , the A320 is a pretty useless machine .
It 's massively underpowered even by handheld standards ( the Nokia 770 will be faster in most uses ) .
The newer cheap MIPS-based use the Loongson 2F , which is a 64-bit superscalar MIPS III implementation ( still little endian ) , and two FPUs , but a lot of them still do n't come with a GPU , so you 're looking at software rendering only .
They 're more than powerful enough for Quake 2 , but Quake 3 required OpenGL hardware , so they 'll probably struggle a lot .</tokentext>
<sentencetext>There are two big differences between the MIPS32 you'll find in the A320 and, basically, any recent ARM SoC.
One is that the last two or three generations of ARM chips have hardware FPUs, while the A320's CPU does not.
If you're running Debian, then the A320 will be painfully slow, because the default Debian install for it was configured for hard float, meaning that every floating point instruction (including loads and stores to the FPU registers) raises an invalid instruction interrupt.
This is then caught by the kernel, which inspects the old program counter, decodes the instruction (in software) and emulates it.
This means FPU-intensive code runs at about 1\% of the speed of a hardware implementation.
Recompiling with softfloat support (which changes the calling conventions, so you need to recompile everything from libc up) makes it a lot faster.
The other big difference is that recent ARM SoCs all come with a GPU.
The latest generation all support OpenGL ES 2.0, so you get a fully programmable pipeline (shaders and so forth), while the older ones have ES 1, which supports only the fixed-function pipeline.
Even the old ES 1 GPUs are faster and more capable than anything on the market when Q3 was released.
In short, the A320 is a pretty useless machine.
It's massively underpowered even by handheld standards (the Nokia 770 will be faster in most uses).
The newer cheap MIPS-based use the Loongson 2F, which is a 64-bit superscalar MIPS III implementation (still little endian), and two FPUs, but a lot of them still don't come with a GPU, so you're looking at software rendering only.
They're more than powerful enough for Quake 2, but Quake 3 required OpenGL hardware, so they'll probably struggle a lot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078</id>
	<title>I thought the NDK couldn't use opengl</title>
	<author>Anonymous</author>
	<datestamp>1267095420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>did they fix that?</p></htmltext>
<tokenext>did they fix that ?</tokentext>
<sentencetext>did they fix that?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270132</id>
	<title>Re:Are libraries even involved</title>
	<author>Tapewolf</author>
	<datestamp>1267096020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>AFAIK, most ARM processors do not currently have an FPU.  Maybe as FPUs become more common support for using the FPU directly will be added.  Just a guess.</htmltext>
<tokenext>AFAIK , most ARM processors do not currently have an FPU .
Maybe as FPUs become more common support for using the FPU directly will be added .
Just a guess .</tokentext>
<sentencetext>AFAIK, most ARM processors do not currently have an FPU.
Maybe as FPUs become more common support for using the FPU directly will be added.
Just a guess.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270862</id>
	<title>There's a map for that</title>
	<author>Anonymous</author>
	<datestamp>1267105020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>If you're looking for a very nice (open) phone, I'd go with the N900.</p></div><p>The advantage of the port to Motorola Droid is that Verizon Wireless carries Motorola Droid. In the United States, the big three wireless carriers don't give a discount for bringing your own phone, so most people who want coverage choose a carrier first and then choose one of the phones that the carrier subsidizes. And as I understand it, Nokia has had trouble getting its Symbian-based and Maemo-based phones into Verizon, Sprint, and AT&amp;T. So which U.S. wireless carrier do you recommend for use with the N900?</p></div>
	</htmltext>
<tokenext>If you 're looking for a very nice ( open ) phone , I 'd go with the N900.The advantage of the port to Motorola Droid is that Verizon Wireless carries Motorola Droid .
In the United States , the big three wireless carriers do n't give a discount for bringing your own phone , so most people who want coverage choose a carrier first and then choose one of the phones that the carrier subsidizes .
And as I understand it , Nokia has had trouble getting its Symbian-based and Maemo-based phones into Verizon , Sprint , and AT&amp;T .
So which U.S. wireless carrier do you recommend for use with the N900 ?</tokentext>
<sentencetext>If you're looking for a very nice (open) phone, I'd go with the N900.The advantage of the port to Motorola Droid is that Verizon Wireless carries Motorola Droid.
In the United States, the big three wireless carriers don't give a discount for bringing your own phone, so most people who want coverage choose a carrier first and then choose one of the phones that the carrier subsidizes.
And as I understand it, Nokia has had trouble getting its Symbian-based and Maemo-based phones into Verizon, Sprint, and AT&amp;T.
So which U.S. wireless carrier do you recommend for use with the N900?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269810</id>
	<title>Re:Mouse</title>
	<author>golden age villain</author>
	<datestamp>1267091400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>There are some FPS on the iPhone were you move using a virtual joystick in the lower left corner and look around using the rest of the screen. It's not perfect but it's ok to play casually on a small mobile device.</htmltext>
<tokenext>There are some FPS on the iPhone were you move using a virtual joystick in the lower left corner and look around using the rest of the screen .
It 's not perfect but it 's ok to play casually on a small mobile device .</tokentext>
<sentencetext>There are some FPS on the iPhone were you move using a virtual joystick in the lower left corner and look around using the rest of the screen.
It's not perfect but it's ok to play casually on a small mobile device.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642</id>
	<title>Good job</title>
	<author>Anonymous</author>
	<datestamp>1267089240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is actually great news. I have been developing a game based on ioquake3 for a couple of years now. Each time someone ports the Q3 engine to a new platform, it opens up a whole new platform that I can target. Good job.</p><p>This does bring up another question. What are the features of the target ARM CPU and what clockspeed does it run at? I have a Dingoo A320 (MIPS32 based CPU with a native clockspeed of 400MHz) that seems to barely run Quake 1. If Q3 can run on an ARM powered phone, it should be able to run at similar speed on the Dingoo.</p></htmltext>
<tokenext>This is actually great news .
I have been developing a game based on ioquake3 for a couple of years now .
Each time someone ports the Q3 engine to a new platform , it opens up a whole new platform that I can target .
Good job.This does bring up another question .
What are the features of the target ARM CPU and what clockspeed does it run at ?
I have a Dingoo A320 ( MIPS32 based CPU with a native clockspeed of 400MHz ) that seems to barely run Quake 1 .
If Q3 can run on an ARM powered phone , it should be able to run at similar speed on the Dingoo .</tokentext>
<sentencetext>This is actually great news.
I have been developing a game based on ioquake3 for a couple of years now.
Each time someone ports the Q3 engine to a new platform, it opens up a whole new platform that I can target.
Good job.This does bring up another question.
What are the features of the target ARM CPU and what clockspeed does it run at?
I have a Dingoo A320 (MIPS32 based CPU with a native clockspeed of 400MHz) that seems to barely run Quake 1.
If Q3 can run on an ARM powered phone, it should be able to run at similar speed on the Dingoo.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271818</id>
	<title>Re:There's a map for that</title>
	<author>Anonymous</author>
	<datestamp>1267111800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Sorry, I'm from the UK here<nobr> <wbr></nobr>:)<br>
T-mobile and Vodafone both carry this phone (with excellent packages I might add: I'm currently on a 2 year contract, 20 pounds per months for 300 texts, 300 callminutes and 'unlimited' internet)<br> <br>
But as said: If you have the chance, certainly have a look at this phone.<br>
I decided to not go with the iPhone (though I love its intuitive interface), as I don't like their restrictions with regards to getting your own software/third party software on there. I think this motivation was a blessing in disguise as the N900 is the same, if not better than the iPhone with regards to interface. With its 4 desktops, plenty of customization possibilities, this is every tinkerer's dream-phone.<br>
Damn, reading back this post, I -should- get paid by Nokia: I look like a damn ad!<nobr> <wbr></nobr>;-)</htmltext>
<tokenext>Sorry , I 'm from the UK here : ) T-mobile and Vodafone both carry this phone ( with excellent packages I might add : I 'm currently on a 2 year contract , 20 pounds per months for 300 texts , 300 callminutes and 'unlimited ' internet ) But as said : If you have the chance , certainly have a look at this phone .
I decided to not go with the iPhone ( though I love its intuitive interface ) , as I do n't like their restrictions with regards to getting your own software/third party software on there .
I think this motivation was a blessing in disguise as the N900 is the same , if not better than the iPhone with regards to interface .
With its 4 desktops , plenty of customization possibilities , this is every tinkerer 's dream-phone .
Damn , reading back this post , I -should- get paid by Nokia : I look like a damn ad !
; - )</tokentext>
<sentencetext>Sorry, I'm from the UK here :)
T-mobile and Vodafone both carry this phone (with excellent packages I might add: I'm currently on a 2 year contract, 20 pounds per months for 300 texts, 300 callminutes and 'unlimited' internet) 
But as said: If you have the chance, certainly have a look at this phone.
I decided to not go with the iPhone (though I love its intuitive interface), as I don't like their restrictions with regards to getting your own software/third party software on there.
I think this motivation was a blessing in disguise as the N900 is the same, if not better than the iPhone with regards to interface.
With its 4 desktops, plenty of customization possibilities, this is every tinkerer's dream-phone.
Damn, reading back this post, I -should- get paid by Nokia: I look like a damn ad!
;-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31274198</id>
	<title>Re:What about the classics?</title>
	<author>Anonymous</author>
	<datestamp>1267122480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>yep, go ask the owners of those games to release the source code under AN FREE AND OPEN SOURCE license.</p></htmltext>
<tokenext>yep , go ask the owners of those games to release the source code under AN FREE AND OPEN SOURCE license .</tokentext>
<sentencetext>yep, go ask the owners of those games to release the source code under AN FREE AND OPEN SOURCE license.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270648</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270164</id>
	<title>Accelerometers</title>
	<author>Anonymous</author>
	<datestamp>1267096260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Wow I can't believe there is so much trouble over the controls, just use the accelerometer to control panning then you can play with just one hand on the dpad for movement and shooting.  That would be amazing.</p></htmltext>
<tokenext>Wow I ca n't believe there is so much trouble over the controls , just use the accelerometer to control panning then you can play with just one hand on the dpad for movement and shooting .
That would be amazing .</tokentext>
<sentencetext>Wow I can't believe there is so much trouble over the controls, just use the accelerometer to control panning then you can play with just one hand on the dpad for movement and shooting.
That would be amazing.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716</id>
	<title>Mouse</title>
	<author>mxh83</author>
	<datestamp>1267090200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The problem is that FPS like Q3 needs a proper mouse.  Otherwise its no fun.</htmltext>
<tokenext>The problem is that FPS like Q3 needs a proper mouse .
Otherwise its no fun .</tokentext>
<sentencetext>The problem is that FPS like Q3 needs a proper mouse.
Otherwise its no fun.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269590</id>
	<title>Great job.</title>
	<author>ipquickly</author>
	<datestamp>1267088460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Q3 is still one of my favorite games. The first thought that came to my mind when I read this was</p><p>"Do we have to hear about every case of someone porting something like this(doom,quake, etc)to a new device"</p><p>But considering all the effort that you put into doing this, I must say that I admire your dedication and attention to detail.</p><p>Great job.</p></htmltext>
<tokenext>Q3 is still one of my favorite games .
The first thought that came to my mind when I read this was " Do we have to hear about every case of someone porting something like this ( doom,quake , etc ) to a new device " But considering all the effort that you put into doing this , I must say that I admire your dedication and attention to detail.Great job .</tokentext>
<sentencetext>Q3 is still one of my favorite games.
The first thought that came to my mind when I read this was"Do we have to hear about every case of someone porting something like this(doom,quake, etc)to a new device"But considering all the effort that you put into doing this, I must say that I admire your dedication and attention to detail.Great job.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270674</id>
	<title>Re:DUDE You're incredible</title>
	<author>TheRaven64</author>
	<datestamp>1267103220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Team Fortress has been running on handhelds for ages, and the source code was open for all except the last few versions, although it didn't need to be because Quake ran it in a bytecode interpreter so it was cross-platform.  If you mean TFC or TF2 then you should specify.</htmltext>
<tokenext>Team Fortress has been running on handhelds for ages , and the source code was open for all except the last few versions , although it did n't need to be because Quake ran it in a bytecode interpreter so it was cross-platform .
If you mean TFC or TF2 then you should specify .</tokentext>
<sentencetext>Team Fortress has been running on handhelds for ages, and the source code was open for all except the last few versions, although it didn't need to be because Quake ran it in a bytecode interpreter so it was cross-platform.
If you mean TFC or TF2 then you should specify.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269968</id>
	<title>mo3 0p</title>
	<author>Anonymous</author>
	<datestamp>1267093920000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext>things I still elected, we took dim. IfQ *BSD is</htmltext>
<tokenext>things I still elected , we took dim .
IfQ * BSD is</tokentext>
<sentencetext>things I still elected, we took dim.
IfQ *BSD is</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270258</id>
	<title>Caution: Rickroll</title>
	<author>Anonymous</author>
	<datestamp>1267097400000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Parent link is a Rickroll.</p></htmltext>
<tokenext>Parent link is a Rickroll .</tokentext>
<sentencetext>Parent link is a Rickroll.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269780</id>
	<title>Re:Mouse</title>
	<author>haystor</author>
	<datestamp>1267091100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I disagree, I think you should look around the world by moving the phone, then thrusting it forward to shoot.  This would be awesome...for everyone else watching.</p></htmltext>
<tokenext>I disagree , I think you should look around the world by moving the phone , then thrusting it forward to shoot .
This would be awesome...for everyone else watching .</tokentext>
<sentencetext>I disagree, I think you should look around the world by moving the phone, then thrusting it forward to shoot.
This would be awesome...for everyone else watching.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272930</id>
	<title>Re:I thought the NDK couldn't use opengl</title>
	<author>Anonymous</author>
	<datestamp>1267117980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yes.</p></htmltext>
<tokenext>Yes .</tokentext>
<sentencetext>Yes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269794</id>
	<title>Re:Mouse</title>
	<author>Anonymous</author>
	<datestamp>1267091280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Not true. Perfect Dark was a wonderful game. But I have to agree that the controls as is are sucky. Most people are used to movement on their left hand, and looking around with the touch screen doesn't really seem to work right now. Either the acceleration curve needs to be tweaked so you can keep your finger in one spot in the corner without having to swipe it all over the place, or looking around needs to be moved to the direction pad, possibly with some aiming assistance like most console fps games have.</p></htmltext>
<tokenext>Not true .
Perfect Dark was a wonderful game .
But I have to agree that the controls as is are sucky .
Most people are used to movement on their left hand , and looking around with the touch screen does n't really seem to work right now .
Either the acceleration curve needs to be tweaked so you can keep your finger in one spot in the corner without having to swipe it all over the place , or looking around needs to be moved to the direction pad , possibly with some aiming assistance like most console fps games have .</tokentext>
<sentencetext>Not true.
Perfect Dark was a wonderful game.
But I have to agree that the controls as is are sucky.
Most people are used to movement on their left hand, and looking around with the touch screen doesn't really seem to work right now.
Either the acceleration curve needs to be tweaked so you can keep your finger in one spot in the corner without having to swipe it all over the place, or looking around needs to be moved to the direction pad, possibly with some aiming assistance like most console fps games have.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270186</id>
	<title>Re:Good job</title>
	<author>Anonymous</author>
	<datestamp>1267096500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The Milestone's based on an ARM Cortex A8 running at 600 MHz. It's probably the slowest-clocked of the "new" superphones. (For Americans, it's a Motorola Droid for Europe and Canada with some small software and SKU differences).</p><p>The Dingoo A320, according to the font of all wisdom, Wikipedia, is underclocked to 336MHz.</p><p>Last I looked, ARM seemed to have a definite edge in memory bandwidth, and had instructions aimed at handling media-rich applications much better than MIPS. I could, of course, be out of date on that.</p><p>So at an educated guess, I wouldn't expect your Dingoo to be able to touch a modern superphone. (Maybe at best a  quarter of the processing power assuming Neon optimizations?) Of course if the Dingoo's screen is low enough resolution, then that may not matter as much.</p></htmltext>
<tokenext>The Milestone 's based on an ARM Cortex A8 running at 600 MHz .
It 's probably the slowest-clocked of the " new " superphones .
( For Americans , it 's a Motorola Droid for Europe and Canada with some small software and SKU differences ) .The Dingoo A320 , according to the font of all wisdom , Wikipedia , is underclocked to 336MHz.Last I looked , ARM seemed to have a definite edge in memory bandwidth , and had instructions aimed at handling media-rich applications much better than MIPS .
I could , of course , be out of date on that.So at an educated guess , I would n't expect your Dingoo to be able to touch a modern superphone .
( Maybe at best a quarter of the processing power assuming Neon optimizations ?
) Of course if the Dingoo 's screen is low enough resolution , then that may not matter as much .</tokentext>
<sentencetext>The Milestone's based on an ARM Cortex A8 running at 600 MHz.
It's probably the slowest-clocked of the "new" superphones.
(For Americans, it's a Motorola Droid for Europe and Canada with some small software and SKU differences).The Dingoo A320, according to the font of all wisdom, Wikipedia, is underclocked to 336MHz.Last I looked, ARM seemed to have a definite edge in memory bandwidth, and had instructions aimed at handling media-rich applications much better than MIPS.
I could, of course, be out of date on that.So at an educated guess, I wouldn't expect your Dingoo to be able to touch a modern superphone.
(Maybe at best a  quarter of the processing power assuming Neon optimizations?
) Of course if the Dingoo's screen is low enough resolution, then that may not matter as much.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</id>
	<title>Not impressed</title>
	<author>Anonymous</author>
	<datestamp>1267089300000</datestamp>
	<modclass>Troll</modclass>
	<modscore>1</modscore>
	<htmltext>I'm not impressed. Epic had Unreal Engine 3 running on the iPhone back in december last year: <a href="http://www.anandtech.com/gadgets/showdoc.aspx?i=3695" title="anandtech.com" rel="nofollow">http://www.anandtech.com/gadgets/showdoc.aspx?i=3695</a> [anandtech.com]   Granted, it's a modified version and I don't think there's a working game available yet that uses it, but the engine is several generations newer than the Quake 3 one...  Still, nice job. It's weird to see 'big' games appearing on tiny devices. Didn't think the mobile technology would be this advanced so soon, tbh.</htmltext>
<tokenext>I 'm not impressed .
Epic had Unreal Engine 3 running on the iPhone back in december last year : http : //www.anandtech.com/gadgets/showdoc.aspx ? i = 3695 [ anandtech.com ] Granted , it 's a modified version and I do n't think there 's a working game available yet that uses it , but the engine is several generations newer than the Quake 3 one... Still , nice job .
It 's weird to see 'big ' games appearing on tiny devices .
Did n't think the mobile technology would be this advanced so soon , tbh .</tokentext>
<sentencetext>I'm not impressed.
Epic had Unreal Engine 3 running on the iPhone back in december last year: http://www.anandtech.com/gadgets/showdoc.aspx?i=3695 [anandtech.com]   Granted, it's a modified version and I don't think there's a working game available yet that uses it, but the engine is several generations newer than the Quake 3 one...  Still, nice job.
It's weird to see 'big' games appearing on tiny devices.
Didn't think the mobile technology would be this advanced so soon, tbh.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270500</id>
	<title>Re:Not impressed</title>
	<author>LingNoi</author>
	<datestamp>1267100940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So lets sum up here.</p><p>This kwaak3, something that runs on most android phones, works, is a game, something you can download right now...</p><p>That's less impressive then a youtube video of a game that, doesn't work on the iPhone 2G, 3G or ipod touches, doesn't have networking, etc<nobr> <wbr></nobr>...</p><p>Why do I get the feeling you're shitting on this simply because it's not related to the iPhone?</p></htmltext>
<tokenext>So lets sum up here.This kwaak3 , something that runs on most android phones , works , is a game , something you can download right now...That 's less impressive then a youtube video of a game that , does n't work on the iPhone 2G , 3G or ipod touches , does n't have networking , etc ...Why do I get the feeling you 're shitting on this simply because it 's not related to the iPhone ?</tokentext>
<sentencetext>So lets sum up here.This kwaak3, something that runs on most android phones, works, is a game, something you can download right now...That's less impressive then a youtube video of a game that, doesn't work on the iPhone 2G, 3G or ipod touches, doesn't have networking, etc ...Why do I get the feeling you're shitting on this simply because it's not related to the iPhone?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269686</id>
	<title>licka my</title>
	<author>Anonymous</author>
	<datestamp>1267089960000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>sucka my stroka my COCK!</p></htmltext>
<tokenext>sucka my stroka my COCK !</tokentext>
<sentencetext>sucka my stroka my COCK!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31273016</id>
	<title>Re:Where's my flying car?!</title>
	<author>Blakey Rat</author>
	<datestamp>1267118280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd say, "who gives a fuck? Quake 3 sucked. When will Unreal Tournament be available?"</p></htmltext>
<tokenext>I 'd say , " who gives a fuck ?
Quake 3 sucked .
When will Unreal Tournament be available ?
"</tokentext>
<sentencetext>I'd say, "who gives a fuck?
Quake 3 sucked.
When will Unreal Tournament be available?
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270944</id>
	<title>Bad ass</title>
	<author>SphericalCrusher</author>
	<datestamp>1267105980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I just purchased a droid and I am looking into all of the things I can do -- the free apps, playing with the SDK, running a web &amp; ftp server on the phone, etc. This project is by far one of the best projects I've seen and I can't wait until you have it available so I can put it on my phone. I'm a huge idSoftware and Quake 3 fan. Great work!</htmltext>
<tokenext>I just purchased a droid and I am looking into all of the things I can do -- the free apps , playing with the SDK , running a web &amp; ftp server on the phone , etc .
This project is by far one of the best projects I 've seen and I ca n't wait until you have it available so I can put it on my phone .
I 'm a huge idSoftware and Quake 3 fan .
Great work !</tokentext>
<sentencetext>I just purchased a droid and I am looking into all of the things I can do -- the free apps, playing with the SDK, running a web &amp; ftp server on the phone, etc.
This project is by far one of the best projects I've seen and I can't wait until you have it available so I can put it on my phone.
I'm a huge idSoftware and Quake 3 fan.
Great work!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270256</id>
	<title>Re:I thought the NDK couldn't use opengl</title>
	<author>Thunderbird2k</author>
	<datestamp>1267097400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>As of NDK 1.6, OpenGL is supported.</htmltext>
<tokenext>As of NDK 1.6 , OpenGL is supported .</tokentext>
<sentencetext>As of NDK 1.6, OpenGL is supported.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270008</id>
	<title>How about integers instead of floating point?</title>
	<author>Anonymous</author>
	<datestamp>1267094700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How about integers instead of floating point? Without knowing anything about the code, how would integers perform here? Couldn't a static table with, eg 3600 precalculated angles simulate what you want?


.</htmltext>
<tokenext>How about integers instead of floating point ?
Without knowing anything about the code , how would integers perform here ?
Could n't a static table with , eg 3600 precalculated angles simulate what you want ?
.</tokentext>
<sentencetext>How about integers instead of floating point?
Without knowing anything about the code, how would integers perform here?
Couldn't a static table with, eg 3600 precalculated angles simulate what you want?
.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269696</id>
	<title>I wonder how fast...</title>
	<author>Anonymous</author>
	<datestamp>1267090080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>&gt; Quake 3 optimized for Cortex-A8 with Neon is about 15\% faster without audio</p><p>I wonder how much faster it will be without video</p></htmltext>
<tokenext>&gt; Quake 3 optimized for Cortex-A8 with Neon is about 15 \ % faster without audioI wonder how much faster it will be without video</tokentext>
<sentencetext>&gt; Quake 3 optimized for Cortex-A8 with Neon is about 15\% faster without audioI wonder how much faster it will be without video</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272636</id>
	<title>Re:Not impressed</title>
	<author>Anonymous</author>
	<datestamp>1267116420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>if you can do something like this, you won't be jobless for long. These are the kinds of things people would love to have on their resume.</p></htmltext>
<tokenext>if you can do something like this , you wo n't be jobless for long .
These are the kinds of things people would love to have on their resume .</tokentext>
<sentencetext>if you can do something like this, you won't be jobless for long.
These are the kinds of things people would love to have on their resume.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269758</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272126</id>
	<title>Re:Where's my flying car?!</title>
	<author>mdwh2</author>
	<datestamp>1267113660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I remember seeing smartphones from around 2002 or before. And handheld PDAs existed before that - it was pretty obvious that we'd get Quake 3 after a matter of time, and that it wouldn't be long.</p><p>The reasons against flying cars are to do with laws, liability, and required training, not technology.</p></htmltext>
<tokenext>I remember seeing smartphones from around 2002 or before .
And handheld PDAs existed before that - it was pretty obvious that we 'd get Quake 3 after a matter of time , and that it would n't be long.The reasons against flying cars are to do with laws , liability , and required training , not technology .</tokentext>
<sentencetext>I remember seeing smartphones from around 2002 or before.
And handheld PDAs existed before that - it was pretty obvious that we'd get Quake 3 after a matter of time, and that it wouldn't be long.The reasons against flying cars are to do with laws, liability, and required training, not technology.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270700</id>
	<title>Re:Not impressed</title>
	<author>fuzzix</author>
	<datestamp>1267103460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm not impressed. Epic had Unreal Engine 3 running on the iPhone back in december last year...</p></div><p>But they have yet to ship a Linux binary. BAH!</p></div>
	</htmltext>
<tokenext>I 'm not impressed .
Epic had Unreal Engine 3 running on the iPhone back in december last year...But they have yet to ship a Linux binary .
BAH !</tokentext>
<sentencetext>I'm not impressed.
Epic had Unreal Engine 3 running on the iPhone back in december last year...But they have yet to ship a Linux binary.
BAH!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270318</id>
	<title>Re:Mouse</title>
	<author>Anonymous</author>
	<datestamp>1267098240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't own a touch-based smartphone, but aiming with a touch screen on FPS games for the DS works quite well.  Local multiplayer in Metroid Prime Hunters is a blast.  Of course, with the android you're limiting by only having one screen, but perhaps a section of the screen could be designated as a "mousepad".</p></htmltext>
<tokenext>I do n't own a touch-based smartphone , but aiming with a touch screen on FPS games for the DS works quite well .
Local multiplayer in Metroid Prime Hunters is a blast .
Of course , with the android you 're limiting by only having one screen , but perhaps a section of the screen could be designated as a " mousepad " .</tokentext>
<sentencetext>I don't own a touch-based smartphone, but aiming with a touch screen on FPS games for the DS works quite well.
Local multiplayer in Metroid Prime Hunters is a blast.
Of course, with the android you're limiting by only having one screen, but perhaps a section of the screen could be designated as a "mousepad".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269758</id>
	<title>Re:Not impressed</title>
	<author>Anonymous</author>
	<datestamp>1267090860000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Yeah and that is Epic Software doing that.  They aren't exactly a hobbyist working without pay...</htmltext>
<tokenext>Yeah and that is Epic Software doing that .
They are n't exactly a hobbyist working without pay.. .</tokentext>
<sentencetext>Yeah and that is Epic Software doing that.
They aren't exactly a hobbyist working without pay...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270006</id>
	<title>Re:Running Demos</title>
	<author>Anonymous</author>
	<datestamp>1267094700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>1.32c is NOT based off of IOQ3. It was a security fix released a couple years ago by Id.</p></htmltext>
<tokenext>1.32c is NOT based off of IOQ3 .
It was a security fix released a couple years ago by Id .</tokentext>
<sentencetext>1.32c is NOT based off of IOQ3.
It was a security fix released a couple years ago by Id.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582</id>
	<title>Where's my flying car?!</title>
	<author>Anonymous</author>
	<datestamp>1267088460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I thought by the time we would have Quake 3 on a phone I'd be flying to work in my hover car.

Imagine taking a trip back in time a few years and telling your younger self that Quake 3 would be [almost] playable on a cell phone - hopefully you wouldn't reply with a "whats a cell phone?"</htmltext>
<tokenext>I thought by the time we would have Quake 3 on a phone I 'd be flying to work in my hover car .
Imagine taking a trip back in time a few years and telling your younger self that Quake 3 would be [ almost ] playable on a cell phone - hopefully you would n't reply with a " whats a cell phone ?
"</tokentext>
<sentencetext>I thought by the time we would have Quake 3 on a phone I'd be flying to work in my hover car.
Imagine taking a trip back in time a few years and telling your younger self that Quake 3 would be [almost] playable on a cell phone - hopefully you wouldn't reply with a "whats a cell phone?
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269596</id>
	<title>Wow great job</title>
	<author>Anonymous</author>
	<datestamp>1267088580000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Now how about porting to a phone people actually buy (read: iPhone)?</p></htmltext>
<tokenext>Now how about porting to a phone people actually buy ( read : iPhone ) ?</tokentext>
<sentencetext>Now how about porting to a phone people actually buy (read: iPhone)?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271448</id>
	<title>Re:Not impressed</title>
	<author>Anonymous</author>
	<datestamp>1267109700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>From what I've read the unreal 3 port used the pixel shaders, since it would only run on the opengl ES 2 devices, and not on the original and 3g iphones.</p></htmltext>
<tokenext>From what I 've read the unreal 3 port used the pixel shaders , since it would only run on the opengl ES 2 devices , and not on the original and 3g iphones .</tokentext>
<sentencetext>From what I've read the unreal 3 port used the pixel shaders, since it would only run on the opengl ES 2 devices, and not on the original and 3g iphones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269900</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572</id>
	<title>DUDE You're incredible</title>
	<author>linhares</author>
	<datestamp>1267131420000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Team fortress by any chance?  Steal the code, kill people, I can help with whatever task is needed.</htmltext>
<tokenext>Team fortress by any chance ?
Steal the code , kill people , I can help with whatever task is needed .</tokentext>
<sentencetext>Team fortress by any chance?
Steal the code, kill people, I can help with whatever task is needed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270352</id>
	<title>Re:Running Demos</title>
	<author>borl</author>
	<datestamp>1267098840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Speconly?!  Far too useful.</p><p>They're too busy adding bloom effects</p></htmltext>
<tokenext>Speconly ? !
Far too useful.They 're too busy adding bloom effects</tokentext>
<sentencetext>Speconly?!
Far too useful.They're too busy adding bloom effects</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269974</id>
	<title>Re:What about the N900?</title>
	<author>kamapuaa</author>
	<datestamp>1267094040000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>If you read the article (I know, I know...) this is actually based on the N900 port.</htmltext>
<tokenext>If you read the article ( I know , I know... ) this is actually based on the N900 port .</tokentext>
<sentencetext>If you read the article (I know, I know...) this is actually based on the N900 port.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269900</id>
	<title>Re:Not impressed</title>
	<author>Anonymous</author>
	<datestamp>1267092660000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>If that is "Unreal 3", then it's a very, very stripped down version. It doesn't even look like it has pixel shaders, which removes all benefit to using it over the Quake III engine.</p><p>By the way, the Quake III engine is capable of handling visuals that look better than the screenshots you linked to. Here are a few examples of what the Quake III engine can do.</p><p><a href="http://www.szico-vii.com/uploads/photos/16.jpg" title="szico-vii.com" rel="nofollow">http://www.szico-vii.com/uploads/photos/16.jpg</a> [szico-vii.com]<br><a href="http://www.szico-vii.com/uploads/photos/17.jpg" title="szico-vii.com" rel="nofollow">http://www.szico-vii.com/uploads/photos/17.jpg</a> [szico-vii.com]<br><a href="http://www.szico-vii.com/uploads/photos/31.jpg" title="szico-vii.com" rel="nofollow">http://www.szico-vii.com/uploads/photos/31.jpg</a> [szico-vii.com]<br><a href="http://www.szico-vii.com/uploads/photos/42.jpg" title="szico-vii.com" rel="nofollow">http://www.szico-vii.com/uploads/photos/42.jpg</a> [szico-vii.com]</p></htmltext>
<tokenext>If that is " Unreal 3 " , then it 's a very , very stripped down version .
It does n't even look like it has pixel shaders , which removes all benefit to using it over the Quake III engine.By the way , the Quake III engine is capable of handling visuals that look better than the screenshots you linked to .
Here are a few examples of what the Quake III engine can do.http : //www.szico-vii.com/uploads/photos/16.jpg [ szico-vii.com ] http : //www.szico-vii.com/uploads/photos/17.jpg [ szico-vii.com ] http : //www.szico-vii.com/uploads/photos/31.jpg [ szico-vii.com ] http : //www.szico-vii.com/uploads/photos/42.jpg [ szico-vii.com ]</tokentext>
<sentencetext>If that is "Unreal 3", then it's a very, very stripped down version.
It doesn't even look like it has pixel shaders, which removes all benefit to using it over the Quake III engine.By the way, the Quake III engine is capable of handling visuals that look better than the screenshots you linked to.
Here are a few examples of what the Quake III engine can do.http://www.szico-vii.com/uploads/photos/16.jpg [szico-vii.com]http://www.szico-vii.com/uploads/photos/17.jpg [szico-vii.com]http://www.szico-vii.com/uploads/photos/31.jpg [szico-vii.com]http://www.szico-vii.com/uploads/photos/42.jpg [szico-vii.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270700
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270750
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270256
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269974
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31274198
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270500
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271818
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270006
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272920
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270008
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270132
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272636
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269758
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269778
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269794
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270186
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269810
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270266
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270324
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269780
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270954
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270318
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270352
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31273016
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270674
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272126
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271448
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269900
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_25_0548259_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270350
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269716
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269810
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269794
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269780
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270324
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270318
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269582
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31273016
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272126
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269596
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270648
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31274198
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269696
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269642
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270750
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270186
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269654
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269808
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270008
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272920
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269600
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270258
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270266
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269572
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270954
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270674
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269648
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269900
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271448
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270700
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269758
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272636
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270500
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269778
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269784
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270862
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31271818
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269974
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269950
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270242
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270350
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270132
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269628
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270006
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270352
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31269590
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_25_0548259.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270078
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31272930
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_25_0548259.31270256
</commentlist>
</conversation>
