mxgx_Jelly3

mxgx_Jelly3

Image Generator Scene. For use in Host apps such as Coge and VDMX. Has controls for Object Rotation, Random position Speed, Noise Speed, Noise Scale and Color.

Uses Vuo default node set to animate parameters with Curves and Gradient Noise. And lastly a Blend Image with Feedback node.

OBJ License: https://www.videocopilot.net/products/3d/motiondesignpack/

Composition and supporting files: 

Exported App: 

1up_150105_1

1up_150105_1

Vuo Composition created as part of the 1up series. Motion is created with default Vuo node set to offset 3d objects with data. Multiple Vuo shader nodes are also applied.

Uses VJ Satoshi's Particle Emitter Node Set: https://vuo.org/node/537

OBJ License: https://www.videocopilot.net/products/3d/motiondesignpack/ https://www.videocopilot.net/products/element2/#motion-design-2

Composition and supporting files: 

Exported App: 

ElectroEye_04

ElectroEye_04

Image Generator Scene. For use in Host apps such as Coge and VDMX. Has controls for Light strobe and Line width.

Uses Martinus Magneson's Spiro Node Set. https://vuo.org/node/817

OBJ License: http://www.badking.com.au/site/shop/industrial/engines-wingsby-mega-mech...

Composition and supporting files: 

Exported App: 

Fill 2D Shapes From Points

From topic Is there a way to simply fill a polygon with an unlit colour or image? these are some simple compositions attempting to fill flat 3D shapes created from a list of points using Smokris Reinterpret Object node

Any improvement and other shapes welcome.

Composition and supporting files: 

Exported App: 

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: 

Pages

Subscribe to RSS - Shader