Tomas Slancik

in H22.0.473 diving into SOP Create LOP or SOP Modify LOP still shows the LOP level camera with BG Image for me, even updates when animated

as for cameras imported as SOP level camera primitives, I don't think they support background images yet

here is a version that automatically figures out UDIMs, transforms to image space and outputs them

however, I'm not completely sure if there is something better than using @UDIM context option as I find it extremely unreliable in terms of updating when I switch the default UDIM, but with a bit of nudging it updates

also in this setup final ROP output correctly updated @UDIM per output only when I checked Compiled Cook, and I don't know the implications of that for copnet that is not compliable

Gaalvk
I’m not sure what the purpose of adjacency is then, since we get the same result by simply copying points based on the UV layout. To be honest, the correct way to utilize adjacency still eludes me.

from my understanding adjacency doesn't create seamless representation of 3D space in 2D, if that was easy, then uv's would not have seams to begin with
what adjacency does is it creates information around seams that can sample/transform boundary data across, like a portal, so that the data moving out of a UV island can be transformed to corresponding location on neighboring island, so it's most useful for simulations where things flow through boundaries or for setups where the inside of an island can be extrapolated from information at the boundary