As I already had similar problem on my laptop: https://vuo.org/node/2209
It might be something similar - something GPU related, but this is happening on my desktop. I have 2 nVidias 1070 Ti.(no Intel iris.) This time no 3d nodes involved, I tried on very simple composition jus to see.It doesnt really affect the funcionality of Vuo though.
After updating to Vuo 2.0 my vuo files do not load in Vdmx. I have replaced the old deprecated 'Render scene to image' nodes to version2.0 as recommended. Cleared the Vuo cache in Vdmx.
As my files contain many 3d object nodes (that were already giving me problems in the past), I made a simplest file just rendering a layer just to see, but still get the same message 'There was a problem loading composition'.
When I try to trigger vuo 1.2.8 files (with old deprecated nodes) Vdmx loads them fine. Only the Vuo 2.0 are affected.
Kinect v1 outputs a depth image, great.
From the node documentation: 'This is a grayscale image in which closer objects are colored darker and farther objects are colored lighter.'
I believe a standard depth image should be the reverse of this, closer objects should be lighter and vice versa.
Have you found a workaround?:
Yes, invert the colours.
All the other Kinect apps around output lighter grey as the closer regions.