Broken UV with Alembic export
Sam3DX
Posts: 11
I see a problem with Alembic exporting. Here is a basic Genesis model exported with OBJ and ABC. I opened them in Maya and they are equal and looking proper but if you look deeper... Obj UV mapping is proper and sewed like it must be and Alembic model has a UV map broken to peaces. It's a big problem that cause impossible the further editing (((
What am I doing wrong and how it could be fixed?
UVproblem.png
800 x 600 - 32K
Comments
Something is not right with either. Do you have some weird import into maya option? This is what I get. from Studio to Maya via Alembic.
Oh, I get it. You translated the stuff. Exporting with "Preserve Subdivision Surfaces" may help, but surely Maya has a combine duplicate uv's.
Hm, "preserving the subdivision" while exporting not help at all ((
My UV still exporting broken apart. And seems like Maya don't work correctly with this subD settings - I just lose details in the model. (I made an example picture)
At first I solve the problem by exporting the OBJ and Alembic, and then transfer the UV from OBJ to ALC, but you'r right - I can fix it with merging the UV with small treshold to sew it back. But I'm still sure - someething gone wrong and it should work another way (
I ran in the same issues with broken uv's with exports from daz to cinema4d on osx. I guess the exporter needs some patching.
Well it apparently does not affect everyone, I have occasionally used alembic export to Octane standalone and know others have to C4D regularly and none have complained so it’s probably due to some other factors in the process rather than a fault with the plugin
Where on the mesh is it happening BTW? The fingernail?
that might be something to do with how DAZ chose to do the nail beds in later figures which causes a few issues
In otherwords the mesh itself not the exporter, geografts also are a problem in some other softwares and we won’t get started on the genesis 8 corneas
I believe that most of the users just didn't check the models deep enough to see the problem. I got exactly this problem on different computers, different software versions in completely different cases.
Hi Sam3DX,
I ran into the same problem in Maya 2020/ daz 4.12 Environment.
Has it still not been fixed?
How did you manage it after all?
if you don't mind, could you please let me know?
many thanks!!
It has not been fixed and became even worse, sorry
I roll back to DAZ 4.9 (it's bugged either, but not so much as 4.12)
Have you had a look at the sagan alembic exporter yet?
https://www.daz3d.com/forums/discussion/428856/sagan-a-daz-to-blender-alembic-exporter#latest
Oh, nice! Never heard about it, thanks for bringing it out