Subcompositions cause instant VDMX crash

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

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

Have you found a workaround?: 

Export the Vuo composition as an app and load into VDMX as a Syphon source.

Other notes: 

I've attached a file containing Visiophone's Spherical Coordinates subcomp as this example, but have tested with a number of of my own subcomps too.

Compositions: 

AttachmentSize
Package icon Subcomposition.zip6.94 KB

Crash reports: 

AttachmentSize
File ConsoleLog.rtf114 KB

Monospaced font jitter

micpool's picture

Status: 

Vuo version: 

OS version: 

  • Mac OS X

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

Monospaced fonts are not positionally stable unless text layer anchor is set to one of the three left positions.

Have you found a workaround?: 

No

Compositions: 

AttachmentSize
Binary Data Monospaced Jitter.vuo3.16 KB

Vuo 128 - 203 many objects FPS difference - Front to Back ?

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

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

Crash reports: 

Smooth Vuo Point Light

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

Steps causing the bug to occur: 

Not sure this is a bug, or if it's the wanted behaviour, but in Vuo 128, if one would shine a Point Light onto a sphere with sharpness set to 0, the light spreads smoothly on the sphere.

Starting Vuo 2, even with sharpness set to 0, it's kinda a hard transition. See screenshots & attached files.

If not a bug, how to get smooth lights on a sphere ?

Thank you

Screenshots: 

Compositions: 

AttachmentSize
Package icon Vuo Light.zip818.81 KB

Different behaviour of 3D nodes in vuo 2

kokot's picture

Status: 

Vuo version: 

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

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.

Screenshots: 

Pages

Subscribe to RSS - Accepted