Comments on: This Is a Small Step For a Zombie, But a Big Step For a Developer

By: Sargon

Sargon — Mon, 27 Oct 2008 15:17:26 +0000

I think textures do take time to load, but not because what you might have thought.
I found(and I might be wrong about this), that decompressing the texture files into a raw bit map, might take alot longer than reading a raw texture bitmap from the hard disk.
Reading from a hard disk that is not SCSI could take as fast as 70MB/Sec.
A SCSI HD would read at about 1.5GB/Sec.
While using the CPU to decompress textures might be suprisngly slow, in some cases.

By: Juuso Hietalahti

Juuso Hietalahti — Fri, 24 Oct 2008 03:37:46 +0000

psycho: good tips.

Leadwerks. ODE has worked greatly for me (and it’s something I’ve used in the past – so I’m familiar with it) so I see no reason to change it to newton, but thanks for tip. I’m sure others appreciate your tips as well.

Jake: yeh.

By: Jake Birkett

Jake Birkett — Thu, 23 Oct 2008 23:37:51 +0000

Good advice and sounds like you’ve been enjoying yourself.

By: Leadwerks

Leadwerks — Thu, 23 Oct 2008 20:36:04 +0000

You might want to try this comparison of ODE and Newton Game Dynamics before you get too heavily embedded in ODE:
http://www.leadwerks.com/files/IntelDemo_DTC_runtime.zip

I have tried ODE, PhysX, and Tokamak, and I found Newton to be much more stable than anything else.

By: psycho

psycho — Thu, 23 Oct 2008 18:53:41 +0000

loading – i’m not sure whats the bottleneck of loading, but it could be textures, so in that case, you can use some default texture for everything.. and compiling should not be a problem in well designed code, it should always compile only the changed files (so if you dont change some core engine stuff, it should be quick).. also try /MP for compilator to use multiple cores, halves the time on dual cores..)
but yeah, prototype outside :)