jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture

We'd like to provide a way to convert between 3D objects and layers easily. For example, this would be useful to overlay text instructions on a 3D scene. I've opened this feature request for voting.

The Parabox nodes are a starting point. But, to avoid unexpected/buggy behavior in some cases, we'll need to go further. The Parabox nodes take advantage of the fact that you can easily turn a layer into a 3D object and vice versa, superficially. We'll need to do a deeper conversion. Layers and 3D objects have different assumptions. (Layer shaders assume they're always going to be rendered in a certain order, on a quad, facing the camera, without depth testing. Scene objects can be rendered in any order, using any mesh, with whatever transformation, with depth testing.) We'll need to convert from one set of assumptions to the other.

having scene based compositions not having to select different Z-axis to blend nicely

Is that covered by Improve rendering of transparent objects (OIT, Depth Peeling)?

jstrecker's picture

No, the change involving symlinks didn't affect the (in)ability to load modules from subfolders.

jstrecker's picture
@jstrecker commented on @marioepsley's Discussion, “Upgrading your OS

The only Mojave-specific issue we know of is that the first time you drag a node from the node library to the canvas, it pops up an accessibility confirmation dialog. All other known issues were fixed in Vuo 1.2.8.

jstrecker's picture

Needs a tweak to the boolean name to display correctly in Resolume but running well enough. (Or is there a better way to switch between the two styles?).

FFGL limits parameter names to 16 chars, so you'd have to pick a shorter name. Or split it into two plugins, one for linear and one for radial.

Also noticed that the position sliders numbers do not display minus number positions, they are displayed as 0-1 in Resolume.

Vuo converts the 0-1 range displayed in Resolume back to the original range in your composition. For example, if your published input port has range -10 to 10, it will display in Resolume as 0-1, but the numbers fed into your composition will range from -10 to 10. An 0.25 in Resolume will become a -5 in your composition.

The reason for doing it that way is a limitation of Resolume (and other FFGL hosts we've looked at). Although the FFGL spec describes a way to override the default 0-1 range, Resolume doesn't support it.