Irrlicht Engine

Use 2 shaders, one that use the cube's texture, other use some other colour to render the cube.
Change the shader of the cube whenever you need.

In my project's case i need to constantly create and delete irrlicht device,i.e to call 'device' = CreatDevice() and to dealloc the 'device', frequently. I got a memory leak of 0.6 MB when ever i create and delete the device. Fixed the leak with few changes,
Add the lines that starts with + symbol ...

Loop the above code by hiding the node collided with ray until you receive null for 'selectedSceneNode1'.


firstEntry = true
while(selectedSceneNode1 || firstEntry) {
if(firstEntry == false){
selectedSceneNode1->setVisible(false);
// store 'selectedSceneNode1' in any containers to reset its ...

Ok it is fine. During the shadercallback irrlicht first calls OnSetMaterial(SMaterial &material) and then calls OnSetConstant(..). So we can use material parameter in OnSetMaterial(..) to identify the node and set the properties according to that.

Thank you.

Oh sorry, I have made a mistake in my question statement 1) In Irrlicht we can not use a common callback class for all the Nodes[A1...An], because each nodes have different properties/uniforms to pass to shaders.
Edited the statement to 1) In Irrlicht we can not use a common callback class for all ...

Would't it be efficient if irrlicht has ShaderCallBacks for Nodes rather than for MaterialRenderers ?
Consider this case: Nodes [A1,A2.....An] want to use single shader and different callback classes (for setting the node properties/uniforms). For loading the shader in irrlicht we need to pass the ...

Ok. I will try it once again and report the result.

iPad4 (Retina) and simulators for iPhone6+,iPhone6.

GL_MULTISAMPLE is not enabled for opengles2.0, so it is throwing error. Any other way ?

Thanks nadro, I followed the steps which is given in the link exactly, but did't find any change in rendering quality. Even tried various sampling values but no use, i might've missed something. Will produce the code after fixing the issue.

Yes For IOS platform.

Thanks Nadro. Any clues on fixing this issue ?

Does irrlicht opengles2.0 supports antialiasing ? While creating the device (creatdevice(Param)) i have tested with the param.AntiAlias values, did't find any change in the aliasing issue. Can anyone suggest the right way to achieve this in irrlicht opengles 2.0 ?

yes you are right, we can edit these methods depending on our convenience.

Irrlicht clears the shader memory only if the irrlicht device is deleted (Irrlicht device is created using CreateDevice(..) method ). This caused a huge memory leak in my project, in which multiple number of unique shaders are needed to be generated and removed without deleting the irrlicht device ...