Shadertoy thumbnails issue
category: code [glöplog]
Today i'm using the free NVIDIA GRID Test Drive:
http://nvda.ly/H4sp4 for Shadertoy and stuff.
Serverside rendering LOL
Work nice :)
http://nvda.ly/H4sp4 for Shadertoy and stuff.
Serverside rendering LOL
Work nice :)
if you have a slow CPU and have problems, you can simply enable thumbnails for shaders. the option is under your profile settings.
(also, make sure you have latest version of Chrome thought, with DX11 enabled. It should be by default.. We are sorry, but the shader compilation is done by the browser and it's not multuthreaded, nothing we can do about it, except for sending emails to Microsoft.
Do not try to use Shadertoy with Firefox, they are still using DX9, nothing will compile)
Do not try to use Shadertoy with Firefox, they are still using DX9, nothing will compile)
Thumbnails should be default.
We can do something about it.
As suggested, the animated previews can be generated when an author saves a shader, and we know for sure that the current machine can handle the shader. I can try to help with that if your web dev is overloaded.
But the main grip is that the default experience, that is for a regular visitor who is not logged in, should be flawless and use sane defaults i.e. don't try to compile 12 -20 shaders on a random machine.
I can count with my fingers the number of times the homepage of shadertoy didn't crash for me :-(
As suggested, the animated previews can be generated when an author saves a shader, and we know for sure that the current machine can handle the shader. I can try to help with that if your web dev is overloaded.
But the main grip is that the default experience, that is for a regular visitor who is not logged in, should be flawless and use sane defaults i.e. don't try to compile 12 -20 shaders on a random machine.
I can count with my fingers the number of times the homepage of shadertoy didn't crash for me :-(
+100 for this for logged off user
because of
this.
Quote:
Thumbnails should be default.
because of
Quote:
I can count with my fingers the number of times the homepage of shadertoy didn't crash for me :-(
this.
Generating 8-16 frames, arranging them in a film stripe and exporting as JPEG is straight forward JS with the Canvas API.
It is ridiculously easy to upload an image on IMGUR and get the various URLs back which can be stored in a extra field on database of ShaderToy. Heck you could even prepend it to the title of the shader.
It is ridiculously easy to upload an image on IMGUR and get the various URLs back which can be stored in a extra field on database of ShaderToy. Heck you could even prepend it to the title of the shader.
"it" = the ID of the image on IMGUR
Nobody is going to adopt webgl until these problems are sorted out. If a shader fails to compile, webgl should still keep working!
Currently nobody will see my cool shader because someone submitted a broken shader right after it and now the "Latest" gallery crashes on the page with my shader.
Currently nobody will see my cool shader because someone submitted a broken shader right after it and now the "Latest" gallery crashes on the page with my shader.
I avoid Shadertoy entirely, because my main home machine is a Macbook Air that can't run the main page at all due to low OpenGL performance. I could run most shaders individually, or pick the ones that I'm interested in, but as it is now, I'm just gonna ignore the entire site.
If you are registered and logged in on Shadertoy, you can set it to load preview images instead now:
Quote:
29/12/2014 - Release 0.5.5 new landing page (faster) and shader preview option at browsing pages.
That's a pretty big "if". Don't extend my password fatigue.
yeah it would fasten things up if that preview thing was a enabled for registered and logged off users by default. site works 90% faster this way.
Previews are awesome... thanks!
Code:
Nobody is going to adopt webgl until these problems are sorted out. If a shader fails to compile, webgl should still keep working!
I can't agree more. The whole browser's DirectX backend crashes when the shader compiler crashes. First, it shouldn't crash (MS fault), it should return an error gracefully. Chrome could workaround that but putting the compiler in another thread, but last time I asked the Chrome team it wasn't in their plans.
Code:
Currently nobody will see my cool shader because someone submitted a broken shader right after it and now the "Latest" gallery crashes on the page with my shader.
I manually disable offensive shaders, about 2 or 3 times a day (it's a constant daily surveillance for two years now). Currently all seems to be fine in all the computers I have tried. What's the shader crashing for you, Dila?
It turns out that my GPU is probably at fault (although Chrome could do better).
Currently I find that https://www.shadertoy.com/view/Xls3RB causes me problems on the first page of results in the "Latest" view.
Also, I posted comments in the shader https://www.shadertoy.com/view/ltsGzB which was also causing me problems, but nobody else had problems with it.
Currently I find that https://www.shadertoy.com/view/Xls3RB causes me problems on the first page of results in the "Latest" view.
Also, I posted comments in the shader https://www.shadertoy.com/view/ltsGzB which was also causing me problems, but nobody else had problems with it.
Wow, doing annoying stuff 2-3 times a day for two years for a non paid project. Kind of of curious if you ask me :)