Hi folks,
 The Unwrap function is very handy. Unfortunately, it automatically creates and works with .bmp files, rather than Targas. I can find no way to swap to a new texture without losing the stored Unwrap coordinates, and so am forced to export as a .obj and to convert using Shockwave's object converter instead - not terribly satisfactory. Has anyone got any ideas?

(As a workaround, I tried altering the binary .3DC file, replacing the .bmp references with .tga to point to my own .tga textures to see if it really was that simple. This worked fine in 3DCanvas, but no Shockwave file was created when I tried to export. No error was given either. But then, that was a hack, so what did I expect? :-) )

There is a plug-in called "Update Material" that should do the job. This tutorial describes using it: http://www.amabilisplus.com/3DCanvasDocumentation/tutorialmstsmaterials.htm. Just search for "updatematerial".

Richard

Hi Richard,
 Thanks for the relpy, but it doesn't seem to solve my problem. the issue is that a .bmp is created by Unwrap, whereas I need to use a Targa - the Update Material plugin appears to have no way to specify a new/different filename?

To be absolutely clear: unwrapping a model results in (say) texture.bmp. Which is fine - I import that into Photoshop, paint over it, and save out as texture.tga. Now I need 3D Canvas to point at that new file without losing it's wrap coordinates.

Any ideas?

Many thanks,
 Ian

I think you'd first  have to wrap your texture.bmp back on your model and then use the update material plugin.

Yes, the Update Material plugin will change a texture a material uses. Or you can use the Swap Texture File plug-in that comes with the MSTS Plug-in Pack: http://www.amabilis.com/mediadownloads.htm#Scripts

Richard

Swap Textures does exactly what I was looking for... many thanks.

As an aside (not sure of the bug-reporting mechanisms, or if this is one for the plugin author) if the texture or the folder containing the texture contains an apostrophe (') then 3D Canvas hangs.

Easily solved by renaming the folder, but it took me a while (and much cursing) to figure out. Just thought it might save someone else the same pain.

Cheers,
 Ian