uv export problems

Messages
70
uv export problems

hi everyone,

i have a couple of texturing/uvmapping/exporting related questions for you. i have owned a cheetah license since 4.x, but only recently with the (beta) release of ShiVa 1.8 which coincided with the cheetah 5.0 update, i have been able to export to fbx properly, then convert to dae with the autodesk fbx converter and then import it into ShiVa. this process is necessary until cheetah's dae export can handle animations.

1. the point is, the animation export is a dream, but all UV information seems to be lost in this process. so i made some tests.

this is my uv layout in cheetah:

(click for the full size image)

now, i exported it to fbx, 3ds and obj, and with all of them, i get the same result:

the UV layout gets diminished to a small red dot at (0,0).

in case you are wondering, this is a screenshot from carrara7pro, which i use for texture painting and displacement painting/sculpting.

now, in wings3d, the uv map shows up, but out of place.



am i doing something wrong, will there be a fix for that or is that already known and worked on?

2. i love the automatic UV mapper. sadly, "sphere" seems to make a mess at the bottom of the uv layout (long needle-like lines?).

finally, a mapper related questions, that i am are probably asking because i am fairly new to unwrapping in cheetah: why can i choose "uv mapper" AND "unwrap UV" , so that i have black plus orange lines in the uv editing window? this is confusing... though i can get used to it.
 
Hi.
I´m sorry but can´t confirm this. I had a play right now and everything looks like expected. See screenshots.

"UV unwrap" and "UV Mapper" are totally different approaches.
While the unwrapping need seams or work on polygons selection the UV mapper provides 5 different projection methods: cubic, spherical, cylindrical, flat and frontal.


Cheers
Frank
 

Attachments

  • UVexport.jpeg
    UVexport.jpeg
    82.3 KB · Views: 380
hi, sorry for the late reply.
but there IS a problem. maybe not entirely on cheetah's site. this happens when you export a model from Wings as 3ds and import it into cheetah:



so it's likely a wings exporter problem, can anyone confirm this?
 
Back
Top