Software rendering allows O3D to use the main processor to render 3D images if the machine running the app doesn't have supported graphics hardware. While the hardware O3D requires to run in hardware-accelerated mode is fairly modest by today's standards (a DirectX 9, Pixel Shader 2.0 capable graphics card), there are nonetheless PCs that don't meet these requirements, and we think it's important for web apps to run on all machines, regardless of hardware.
Because software rendering is significantly slower than hardware-accelerated rendering, we're also introducing a concept called "feature requirements" that will help minimize how often O3D will have to fall back to software rendering. Feature requirements allow developers to state upfront that their app will require certain hardware capabilities to render properly. If the machine running the app supports those features, O3D will run it fully hardware accelerated; if however, it is lacking any of the required capabilities, O3D will drop into a software rendered mode. Anecdotally, we found that this tiering allows 45 of our 48 samples to now run in hardware-accelerated mode with less capable graphics cards.

This is really great news and an admirable reponse to the feedback of the fast growing community. Plugin update was fast and painless, another bonus feature worth mentioning :O)
ReplyDeleteO3D ticks all the boxes. Any plans for an IDE? Can we expect a scripting interface in Sketchup?
Cheers!
Sad that the Linux development is lagging behind as it is for a lot of Google applications. Why continue to give Microsoft this free promotion?
ReplyDelete@ Joris Willems: Probably because Microsoft's operating environment runs on 90%+ of machines, and because IE is still the Net's most prominent browser. Food for thought. ;)
ReplyDelete//Videometry.net > I'm looking forward to the scripting interface in Sketchup, as well.
ReplyDelete