Horde3D Wiki - User contributions [en]

Community Roadmap

2008-09-13T12:24:40Z

Kal:

As a way to keep the Horde3D community on the same page in regards to the development of future features, this Community Roadmap will keep an up to date log of the undergoing activities.

{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
| Assigned to
| Completion
| Released in
|-
| D3D Backend
| Write a D3D9/D3D10 backend, in addition to the current OpenGL backend
|  
|  
|  
|- bgcolor="#ECECEC"
| [[Community_Roadmap_-_Compressed_Texture_Support|Compressed Texture Support]]
| Support for DDS, PowerVR, and other Texture formats.
| swiftcoder
|  
|  
|-
| OpenGL ES2.x Backend
| Write a OpenGL ES2.x backend, Horde3D port for mobile platforms
| DDd
| 10%
| (EST.) December 2008
|- bgcolor="#ECECEC"
| Ambient Occlusion
| Add ambient occlusion support for Horde3D
|  
|  
|  
|-
| Alpha & Depth Test
| Provide support for the different tests in the shader context configuration, [http://www.horde3d.org/forums/viewtopic.php?f=8&t=500 public draft available]
| AcidFaucet
| 40%
| (EST.) September 15th, 2008
|}

<h3>Wishlist:</h3>
{| cellpadding="2" cellspacing="0" style="width: 100%"
|- bgcolor="#6699FF" style="font-size: medium; font-weight: bold"
| Feature
| Description
|-
| Texture Improvements
| Support for simple downloading of texture data, mipmaps for RTT render targets (for e.g. impostors)
|}
----

{| style="width: 100%"
|-
| <h3><span class="mw-headline">Upcoming Horde3D Version: 1.0</span></h3>
| <h3><span class="mw-headline">Upcoming Horde3D Editor version: 1.0</span></h3>
|-
| <b>The current version is: v1.0.0 Beta1</b>
| <b>The current version is: v0.7.0</b>
|-
|For version 1.0.0 Beta1 of Horde3D the following features have been
integrated:</p>
<ul>
<li><b>Occlusion Culling</b></li>
<li><b>Render-to-Texture</b></li>
<li><b>Stereo Rendering</b></li>
<li><b>Software Skinning</b></li>
<li><b>Node Sorting</b></li>
</ul>
The first will give polygonally dense worlds a boost in speed and the second can be used to do all sorts of effects. See also the
[http://www.horde3d.org/docs/_changeLog.html changelog] for more details.
In the following weeks no new features will be implemented. Instead the development will be focused on bug fixes and further documentation.
| The next version 0.7.0 will be based on Horde3D v.1.0.0 Beta1 and will focus on a better extensibility using plugins (e.g. the terrain node extension will be a plugin and not a fixed part of the editor anymore). Further on there will be support for front, top, and right view of the scene with orthographic projection.
|}

Talk:Community Roadmap

2008-09-13T12:20:12Z

Kal: New page: =is occlusion culling object level?=

=is occlusion culling object level?=

Template:ContentBlock

2008-09-12T13:22:07Z

Kal: Undo revision 360 by Kal (Talk)

{{#vardefine:boxwith|{{{width| 300}}} }}{{#vardefine:iconwith|{{{iconsize|45}}} }}
{| width="{{{width|800}}}" cellspacing="0" style="border: 0px; padding: 0px; border-style: solid; border-color: {{{color|#8BC3DF;}}}; border-width: {{{thickness|2}}}px;"
{{#if: {{{icon|}}} | {{#if: {{{sub-header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{{iconsize|45}}}" rowspan="2" {{!}} [[Image:{{{icon}}}]] | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{{iconsize|45}}}" {{!}} [[Image:{{{icon}}}]]}} }}

{{ #if: {{{header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{ #expr: {{#var:boxwith}} - {{#var:iconwith}} }}" valign="{{{halign|bottom}}}" {{!}} '''{{{header}}}'''| }}
|-
{{ #if: {{{sub-header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{ #expr: {{#var:boxwith}} - {{#var:iconwith}} }}" valign="top" {{!}} {{{sub-header}}} |}}
|-
{{ #if: {{{content|}}} | {{!}} style="background-color: {{{content-color|#FFFFEF;}}}" colspan="2" {{!}} {{#if: {{{center|}}}|<div align="center">|}} {{{content}}} {{#if: {{{center|}}}|</div>|}} |}}
|-
{{ #if: {{{description|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" colspan="2" {{!}} {{{description}}} |}}
|}
<noinclude>
ContentBox is a very flexible layout configuration tool. You can use it to render all sorts of content and to layout multiple pages in your articles. It is very configurable: icon, header, sub-header, content, description, border, border thickess, color, content color and size.
You can see how such a configurable box can be very easy and flexible to use.
==Usage==
Here is how you use it and the parameter list:
like every other template you include it by using the
<pre>{{ContentBox
|content= Content Goes here. (issue, for lists and other items it may be necessary to add the following hack {{!!}}. This is necessary due to weaknesses in the parser, that remove all white space. This is only one of the multiple flaws of the mediawiki parser.
}}</pre> If no parameter apart from content are passed then the template uses a set default parameters.
</noinclude>

Template:ContentBlock

2008-09-12T13:20:03Z

Kal:

{{#vardefine:boxwith|{{{width| 300}}} }}{{#vardefine:iconwith|{{{iconsize|45}}} }}
{| width="{{{width|800}}}" cellspacing="0" style="border: 0px; padding: 0px; border-style: solid; border-color: {{{color|#8BC3DF;}}}; border-width: {{{thickness|2}}}px;"
{{#if: {{{icon|}}} | {{#if: {{{sub-header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{{iconsize|45}}}" rowspan="2" {{!}} [[Image:{{{icon}}}]] | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{{iconsize|45}}}" {{!}} [[Image:{{{icon}}}]]}} }}

{{ #if: {{{header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{ #expr: {{#var:boxwith}} - {{#var:iconwith}} }}" valign="{{{halign|bottom}}}" {{!}} '''{{{header}}}'''| }}
|-
{{ #if: {{{sub-header|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" width="{{ #expr: {{#var:boxwith}} - {{#var:iconwith}} }}" valign="top" {{!}} {{{sub-header}}} |}}
|-
{{ #if: {{{content|}}} | {{!}} style="background-color: {{{content-color|#FFFFE0;}}}" colspan="2" {{!}} {{#if: {{{center|}}}|<div align="center">|}} {{{content}}} {{#if: {{{center|}}}|</div>|}} |}}
|-
{{ #if: {{{description|}}} | {{!}} style="background-color: {{{color|#8BC3DF;}}}" colspan="2" {{!}} {{{description}}} |}}
|}
<noinclude>
ContentBox is a very flexible layout configuration tool. You can use it to render all sorts of content and to layout multiple pages in your articles. It is very configurable: icon, header, sub-header, content, description, border, border thickess, color, content color and size.
You can see how such a configurable box can be very easy and flexible to use.
==Usage==
Here is how you use it and the parameter list:
like every other template you include it by using the
<pre>{{ContentBox
|content= Content Goes here. (issue, for lists and other items it may be necessary to add the following hack {{!!}}. This is necessary due to weaknesses in the parser, that remove all white space. This is only one of the multiple flaws of the mediawiki parser.
}}</pre> If no parameter apart from content are passed then the template uses a set default parameters.
</noinclude>

Template:CppSourceCode

2008-09-12T13:16:29Z

Kal:

{| width="800" cellspacing="0" style="border: 0px; padding: 0px; border-style: solid; border-color: #FF9900; border-width: 2px;"
| bgcolor="#FFCC33" | '''{{{description}}}'''
|-
| bgcolor="#FFFFE0" |{{{code}}}
|}

Template:CppSourceCode

2008-09-12T13:15:04Z

Kal:

Template:CppSourceCode

2008-09-12T13:12:14Z

Kal:

{| width="800" cellspacing="0" style="border: 0px; padding: 0px; border-style: solid; border-color: #CCCC00; border-width: 2px;"
| bgcolor="#CCCC00" | '''{{{description}}}'''
|-
| bgcolor="#DDDDFF" |{{{code}}}
|}

Template:CppSourceCode

2008-09-12T13:11:39Z

Kal:

Terrain Extension

2008-05-20T22:47:32Z

Kal:

[[category: Extensions]]
{| border="0"
| {{ContentBlock|width=800|color=white |content=
The Terrain Extension extends Horde3D with the capability to render large landscapes. A special level of detail algorithm adapts the resolution of the terrain mesh so that near regions get more details than remote ones. The algorithm also considers the geometric complexity of the terrain to increase the resolution solely where this is really required. This makes the rendering fast and provides a high quality with a minimum of popping artifacts.

A height map is used to define the altitude of the terrain. The height map is a usual texture map that encodes 16 bit height information in two channels. The red channel of the texture contains the coarse height, while the green channel encodes finer graduations. The encoding of the information is usually done with an appropriate tool. If you just want to use 8 bit height information, you can simply copy the greyscale image to the red channel of the height map and leave the green channel black.

= Installation Windows =
To install the extension, simply copy the contents of the extension root directory to the Horde3D SDK folder and merge the directories. In Visual Studio, add the extension and sample projects to the solution. Then add the extension project to the project dependencies of the Horde3D Engine and the Horde3D Engine to the dependencies of the Terrain Sample. After that, include 'Terrain/extension.h' in 'egExtensions.cpp' of the engine and add '#pragma comment( lib, "Extension_Terrain.lib" )' to link against the terrain extension (under Windows). Finally, add the following line to ExtensionManager::installExtensions to register the extension:

<pre>
installExtension( Horde3DTerrain::getExtensionName,
Horde3DTerrain::initExtension, Horde3DTerrain::releaseExtension );
</pre>

The extension is then part of the Horde3D DLL and can be used with the Horde3DTerrain.h header file.

= Installation Linux =
Go to your target directory where you want to install Horde3D. Then extract the files, replace versions as needed.
<pre>
unzip Horde3D_SDK_1.0.0_Beta1.zip
unzip Horde3D_ExtTerrain_0.1.1.zip
</pre>

Now change Horde3D/Source/Horde3D Engine/egExtensions.cpp. Basically just uncomment all lines with code regarding the terrain extension:
<pre>
--- Horde3D/Source/Horde3D Engine/egExtensions.cpp.old 2008-04-14 23:19:44.000000000 +0200
+++ Horde3D/Source/Horde3D Engine/egExtensions.cpp 2008-04-14 22:56:19.000000000 +0200
@@ -25,16 +25,16 @@
#include "egExtensions.h"

// Include files for extensions
-//#include "Terrain/Source/extension.h"
+#include "Terrain/Source/extension.h"

// Lib files for extensions
-//#pragma comment( lib, "Extension_Terrain.lib" )
+#pragma comment( lib, "Extension_Terrain.lib" )

bool ExtensionManager::installExtensions()
{
// Install desired extensions here
- //installExtension( Horde3DTerrain::getExtensionName,
Horde3DTerrain::initExtension, Horde3DTerrain::releaseExtension );
+ installExtension( Horde3DTerrain::getExtensionName,
Horde3DTerrain::initExtension, Horde3DTerrain::releaseExtension );

return true;
}
</pre>

Now fix Horde3D/Source/Horde3D Engine/makefile:
<pre>--- Horde3D/Source/Horde3D Engine/makefile.old 2008-04-01 20:42:58.000000000 +0200
+++ Horde3D/Source/Horde3D Engine/makefile 2008-04-14 23:09:49.000000000 +0200
@@ -6,13 +6,15 @@
egRenderer.o egResource.o egScene.o egSceneGraphRes.o egShader.o egTextures.o \
utImage.o utOpenGL.o ../Shared/utXMLParser.o

+TERRAIN_OBJECTS = ../../../Extensions/Terrain/Source/extension.o
../../../Extensions/Terrain/Source/terrain.o
+

libHorde3D: $(OBJECTS)
- g++ $(OBJECTS) -olibHorde3D.so -lGL -shared
+ g++ $(OBJECTS) $(TERRAIN_OBJECTS) -olibHorde3D.so -lGL -shared
mv libHorde3D.so ../../Binaries/Linux_x86

%.o: %.cpp
- g++ -c $< -o$@ -I../Shared -I../../Extensions -fPIC ${CFLAGS}
+ g++ -c $< -o$@ -I../Shared -I../../../Extensions -fPIC ${CFLAGS}

clean:
</pre>

If you are using the 1.0.0 Beta1 on a 64 bit system you have to fix Horde3D/Source/Horde3D Engine/utImage.cpp:
<pre>--- Horde3D/Source/Horde3D Engine/utImage.cpp.old 2008-04-01 23:28:22.000000000 +0200
+++ Horde3D/Source/Horde3D Engine/utImage.cpp 2008-04-14 23:03:28.000000000 +0200
@@ -1257,7 +1257,7 @@
}
return e("outofmem", "Out of memory");
}
- img_comp[i].data = (uint8*) (((int) img_comp[i].raw_data + 15) & ~15);
+ img_comp[i].data = (uint8*) (((size_t) img_comp[i].raw_data + 15) & ~15);
img_comp[i].linebuf = NULL;
}
</pre>

Now we can compile the project: Call make in the following directories in the specified order:
<pre>
Extensions/Terrain/Source
Horde3D
Extensions/Terrain/Sample
</pre>

Now everything should be working. Go to Horde3D/Binaries/Linux_x86 to try the samples.

= Using the extension =

The extension defines the uniform *terBlockParams* and the attribute *terHeight* that can be used in a shader to render the terrain. To see how this is working in detail, have a look at the included sample shader.

In the Terrain Sample distributed with the extension, there's also a normal map encoded in the heightmap texture. The data for the
normal map is encoded in the blue and alpha channel. A simple tool to create such a combined normal height map is integrated in the Horde3D Scene Editor. It can use 8-bit or 16-bit images as heightmap input. In case of 8-bit images you can also specify a smoothing operator to convert the 8-bit heightmap into a more smooth 16-bit one.
}} 
| valign="top" |{{Extension_Summary|
name = Terrain Extension|
screenshot = H3Dterrain.jpg|
description = The Terrain Extension extends Horde3D with the capability to render large landscapes.|
version = 0.1.0|
horde3dversion = 0.15|
released = 2008-03-30|
author = Nicolas Schulz and Volker Wiendl|
}}
|}

Tutorial - Hello World

2008-05-20T22:43:41Z

Kal:

{| border="0"
| {{ContentBlock|width=800|color=white
|content='''In this section we will create a simple application that loads a character and animates it using a walk cycle. You will see how straightforward it is to use the Horde3D API.'''

As a first step you have to create an application that opens a window which can be used for rendering. This is a pretty standard task and if you are a novice and have problems with that on your platform use Google to find one of the numerous good tutorials on the net or have a look at the samples that come with the Horde3D SDK. The next step is to initialize an OpenGL context for our rendering window. You can do this manually or use the Horde3D Utility Library to make your life easier. After that is done we can finally get to the engine related part.

{{CppSourceCode|
description= Simple Setup of the Horde3D renderer.|
code=
<source lang="cpp" line="1">
NodeHandle model = 0, cam = 0;

void initGame( int winWidth, int winHeight )
{
// Initialize engine
Horde3D::init();
Horde3D::resize( 0, 0, winWidth, winHeight );

// Add pipeline resource
ResHandle pipeRes = Horde3D::addResource( ResourceTypes::Pipeline, "standard.pipeline.xml", 0 );
// Add model resource
ResHandle modelRes = Horde3D::addResource( ResourceTypes::SceneGraph, "character.scene.xml", 0 );
// Add animation resource
ResHandle animRes = Horde3D::addResource( ResourceTypes::Animation, "walk.anim.xml", 0 );
// Load added resources
Horde3DUtils::loadResourcesFromDisk( "" );

// Add model to scene
model = Horde3D::addNodes( RootNode, modelRes );
// Apply animation
Horde3D::setupModelAnimStage( model, 0, animRes, "" );

// Add light source
NodeHandle light = Horde3D::addLightNode( RootNode, "Light1", 0, "LIGHTING", "SHADOWMAP" );
// Set light position and radius
Horde3D::setNodeTransform( light, 0, 20, 0, 0, 0, 0, 1, 1, 1 );
Horde3D::setLightParam( light, LightNodeParams::Radius, 50.0f );

// Add camera
NodeHandle cam = Horde3D::addCameraNode( RootNode, "Camera", pipeRes );
}
</source>
}}

The first line of the code above declares two global handles to Horde scene graph nodes. All objects in Horde are accessible via handles, a concept similar to pointers. The first thing we need to do in our initGame function to use Horde3D is initializing the engine. This happens with the function init. After that we tell the engine the size of our rendering window so that it can adjust the viewport.

The next step is to load the required resources. In Horde resources are data files that are loaded once and can be referenced by several objects for rendering. The function addResource takes the resource type we want to add and the name of the resource (usually the filename) as parameters and returns a handle to the created resource object. In our case we want a model which is represented as a scene graph file in Horde and additionally an animation. Now the resources are created but we still need to load them. Horde supports loading from any sources including encrypted archives or a network but in this case we just want to load our resources from the local hard disk which is done with the utility function loadResourcesFromDisk. Besides our model and animation we also load a pipeline resource. A pipeline defines how the the scene is rendered and can be used to realize post-processing effects or high dynamic range rendering. For the beginning you can just use the files that come with the SDK samples.

After we have loaded the required resources we can finally build up the scene graph. The scene graph represents the objects in our virtual world in a hierarchical tree structure. First we add the model that we have loaded before. We use the function addNodes for doing this which takes a scene graph resource and a parent node. The parent is the scene object to which the new node is attached, in our case just the root node which is the base of the virtual world. Similar to addResource this function also returns a handle to the created scene graph subtree. After that we assign the loaded animation to our model node with the function setupModelAnimStage. Horde allows you to apply several different animations to a model and makes it possible to blend and mix them but for the beginning one should be enough. Now that adding the model is finished we still need a light source. It would be possible to load another scene graph file which contains the light source but we want to add it manually by using the addLightNode function. This function requires several parameters specifying the shaders used for rendering. More information on this can be found in other sections of the manual. The next step is to set the position and orientation which is done with setNodeTransform. After that we specify the light radius which defines the zone of influence using setLightParam. Finally we still need a camera which represents the viewer. It is added with the function addCameraNode and takes our loaded pipeline resource as parameter.

{{CppSourceCode|
description= Game Loop and Destructor|
code=
<source lang="cpp" line="1">
void gameLoop( float fps )
{
static float t = 0;

// Increase animation time
t = t + 10.0f * (1 / fps);

// Play animation
Horde3D::setModelAnimParams( model, 0, t, 1.0f );

// Set new model position
Horde3D::setNodeTransform( model, t * 10, 0, 0, // Translation
0, 0, 0, // Rotation
1, 1, 1 ); // Scale

// Render scene
Horde3D::render( cam );
}

void releaseGame()
{
// Release engine
Horde3D::release();
}
</source>
}}

The next function in our sample is the game loop which is called once every frame. Here we will animate our character model. For doing this we define a time counter which is increased in every frame. To make the animation speed independent from the framerate, we scale the time step by the inverse of the current frames per second value. After that we tell the engine to update the model animation using the setModelAnimParams function. We could also specify a blend weight for combining animations here but since we have only one animation we don't need that. Now we can displace our character a bit so that it moves through the scene. This is achieved by updating the model node transformation. Finally we need to tell the engine to render the scene and recalculate the model animation. This happens with the function render that expects the camera from which the scene is viewed.

The last function releaseGame is called when the application is closed. All we have to do here is freeing the engine with the release function.

That's it so far with the basic tutorial. You can have a look at the Usage Guide now to learn more details.
}}
| valign="top" | {{Extension_Summary|
name = Hello World Tutorial|
screenshot = H3DPlaceHolder.png|
description = This tutorial introduces the basic steps necessary to setup horde3d|
version = 1.0|
horde3dversion = 1.0 beta|
released = 2008-03-30|
author = Nicolas Schulz|
}}
|}
[[category: Tutorials]]

Shading Technique - Dot Product Detail Texturing

2008-05-20T22:41:33Z

Kal:

{| border="0"
| {{ContentBlock|width=800|color=white
|content={{!!}}
== Overview ==
'''Defining a detail texture:''' a texture that contains commonly occuring high frequency surface variations.

'''Why might you want to use this technique?'''<br/>
- As a fall-back for lower end hardware<br/>
- In circumstances where mid-ranged detail is more important than up close

== The Technique ==

'''Requirements:'''<BR/>
- RGB Color Map<BR/>
- RGBA Opacity/Blend Map<BR/>
- RGBA Composite Detail Textures<BR/>

{{CppSourceCode|
description= GLSL Code|
code=
<source lang="cpp" line="1">
vec3 col = texture2D(__ColorMap__, texCoords).rgb;
vec4 blend = texture2D(__BlendMap__, texCoords).rgba;
vec4 detVal = texture2D(__DetailComposite__, texCoords * 200.0).rgba;
float dotValue = dot(detVal, blend);
float sVal = 1.0 - (dotValue * 2.0);
col += (-sVal);
</source>}}

The objective of the technique is to use the channels of an RGBA image to hold four different grayscale detail texture maps which are extracted by the dot product of the vectors for the composite image and its corresponding RGBA blend, dominance, opacity, w/e map.

Because multiplication against a range of 0 to 1 can only reduce the brightness of a texture the consequence of repeating this with multiple blends and/or overlapping layers is that the surface will continually get darker. By transforming the detail from a range of 0 to 1 to a range of -1 to +1 addition can be used to make it possible to darken the texture by adding a negative value to it and lighten it by adding a positive value. The last five lines of the shader can be repeated for any number of blend and composite maps.

The line:

float sVal = 1.0 - (dotValue * 2.0);

accomplishes this objective, however it inverts the light and dark values making it necessary to add the opposite of "sVal" to invert it again so the textures will behave as expected.

The technique is very fast and ideal for use as a material fallback for machines with lower end hardware. With the addition of 1D color lookups for some of the detail maps it could also add small highlights such as flowers and sea-shells, this would require the addition of 1D textures to Horde3D, so it is not currently an option at the moment, but is worth thinking about. 2D textures could be used however.

{{CppSourceCode|
description= Full GLSL Fragment Shader for Terrain Lighting Context|
code=
<source lang="cpp" line="1">
uniform sampler2D tex0, tex1, tex2, tex3;
varying vec4 pos, vsPos;
varying vec2 texCoords;

void main( void )
{
vec3 colMap = texture2D( tex1, texCoords).rgb;
vec4 blendMap = texture2D(tex2, texCoords).rgba;
vec4 blendTex = texture2D(tex3, texCoords * 300.0).rgba;
float detResult = dot(blendTex, blendMap);
detResult = 1.0 - (detResult * 2.0);
colMap += (-detResult);

vec4 texel = texture2D( tex0, texCoords ) * 2.0 - 1.0;
float ny = sqrt( max( 1.0 - texel.b*texel.b - texel.a*texel.a, 0.0 ) );
vec3 normal = vec3( texel.b, ny, texel.a );

gl_FragColor.rgb =
calcPhongSpotLight( pos.xyz, normalize( normal ), colMap, 0.0, 16.0, -vsPos.z, 0.3 );
}</source>}}

== Example Result ==
[[Image:signeddetmappingmp3.jpg]]

== To-Do List for this Article ==
- Add more pictures<BR/>
- Figure out proper Wiki formatting for code and lists<BR/>
- If in some spots something that isn't as clear as it could be, edit it or point it out please
- Posted by AcidFaucet, for fastest response in regards to this article: send a PM

}}
| valign="top" | {{Extension_Summary
|name = Technique - Texturing
|screenshot = Signeddetmappingmp3Thumb.jpg
|description = Using the dot product of vectors and signed textures for high frequency detail.
|version = 1.0
|horde3dversion = 1.0 beta
|released = 2008-04-20
|author = [http://www.horde3d.org/forums/memberlist.php?mode=viewprofile&u=128 AcidFaucet]|
}}
|}
[[category: Technique]]

Shading Technique - Palette Coloring

2008-05-20T22:40:36Z

Kal:

== Explanation of the Technique ==

By definition palette recoloration is the use of defined colors that replace or modify any other colors within their specified domain. The best example in use is team colors in real-time strategy titles or the color variations of enemies in role-playing games.

== Example Fragment Shader ==

{{CppSourceCode|
description= GLSL Code|
code=
<source lang="cpp" line="1">
uniform vec4 Rkey;
uniform vec4 Bkey;
uniform vec4 Gkey;
uniform vec4 Akey;
uniform sampler2D tex0;
uniform sampler2D tex1;
varying vec3 tsbNormal;
varying vec4 pos, vsPos;
varying vec2 texCoords;

void main( void )
{
vec3 albedo = texture2D( tex0, texCoords ).rgb;
vec3 outAl;
float luminous;
vec4 blender = texture2D( tex1, texCoords ).rgba;
outAl = (Rkey.rgb * blender.r) +
(Bkey.rgb * blender.b) +
(Gkey.rgb * blender.g) +
(Akey.rgb * blender.a);
luminous = (Rkey.a * blender.r) +
(Bkey.a * blender.b) +
(Gkey.a * blender.g) +
(Akey.a * blender.a);
vec3 final = albedo-luminous + outAl-luminous;
gl_FragColor.rgb =
calcPhongSpotLight( pos.xyz, normalize( tsbNormal ), final, 0.5, -vsPos.z );
}
</source>}}

== Explanation of the Fragment Shader ==

This technique uses an RGBA blend map to define the regions and intensities at which the uniforms are used for color replacement. The uniforms can be thought as being RGBL (Red, Green, Blue, Luminance/Brightness).

The principle concept is that the base texture is colored based solely by value (in reference to the "art" definition of value as being the variance of light and dark in a composition) or color that will be unaltered. The uniform is adapted to the value and then adjusted by its luminosity in order to enable proper adjustment of the value of the RGB color.

== To Do List for This Article ==

- Cut down on esoteric terms or explain those that are esoteric<BR/>
- Explain the not so obvious reasons behind the choice of math operations<BR/>
- Add pictures!!

Horde3D Wiki:Community portal

2008-05-20T22:39:57Z

Kal:

__NOEDITSECTION__{{ContentBlock|width=800|color=orange
|content= '''The community portal section of the Horde3D wiki contains community contributed articles that are not part of the official documentation. Feel free to add articles to our wiki or links to external tutorials.'''}}
{{SpacerBlock}}
{{ContentBlock|width=800
|header=Horde3D is a cross-platform graphics engine. The currently supported platform are Windows, Linux and Mac OS X.
|content={{!!}}
==How-To setup a Horde3D Development Environment==
*[[Horde3D Development Environment for Windows]]
*[[Horde3D Development Environment for Linux]]
*[[Horde3D Development Environment for Mac OS X]]

==Tutorials==
[[Category: Tutorials]]

Fell free to write your tutorials here, for the benefit of the whole community.
===Beginner===
#[[Tutorial - Hello World]] - In this section we will create a simple application that loads a character and animates it using a walk cycle.
#[[Tutorial - Picking]] - In this section we will demonstrate picking the node under the mouse cursor
#[[Tutorial - Simple HUD]] - How to use showOverlay to create a simple HUD.

===Intermediate===

===Advanced===

==Techniques==
[[Category: Techniques]]

===Shading===
#[[Shading Technique - Dot Product Detail Texturing]] - Using the dot product of vectors and signed textures for high frequency detail
#[[Shading Technique - Palette Coloring]] - Quick and dirty palette recoloration of objects
}}

Shading Technique - Palette Coloring

2008-05-20T22:39:36Z

Kal: Shading Technique - Palatte Coloring moved to Shading Technique - Palette Coloring: spelling

== Explanation of the Technique ==

By definition palatte recoloration is the use of defined colors that replace or modify any other colors within their specified domain. The best example in use is team colors in real-time strategy titles or the color variations of enemies in role-playing games.

== Example Fragment Shader ==

{{CppSourceCode|
description= GLSL Code|
code=
<source lang="cpp" line="1">
uniform vec4 Rkey;
uniform vec4 Bkey;
uniform vec4 Gkey;
uniform vec4 Akey;
uniform sampler2D tex0;
uniform sampler2D tex1;
varying vec3 tsbNormal;
varying vec4 pos, vsPos;
varying vec2 texCoords;

void main( void )
{
vec3 albedo = texture2D( tex0, texCoords ).rgb;
vec3 outAl;
float luminous;
vec4 blender = texture2D( tex1, texCoords ).rgba;
outAl = (Rkey.rgb * blender.r) +
(Bkey.rgb * blender.b) +
(Gkey.rgb * blender.g) +
(Akey.rgb * blender.a);
luminous = (Rkey.a * blender.r) +
(Bkey.a * blender.b) +
(Gkey.a * blender.g) +
(Akey.a * blender.a);
vec3 final = albedo-luminous + outAl-luminous;
gl_FragColor.rgb =
calcPhongSpotLight( pos.xyz, normalize( tsbNormal ), final, 0.5, -vsPos.z );
}
</source>}}

== Explanation of the Fragment Shader ==

This technique uses an RGBA blend map to define the regions and intensities at which the uniforms are used for color replacement. The uniforms can be thought as being RGBL (Red, Gree, Blue, Luminance/Brightness).

The principle concept is that the base texture is colored based solely by value (in reference to the "art" definition of value as being the variance of light and dark in a composition) or color that will be unaltered. The uniform is adapted to the value and then adjusted by its luminosity in order to enable proper adjustment of the value of the RGB color.

== To Do List for This Article ==

- Cut down on esoteric terms or explain those that are esoteric<BR/>
- Explain the not so obvious reasons behind the choice of math operations<BR/>
- Add pictures!!

Shading Technique - Palatte Coloring

2008-05-20T22:39:36Z

Kal: Shading Technique - Palatte Coloring moved to Shading Technique - Palette Coloring: spelling

#REDIRECT [[Shading Technique - Palette Coloring]]