Also problem loading Textures (opengl only)

bassiks · Post by **bassiks** » Wed Feb 23, 2011 8:39 am

Hi!

This is what I'm trying:

ISceneNode* node=m_Smgr->addBillboardSceneNode(0, dimension2d<f32>(10.0f,10.0f));
node->setMaterialTexture(0, m_Driver->getTexture(texture_path.c_str()) );
    node->setMaterialFlag(EMF_LIGHTING, false);

Path and everything is fine. With EDT_SOFTWARE the texture is displayed correctly. With EDT_OPENGL everything is white.

I thought it may be opengl, but then I tried the Movement example with OpenGL and the cube and the sphere have textures. Everything seems to work there.

I compared how they create the device etc. in the example, but found no difference.

Don't know what to try else.

I can not use DirectX because I'm on a linux machine.

Any idea?

greez,
bassiks

Sylence · Post by **Sylence** » Wed Feb 23, 2011 8:46 am

Is the texture size a power of two?
If not, resize your texture to a power of two (128,256,512, etc)

bassiks · Post by **bassiks** » Wed Feb 23, 2011 8:59 am

The texture is 512x256

It is the earth texture from the media directory which comes with irrlicht...

REDDemon · Post by **REDDemon** » Wed Feb 23, 2011 9:18 am

are you sure that also nsquare texture is supported? some computers supports only

pow2xpow2

and not

pow2Axpow2B

bassiks · Post by **bassiks** » Wed Feb 23, 2011 9:46 am

I also tried a 256x256 jpeg. Everything works fine with EDT_SOFTWARE but with EDT_OPENGL everything is white

ErUs · Post by **ErUs** » Thu Feb 24, 2011 11:02 am

Sounds like a lighting issue.

REDDemon · Post by **REDDemon** » Thu Feb 24, 2011 12:19 pm

does irrlicht examples compile and run corretly using OpenGL?

serengeor · Post by **serengeor** » Thu Feb 24, 2011 12:23 pm

Strange, this only happened to me when I was trying out multithreading.

bassiks · Post by **bassiks** » Thu Feb 24, 2011 2:57 pm

yeah irrlicht examples compile and run correctly with opengl...

the point with multithreading sounds interesting...i have the irrlicht engine running in an own posix thread. (the rendering loop with beginSecen etc.)...

I'm loading and setting the material and textures from a different thread while engine is already in rendering loop. the threads are protected by pthread_mutex_lock and unlock...

Is that a problem?

serengeor · Post by **serengeor** » Thu Feb 24, 2011 3:03 pm

I think that it is the problem as I was doing almost the same, tough without mutexes, I used python in my app, python was running in other thread and it had exposed loading functions, so when I was loading from python it went white, I fixed it by running it in the same thread.

bassiks · Post by **bassiks** » Fri Feb 25, 2011 9:28 am

Wow that's the key... Thanks a lot. That was the last I was thinking about. So I think I'll implement a message queue

Thank you very much!

hybrid · Post by **hybrid** » Fri Feb 25, 2011 2:07 pm

You must have everything which does OpenGL calls inside the very same thread. From device creation until releasing it at the end. You can spawn any thread from there, which does not do any graphics related stuff. No problem with that. But putting gl codes into different threads is not possible (besides some complex stuff such a s multiple contexts, or opengl 4, which might allow such things)