DeleD Community Edition

[Coty]

My maps are in a separate folder than the textures. My path is relative to the folder the object is in.

../Tex/textureName.dds is not recognized by DeleD as a valid texture path.


I wish DeleD had a 'tag' slot I could add to my relative texture paths when exporting objects, or at least recognize '../Tex/' in front of my texture's name when importing objects.

Thanks

[Paul-Jan]

I'm a bit confused here. I don't fully understand your problem, thus making it difficult to judge the proposed solution.

Here are some dry facts:

1. Inside DeleD, texture paths are always relative to the texture base path.
2. When importing, the importer takes your texture files and copies them into the appropriate subfolder of the texture path.
3. When exporting, the exporter will copy the texture to the specified path. Most exporters will accept a relative path to the exported model here.

Your problem is related to some combination of importing and exporting, or probably a disagreement with the way we handle (1), but I just don't quite understand it. Could you please elaborate? If importers and exporters are involved, could you specifiy which ones? Thanks!

p.s. Is this request related to your post in this thread?

[Coty]

Thanks,

Beyond Virtual imports obj files (prefabs) and moves them around in their own world editor, which is really a text file pointing to the prefabs. I have hundreds of objects (prefabs) in one folder, like 'Arena.' All of the textures point to ../Tex/textureName.dds in the mtl file. So that's a folder called Anubis with 100 obj files, 100 mtl files, and 100 opr (object properties) files. All my textures for all my prefabs folders are in a ../Tex/ folder.

DeleD doesn't find the textures with the tag ../Tex/ in front of my filename in the mtl file of an obj file, if that makes sense. This is really not a problem with me, because I can change the texture filenames of the .mtl files with a text editor, like I've been doing. I don't need to import a completed obj file into DeleD anyway. I just thought it would be nice to be able to read that tag when importing, or add that tag to a filename when exporting. I realize this is probably an import/export plug-in thing now, and I don't won't to bother you with it.



Don't get me wrong. I love this world editor. It is well worth the money I paid for it. It is the best editor for non BSP world editing for that price on planet Earth.

[Paul-Jan]

Ah, thank you for explaining that! Seems like your problem would be solved by proper relative path support in both the OBJ importer and OBJ exporter. Both are maintained by us, so by all means, do bother us with this!

I've put it on the todo-list for the .OBJ importer/exporter, and will get to it soonish.

[Coty]

Thanks Man!