"You are cheating the fps counter...aren't you". Well, you've got me... Come on! I'm not cheating; the source code and the wmp file are included in the archive. The camera movement code is really simple, so all the heavy frame rate variations impact it. If any of you has a big level made out of mdls I'll be happy to make a new demo when I get some free time. Just make sure that the level has over 500,000 polys, so that we can give A7 a run for its money

I ran a quick test with 1,500 auge.mdl entities (the model is in the demo folder) using the same level. The frame rate is kept steady at 75fps on my pc (the limit given by my monitor's refresh rate).

A7: 25fps: Pentium D 820 (2*2.8Ghz), 1gb ram, Geforce 6600 GT
A6.50.6: 24fps

Not that much difference. The speed increase would be bigger if you use the mouse to select modells (mouse_mode==2), this is MUCH! faster with the current A6.57.b Beta then with the A6.5 release. Hope there is a A6.6 soon.

20 fps while viewing 1 million polygons:

xp pro sp2
core 2 cpu 6300 @ 1.86ghz
1gb ddr2 ram
geforce 7600 gs

also the same problem as every aX version bevore, jerky frame rate dependent mouse movement...

What concerned me was the jerky mouse movements when the balls are in view. :?

56 FPS ...

- Intel Core2Duo 2.13 GHz (E6400)
- 1024 MB DDR2-800
- ATI Radeon X1900 GT ( 256 MB DDR3 )

"What concerned me was the jerky mouse movements when the balls are in view". That will happen with the current camera movement code if the frame rate is small. A more improved movement code should fix the problem (but will not fix the jerkiness if the frame rate is below 20 fps or so). The sole purpose of the demo is to benchmark an early version of A7; however, I might rewrite the movement code and post an update here.

fps: 54 still 48when moving arround

p4 3ghz/512ram and ati radeon1600pro

quite early to judge anything but very impressive so far!

cheers and thanks for the info

20 FPS: Pentium 4 (3.1GHz), 512MB Ram, GEForce 6600 GT 125mb

We experienced recently, that there is not much speed _de_crease if you take one model and create multiple instances of it (see -here-). JCL said:

Quote:

---

If you send 1000 models into the rendering pipeline, CPU and GPU can run in parallel, the CPU preparing the next rendering steps while the GPU is processing the pipeline.

However one extremely large object will need the CPU to wait for the GPU, thus wasting processing power. This is the unbalanced pipeline case that should also be avoided by level design.

The latter case is only slightly slower, but due to the 60 Hz lock you'll see a huge difference in fps.

---

So this whole test environment shows that A7 may be faster, but in a very rare circumstance. Please embed the texture of your ball into the modelfile and make 20 fileclones. Now place all clones randomly into the level (20 entities) and duplicate them 1000 times so that you have finally 2000 entities basing on 20 source entities with individual textures. Compile it with the latest A6 beta and with your A7 version and then lets have a go...

cheers
Christian