The more I think about this, the more I think there is something fishy...I just don't see how you could get that kind of performance rendering to the screen without having a lower level interface to the renderer in Silverlight 2.

It is not a hoax and there is nothing fishy about it. Unfortunately, there is no low-level access to the rendering system in Silverlight.
This is pure, safe C# code (unsafe code would help to optimize) and default Silverlight API.

Of course, if in the future, Microsoft extends the range of WPF supported functions in Silverlight, my techniques would become obsolete but the rendering will be even faster!

Rendering performance put aside (which is now as fast as possible, given the current Silverlight limitations), recent additions to the code (3D meshes for monsters and dynamic lights) use a lot of CPU (I lost about 10 FPS in the process) so the keypoint is again optimize, optimize, optimize... My final goal being Quake running in 640x480 at 60 FPS (I am currently stuck at 40 FPS-ish).

Keep it up 3d Silverlight

Brute force it would appear.

We did this '3D' layout for DeepZoom which was not too bad.

www.domaindotnet.com/ClientBin/DeepZoom3d.html

Damon Wilder Carr

Silverlight stops rendering if the browser is minimized.
Is there a way to keep the rendering going even when the browser is minimized?

Ethen

thanks! very helpful post!! like the template btw ;)