Thanks for trying it guys!

Quote Originally Posted by renderhjs
What would interest me how the engine handles larger maps,- not necessary more complex maps but lets say this same room placed like over 20 - 50 times next to each other and one could walk along a corner (so you dont see the rest ahead at once) to the next room and so on.
Like how is the initializing time,- does it need to build up alot of things? Does performance still runs fine just like now?
I plan to do a larger map soon, which will be a testbed for more scripts and gameplay elements (buttons, doors, keys, traps, etc). I expect that the game will scale very well with map size - testing on the descent maps it what convinced me. If none of a sectors geometry is visible then it has zero rendering impact - there's no overdraw waste, and its vertices are not even transformed! I/O and initialization time will always be linear in the size of the map, and the lazy evaluation of shadowed surfaces tends to spread out the highish cost of the lighting routines - shadows aren't computed until the surface is visible for the first time.

The editor is a different story. It doesn't have any of the occlusion tricks so it draws the whole map on every frame. It will become a real bottleneck as mapsize grows. There might be a need to cull the map to just a short distance in front of the camera in order to make the editor more responsive. Exporting a map is also quadratic in the number of polygons it contains, this is a known issue which will be resolved in the future.

Quote Originally Posted by makc
it's v10 isnt it... cant enjoy this
If you don't have the 10 player installed in your browser (I don't either), then you can fetch the standalone debug player from:
http://opensource.adobe.com/svn/open.../in/player/10/
That's the same environment I debug and test with, so you'll see what I see.