Jeff Lait

Yeah, this is a use case we have on our radar but definitely didn't get completed for H21 :<

We have a lot of the pieces but are frustratingly close to being able to answer well.

In an ideal world, you'd just wire into the Preview Material COP and see your multiple UDIMs. But we weren't able to get the viewport to cook the separate UDIMs live.

So currently the "workflow" involves saving out your UDIMs to update. If they are contiguous, this can be done with the ROP Image Output with a single click; but this is not the smooth live update we desire.

In 21 the font cop has a smoothing option to deal with that.

If you look how it is implemented, it is by doing a pair of rasterizations.

We rasterize the geometry to get the jagged on/off. And we rasterize as curves to get the partial coverage. The two can be then combined together.

For the Font COP we do it in a way that is balanced, but this requires you don't have internal lines, ie, only have the outline of the object. Otherwise you can do a one-sided antialiasing on the outside only by only using the curve values less than 0.5.

Hmm... the size_ref input should work the same way as a camera_ref input. In both cases they will override the default layer with the input provided.

The name camera_ref is to hint it is more likely to stem from a camera, while size_ref is more likely to stem from just trying to set a default size. But to the code they are the same.