1. Create a composition and add a subcomposition
2. Drag into VDMX
3. VDMX Crashes

Joined is a composition with quite many vertices, about 50k, as a line object.
In Vuo 128 it ran at 60 fps on my machine.

In Vuo 2, wether I open the old composition with the deprecated nodes, or update the composition with the new nodes, I get only about 10 fps.

I was wondering if this could have anything to do with how Vuo 2 renders / sorts objects front-to-end, that for fewer vertices it's not noticeable, but with more, the calculation is being seen ?

If yes, could / should the sort option not be an option, depending if you need it or not depending ont the case ?
I don't know if those changes where made on node code levels or on .h files, but an option would be cool.

Or maybe the problem lies somewhere else.

Thanks

Hi,

Has the behaviour of the 3d nodes changed in vuo2? For example 'Spike 3d object' in vuo1 reads the texture correctly and when the effect is applied it spikes the object with the texture applied. But in vuo2 the same composition doesn't 'recognize' the texture the same way and even with the value 0 in 'Spike effect' it doesnt load it. When I take the effect out, it's fine. Is this the way it's meant to work? Or has something been changed? First 2 photos are from vuo1 composition and second 2 from the same composition but ran in vuo2.