Point cache animation gets destroyed
Hi,
I'm a 3d designer based in Eindhoven (Netherlands). I'm assigned with a job to export cloth animations from
Clo3d to 3ds max for rendering in Corona.
Clo3d has a few exporting options for animation: Point cache, mdd cache, alembic, fbx with cache.
Alembic works fine but does not send material id's out of Clo3d so I can't use it.
Point cache with an OBJ works fine at first but as you can see in the movie my trousers are getting smashed.
Here's a link to the movie : https://youtu.be/Kz0A5XHOrpc
I exported the shirt and pants separate so there's a bit clipping but that is not the issue.
The shirt exports just fine without any collapse of geometry, the pants however get destroyed every time.
In Clo3d this is not the case, everything works fine there.
Anybody got an idea what could cause this behavour?
Thanks in advance,
Wilbert
-
Looks like the swizzle orientation (x,y,z) has moved in the sequence. Basically you have to ensure when you export and then import you don't change the max import orientation. So what is happening is the vertex cache data is there in the file but the object (trousers) are now referencing the wrong swizzle (co-ordinate) orientation for the trouser object and their respective vertex ID and vector transitions. The mesh cache vertex data drives the vertex ID vectors but because you screwed up your import swizzle orientation to max it pushes all the vertex ID for each point on the trouser mesh object into what it thinks you want (on it's side). So you need to re-check the swizzle orientation for your shirt (that works) and make sure your trousers are matching.
What I do is run a test object and then produce an export note on my x,y,z swizzle orientation > I then make a preset (max) for import that is saved and I stick to that like mud to the underside of a gumboot. Then if using my pipeline I set a rule up so in future I don't need to manually do it each time.
Check your x,y,z axis on export from CLO3D and then on import to Max again and ensure they are correct. That's the issue.
1 -
Thanks Otto, I will check it out first thing this morning.
0 -
Hi Otto, It has been two years since the last time I posted a reaction to this thread.
Since then the same problem is still a thing. With the ever slightest chance that you are reading this, could you please elaborate a bit more on how you are achieving a correct result.
I tried all different import options with different axis (z or y up), thin or thickness export, you name it. Nothing works at all.
0
Comentários