irrlicht 1.5 saving absolute paths of textures to irr scene

pera · Post by **pera** » Mon May 11, 2009 8:40 pm

irrlicht 1.5 saving absolute paths of textures to irr scene file like this:
<texture name="Texture1" value="c:\documents and settings\f\my documents\race\le\media\gameobjects\monsters\beast1.png" />

is this known issue?
any fix?

Nox · Post by **Nox** » Mon May 11, 2009 9:49 pm

yes, its a known bug. Fixes:
1. write a little postprocess tool which replaces the paths
2. replace them manually
3. revert the NullDriver to the old version which does not use absolute paths

Acki · Post by **Acki** » Tue May 12, 2009 1:09 am

4. use my IrrExtensions (I made a patch so it saves relative pathes) !!!

pera · Post by **pera** » Tue May 12, 2009 6:48 am

I tried to figure out how NullDriver is getting that path, to make local change, but was lost somewhere around attr->addTexture("Texture1", material->getTexture(0));
Seems like ITexture is holding the full path somewhere.

to Acki: checking IrrExtensions now...
your FAQ page contains only questions... well no one said they are "frequently answered questions".

Nox · Post by **Nox** » Tue May 12, 2009 7:31 am

Take a look at SVN revision 1673. But to be honest, this fix is completly correct. I guess you should check ackis extension or write a own patch, which you can add to the patch tracker. Maybe it will be accepted and integrated.

Acki · Post by **Acki** » Tue May 12, 2009 3:14 pm

pera wrote:your FAQ page contains only questions...

no, just click on a question and you'll get the answer...

mc08 · Post by **mc08** » Tue May 12, 2009 4:49 pm

I can't click them either

FuzzYspo0N · Post by **FuzzYspo0N** » Tue May 12, 2009 6:20 pm

Is this a known issue in irrEDIT or irrlicht? thats totally random that that was not fixe long ago, its really a stupid bug to leave in the engine

Acki · Post by **Acki** » Tue May 12, 2009 6:52 pm

mc08 wrote:I can't click them either

I'll have a look at it, seems something was changed...

Nox · Post by **Nox** » Tue May 12, 2009 6:53 pm

Its not a bug. I makes all texturepaths absolut during the loadprocess. The serialisationsystem just save these paths. Only proper way to "fix" this in the engine is to add a parameter to the save- and loadmethods with a workingpath to refer to.

Acki · Post by **Acki** » Tue May 12, 2009 7:04 pm

Acki wrote:
mc08 wrote:I can't click them either
I'll have a look at it, seems something was changed...

I'm not sure what happened to this page, but now it works again...

thx for the bug report !!!

FuzzYspo0N · Post by **FuzzYspo0N** » Tue May 12, 2009 7:39 pm

ah i see now, thanks nox. absolute paths, not THIS absolute path

pera · Post by **pera** » Wed May 13, 2009 9:47 am

what do you mean its not a bug?

path to model is saved as relative path few lines above, and texture is saved as absolute path.

if i move map to another computer its not going to work for texture,
if I move map to another folder on the same computer its not going to work for model.

its totally scr**d.

I hope you'll revert it to relative paths soon. It worked like that in 1.4.2

Nox · Post by **Nox** » Wed May 13, 2009 5:19 pm

Well. Just think about the following situation:
- 2 images. ./graphics/test.png and ./test.png
- call getTexture("test.png") -> ./test.png will be loaded (if the workingdir was not changed)
-change the workingdir to ./graphics
- call getTexture("test.png") -> the engine looks into it caches, sees that there is already a test.png and return the wrong texture!

So the engine uses absolut paths for textures now. That makes the trouble with the saving.

pera · Post by **pera** » Thu May 14, 2009 10:56 am

can texture have two member fields?

absolutePath
relativePath

one used for saving and the other for cash check?