3Ds MAX UV 2k9 problem or ... ?

TSM

I find this to be a bit confusing. I've also found if I export this and slap it into the C4 engine, that all the UVs are flipped. Also, if I have the faces selected and I push 'F2' (wireframe selection), the mess shows up again.

I've tried to make a new scene and merge this into it - no luck, collasped the UV unwrap onto editable poly, then added the modifier again, no luck. (Yes, I've restarted Max too).

Ideas?

kio

this bug is somewhat older - had that a lot in max9

try reset x form or add an edit mesh modifier on top. try searching the forums ive seen a thread about this a while ago.

TSM

Thanks kio!

Changing to editable mesh did the trick! Bringing it back to editable poly brought back the soup - very odd.

I reset Xforms in the Hierarchy tab under Adjust Transform yes?

Does this mean I should just export this guy in Edit mesh?

Michael Knubben

You reset xform under the last tab (err, tools? I have somewhat of a graphic memory. I can place it, but not name it ), the button's labelled 'reset xform'. Maybe what you did does the same though, I don't know.

TSM

K, new knowledge every day.

I reset it, and the texture looks fine then, however, if I move the viewport closer (not further way) then the soup returns. Does it affect my export?

Andrew_Morris

We've had a very similar problem on our game whenever we exported something with the .fbx exporter. It would mess up the display of uvs in the viewport on all the objects in the scene (but not actually screwing up the uvs, in engine the objects looked fine). The only fix we found was to apply an edit poly modifier to all the objects and collapse the stack. The problem went away after that.

TSM

Interesting, in C4, the UV's are flipped, or rather, turned 90D (since the wood is facing the wrong direction everywhere).

I'm using the .DAE exporter that came with Max 2k9 ( I did do the web update, no effect ) - is there another good .dae exporter lying around?

Eric Chadwick

IIRC this problem has to do with some options in the D3D display driver, might have been fixed by disabling "Use Cached D3DXMeshes".

TSM

Yup! That fixed it. Thanks everyone!