irr 1.4 beta loading textures 2 times

If you are a new Irrlicht Engine user, and have a newbie-question, this is the forum for you. You may also post general programming questions here.
Post Reply
kimgar
Posts: 37
Joined: Fri Apr 13, 2007 2:53 pm
Location: norway

irr 1.4 beta loading textures 2 times

Post by kimgar »

i just got codeblocks and irrlicht 1.4beta up and running, i got no prior experience with c++ so please bear with me if this sounds stupid...

first, the new X loader is great, large models that could take many minutes to load, now loads in 1 second! but i am curious about how it handles meshes that are exported with textures...

when deliberately removing the texture file i get 3 errors saying:
could not open file of texture: xxx.jpg
with 2 copies of the texture file, one in the same folder as irrlicht.dll and one in the folder with the mesh, there's no errors but it loads twice.

...is there a way to get rid of the errors, or force irrlicht to look only once for the file?
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

It won't load twice, and the output is just a message saying that the first try was unsuccessful. The former loader had also some problems with paths, but it simply did not tell you about it.
kimgar
Posts: 37
Joined: Fri Apr 13, 2007 2:53 pm
Location: norway

Post by kimgar »

yeah, sorry, my bad - i kinda suspected it didn't actually load the file twice, it's just that i'm off to a client tomorrow, and when the command line outputs 20 errors or so, it looks kind of 'unprofessional', not that i am professional by any means, but that output doesn't help, if you know what i mean :)

i'm sure i saw somewhere in codeblocks settings, an option to turn off the whole splash/command line window altogether, but i can't find it again...maybe i'll just keep two copies of the textures as a temporary workaround, hm, or put the .dll in the media fodler...hmm...
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

I guess the best way is to change the warn level in getTexture from ERROR to WARNING (because it's a common and non-fatal problem). Then you can set the loglevel to ERROR which will only show major problems.
kimgar
Posts: 37
Joined: Fri Apr 13, 2007 2:53 pm
Location: norway

Post by kimgar »

ah, that sounds a lot smoother, thanks for the tips hybrid!
Post Reply