You discovered a bug in the engine, and you are sure that it is not a problem of your code? Just post it in here. Please read the bug posting guidelines first.
Hi all,
i've just tried to run the examples of irrlicht 1.2 and i've was surprised to see that they don't run. The error is : "couldn't create direct x driver" or something like that. This error occurs with both directx and opengl doesn't display textures. But i don't understand because the examples of irrlicht 1.1 run without any problems. The code is exatly the same in the two examples (1.1 and 1.2 versions). Why does this error occurs only in irrlicht 1.2 ?
tkanks
KIC : frateamkic.info
(i'm frensh so scuse me for my english ...)
Probably due to problems with the screen init. If you only have 16bit screens there could be a problem with proper initialisation. We fixed that somewhat after the last release. Try to change your screen depth or run fullscreen.
i gues you are using gcc compiler. i had same problem directx is not supported for gcc compilers yet but i saw some threads on this forum how to compile your own dll for gcc with d8 - d9 support. try to search
He said it happens with opengl as well, and the error message would be "driver not compiled in". So it's a problem with the win32 screen init. You should try Irrlicht SVN in that case (most revisions after 400 should probably do), or wait for the next release.
yes i've exactly this error, unable to use any directx and opengl doesn't display textures . And it occurs even if i use the compiled bins wich are included in the zip of the 1.2 release. i think there is something different that make irrlicht hate my graphic card =( .Well i'm trying to download the svn ...
Wait and see.
KIC : frateamkic.info
(i'm frensh so scuse me for my english ...)
Yes, it's a problem with some kind of graphics cards. I can only speak for the OpenGL part, but all necessary features to display at least some textures are available on those systems. So it's something more sophisticated. Maybe it's also a problem with mipmapping. Is there any change if you are rather near to the untextured object, or very far away?
I'll move this thread to bug forum as well.