unicode's picture

@unicode

Compositions

9 months ago
9 months ago
9 months ago
unicode's picture

Sounds like that's exactly what I was hoping for. Thanks! :)

unicode's picture
@unicode posted a new Feature Request, “Ability to pass arbitrary data into ShaderToys

Ability to pass arbitrary data into ShaderToys

unicode's picture

Often, in order to get a ShaderToy to respond to external control parameters as desired, I find myself coming up with encoding schemes in order to pass data into the shader using the "Time" and "Mouse Position" inputs to carry information which have nothing to do with the time or the mouse position.

I suppose I could also come up with ways to encode this data into the input images. :)

But it would be great if the Make Image With Shadertoy node had another input, which takes some kind of arbitrary data, which can be accessed by the shader code.

A Tree object would seem to be perfect and versatile, but tree values are all text and as far as I know GLSL doesn't provide facilities for strings. :( So if providing structured data to shaders is unfeasible, a list of ints or floats or vec3's would be the next greatest thing.

Component: 

unicode's picture
@unicode commented on @mastsk07's Discussion, “Vuo and Mix Emergency

Hi and welcome!

Bad news: as far as I know, there's no way to mechanically export or translate your Vuo projects to Qtz files.

Custom Vuo -> Qtz porting might be offered as a paid development service, though. You could contact support to ask if interested.

unicode's picture

OSX Sierra isn't end-of-life yet, so it should be receiving the same patch/mitigation measures against Spectre and Meltdown that High Sierra gets, no?

Pages