Status:
Fixed in Vuo version:
Steps causing the bug to occur:
ShaderToy has changed their syntax, so the Make Image with Shadertoy
node needs to be updated (as noted on is there a way to realize a GreenScreen / Chroma Keying and ShaderToy GLSL node re-purpose).
Have you found a workaround?:
Instructions for modifying newer Shadertoy code to work in Vuo 1.2.8 and earlier. Thanks to alexmitchellmus and Kewl.
- Change the
void mainImage( out vec4 fragColor, in vec2 fragCoord )
function tovoid main()
(no text in function brackets) some people do:void main(void)
but it works in Vuo without. - Change
FragColor
(or)fragColor
togl_FragColor
- Change
FragCoord
(or)fragCoord
togl_FragCoord
- Change
iTime
toiGlobalTime
- Change
textureLod
(or)texture
totexture2D
and adjust the input texture accordingly
If you've made all these adjustments and your Shadertoy code still isn't working in Vuo 1.2.8, check Console.app for error messages.
Comments
Can we have it so that the
Can we have it so that the old (current) syntax also is valid ?
So that for example:
So that for example:
gl_FragCoord & fragCoord are both legal.
Can we have it so that the
Yeah, it would be good if we could auto-detect the syntax. Otherwise people would be confused and older compositions would break.
How is this coming along? I
How is this coming along? I've tried using various Fragment Shader from the Shadertoy website (editing them with the workaround), but without success: I always end up with a black screen. Thanks.
The workaroud should include:
The workaround should include:
Change
iTime
toiGlobalTime
Here's a fragment that I can
Here's a fragment that I can't make work, even with the edits:
Any ideas?
The source: https://www.shadertoy.com/view/ltB3zD
@Kewl, remove the precision
Kewl, remove the
precision lowp float
(that's not supported on desktop OpenGL), and changegl_FragCoord
togl_FragCoord.xy
.Sorry, we don't have the new syntax implemented yet, but are still planning to include it in the next major release.
Thanks for the time workaround. Added to the list.
Thanks!
Thanks!
Whats the status of the GLSL
Whats the status of the GLSL changes? Vuo 2.0? Thx Update: [Apparently the Shadertoy node now works with the changes described on the earlier post....kewl]
Another update: Apparently just those changes (modifying fragCoord, fragColor & iTime) dont seem sufficient to make a shadertoy example work in Vuo. Is there a list someplace of all the potentially required changes? Thx
Looking forward to updated
Looking forward to updated syntax support and I agree some more information in the manual on how to adapt ShaderToys to work in Vuo would be great!
Yep, the new Shadertoy syntax
Yep, the new Shadertoy syntax will be supported in Vuo 2.0.
eseftel, could you post the shader that's not working for you?
From https://www.shadertoy
From https://www.shadertoy.com/view/XtS3DD with the required (I hope) changes for Vuo and a .png on Channel0
cloudTen.txt
cloudTen.txt
Aha, it's a similar problem
Aha, it's a similar problem to this one — need to replace
textureLod
withtexture2D
. I'll add that to the workaround steps above.Great thanks.that worked.
Great thanks.that worked.
What about these? Don't have a textureLod..from https://www.shadertoy.com/view/MsBXWy & https://www.shadertoy.com/view/WlXGWl
afterRain.txt
magicWhale.txt
How does the Cloud Ten
How does the Cloud Ten example show up on your computer eseftel ?
No small noise clouds for me, more like smooth big clouds.
Magic Whale one I don't know either,
For the After Rain, I don't understand anything about GLSL but changing "texture" to "texture2D" at least I don't get a black screen, but still a bit different (like sliced in the z-axis, due to texture -> texture2D ? I don't know ;).
afterRain 1.1.txt
Capture d’écran 2019-05-19 à 03.27.28.png
Bodysoulspirit CloudTen shows
Bodysoulspirit CloudTen shows up sort of ok, at least a starting point.
I don't know much about GLSL myself (hence the reason I want to study and mess with these comps in Vuo) but changing texture to textture2D in the after rain comp caused Vuo to crash. repeatedly :-(
cloudten.png
Sorry it crashed or you.
Sorry it crashed or you. Maybe upload the crash report so the team can look at it.
Ok so CloudTen look the same for me. Maybe because textureLod -> texture2D ain't the same parameter, and we need to make adjustments.
Hope the upcoming updated syntax will allow Shadertoys to look exactly the same in Vuo.
eseftel — For After Rain,
eseftel — For After Rain, you do need to change
texture
totexture2D
. (You can post the crash report if you want, but I doubt we'll fix this since the issue will be moot soon.) For Magic Whale, changegl_FragCoord/iResolution.xy
togl_FragCoord.xy/iResolution.xy
.Bodysoulspirit — Whatever the Shadertoy site shows in the iChannel slots, you have to put those images/videos/etc. into your Vuo composition for it to behave the same as on the site. You can download a package of Shadertoy input files here.
AfterRain.vuo
MagicWhale.vuo
Jaymie aaah, I had the images
Jaymie aaah, I had the images, but from your composition I realized I was missing the repeat wrap mode for "After Rain" to look exactly the same.
Thank you.
eseftel until the syntax update, if you don't want to check for every word to replace, use joined compositions as work bases, it's a cascade of
Replace Text
nodes that does the job for you (blue nodes). With the composition launched, you can remove the blue nodes & the updated code is saved to the Shadertoy node (it does not always work though, missing some ray marching syntax updates maybe).PS : you still need to drag and drop your image onto the "Fetch Image" node to update the URL path (if images).
Capture d’écran 2019-05-22 à 01.00.49.png
#BASE 1.2.vuo
#BASE + Buffer 1.2.vuo
Thanks very much guys -
Thanks very much guys - appreciate the help.
Hello all,
Hello all, Thanks for the replace text composition Bodysoulspirit
I'm playing with this Bokeh code: https://www.shadertoy.com/view/Md3cWs It works but only blurs/smears in one direction rather than creating the hexagonal bokeh (smearing in three directions I assume). Any ideas what's wrong with that?
Resolved in Vuo 2.0 beta.
Resolved in Vuo 2.0 beta.