XSI Mod Tool UV Problems.

Hey guys, I've been having some problems with XSI. I use Wings 3D to uv map models, then I export them to .obj format for XSI. Usually this works perfectly fine, but the two most recent models I imported had two different problems:

1. One model displays in xsi as having very, very bad texture quality. The problem is not mipmaps, and as far as I can tell its not a problem with the texture, I checked it, and it has perfectly good quality. Is this just a problem in XSI? Will it go away on export to .MESH?

2. The other model loses its UV map on import into XSI. It has a UV map in wings, and from what I can see the data fr the UV map is there in the .obj file itself, but XSI refuses to import it. I have the "Import UV" option checked, yet it just disappears when the model is imported. This one is very, very aggravating. What. The. Hell.

Anyone got any ideas? 

13,802 views 8 replies
Reply #1 Top

1 yes

2 hmm, not sure. Can you upload the obj? are you sure the UV is attached to the model when you export?

Reply #3 Top

tries a couple different ways and no UV, sorry. Never used wings but I bet its some kind of export option.

EDIT: looks looks an easy enough job to UV in XSI though.

Reply #4 Top

That's weird....really weird... I just imported it into wings again and it still has its UV. I didn't do anything different with this model than my other ones, yet they still work. Oh well, guess I'll have to keep working on it.

I have no idea how to UV map in XSI and the interface drives me insane, plus I've already textured it using the UV map it has now.

EDIT: I fixed it. It apparently had something to do with the model being one object. When I split it up into its component objects it imported the uv map just fine... interesting...

Reply #5 Top

+1 Loading…
Reply #6 Top
Now I have a new problem. When entering the pick session to assign the tangents to a second uv set, I click on the 2nd set in the explorer, but it says "CAV is already using the specified data type, there is no need to install an operator." and it applies the tangents to the first set. So I start over, and bam, the same thing happens.
Reply #7 Top

simple model, I can do tangents for that in about 2 mins. Try selecting the model and open the selection and delete all the tangent stuff, Tangents and tangentData, then start over. Or put to DB.

Property name "Sample"? I found it don't like that one. I always rename to whats in documentation,

Texture_Coordinates_AUTO

+1 Loading…
Reply #8 Top

Changing the name to Texture_Coordinates_AUTO worked, strangely. Thanks Myfist, you've been a great help.