view3dscene 3.11.0, engine 3.0.0 releases
We're proud to release new view3dscene 3.11.0, our VRML/X3D browser and viewer for other 3D models, and Castle Game Engine 3.0.0, our 3D game engine (used under the hood by view3dscene and other programs here).
New features in view3dscene 3.11.0 for users:
Huge improvements to Collada support. Rendering and converting Collada to X3D supports now: textures, normals, cameras, light sources, all primitives (triangle strips, fans, lines and more), multiple polygon lists, objects sharing, double-sided information, 1.5 specification support. See earlier news about Collada for a complete description of new Collada features handled.
Geometry shaders are supported (see here for docs and examples). Tested on NVidia and ATI GPUs (see ticket #2 for some history about fglrx fixes).
"Limit FPS" option implemented, to not exhaust CPU. This way all our programs and games allow the OS and CPU to rest, to allow other applications to run normally and do not exhaust battery life on laptops.
This is configurable by view3dscene menu item "File -> Preferences -> Frames Per Second Limit ...". Default is 100. For developers, this is configurable by
Many improvements to our compositing shaders extensions. This is a way to implement reusable effects using the GLSL (OpenGL shading language). Effects implemented this way seamlessly cooperate with each other and with standard renderer shaders (so you have standard lighting, texturing and such for free).
My Ph.D. thesis, describing the whole idea, is also published on the page linked above :)
--viewpointcommand-line option to choose a different viewpoint as the default (initial) one. Especially useful in combination with
For engine 3.0.0, I have to admit that we didn't implement all planned features. Most importantly: easy AI, and engine tutorials, are postponed to next engine 3.1.0 release. However, we still have many new features in Castle Game Engine 3.0.0 for developers:
The first release of the engine under "Castle Game Engine" name, previous versions were called "Kambi VRML game engine". See earlier news about name change for detailed reasoning.
Note: This engine release breaks compatibility with earlier versions. Although there is no major change of the engine design (our scene manager design in engine 2.x was really good, and we want to push using it even further in engine 3.x). But there are a lot of renames around important units and classes. And some small things were redesigned more heavily.
Everything is detailed below, to help you with the migration to the new engine version. If you have any questions about the reasoning of the changes, or if you want to ask how to migrate some particular construct to new engine version, don't hesitate to ask on our forum.
Examples completely reorganized. Many useless examples removed, many good examples rewritten and renamed to be better visible.
Isometric game (sandbox) and fixed camera game (rift) examples were added to engine sources.
A lot of engine identifiers are renamed and changed, to emphasize:
TCastleControl. They include ready
See previous news for detailed reasoning and explanation, and see renaming details document for even more details. If you want to port existing games to engine 3.0.0, you will want to perform the same renames in your code.
Other programs are released too, to give them small improvements and update their sources to be compatible with latest engine 3 API. In particular, glViewImage 1.4.0 is improved with new image formats support.