UDIM support updated?

Comments

11 comments

  • Avatar
    Erik Kubiňan CR

    Hello dear user,
    UDIM directly is not supported, but you can have and use multiple textures for one UV space in RC. Overlaps should not be present and by adjusting Gutter (UV islands spacing) parameter in Unwrap settings you can prevent this easily if so.

    0
    Comment actions Permalink
  • Avatar
    Vlad Kuzmin

    imagingcombine, RealityCapture have UDIM support already for couple years. At least, Houdini, Blender, 3D-Coat, zBrush understand RC multi textures as UDIMs without issues.

    And you can import multi UDIM cleaned mesh to RealityCapture from modern DCC hosts like Blender, Houdini, etc., without any issues.

    Erik Kubiňan, we using UDIMs in RC in our studio scans :)

    0
    Comment actions Permalink
  • Avatar
    Erik Kubiňan CR

    Well, it is good that you have found such workaround but until it is not directly UDIM unwrap, I cannot call it so. If we have had a regular UDIM support you would have multiple Unwrap spaces side to side. What we do is a classic 0-1 Unwrap space where more textures can fit in, but not more than one space will be used to fit the islands in. Anyways good point if above stated works.

    0
    Comment actions Permalink
  • Avatar
    Jesse Rapczak

    Is proper UDIM support coming soon? It would be nice to load an Alembic file directly from Reality Capture without having to process the UVs before the textures map correctly. 

    0
    Comment actions Permalink
  • Avatar
    Vlad Kuzmin

    Jesse, can you tell me what exactly not working for you if you using this settings?

    0
    Comment actions Permalink
  • Avatar
    Jesse Rapczak

    When using the UDIM tile type from the UI, the textures are generated correctly but the UVs are all stacked on top of each other instead of being offset per tile. When importing the Alembic file into Maya, 3DSMAX, or Houdini, the UVs must be manually processed and laid out. Attached is a comparison of the before (all UVs in 0-1 range) and after (UVs in 1001-1030 range). 

    I would also like to add that it does not appear vertex colors export correctly with Alembic. I had to use .ply export in order to get vertex colors in Maya and Houdini.

    0
    Comment actions Permalink
  • Avatar
    Vlad Kuzmin

    This is looks more like Alembic export issue.

    Any reason to use Alembic instead of OBJ that support all you mentioned?

    0
    Comment actions Permalink
  • Avatar
    Jesse Rapczak

    Yes. Alembic caches load very quickly and take very little memory. OBJ files are huge, slow, take up a lot of memory, and are not optimized for viewport display or rendering. 

    0
    Comment actions Permalink
  • Avatar
    Jesse Rapczak

    I verified that OBJ UDIM tiles export works as expected. UDIM export does not work properly for Alembic or FBX (maybe other file formats). It would be great if UDIM tiles worked properly for all formats so we aren't forced to use .OBJ. 

    0
    Comment actions Permalink
  • Avatar
    Vlad Kuzmin

    Thank you!

    Alembic support was added not far ago, and not so many RC users using it. So i guess developers missed possible bugs in implementation.

    But FBX always a pain for every apps that not an Autodesk. 

    Definitely need to fix this issues. Asap.

     

    0
    Comment actions Permalink
  • Avatar
    Erik Kubiňan CR

    Reported this issue further. Thank you for your description.

    0
    Comment actions Permalink

Please sign in to leave a comment.