Open totetmatt opened 4 years ago
Hi, thanks for your interest and sorry for the delay!
I already had this bug a couple of times on a browser. It only occurs on some shaders, and it's hard to tell how they are any different. Maybe some newest features that the GPU doesn't support? Well the fact that it occured on a browser suggest that the app can't do much about it. Under the hood, the app is just loading the website with an additional UI, in a Chrome-based environment.
Can you please check that the shader is loading fine in Chrome, and if so, that the app uses the same GPU as Chrome?
Hi, thank you for developing this tool, which appears very convenient. The issue is reproduced on my system (Windows 10 with Intel Core i5 CPU and two GPUs, Intel UHD Graphics 630 and NVIDIA GTX1050) on all shaders.
The shaders run fine in Firefox and in Chrome, whether using the integrated or the NVIDIA graphics card. They always fail to load in the Shadertoy Exporter app as described above. I've tried the following combinations:
It also seems to make no difference whether the shader is old or recent: the issue is also present when trying to load the oldest public shader.
Screenshot:
Hello,
I noticed recently that when using shadertoy-exporter, if doing a new shader or going to an existing one, the website is loaded but the webgl cavenas doesn't run and the code part is empty. It's making export impossible.
Noticed this on Windows and Ubuntu (18 and 20)
Thanks