# GLSL Shaders using Processing Pi on a Pi 3 B+

**URL:** <https://discourse.processing.org/t/glsl-shaders-using-processing-pi-on-a-pi-3-b/18614>\
**Category:** Processing for Pi\
**Created:** [March 12, 2020, 3:33am UTC](https://discourse.processing.org/t/glsl-shaders-using-processing-pi-on-a-pi-3-b/18614 "2020-03-12T03:33:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)\
**Post date:** [March 17, 2020, 6:13pm UTC](https://discourse.processing.org/t/glsl-shaders-using-processing-pi-on-a-pi-3-b/18614/2 "2020-03-17T18:13:22Z")

</div>

Hi @jshaw3 – were you able to resolve this issue? I am not a GLSL expert, but the ShaderToy porting guide / example in this thread might be helpful:

> [@Porting GLSL from Shadertoy to Processing](https://discourse.processing.org/t/porting-glsl-from-shadertoy-to-processing/2762):
>
> A few years ago, I wrote an example on how to port GLSL shader code from [Shadertoy.com](http://Shadertoy.com) to Processing. Since then, Shadertoy has changed quite a lot (adding a lot of new uniforms and input methods) so an update was long overdue. You can find it here: [https://github.com/SableRaf/Shadertoy2Processing](https://github.com/SableRaf/Shadertoy2Processing) There is still work to be done, but it should be a good starting point for anyone wanting to learn about shaders from the great material available at Shadertoy, and experiment with it in Processing. …

---

_[View the full topic](https://discourse.processing.org/t/glsl-shaders-using-processing-pi-on-a-pi-3-b/18614)._
