That still doesn't explain WHY I'm getting the same exact incorrect UV mapping results after creating my mesh/UVs with any other programs....
Can't blame it on Wings3D if I get the same erroneous results in 3D Rad when I didn't use Wings3D at any time in the process...
Hmmm
Thank you for reporting this issue DeveloperX !
Does it happen in any other modeler you use even if you create a new model from scratch?
What other application have you tried? Other users here have different modelers but aren't experiencing UV issues apparently.
Please note that UV information isn't 'interpreted' by 3drad (or DirectX) in any way. UV information is encoded within the .x file and used as is by 3D Rad, so the problem is very likely in the procedure you are using to generate the .x file.
As I said earlier, I've tried:
1. Using fragMOTION to create a new UV map for the mesh.
2. Using fragMOTION to create a new mesh with new UVs.
3. Using UV Mapper to create new UVs.
4. Using 3D Canvas to create a new mesh and UVs.
5. Using gmax to create a new mesh and fragMOTION to create new UVs.
So using fragMOTION, gmax, and Wings3D to create the .x file all result in an incorrectly mapped object once it is loaded into 3D Rad.
Don't know why this is happening to me. When I get home from work tonight, I'll try a different computer and see if I obtain the same results..