<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
<title>Irrlicht Engine: Tutorial 10: Shaders</title>
<link href="doxygen.css" rel="stylesheet" type="text/css">
</head><body>
<table class="irrlicht" >
<tr valign="middle">
<td><font size="2"><a class="qindex" href="index.html"><font color="#FFFFFF">Home</font></a>
| <a class="qindex" href="namespaces.html"><font color="#FFFFFF">Namespaces</font></a>
| <a class="qindex" href="hierarchy.html"><font color="#FFFFFF">Hierarchy</font></a>
| <a class="qindex" href="classes.html"><font color="#FFFFFF">Alphabetical
List</font></a> | <a class="qindex" href="annotated.html"><font color="#FFFFFF">
Class list</font></a> | <a class="qindex" href="files.html"><font color="#FFFFFF">Files</font></a>
| <a class="qindex" href="namespacemembers.html"><font color="#FFFFFF">
Namespace Members</font></a> | <a class="qindex" href="functions.html"><font color="#FFFFFF">Class
members</font></a> | <a class="qindex" href="globals.html"><font color="#FFFFFF">File
members</font></a> | <a class="qindex" href="pages.html"><font color="#FFFFFF">Tutorials</font></a></font> </td>
</tr>
</table>
<!-- Generated by Doxygen 1.5.6 -->
<div class="contents">
<h1><a class="anchor" name="example010">Tutorial 10: Shaders </a></h1><div align="center">
<img src="010shot.jpg" alt="010shot.jpg">
</div>
<p>
This tutorial shows how to use shaders for D3D8, D3D9, and OpenGL with the engine and how to create new material types with them. It also shows how to disable the generation of mipmaps at texture loading, and how to use text scene nodes.<p>
This tutorial does not explain how shaders work. I would recommend to read the D3D or OpenGL documentation, to search a tutorial, or to read a book about this.<p>
At first, we need to include all headers and do the stuff we always do, like in nearly all other tutorials: <div class="fragment"><pre class="fragment"><span class="preprocessor">#include <<a class="code" href="irrlicht_8h.html" title="Main header file of the irrlicht, the only file needed to include.">irrlicht.h</a>></span>
<span class="preprocessor">#include <iostream></span>
<span class="keyword">using namespace </span>irr;
<span class="preprocessor">#ifdef _MSC_VER</span>
<span class="preprocessor"></span><span class="preprocessor">#pragma comment(lib, "Irrlicht.lib")</span>
<span class="preprocessor">#endif</span>
</pre></div><p>
Because we want to use some interesting shaders in this tutorials, we need to set some data for them to make them able to compute nice colors. In this example, we'll use a simple vertex shader which will calculate the color of the vertex based on the position of the camera. For this, the shader needs the following data: The inverted world matrix for transforming the normal, the clip matrix for transforming the position, the camera position and the world position of the object for the calculation of the angle of light, and the color of the light. To be able to tell the shader all this data every frame, we have to derive a class from the IShaderConstantSetCallBack interface and override its only method, namely OnSetConstants(). This method will be called every time the material is set. The method setVertexShaderConstant() of the IMaterialRendererServices interface is used to set the data the shader needs. If the user chose to use a High Level shader language like HLSL instead of Assembler in this example, you have to set the variable name as parameter instead of the register index. <div class="fragment"><pre class="fragment">IrrlichtDevice* device = 0;
<span class="keywordtype">bool</span> UseHighLevelShaders = <span class="keyword">false</span>;
<span class="keyword">class </span>MyShaderCallBack : <span class="keyword">public</span> video::IShaderConstantSetCallBack
{
<span class="keyword">public</span>:
<span class="keyword">virtual</span> <span class="keywordtype">void</span> OnSetConstants(video::IMaterialRendererServices* services,
<a class="code" href="namespaceirr.html#c66849b7a6ed16e30ebede579f9b47c6" title="32 bit signed variable.">s32</a> userData)
{
video::IVideoDriver* driver = services->getVideoDriver();
<span class="comment">// set inverted world matrix</span>
<span class="comment">// if we are using highlevel shaders (the user can select this when</span>
<span class="comment">// starting the program), we must set the constants by name.</span>
<a class="code" href="namespaceirr_1_1core.html#73fa92e638c5ca97efd72da307cc9b65" title="Typedef for f32 matrix.">core::matrix4</a> invWorld = driver->getTransform(<a class="code" href="namespaceirr_1_1video.html#15b57657a320243be03ae6f66fcff43d843cf42adb3fa9caf61c9e228cf14e85" title="World transformation.">video::ETS_WORLD</a>);
invWorld.makeInverse();
<span class="keywordflow">if</span> (UseHighLevelShaders)
services->setVertexShaderConstant(<span class="stringliteral">"mInvWorld"</span>, invWorld.pointer(), 16);
<span class="keywordflow">else</span>
services->setVertexShaderConstant(invWorld.pointer(), 0, 4);
<span class="comment">// set clip matrix</span>
<a class="code" href="namespaceirr_1_1core.html#73fa92e638c5ca97efd72da307cc9b65" title="Typedef for f32 matrix.">core::matrix4</a> worldViewProj;
worldViewProj = driver->getTransform(<a class="code" href="namespaceirr_1_1video.html#15b57657a320243be03ae6f66fcff43de7ec186418508c67a7562af012d7b63f" title="Projection transformation.">video::ETS_PROJECTION</a>);
worldViewProj *= driver->getTransform(<a class="code" href="namespaceirr_1_1video.html#15b57657a320243be03ae6f66fcff43d152f4262d5874186e0288934c7d31e14" title="View transformation.">video::ETS_VIEW</a>);
worldViewProj *= driver->getTransform(<a class="code" href="namespaceirr_1_1video.html#15b57657a320243be03ae6f66fcff43d843cf42adb3fa9caf61c9e228cf14e85" title="World transformation.">video::ETS_WORLD</a>);
<span class="keywordflow">if</span> (UseHighLevelShaders)
services->setVertexShaderConstant(<span class="stringliteral">"mWorldViewProj"</span>, worldViewProj.pointer(), 16);
<span class="keywordflow">else</span>
services->setVertexShaderConstant(worldViewProj.pointer(), 4, 4);
<span class="comment">// set camera position</span>
<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a> pos = device->getSceneManager()->
getActiveCamera()->getAbsolutePosition();
<span class="keywordflow">if</span> (UseHighLevelShaders)
services->setVertexShaderConstant(<span class="stringliteral">"mLightPos"</span>, reinterpret_cast<f32*>(&pos), 3);
<span class="keywordflow">else</span>
services->setVertexShaderConstant(reinterpret_cast<f32*>(&pos), 8, 1);
<span class="comment">// set light color</span>
video::SColorf col(0.0f,1.0f,1.0f,0.0f);
<span class="keywordflow">if</span> (UseHighLevelShaders)
services->setVertexShaderConstant(<span class="stringliteral">"mLightColor"</span>,
reinterpret_cast<f32*>(&col), 4);
<span class="keywordflow">else</span>
services->setVertexShaderConstant(reinterpret_cast<f32*>(&col), 9, 1);
<span class="comment">// set transposed world matrix</span>
<a class="code" href="namespaceirr_1_1core.html#73fa92e638c5ca97efd72da307cc9b65" title="Typedef for f32 matrix.">core::matrix4</a> world = driver->getTransform(<a class="code" href="namespaceirr_1_1video.html#15b57657a320243be03ae6f66fcff43d843cf42adb3fa9caf61c9e228cf14e85" title="World transformation.">video::ETS_WORLD</a>);
world = world.getTransposed();
<span class="keywordflow">if</span> (UseHighLevelShaders)
services->setVertexShaderConstant(<span class="stringliteral">"mTransWorld"</span>, world.pointer(), 16);
<span class="keywordflow">else</span>
services->setVertexShaderConstant(world.pointer(), 10, 4);
}
};
</pre></div><p>
The next few lines start up the engine just like in most other tutorials before. But in addition, we ask the user if he wants to use high level shaders in this example, if he selected a driver which is capable of doing so. <div class="fragment"><pre class="fragment"><span class="keywordtype">int</span> main()
{
<span class="comment">// let user select driver type</span>
<a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d0" title="An enum for all types of drivers the Irrlicht Engine supports.">video::E_DRIVER_TYPE</a> driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d04691ca314f9018f508dcf2c57dcaacec" title="Direct3D 9 device, only available on Win32 platforms.">video::EDT_DIRECT3D9</a>;
printf(<span class="stringliteral">"Please select the driver you want for this example:\n"</span>\
<span class="stringliteral">" (a) Direct3D 9.0c\n (b) Direct3D 8.1\n (c) OpenGL 1.5\n"</span>\
<span class="stringliteral">" (d) Software Renderer\n (e) Burning's Software Renderer\n"</span>\
<span class="stringliteral">" (f) NullDevice\n (otherKey) exit\n\n"</span>);
<span class="keywordtype">char</span> i;
std::cin >> i;
<span class="keywordflow">switch</span>(i)
{
<span class="keywordflow">case</span> <span class="charliteral">'a'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d04691ca314f9018f508dcf2c57dcaacec" title="Direct3D 9 device, only available on Win32 platforms.">video::EDT_DIRECT3D9</a>;<span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <span class="charliteral">'b'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d08cc3807f6f28404f3424ad7e31b3142f" title="Direct3D8 device, only available on Win32 platforms.">video::EDT_DIRECT3D8</a>;<span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <span class="charliteral">'c'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d02715182a79f1cb8e2826fd68a8150a53" title="OpenGL device, available on most platforms.">video::EDT_OPENGL</a>; <span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <span class="charliteral">'d'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d01598cd235a1a6bd052e2011b559e8995" title="The Irrlicht Engine Software renderer.">video::EDT_SOFTWARE</a>; <span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <span class="charliteral">'e'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d0e85481da26159b967191ccc6de1e4a05" title="The Burning&#39;s Software Renderer, an alternative software renderer.">video::EDT_BURNINGSVIDEO</a>;<span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <span class="charliteral">'f'</span>: driverType = <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d0cfdbd476cbfd4d05e72f9adffcc42210" title="Null driver, useful for applications to run the engine without visualisation.">video::EDT_NULL</a>; <span class="keywordflow">break</span>;
<span class="keywordflow">default</span>: <span class="keywordflow">return</span> 1;
}
<span class="comment">// ask the user if we should use high level shaders for this example</span>
<span class="keywordflow">if</span> (driverType == <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d04691ca314f9018f508dcf2c57dcaacec" title="Direct3D 9 device, only available on Win32 platforms.">video::EDT_DIRECT3D9</a> ||
driverType == <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d02715182a79f1cb8e2826fd68a8150a53" title="OpenGL device, available on most platforms.">video::EDT_OPENGL</a>)
{
printf(<span class="stringliteral">"Please press 'y' if you want to use high level shaders.\n"</span>);
std::cin >> i;
<span class="keywordflow">if</span> (i == <span class="charliteral">'y'</span>)
UseHighLevelShaders = <span class="keyword">true</span>;
}
<span class="comment">// create device</span>
device = <a class="code" href="namespaceirr.html#baf4d8719cc26b0d30813abf85e47c76" title="Creates an Irrlicht device. The Irrlicht device is the root object for using the...">createDevice</a>(driverType, core::dimension2d<u32>(640, 480));
<span class="keywordflow">if</span> (device == 0)
<span class="keywordflow">return</span> 1; <span class="comment">// could not create selected driver.</span>
video::IVideoDriver* driver = device->getVideoDriver();
scene::ISceneManager* smgr = device->getSceneManager();
gui::IGUIEnvironment* gui = device->getGUIEnvironment();
</pre></div><p>
Now for the more interesting parts. If we are using Direct3D, we want to load vertex and pixel shader programs, if we have OpenGL, we want to use ARB fragment and vertex programs. I wrote the corresponding programs down into the files d3d8.ps, d3d8.vs, d3d9.ps, d3d9.vs, opengl.ps and opengl.vs. We only need the right filenames now. This is done in the following switch. Note, that it is not necessary to write the shaders into text files, like in this example. You can even write the shaders directly as strings into the cpp source file, and use later addShaderMaterial() instead of addShaderMaterialFromFiles(). <div class="fragment"><pre class="fragment"> <a class="code" href="namespaceirr_1_1io.html#b1bdc45edb3f94d8319c02bc0f840ee1" title="Type used for all file system related strings.">io::path</a> vsFileName; <span class="comment">// filename for the vertex shader</span>
<a class="code" href="namespaceirr_1_1io.html#b1bdc45edb3f94d8319c02bc0f840ee1" title="Type used for all file system related strings.">io::path</a> psFileName; <span class="comment">// filename for the pixel shader</span>
<span class="keywordflow">switch</span>(driverType)
{
<span class="keywordflow">case</span> <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d08cc3807f6f28404f3424ad7e31b3142f" title="Direct3D8 device, only available on Win32 platforms.">video::EDT_DIRECT3D8</a>:
psFileName = <span class="stringliteral">"../../media/d3d8.psh"</span>;
vsFileName = <span class="stringliteral">"../../media/d3d8.vsh"</span>;
<span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d04691ca314f9018f508dcf2c57dcaacec" title="Direct3D 9 device, only available on Win32 platforms.">video::EDT_DIRECT3D9</a>:
<span class="keywordflow">if</span> (UseHighLevelShaders)
{
psFileName = <span class="stringliteral">"../../media/d3d9.hlsl"</span>;
vsFileName = psFileName; <span class="comment">// both shaders are in the same file</span>
}
<span class="keywordflow">else</span>
{
psFileName = <span class="stringliteral">"../../media/d3d9.psh"</span>;
vsFileName = <span class="stringliteral">"../../media/d3d9.vsh"</span>;
}
<span class="keywordflow">break</span>;
<span class="keywordflow">case</span> <a class="code" href="namespaceirr_1_1video.html#e35a6de6d436c76107ad157fe42356d02715182a79f1cb8e2826fd68a8150a53" title="OpenGL device, available on most platforms.">video::EDT_OPENGL</a>:
<span class="keywordflow">if</span> (UseHighLevelShaders)
{
psFileName = <span class="stringliteral">"../../media/opengl.frag"</span>;
vsFileName = <span class="stringliteral">"../../media/opengl.vert"</span>;
}
<span class="keywordflow">else</span>
{
psFileName = <span class="stringliteral">"../../media/opengl.psh"</span>;
vsFileName = <span class="stringliteral">"../../media/opengl.vsh"</span>;
}
<span class="keywordflow">break</span>;
}
</pre></div><p>
In addition, we check if the hardware and the selected renderer is capable of executing the shaders we want. If not, we simply set the filename string to 0. This is not necessary, but useful in this example: For example, if the hardware is able to execute vertex shaders but not pixel shaders, we create a new material which only uses the vertex shader, and no pixel shader. Otherwise, if we would tell the engine to create this material and the engine sees that the hardware wouldn't be able to fullfill the request completely, it would not create any new material at all. So in this example you would see at least the vertex shader in action, without the pixel shader. <div class="fragment"><pre class="fragment"> <span class="keywordflow">if</span> (!driver->queryFeature(<a class="code" href="namespaceirr_1_1video.html#57b1721e42a79c5dcf8e830e3621e08fe3c30045e54cd02efdb3e67eff12664f" title="Is Pixel Shader 1.1 supported?">video::EVDF_PIXEL_SHADER_1_1</a>) &&
!driver->queryFeature(<a class="code" href="namespaceirr_1_1video.html#57b1721e42a79c5dcf8e830e3621e08f85cee74794874723bd275226ad0ded76" title="Are ARB fragment programs v1.0 supported?">video::EVDF_ARB_FRAGMENT_PROGRAM_1</a>))
{
device->getLogger()->log(<span class="stringliteral">"WARNING: Pixel shaders disabled "</span>\
<span class="stringliteral">"because of missing driver/hardware support."</span>);
psFileName = <span class="stringliteral">""</span>;
}
<span class="keywordflow">if</span> (!driver->queryFeature(<a class="code" href="namespaceirr_1_1video.html#57b1721e42a79c5dcf8e830e3621e08fe85fe645c5839d5b015047abf5fff3e6" title="Is Vertex Shader 1.1 supported?">video::EVDF_VERTEX_SHADER_1_1</a>) &&
!driver->queryFeature(<a class="code" href="namespaceirr_1_1video.html#57b1721e42a79c5dcf8e830e3621e08f1eca6110e4fd3ee59e1aee60cf20e88b" title="Are ARB vertex programs v1.0 supported?">video::EVDF_ARB_VERTEX_PROGRAM_1</a>))
{
device->getLogger()->log(<span class="stringliteral">"WARNING: Vertex shaders disabled "</span>\
<span class="stringliteral">"because of missing driver/hardware support."</span>);
vsFileName = <span class="stringliteral">""</span>;
}
</pre></div><p>
Now lets create the new materials. As you maybe know from previous examples, a material type in the Irrlicht engine is set by simply changing the MaterialType value in the SMaterial struct. And this value is just a simple 32 bit value, like video::EMT_SOLID. So we only need the engine to create a new value for us which we can set there. To do this, we get a pointer to the IGPUProgrammingServices and call addShaderMaterialFromFiles(), which returns such a new 32 bit value. That's all.<p>
The parameters to this method are the following: First, the names of the files containing the code of the vertex and the pixel shader. If you would use addShaderMaterial() instead, you would not need file names, then you could write the code of the shader directly as string. The following parameter is a pointer to the IShaderConstantSetCallBack class we wrote at the beginning of this tutorial. If you don't want to set constants, set this to 0. The last paramter tells the engine which material it should use as base material.<p>
To demonstrate this, we create two materials with a different base material, one with EMT_SOLID and one with EMT_TRANSPARENT_ADD_COLOR. <div class="fragment"><pre class="fragment"> <span class="comment">// create materials</span>
video::IGPUProgrammingServices* gpu = driver->getGPUProgrammingServices();
<a class="code" href="namespaceirr.html#c66849b7a6ed16e30ebede579f9b47c6" title="32 bit signed variable.">s32</a> newMaterialType1 = 0;
<a class="code" href="namespaceirr.html#c66849b7a6ed16e30ebede579f9b47c6" title="32 bit signed variable.">s32</a> newMaterialType2 = 0;
<span class="keywordflow">if</span> (gpu)
{
MyShaderCallBack* mc = <span class="keyword">new</span> MyShaderCallBack();
<span class="comment">// create the shaders depending on if the user wanted high level</span>
<span class="comment">// or low level shaders:</span>
<span class="keywordflow">if</span> (UseHighLevelShaders)
{
<span class="comment">// create material from high level shaders (hlsl or glsl)</span>
newMaterialType1 = gpu->addHighLevelShaderMaterialFromFiles(
vsFileName, <span class="stringliteral">"vertexMain"</span>, <a class="code" href="namespaceirr_1_1video.html#9decae50d4dc2455e7b009f5c71b24f960cc4ef72d14e7192dc721bde0f07461">video::EVST_VS_1_1</a>,
psFileName, <span class="stringliteral">"pixelMain"</span>, <a class="code" href="namespaceirr_1_1video.html#07fb77e9aec681402ad376f7ef9b724c600133dcb93a6cbdddaed1e09cc8a2cc">video::EPST_PS_1_1</a>,
mc, <a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f19bc471b9c18c9e2d20496004d2a2e803" title="Standard solid material.">video::EMT_SOLID</a>);
newMaterialType2 = gpu->addHighLevelShaderMaterialFromFiles(
vsFileName, <span class="stringliteral">"vertexMain"</span>, <a class="code" href="namespaceirr_1_1video.html#9decae50d4dc2455e7b009f5c71b24f960cc4ef72d14e7192dc721bde0f07461">video::EVST_VS_1_1</a>,
psFileName, <span class="stringliteral">"pixelMain"</span>, <a class="code" href="namespaceirr_1_1video.html#07fb77e9aec681402ad376f7ef9b724c600133dcb93a6cbdddaed1e09cc8a2cc">video::EPST_PS_1_1</a>,
mc, <a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f11b5a814c4466aca2943ff056003a50d1" title="A transparent material.">video::EMT_TRANSPARENT_ADD_COLOR</a>);
}
<span class="keywordflow">else</span>
{
<span class="comment">// create material from low level shaders (asm or arb_asm)</span>
newMaterialType1 = gpu->addShaderMaterialFromFiles(vsFileName,
psFileName, mc, <a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f19bc471b9c18c9e2d20496004d2a2e803" title="Standard solid material.">video::EMT_SOLID</a>);
newMaterialType2 = gpu->addShaderMaterialFromFiles(vsFileName,
psFileName, mc, <a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f11b5a814c4466aca2943ff056003a50d1" title="A transparent material.">video::EMT_TRANSPARENT_ADD_COLOR</a>);
}
mc->drop();
}
</pre></div><p>
Now it's time for testing the materials. We create a test cube and set the material we created. In addition, we add a text scene node to the cube and a rotation animator to make it look more interesting and important. <div class="fragment"><pre class="fragment"> <span class="comment">// create test scene node 1, with the new created material type 1</span>
scene::ISceneNode* node = smgr->addCubeSceneNode(50);
node->setPosition(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,0,0));
node->setMaterialTexture(0, driver->getTexture(<span class="stringliteral">"../../media/wall.bmp"</span>));
node->setMaterialFlag(<a class="code" href="namespaceirr_1_1video.html#8a3bc00ae8137535b9fbc5f40add70d3cea597a2692b8415486a464a7f954d34" title="Will this material be lighted? Default: true.">video::EMF_LIGHTING</a>, <span class="keyword">false</span>);
node->setMaterialType((<a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f1" title="Abstracted and easy to use fixed function/programmable pipeline material modes.">video::E_MATERIAL_TYPE</a>)newMaterialType1);
smgr->addTextSceneNode(gui->getBuiltInFont(),
L<span class="stringliteral">"PS & VS & EMT_SOLID"</span>,
video::SColor(255,255,255,255), node);
scene::ISceneNodeAnimator* anim = smgr->createRotationAnimator(
<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,0.3f,0));
node->addAnimator(anim);
anim->drop();
</pre></div><p>
Same for the second cube, but with the second material we created. <div class="fragment"><pre class="fragment"> <span class="comment">// create test scene node 2, with the new created material type 2</span>
node = smgr->addCubeSceneNode(50);
node->setPosition(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,-10,50));
node->setMaterialTexture(0, driver->getTexture(<span class="stringliteral">"../../media/wall.bmp"</span>));
node->setMaterialFlag(<a class="code" href="namespaceirr_1_1video.html#8a3bc00ae8137535b9fbc5f40add70d3cea597a2692b8415486a464a7f954d34" title="Will this material be lighted? Default: true.">video::EMF_LIGHTING</a>, <span class="keyword">false</span>);
node->setMaterialType((<a class="code" href="namespaceirr_1_1video.html#c8e9b6c66f7cebabd1a6d30cbc5430f1" title="Abstracted and easy to use fixed function/programmable pipeline material modes.">video::E_MATERIAL_TYPE</a>)newMaterialType2);
smgr->addTextSceneNode(gui->getBuiltInFont(),
L<span class="stringliteral">"PS & VS & EMT_TRANSPARENT"</span>,
video::SColor(255,255,255,255), node);
anim = smgr->createRotationAnimator(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,0.3f,0));
node->addAnimator(anim);
anim->drop();
</pre></div><p>
Then we add a third cube without a shader on it, to be able to compare the cubes. <div class="fragment"><pre class="fragment"> <span class="comment">// add a scene node with no shader</span>
node = smgr->addCubeSceneNode(50);
node->setPosition(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,50,25));
node->setMaterialTexture(0, driver->getTexture(<span class="stringliteral">"../../media/wall.bmp"</span>));
node->setMaterialFlag(<a class="code" href="namespaceirr_1_1video.html#8a3bc00ae8137535b9fbc5f40add70d3cea597a2692b8415486a464a7f954d34" title="Will this material be lighted? Default: true.">video::EMF_LIGHTING</a>, <span class="keyword">false</span>);
smgr->addTextSceneNode(gui->getBuiltInFont(), L<span class="stringliteral">"NO SHADER"</span>,
video::SColor(255,255,255,255), node);
</pre></div><p>
And last, we add a skybox and a user controlled camera to the scene. For the skybox textures, we disable mipmap generation, because we don't need mipmaps on it. <div class="fragment"><pre class="fragment"> <span class="comment">// add a nice skybox</span>
driver->setTextureCreationFlag(<a class="code" href="namespaceirr_1_1video.html#caf6f7414534f7d62bff18c5bf11876f288b302e9d4faaba80c7796c7bc1682c">video::ETCF_CREATE_MIP_MAPS</a>, <span class="keyword">false</span>);
smgr->addSkyBoxSceneNode(
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_up.jpg"</span>),
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_dn.jpg"</span>),
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_lf.jpg"</span>),
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_rt.jpg"</span>),
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_ft.jpg"</span>),
driver->getTexture(<span class="stringliteral">"../../media/irrlicht2_bk.jpg"</span>));
driver->setTextureCreationFlag(<a class="code" href="namespaceirr_1_1video.html#caf6f7414534f7d62bff18c5bf11876f288b302e9d4faaba80c7796c7bc1682c">video::ETCF_CREATE_MIP_MAPS</a>, <span class="keyword">true</span>);
<span class="comment">// add a camera and disable the mouse cursor</span>
scene::ICameraSceneNode* cam = smgr->addCameraSceneNodeFPS();
cam->setPosition(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(-100,50,100));
cam->setTarget(<a class="code" href="namespaceirr_1_1core.html#06f169d08b5c429f5575acb7edbad811" title="Typedef for a f32 3d vector.">core::vector3df</a>(0,0,0));
device->getCursorControl()->setVisible(<span class="keyword">false</span>);
</pre></div><p>
Now draw everything. That's all. <div class="fragment"><pre class="fragment"> <span class="keywordtype">int</span> lastFPS = -1;
<span class="keywordflow">while</span>(device->run())
<span class="keywordflow">if</span> (device->isWindowActive())
{
driver->beginScene(<span class="keyword">true</span>, <span class="keyword">true</span>, video::SColor(255,0,0,0));
smgr->drawAll();
driver->endScene();
<span class="keywordtype">int</span> fps = driver->getFPS();
<span class="keywordflow">if</span> (lastFPS != fps)
{
<a class="code" href="namespaceirr_1_1core.html#ef83fafbb1b36fcce44c07c9be23a7f2" title="Typedef for wide character strings.">core::stringw</a> str = L<span class="stringliteral">"Irrlicht Engine - Vertex and pixel shader example ["</span>;
str += driver->getName();
str += <span class="stringliteral">"] FPS:"</span>;
str += fps;
device->setWindowCaption(str.c_str());
lastFPS = fps;
}
}
device->drop();
<span class="keywordflow">return</span> 0;
}
</pre></div><p>
Compile and run this, and I hope you have fun with your new little shader writing tool :). </div>
<hr size="1">
<address style="align: right;">
<small> </small>
</address>
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr>
<td width="0"> <div align="left"><small><a href="http://irrlicht.sourceforge.net" target="_blank"><img src="irrlicht.png" alt="The Irrlicht Engine" align="middle" border=0 width=88 height=31></a></small></div></td>
<td> <div align="left"><small><em><font size="2">The <a href="http://irrlicht.sourceforge.net" target="_blank">Irrlicht
Engine</a> Documentation © 2003-2009 by Nikolaus Gebhardt. Generated
on Sun Jan 10 09:24:07 2010 by <a href="http://www.doxygen.org" target="_blank">Doxygen</a>
(1.5.6)</font></em></small></div></td>
</tr>
</table>
<address style="align: right;">
</address>
</body>
</html>
