This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
etm [2007/05/15 21:06] cabalistic |
etm [2015/08/23 13:06] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Editable Terrain Manager ====== | ====== Editable Terrain Manager ====== | ||
+ | ==== About ==== | ||
The Editable Terrain Manager is an addon library for OGRE which manages and displays terrain based on heightmap data. It can be used as a replacement for the Terrain Scene Manager, but its main advantage is the edit possibility for the terrain: You can deform and set the terrain heights in real time, as you would need to if you are developing an editor application. | The Editable Terrain Manager is an addon library for OGRE which manages and displays terrain based on heightmap data. It can be used as a replacement for the Terrain Scene Manager, but its main advantage is the edit possibility for the terrain: You can deform and set the terrain heights in real time, as you would need to if you are developing an editor application. | ||
In addition, the library also has means to support editable splatting, probably the current standard for detailed terrain texturing. | In addition, the library also has means to support editable splatting, probably the current standard for detailed terrain texturing. | ||
All of the parts have been designed to be as flexible as possible and do not even depend upon each other. That means you don't need to use splatting if you don't want to - or you can use that part with a different terrain renderer. Unlike OGRE's TSM, it's not a scene manager, either, so you could (in theory) choose whatever scene manager you like. All its headers are light-weight, | All of the parts have been designed to be as flexible as possible and do not even depend upon each other. That means you don't need to use splatting if you don't want to - or you can use that part with a different terrain renderer. Unlike OGRE's TSM, it's not a scene manager, either, so you could (in theory) choose whatever scene manager you like. All its headers are light-weight, | ||
+ | |||
+ | |||
+ | |||
+ | |||
==== Get it ==== | ==== Get it ==== | ||
There are currently no precompiled binaries available. You will have to compile it from code yourself. The library was tested against OGRE v1.4.x. | There are currently no precompiled binaries available. You will have to compile it from code yourself. The library was tested against OGRE v1.4.x. | ||
- | Buildfiles are included for Visual Studio 2005 and CodeBlocks (for MinGW). | + | Buildfiles are included for Visual Studio 2005 and CodeBlocks (for MinGW and GCC/Linux). A very basic Makefile |
+ | |||
+ | Get the source code here: [[http:// | ||
- | Get the source code here: [[http:// | ||
==== License ==== | ==== License ==== | ||
- | ETM is released under the terms of the [[http:// | + | ETM is released under the terms of the [[http:// |
+ | |||
Line 22: | Line 30: | ||
I've also written on overview over the components of the library, which you can find here: [[etm: | I've also written on overview over the components of the library, which you can find here: [[etm: | ||
+ | ==== Support ==== | ||
+ | Got any questions about ETM? Do you experience problems with the library? Do you have feature requests? Or do you just want to say thanks? :) The right place to express either is in the Ogre addon forum for ETM, which you can find here: [[http:// | ||
+ | |||
+ | ==== Screenshots ==== | ||
{{etsm_demo.jpg|}} | {{etsm_demo.jpg|}} | ||
+ | |||
+ | {{etminimap.jpg|}} | ||
+ | |||
+ | {{etmv23.jpg|}} |