As many of you know, we’ve been beavering away on the vbo-unstable branch completely overhauling the geometry core of the engine to make it faster and more flexible. It’s now mature enough for general consumption, and I’ve just merged the branch into the main CVS trunk.
Sourceforge’s anonymous CVS is still up to 2 days behind our development CVS, and is both slow and unreliable (they promise this will be resolved soon). In the meantime, I’ve uploaded new Unstable CVS Snapshots for you to play with – please try them out, we’d like as many testers in the run up to the official release (on or soon after the weekend) as possible. There are a couple of known issues (see the full details of this story), please review them before reporting any bugs.
The new classes are well documented, but I intend to write a section in the release notes on the geometry changes between 0.11 and 0.12; they will only affect those of you who are manipulating geometry directly, which will only be those writing geometry tools or custom scene managers. People who use the higher level classes won’t notice except for the better frame rates.
Known Issues:
- Demo_BSP will not work under D3D7; this is because the new VBO implementation of BspSceneManager requires 32-bit indexes which D3D7 does not support. D3D9 or GL must be used.
- Gui demo crashes on shutdown – will be fixed before release.
- Cube mapping is not working under D3D7, should be fixed before release.
- In VC7.0 some optimisation setting causes cube mapping not to work under GL in release mode. VC6 and gcc are unaffected and debug mode is fine. May or may not be fixed before release (difficult to track).