Hello,
I’m wondering if importing and exporting UDIM texture is now available in RC.
I’ve read some in community, but those were few years passed.
In the articles, some says there is a overlapping problem when exporting texture from RC.
If any updates, please let me know.
Thanks!
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.
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 
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.
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.
Jesse, can you tell me what exactly not working for you if you using this settings?
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.
This is looks more like Alembic export issue.
Any reason to use Alembic instead of OBJ that support all you mentioned?
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.
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.
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.
Reported this issue further. Thank you for your description.
Any update on this? I’m trying to use blender to delete the hundreds of materials RC makes, delete them and replace with a single material and apply the UDIM textures to that and then export to substance painter. Today, that didn’t work suddenly. Im not able to paint across tiles in Substance Painter, been using RC for 5 years now and I cant believe you have not fixed this yet…
Yes, made a Houdini UDIM UV maker to find out in the end RealityCapture cant bring back in a new model with uv that are properly setup UDIM. Only Stacked uv in a single layout but split my materials. Wish it was not like this and could import a proper UDIM layout.