DeleD Community Edition

[feejo]

- Material : Texture map file "Violette.jpg" not found, generating dummy texture. message.

Also trying to export direct X.
1. I put the name of the file
2. I put the texture folder E:\download\video game software\texture\
3. Click OK

I receive a message

Cannot open file "E:\download\video game software\texture\SYSTEM\SYSTEM.BMP

[Paul-Jan]

1st question) OK, we are going to need a bit more info there. What file were you trying to load? Are you loading a .map file or importing through a plugin? Does the violette.jpg file exist in the location where you would expect it to be?



2nd question) It seems an ancient version of the plugin got included in the DeleD distribution, we are sorry for the inconvenience!

What version of the .X exporter are you running? It should display this on the right hand side of the plugin logo. If you can't tell because there is nothing there, you are running an old version, and you need to fill in the DeleD Texture folder in that field (i.e. the SOURCE, not the destination).

A much better solution would be to download the latest version (2.2) of the plugin here.

As an alternative, you can try Jon Watte's DirectX exporter from the same page. It uses the DirectX api to export the .X file, so they conform better to the Microsoft standard.

Hope that helps!

[feejo]

1. I try to load a .3ds of a object. violette.jpg is the texture of it. should the .3ds be in the same folder than the .3ds? I guess.

2. Yes 2.2 is way better, got more options.

I notice when I import obj the texture dose not come with it. Got my software from download.com

Is it possible that even on v.2.2 when I export .x the texture dose not get through?

[Paul-Jan]

1) Yes, it's most common to have the textures in the same folder as the .3DS file. It is however possible that the .3DS file refers to a local path (or even an absolute path, usually due to a bug in some application's exporter), in which case the textures need to be in that path. Can't tell without access to that particular .3DS file really.

Note how a more recent version of the .3DS importer is also available from the plugin pages.

If you suspect the plugin doesn't load a certain .3DS file properly, you can always send it to me (paul [at] delgine [dot] com) or put it at some public place to download, and I'll give it a run and see where the importer gets things wrong.

2) The .OBJ importer supports textures through .mtl files. Again, a more recent version of this importer is available from the plugin section. In 2.01 a bug in the texture import mechanisme was released, so that might be the issue you are running into.

3) No, the textures should export just fine (I just doublechecked). If you leave the Texture Folder field empty, the textures will be exported to the same folder as the model. If you put an invalid folder in the Texture Folder edit, the exporter will tell you about it. Do note that the exporter will only export textures that are actually referenced by your model, i.e. that are used on at least one polygon.

4) You mentioned you used our alternative Download.Com download to get access to DeleD. Does this mean you are running 1.71? If so, you might want to consider downloading 1.81 here, for a number of reasons to do so see here, here, here and here. DeleD updates more frequently then Download.com does.