Irrlicht Engine

video::EDT_OPENGL

Void Linux, Intel HD5500

Hm, guess I'd have to code a test - can't really tell from the image (it's pretty hard as that stuff depends on the angle between light and normal and I don't even see the light here - somehwere to the left I guess). Also long thin triangles like those are somewhat tricky for per-vertex lighting (s...

kornwaretm wrote:have you try recalculating normals?

Code: Select all

 
yourNode->getMaterial(0).setFlag(video::EMF_NORMALIZE_NORMALS, true);
 

or

Code: Select all

 
yourNode->setMaterialFlag(video::EMF_NORMALIZE_NORMALS, true);
 

already tried that without change

http://bedroomcoders.co.uk/tmp/2017-02-07-120835_1280x720_scrot.png I've changed to a loaded obj - notice the shading is at 90 degrees to some of the other objects, and also its not interpolated between vertexes as I'd expect and see with the same model in libgdx I'm now loading the scene node like ...

I can throw the same 3d objects at libgdx and get nice shading so I'll probably just stick with that...

there is only 1 light - additionally touching cylinders that are at different angles, often don't have constant shading

I have created a light like this       scene::ILightSceneNode* l = smgr->addLightSceneNode(0, core::vector3df(100.f,100.f,100.f),                             video::SColorf(1.f, 1.f, 1.f, 1.0f), 600.0f);     l->setLightType(video::ELT_POINT);     smgr->setAmbientLight(video::SColorf(.4f, .4f, .4f, 1...

couldn't resist having a play with trimesh and got it working without too much trouble (need to encapsulate it now), which is nice, just gotta find some nice resources 'cause I suck at making terrains...

thx - please do contact me if you should think of any improvements, I'd like to improve it and provide a more in depth tutorial at some point...

It was news to me that the site was hacked some time ago, and trying to look at some source for an irrlicht / ode example prompted me to throw something together. It's probably not the best example of C++ but it's a simple starting point and I'm more than willing to work with someone to improve it, ...

I had to change #include <irrlicht/irrlicht.h> to #include <irrlicht.h> I made a simple makefile for linux hope someone finds it useful FLAGS=`pkg-config bullet --cflags --libs` \ -L../irrlicht-1.4.2/lib/Linux -lIrrlicht \ -I../irrlicht-1.4.2/include -lGL -lXxf86vm main: main.cpp g++ -o main main.cp...

at any rate the *simplest* example (for example!) is NOT cleanly releasing memory and relying on the OS to do this, hence the post in other examples there are plenty examples of LOST memory which do relate to a leak can you demonstrate loading up a scene releasing it ALL and then repeating a few tho...

Yes but this is the simplest example I could find... I see what you are getting at and I am aware of what you are talking about however the problem is worse with more complex examples try for example texturing 3 or 4 scene nodes with different textures using the same mesh for one... theres also some...

this log is from 01.helloworld, there are 100's more items but I've only included the ones over 1k as the whole log wouldnt fit! ==5527== 1,199 bytes in 2 blocks are still reachable in loss record 62 of 67 ==5527== at 0x040206d5: calloc (vg_replace_malloc.c:279) ==5527== by 0x0400961a: ??? (in /lib/...