support for texture arrays, MRT, integer textures, image load/store?

[bernief1]

hi, i just came across your project - nice!
i'm currently working on something similar to help me with my lightmapping / path tracing research. i'd be interested in collaborating. here's the list of features beyond what ShaderToy supports that i'm currently supporting:

texture arrays
volume textures
multiple rendertargets
up to 32 texture inputs per pass
arbitrary texture resolutions
all GPU-supported texture formats
image load/store (and atomics)
arbitrary number of passes
slider widgets defined in metadata and rendered as an overlay
all declarations in metadata in the shader code .. e.g. to create a 1024x1024 buffer you just write "//$BUFFER:mybuffer,w=1024,h=1024" in the shader code, and then you can sample it with "texture(mybuffer,...)" etc.

send me an email if you are interested in sharing ideas or unifying our syntax!
bernie.freidin@gmail.com

[stevensona]

@bernief1 Is your project public and/or open-source?

[bernief1]

I threw it on github (I don't normally use github so forgive me if there are any issues). You will need two repositories to compile: https://github.com/bernief1/common https://github.com/bernief1/shader_toy_player And you will need to copy the following dll to somewhere in your path (e.g. C:\Windows) *common\GraphicsTools\external\glut\freeglut\bin\x64\freeglut.dll* Then, assuming you have visual studio 2017, you should be able to compile the .sln. For commandline args, just pass it the path of the directory containing the .glsl files you want to run, e.g. "shaders\Underwater_Fractal_Creature" Let me know if this works! B

…

On Fri, Jun 28, 2019 at 7:05 AM Adam Stevenson ***@***.***> wrote: @bernief1 <https://github.com/bernief1> Is your project public and/or open-source? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYJZPJS72YPW76F4FIDP4YLBNA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2FLXQ#issuecomment-506746334>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYKNPGZ2D44RRWIK4PDP4YLBNANCNFSM4H37X7IA> .

[Malacath-92]

You're missing some libraries in your repo, so I can't actually build it without searching for the right versions myself.

Regardless of that, it sounds like you have a set of really nice features. However I don't see how the projects can benefit from each other. The fact alone that one project is written in TypeScript/HTML and the other is written in C++ makes most efforts to port features very non-trivial. On top of that one works based on WebGL, the other on the full OpenGL feature set.

I don't say this to be discouraging or mean, I just honestly think that the two projects live in very different domains, where they each are completely valid and valuable solutions.

When you speak of unifying syntax, of course this is a different question and could bring value to users who might not always be able to use one or the other solution. Thus having a standalone desktop version of shader-toy that obeys the same syntax as the VSC integrated version (and partially the online version) could help a lot. On a side note though, we have many active users on this extension, thus radically changing our syntax would be dangerous.

For now, if you are interested in growing your project and making it inviting to contributors, I would suggest you to clean up the repo a bit, introduce a build-system, make the code portable (if it isn't already), eventually introduce CI and testing. I'd be happy to spend some time to help you with that, because I think having a desktop version of shadertoy is an amazing prospect.

Edit: I hope I didn't come across as negative, I've been told it happens. Instead I am really positive about this project 😄

[bernief1]

Sure, I'd be interested in help cleaning up the repo so that it's more usable. I have little experience sharing code outside of the game projects I've worked on. First off - which libraries am I missing? Besides OpenGL, the project depends on FreeImage, GLUT (freeglut), and GLEW. All of these should be in the *common\GraphicsTools\external\ *directory (which should be parallel to the *shader_toy\* directory). The settings in the vcxproj specify additional include and library directory "..\common\;" so the #includes and #pragma comment(lib,..)'s can find the appropriate files. As I mentioned, you need to copy the freeglut dll from *common\GraphicsTools\external\glut\freeglut\bin\x64\freeglut.dll* to somewhere in your PATH such as C:\Windows - or I suppose you could copy it to *shader_toy\* directly .. in my local setup I have a common directory and then many separate projects which use freeglut so I didn't want to have to duplicate the dll all over the place.

…

On Sat, Jun 29, 2019 at 4:47 AM Malacath-92 ***@***.***> wrote: You're missing some libraries in your repo, so I can't actually build it without searching for the right versions myself. Regardless of that, it sounds like you have a set of really nice features. However I don't see how the projects can benefit from each other. The fact alone that one project is written in TypeScript/HTML and the other is written in C++ makes most efforts to port features very non-trivial. On top of that one works based on WebGL, the other on the full OpenGL feature set. I don't say this to be discouraging or mean, I just honestly think that the two projects live in very different domains, where they each are completely valid and valuable solutions. When you speak of unifying syntax, of course this is a different question and could bring value to users who might not always be able to use one or the other solution. Thus having a standalone desktop version of shader-toy that obeys the same syntax as the VSC integrated version (and partially the online version) could help a lot. On a side note though, we have many active users on this extension, thus radically changing our syntax would be dangerous. For now, if you are interested in growing your project and making it inviting to contributors, I would suggest you to clean up the repo a bit, introduce a build-system, make the code portable (if it isn't already), eventually introduce CI and testing. I'd be happy to spend some time to help you with that, because I think having a desktop version of shadertoy is an amazing prospect. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYITANSIWEGGIGAPI7DP45DTZA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY3XMHA#issuecomment-506951196>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYIPTOBGHBNZZUY5AUTP45DTZANCNFSM4H37X7IA> .

[bernief1]

Just to clarify .. the files should be located as follows (this is a subset of the actual file list for illustration only): (C:\dev\projects\ is where I have my projects but of course this can be anything - all file paths are relative) C:\dev\projects\common\common\common.h C:\dev\projects\common\GraphicsTools\external\FreeImage\FreeImage.h C:\dev\projects\common\GraphicsTools\external\FreeImage\x64 C:\dev\projects\common\GraphicsTools\external\FreeImage\x64\FreeImage2015Lib.lib C:\dev\projects\common\GraphicsTools\external\FreeImage\x64\FreeImage2015Libd.lib C:\dev\projects\common\GraphicsTools\util\camera.cpp C:\dev\projects\common\GraphicsTools\util\camera.h C:\dev\projects\common\GraphicsTools\util\color.h C:\dev\projects\common\GraphicsTools\util\crc.cpp C:\dev\projects\common\GraphicsTools\util\crc.h C:\dev\projects\common\vmath\vmath.cpp C:\dev\projects\common\vmath\vmath.h C:\dev\projects\common\vmath\vmath_box.cpp C:\dev\projects\common\vmath\vmath_box.h C:\dev\projects\shadertoy_player\shadertoy_player.cpp C:\dev\projects\shadertoy_player\shadertoy_player.sln C:\dev\projects\shadertoy_player\shadertoy_player.vcxproj C:\dev\projects\shadertoy_player\shadertoy_player.vcxproj.filters On Mon, Jul 1, 2019 at 10:00 AM Bernie Freidin <bernie.freidin@gmail.com> wrote:

…

Sure, I'd be interested in help cleaning up the repo so that it's more usable. I have little experience sharing code outside of the game projects I've worked on. First off - which libraries am I missing? Besides OpenGL, the project depends on FreeImage, GLUT (freeglut), and GLEW. All of these should be in the *common\GraphicsTools\external\ *directory (which should be parallel to the *shader_toy\* directory). The settings in the vcxproj specify additional include and library directory "..\common\;" so the #includes and #pragma comment(lib,..)'s can find the appropriate files. As I mentioned, you need to copy the freeglut dll from *common\GraphicsTools\external\glut\freeglut\bin\x64\freeglut.dll* to somewhere in your PATH such as C:\Windows - or I suppose you could copy it to *shader_toy\* directly .. in my local setup I have a common directory and then many separate projects which use freeglut so I didn't want to have to duplicate the dll all over the place. On Sat, Jun 29, 2019 at 4:47 AM Malacath-92 ***@***.***> wrote: > You're missing some libraries in your repo, so I can't actually build it > without searching for the right versions myself. > > Regardless of that, it sounds like you have a set of really nice > features. However I don't see how the projects can benefit from each other. > The fact alone that one project is written in TypeScript/HTML and the other > is written in C++ makes most efforts to port features very non-trivial. On > top of that one works based on WebGL, the other on the full OpenGL feature > set. > > I don't say this to be discouraging or mean, I just honestly think that > the two projects live in very different domains, where they each are > completely valid and valuable solutions. > > When you speak of unifying syntax, of course this is a different question > and could bring value to users who might not always be able to use one or > the other solution. Thus having a standalone desktop version of shader-toy > that obeys the same syntax as the VSC integrated version (and partially the > online version) could help a lot. On a side note though, we have many > active users on this extension, thus radically changing our syntax would be > dangerous. > > For now, if you are interested in growing your project and making it > inviting to contributors, I would suggest you to clean up the repo a bit, > introduce a build-system, make the code portable (if it isn't already), > eventually introduce CI and testing. I'd be happy to spend some time to > help you with that, because I think having a desktop version of shadertoy > is an amazing prospect. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#62?email_source=notifications&email_token=AIAYGYITANSIWEGGIGAPI7DP45DTZA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY3XMHA#issuecomment-506951196>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AIAYGYIPTOBGHBNZZUY5AUTP45DTZANCNFSM4H37X7IA> > . >

[Malacath-92]

In particular I fail linking against the static libraries for FreeImage 'GraphicsTools/external/FreeImage/x64/FreeImage2017Lib.lib'

Edit: I'm sorry I'm slow in responding. I just changed job and everything is a bit stressful.

[bernief1]

You fail because the file doesn't exist in the correct location? It's in my repo - https://github.com/bernief1/common Did you check that the file locations are correct? In the last email I sent, I gave a bunch of file location examples. I apologize for any difficulties getting my repro to compile - I'm not used to sharing my code. I promise you that all the libraries are there in the two repos. Can you send me your error, and also run a *dir /S /B* from the parent directory that you put shader_toy in so I can see all the files are there?

…

On Tue, Jul 2, 2019 at 11:35 AM Malacath-92 ***@***.***> wrote: In particular I fail linking against the static libraries for FreeImage 'GraphicsTools/external/FreeImage/x64/FreeImage2017Lib.lib' — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYOWHEX5DVPVBVYVIUDP5ONXHA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCFVUA#issuecomment-507796176>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYPXN4WXGMQNPWQ6B3DP5ONXHANCNFSM4H37X7IA> .

[Malacath-92]

No, there is no static library for FreeImage in your repo. It should be in this folder

Edit: I also think we should continue this conversation on your repo instead of here.

[bernief1]

Ah - my mistake! I'm sorry I'm not used to github. When I try to copy the files over it complains that they are over 25MB. I've zipped up both the shader_toy and common directories and uploaded them to cloud storage here: https://www.amazon.com/clouddrive/share/jBVV3yA1PlkWSTNGvkeneBJfSbcniLz48j0oQR5vwqS

…

On Tue, Jul 2, 2019 at 10:55 PM Malacath-92 ***@***.***> wrote: No, there is no static library for FreeImage in your repo. It should be in this <https://github.com/bernief1/common/tree/master/GraphicsTools/external/FreeImage> folder — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYPVUJCKGDP4FA5D4YDP5Q5NPA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDLEQQ#issuecomment-507949634>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYLM4N2WMOW6VPABW2TP5Q5NPANCNFSM4H37X7IA> .

[Malacath-92]

Closing this since the conversation doesn't belong here, as mentioned previously.
@bernief1 I'm sorry this slipped my mind. If you are still interested in making your repo more open-source friendly just get in touch, I should have some time to help you.