DeleD Community Edition

[Paul-Jan]

If you have any questions or remarks regarding the tutorial Adding your own textures to a model, post them in this thread!

[nextdoorscat]

I had a go at it, but got a bit confused, with all the stuff about the layers, though, but I got there in the end!

I couldn't drag the texture to the top left hand side like in the illustration. Maybe where I went wrong was that when I navigated to the textures folder in the directory, I thought it should be in its own subfolder so I created a folder in the texture directory called misc, put my texture in there, and when I opened DeleD and found the texture picker the texture was in the bottom pane in a new misc category, so I dragged it to the top pane, next to the system texture sphere. Then it appeared on it's own little sphere shape. But I still couldn't drag it to a layer.

Still, when I closed out the materials window there was my new texture sitting in its place at the side of the screen, and I was able to assign it to a primitive just like that. It automatically wrapped, I guess it has automatic UV's.

So now I can assign textures.

And I like the eyeball....

[Paul-Jan]

Glad you liked the eyeball

By dragging the texture into the top right pane, you already created the material, so no need to do any dragging onto layers then. Glad that worked for you!

Before you can drag a texture onto a layer, you gotta first make sure you select an existing material (or create a new one). Once a material is selected, available layers for that material will become enabled in the left pane. Once enabled, you can drag textures from the bottom right panel to any layer on the left. Hmmm, that sounds more confusing than it actually is, hope it made sense somehow

Oh, and in DeleD 'auto UV' is an Object property, not a material property. By default it is on for new objects, so yes, the new material will wrap

(and yes, we do plan to do a dedicated material editor tutorial / reference in the future)

[duckstab]

Hi got the engine last week nice bit of kit

Some thing thats giving me problems

When you export to .x and load into another app you discover that it has included references to all textures you have loaded into your material browser even if they were not used

this is creating media that makes further editing of the models in other applications very tiresome.

ie have my 120 favorite textures in the material browser use 2 textures on a cube when this is exported if contains 120 material refernces of which i only need 2

okay cpu are up to speed now but 118 texture references to nothing is a bit of a waist

and take into account that my game normals have 250-300 models to load
that sa maximun of 35700 null calls

thanks for you help in advance

[Paul-Jan]

Hi duckstab,

Thanks for the feedback. You are completely right, that is a bit annoying. This issue has been reported before, and here are the steps we are going to take:

1. The .X exporter will be modified to only export the textures that are actually used (1.5x)
2. DeleD will get functionality to strip unused textures, so you could even do this manually if desired.

In the meanwhile, you might want to try JWatte's nuXporter (Windows XP only) to see if it better meets your .X exporting needs.

Hope that helps!

[duckstab]

thanks for your swift reply will have a look at the link in the mean time ive set a default dml with only system texture.

cheers