Difference between revisions of "Utility:Overseer"

Revision as of 08:02, 3 March 2011

Overseer Screenshot

Fortress Overseer

Fortress Overseer is a full 3D DF2010 visualizer by thewonderidiot and sexymustard. More information can be found in the bay12forums topic, and Overseer itself can be downloaded from its page on DFFD or the github mirror. The currently outdated) linux version can be downloaded here.

Overseer uses Ogre3D in conjunction with the DFHack library.

Adding Custom Content

Models

Models are stored in the /models/ directory. Models use Ogre's .mesh format. Exporters can be downloaded from the Ogre wiki for various 3D modelling programs.

Materials

Ogre has a very robust material system. More information can be found in the Ogre manual. The included generateMaterials.py script will populate the material scripts using info from the diffuse and normal texture directories, generating colors for other techniques from the colors directory (thanks to Japa for use of his stonesense colors).

Images

Images for a material must have the same name the material has in the raws. Diffuse textures are found in /materials/images/diffuse. Their dimensions should be a power of two. If they have an accompanying normal map, it needs to be named with the same name as the diffuse texture but with an n on the end (eg, if native_gold.bmp is the diffuse texture, native_goldn.bmp is its normal map). The normal maps go in /materials/images/normal. Of course, this layout can be changed as long as the resources.cfg file in the root Overseer directory is updated accordingly.

@@ Line 1: / Line 1: @@
 [[File:overseer.png|thumb|right|Overseer Screenshot]]
 ==Fortress Overseer==
-Fortress Overseer is a full 3D DF2010 visualizer by thewonderidiot and sexymustard. The generated model can be exported to several popular 3D formats(eg .obj). More information can be found in the [http://www.bay12forums.com/smf/index.php?topic=63484.0 bay12forums topic], and Overseer itself can be downloaded from [http://dffd.wimbli.com/file.php?id=2922 its page on DFFD]. [http://dffd.wimbli.com/file.php?id=3291 The linux version.]
+Fortress Overseer is a full 3D DF2010 visualizer by thewonderidiot and sexymustard. More information can be found in the [http://www.bay12forums.com/smf/index.php?topic=63484.msg2037888#msg2037888 bay12forums topic], and Overseer itself can be downloaded from [http://dffd.wimbli.com/file.php?id=3882 its page on DFFD] or [https://github.com/downloads/mikestewart/Overseer/Overseer0.50.exe the github mirror]. The currently outdated) linux version can be downloaded [http://dffd.wimbli.com/file.php?id=3291 here.]
-Overseer uses OpenSceneGraph in conjunction with the DFHack library.
+Overseer uses Ogre3D in conjunction with the DFHack library.
 ==Adding Custom Content==
 ===Models===
-Models are stored in the /models/ directory. For now, they must be in the OSG IVE format. Many model types can be converted to IVE via the osgconv tool included with the binary OSG distributions, available [http://www.openscenegraph.org/projects/osg/wiki/Downloads here]. IVE bundles textures with the model, so textures used on the model need not be included when distributing the IVE.
+Models are stored in the /models/ directory. Models use Ogre's .mesh format. Exporters can be downloaded from the Ogre wiki for various 3D modelling programs.
-Currently only the included IVE's can be swapped out for new things. In the near future, Overseer will load in models sharing the name as the item/construction name.
+===Materials===
+Ogre has a very robust material system. More information can be found in [http://www.ogre3d.org/docs/manual/manual_14.html the Ogre manual]. The included generateMaterials.py script will populate the material scripts using info from the diffuse and normal texture directories, generating colors for other techniques from the colors directory (thanks to Japa for use of his stonesense colors).
-For most things that can be different kinds of materials in the game, textures should not be included in the IVE. Rather, if the IVE contains texture coordinates, Overseer will simply assign the proper material type to it, using the same textures, normals, and shaders as the world geometry.
-===Textures===
-All textures are detected live. Overseer looks for a texture file with the same name as the material's name in the raws, and uses it if it exists. If not, it defaults to a rough-stone-looking texture blended with Japa's colors for Stonesense (stored in /colors/).
 ====Images====
-Images for a material must have the same name the material has in the raws. Diffuse textures are found in /materials/images. Their dimensions should be a power of two. If they have an accompanying normal map, it needs to be named with the same name as the diffuse texture but with an n on the end (eg, if native_gold.bmp is the diffuse texture, native_goldn.bmp is its normal map). The normal maps go in /materials/normals.
+Images for a material must have the same name the material has in the raws. Diffuse textures are found in /materials/images/diffuse. Their dimensions should be a power of two. If they have an accompanying normal map, it needs to be named with the same name as the diffuse texture but with an n on the end (eg, if native_gold.bmp is the diffuse texture, native_goldn.bmp is its normal map). The normal maps go in /materials/images/normal. Of course, this layout can be changed as long as the resources.cfg file in the root Overseer directory is updated accordingly.
-====Shaders====
-Shaders for Overseer are written in GLSL. The included shader is defaulted to when a normal map for a texture is found -- it provides simple bumpmapping. If there is a program found that shares the same name as the material's raw name, however, it prefers to use that instead. This way, each material can have its own shader programs.
-Shaders are somewhat limited right now and can only take in the parameters used in the default shaders. This will be threshed out more in the future.
 [[Category:Utilities]]