http://www.allforthecode.co.uk/away3d/Away3D_4/CityTest/
To move around, use the keys:
w = forward
s = backward
a = left
d = right
space = up
x = down
Running stats:
Only applications that change to open here are firefox and chrome.
Chrome
EvgaPrecision (free tool google it for download pc) for GTX 570 reads changes of:
GPU usage running demo in chrome: 5% (spinning scene round)
GFX Card Ram usage running demo in chrome: 312mb
GPU usage running blank tab in chrome: 0%
GFX Card Ram usage running blank tab in chrome: 199mb
FireFox
GPU usage running demo in firefox 3.6.22: 5% (spinning scene round)
GFX Card Ram usage running demo in firefox 3.6.22: 330mb
GPU usage running blank tab in firefox 3.6.22: 0%
GFX Card Ram usage running blank tab in firefox 3.6.22: 201mb
Windows task manager stats:
Chrome
CPU usage running demo in chrome: Jumping between 3% and 6%
CPU Ram usage running demo in chrome: 2.72GB
CPU usage blank page in chrome: Bouncing between 0% and 1%
Ram usage blank page in chrome: 2.54GB
FireFox
CPU usage running demo in firefox: Jumping between 3% and 9%
Ram usage running demo in firefox: 2.71GB
CPU usage blank page in firefox: Bouncing between 0% and 1%
Ram usage blank page in firefox: 2.52GB
Framerates for Chrome and FireFox 3.6.22
Framerate 58 to 62 when not moving
Framerate 50 to 62 when moving
Hardware
GTX 570
Win 7
CPU i7 @ 2.8GHz
10GB DDR3
Bugs
1. Alpha cannot be applied as this messes up z depth sorting (known bug I think)
2. 3DS mesh is flipped and had to be scaled in the negative to show up the same as what it looked like in Blender
3. Reflection is not quite right from the cubemap.
Post your stats and hardware, the more data we get, the better idea we will have to know what we can get away with building in the FP11.
D