Demo with dual render: OpenGL/Direct3D9 (benchmark inside)

[DenDiesel]

0.40 seems to be considerably slower than 0.33 IIRC. It could be the new features -- I really can't remember.

New features, heavier art content. Unigine v0.4 is faster than v0.33 on the same content.

Also, it appears the rendering engine runs in a single thread. Will the physics, scripting engine, sounds, or AI be run on another thread?

Sure it will. Physics already runs as a dedicated thread by default. The demo shows only rendering capabilities, so it provides load for single CPU only.

Will the engine compile as 64-bit version?

64bit builds of Unigine v0.4 are available for a long time.

Any plans on releasing one for GNU/Linux?

You mean 64bit builds for Linux? If so, then yes, we plan to provide 64bit builds for Linux, however there is very little demand on this. Anyway technically Unigine can be easily compiled as 32 or 64 bit application, there is no problem.

[mynakedrat]

to madpistol, y cant you turn up the resolution??

[mynakedrat]

to everyone...TRY THIS WITH THE 3D GLASSES!!!!!!
OMF!
ITs like a huge hole in my wall that i can put my hand in.
its like, real 3-d.lololoehheheleol

(but it is really neato)

[Obie]

oops nevermind

[abtomat74]

0.40 seems to be considerably slower than 0.33 IIRC. It could be the new features -- I really can't remember. Also, it appears the rendering engine runs in a single thread. Will the physics, scripting engine, sounds, or AI be run on another thread? Will the engine compile as 64-bit version? Any plans on releasing one for GNU/Linux?

http://iki.fi/wnd/tmp/unigine_0.40_a.png

I notice your "CPU flags" shows 1000MHz, which is much slower than it should be displaying for your CPU. My X2 4800 shows 2412MHz by comparison. Are you running Cool & Quiet by chance?

[wnd]

I notice your "CPU flags" shows 1000MHz, which is much slower than it should be displaying for your CPU. My X2 4800 shows 2412MHz by comparison. Are you running Cool & Quiet by chance?

I'm running cpufreq/powernowd (with userspace policy governor), which can be thought as a GNU/Linux-equivalent for "Cool & Quiet". I wouldn't pay too much attention to reported CPU clock as it could be read at startup instead of at the end of benchmark. When the demo is just started, the governor has not yet had a reason to increase processor frequency. Normally, the governor would notice increased CPU demand withing one second. It is also possible that the demo is significantly more GPU- than CPU-bound, and the CPU clock frequency never needs to be brought up.

Thanks anyway.