PDA

View Full Version : LIghtWave 2018 UDIM



samurai_x
01-13-2018, 08:24 PM
Super glad lw 2018 has this. Not much hyped in the product page but this feature is actually used a lot outside of lw.


https://www.youtube.com/watch?v=AA__NsJeHug

Reco
01-14-2018, 04:33 PM
What am I missing here? I know how it works, and know how to do it. But why is a single ten tiled UV a better workflow than ten separate UV’s?


Reco

jwiede
01-14-2018, 08:37 PM
What am I missing here? I know how it works, and know how to do it. But why is a single ten tiled UV a better workflow than ten separate UV’s?

Put briefly, the benefit is the ability to adjust the proportions of the poly-to-texture mappings tile by tile.

When unwrapping to a single tile, you're limited by the need to fit all polys into that single space. It's also best to maintain similar proportions for all mappings in a specific tile, to avoid certain types of texture distortion/scaling issues. Together that practically limits you to a single proportion between UV space and spatial poly coordinates for all polys mapped within a single UV tile.

Using multiple UV tiles enables moving polys which need more detail into entirely separate UV tiles, with potentially greater proportions of the 0..1 UV space (and thus potentially more texture detail for the polys which need it, without impacting the ones that do not). Multiple UV tiles offer multiple UV mapping proportions.

Hope that helps.

samurai_x
01-14-2018, 11:50 PM
What am I missing here? I know how it works, and know how to do it. But why is a single ten tiled UV a better workflow than ten separate UV’s?


Reco

Actually the real benefits of UDIM is lightwave following the standards of other 3d packages.
We always had the ability to create multiple tiles in any material while maximizing the uv space in lightwave. But importing or exporting uvmap info in lightwave has always created issues.
Now with UDIM there won't be issues because its a standard workflow with naming conventions, etc that any app with UDIM support can read. Everything just works. No more overlapping uvs, merged uvs, etc.

BeeVee
01-15-2018, 12:56 AM
Plus many other packages, and especially game engines, are restricted to only one UV map per object.

B

samurai_x
01-15-2018, 01:23 AM
Yep. This is one of the highlights for lw 2018 for me. Always hated getting files from other people and the uvmaps are merged in lw and I have to manually fix stuff in modeler.
And when you send it back that's a whole lot of problem for them, too.

MarcusM
01-15-2018, 01:27 AM
Plus many other packages, and especially game engines, are restricted to only one UV map per object.

B

Unity import UV01 and UV02 from fbx.
https://docs.unity3d.com/Manual/HOWTO-importObject.html

Unreal can use up to 8 UV channels.
https://docs.unrealengine.com/latest/INT/Engine/Rendering/Materials/CustomizedUVs/index.html

In both coordinates 0 - 1.

BeeVee
01-15-2018, 01:43 AM
Okay, maybe I should have said *were* :)

B

hrgiger
01-15-2018, 01:48 AM
What am I missing here? I know how it works, and know how to do it. But why is a single ten tiled UV a better workflow than ten separate UV’s?


Reco

I made the video above. As far as benefits go, for one, its essentially one UV map assignment instead of having to apply textures to 10 different texture channels. In some pipelines its not uncommon to have hundreds of textures associated with objects and with UDIMs, textures as assigned automatically based on the tile number instead of having to assign to individual UV maps. You're also sometimes limited by texture resolution, PTEX for example, and UDIMs will allow for higher resolution. In Substance Painter like I used in the video is limited to one UV map per object so UDIMs allow you to gain more texture resolution in a single UDIM UV.

samurai_x
01-15-2018, 03:26 AM
Keyword there is automatic. Its really great not to have to do this all manually.

Reco
01-15-2018, 11:16 AM
Thank you all for clearing things up.
I understand now. Only one UV for one object is absolute a benefit. Following the standard canít be wrong either, and import all ďchannelĒ images as one file will
simplify my workflow. Iím using 3D Coat, and are not familiar with Substance. Iíll try it for my next project. Hopefully 3D Coat can handle UDIMís as well.


Reco