CD PROJEKT®, Cyberpunk®, Cyberpunk 2077® are registered trademarks of CD PROJEKT S.A.
© 2021 CD PROJEKT S.A. All rights reserved. All other copyrights and trademarks are the property of their respective owners.

English (United States)

Help Center

Marvelous Designer Support

  1. Marvelous Designer
  2. Community
  3. Need Help
c96cb56df6c3f4a849b6
Follow

Exporting Alembic From MD to C4D Crashes C4D (Maxon says thickness issue)

Hello,

 

I have been dealing with this terrible issue for three days and I noticed that others have asked to same question with no solution given by the support team. Basically I have an animation from marvelous that I need to export as an alembic. I have tried both File types for Alembic and I have used un-weld + Thin and every combination in between. Also UV coordinates is checked. The animation is set to the entire region. When I import the Alembic it crashes Cinema 4D. I contacted Maxon and sent them my project files and they said that the application is crashing because of a thickness added to the Geo even though I have turned it off in the export settings. I then went into each fabric piece and put the thickness to .01 and made sure that all of the fabrics thickness added at render is 0. What else could I possibly be doing wrong?

My MD project file is here: https://drive.google.com/drive/folders/1GTRRaIKurG734xNLTMExnXvgrWZ-Wg6X?usp=drive_link

  • ● Marvelous Designer Version (ex: 7.1.111) :
  • ● OS Type : Windows 11 
  •  
  • ● CPU : 9-12900K   3.20 GHz
  • ● Graphic Card : 1080ti x 2

 

If you need a staff member to look closer at your issue for technical support. Please contact the Marvelous Designer support team.

  • libor.sykora Comment actions Permalink

    Hey, 

    I'd like to ask if you've figured out this problem, because I'm having the exact same problem right now.

    Thanks for the answer

  • c96cb56df6c3f4a849b6 Comment actions Permalink

    @... Yes I did. I found out that the File I was using from Artstation came from a pirated copy of MD. The best way to get around this is to import it into Blender and then re-export the Alembic from there. That's the only solution I was able to find.

  • ryan_scammell Comment actions Permalink
    I've had a similar issue and may have solved it (or at least did on my end).
     
    Quick background: I have clothing I have made for a character and my workflow is export alembic animation of character from C4D, import animated character into MD, animate cloth in MD, export as alembic from MD, import cloth into C4D.   
     
    Recently I've been having issues consistent issues with importing the clothing from one specific character into C4D.  One of two things happen -- either A) C4D immediately crashes on import of the alembic from Marvelous or B) it imports, but the UDIM style UVs are all messed up and overlapping and scaled incorrectly. 
     
    I think this is maybe an issue of the export on Marvelous's end and here's why. Let's say I take this Marvelous file, export an alembic (let's call it "Export 1"), and import it into Cinema.  This one comes into Cinema ok but the UVs are all wrong.  Then I run the export again with no changes at all to the Marvelous file (call it "Export 2").  This one will crash C4D immediately every time I try to import it.  Subsequently, every time I try to import Export 1 it comes in ok, but the UVs are wrong and in Export 2 it crashes C4D every time. Because these both came from the same project file with no changes to the file or the export settings, that makes me think something is being funky in the exporting process from Marvelous.
     
    Two notes:
    1) This exact same Marvelous project file and garment imported correctly with no issues back in it looks like December 2024. So it could be related to a 2025 update to Marvelous or Cinema.
    2) If on import to C4D, I choose to not import the UVs in my import alembic dialogue box, the geometry will come in fine.
     
    SOLVE:
    With a lot of testing I was able to figure out what was causing the issue.  The Buttons.  When I deleted all the buttons from the project file and re-exported it came in correctly with correct UV map and no crashing.  Again, this exact garment including the buttons at one point exported/imported fine without issues but I'm guessing some update has a change that's affecting something during the export. Anyways, it took a number of hours to solve so I figured I'd share the note in case anyone else comes across it.
     
    • MD VERSION: 2024.2.177
    • OS: Windows 11
    • CPU: 13th Gen Intel(R) Core(TM) i9-13980HX   2.20 GHz
    • GPU: 4090 Laptop

Please sign in to leave a comment.