>> https://www.shadertoy.com/view/ld2GRz
>>
> I just love it when shadertoy crashes my computer :(

Was it your video driver that crashed? That happened to mine (black 
screen for a second before desktop coming back with the "Windows has 
recovered from video card driver fault" or whatever message. I then 
updated the drivers and it's never crashed like that since.

Post a reply to this message

On 19/07/2015 10:47 AM, Nekar Xenos wrote:
> All voxels seem to be cubes. I came across this though.

Yeah, that's like saying "all pixels tend to be squares"...

(Still, when you resize a picture, you can apply various filtering to 
remove the square edges.)

> I'm still trying to wrap my head around it:
> http://www.geisswerks.com/ryan/BLOBS/blobs.html

Seems straight-forward enough...

Post a reply to this message

scott <sco### [at] scottcom> wrote:
> >> https://www.shadertoy.com/view/ld2GRz
> >>
> > I just love it when shadertoy crashes my computer :(
>
> Was it your video driver that crashed?

Yeah, probably.

> That happened to mine (black
> screen for a second before desktop coming back with the "Windows has
> recovered from video card driver fault" or whatever message. I then
> updated the drivers and it's never crashed like that since.

Always fun. That used to mess up my color settings every time it happened
(before I realized my GPU/driver wanted me to actually use the GLSL functions I
had written and left sitting around in the code).

I was able to update the driver today (wasn't sure I could, since it was
impossible before a recent major OS update). No crash when I tried the link this
time! But there was nothing to see once I got there, either. Of course, this
isn't the best GPU in the world, so it's not surprising :/

Post a reply to this message

>> That happened to mine (black
>> screen for a second before desktop coming back with the "Windows has
>> recovered from video card driver fault" or whatever message. I then
>> updated the drivers and it's never crashed like that since.
>
> Always fun. That used to mess up my color settings every time it happened
> (before I realized my GPU/driver wanted me to actually use the GLSL functions I
> had written and left sitting around in the code).

I find still though if you write a shader that is too long (eg more than 
a second or two run-time) then it won't get an error, just a black 
screen eventually. Windows recovers OK, but other apps sometimes get 
annoyed and stop redrawing their windows properly or just crash. Still, 
it's a million times better than previously, when a video driver crash 
would generate an instant BSOD.

Post a reply to this message

>>> https://www.shadertoy.com/view/ld2GRz
>>>
>>> I don't know exactly what type of data you want to visualise, but you
>>> might be able to edit the script (that one is fairly straightforward
>>> to see how it's moving the blobs) to show your data instead.
>>>
>>
>> IIRC shadertoy is only online.
>
> I'm not sure if you can just save the page and run it locally. It might
> need some tweaks. But in the end shadertoy is just a friendly front-end
> to webGL. The shader code should be copy&pastable into a local webGL page.

Actually, shadertoy only just does a small amount of variable renaming 
(and handles mouse input and textures etc), so if you can do without 
them it's simply a case of copying and pasting the shadertoy code into a 
simple webgl html page, renaming a couple of variables and removing the 
texture lookups. See attached - that should run standalone locally.

Post a reply to this message

Attachments:
Download 'iso-8859-1' (12 KB)

On Wed, 22 Jul 2015 12:43:15 +0200, scott <sco### [at] scottcom> wrote:

>>>> https://www.shadertoy.com/view/ld2GRz
>>>>
>>>> I don't know exactly what type of data you want to visualise, but you
>>>> might be able to edit the script (that one is fairly straightforward
>>>> to see how it's moving the blobs) to show your data instead.
>>>>
>>>
>>> IIRC shadertoy is only online.
>>
>> I'm not sure if you can just save the page and run it locally. It might
>> need some tweaks. But in the end shadertoy is just a friendly front-end
>> to webGL. The shader code should be copy&pastable into a local webGL  
>> page.
>
> Actually, shadertoy only just does a small amount of variable renaming
> (and handles mouse input and textures etc), so if you can do without
> them it's simply a case of copying and pasting the shadertoy code into a
> simple webgl html page, renaming a couple of variables and removing the
> texture lookups. See attached - that should run standalone locally.
>

Thanks! Now I have something to work with.

-- 
-Nekar Xenos-

Post a reply to this message

"Samuel Benge" <stb### [at] hotmailcom> wrote:
> I was able to update the driver today (wasn't sure I could, since it was
> impossible before a recent major OS update). No crash when I tried the link this
> time! But there was nothing to see once I got there, either. Of course, this
> isn't the best GPU in the world, so it's not surprising :/
>
As it turns out, Internet Explorer is my main problem when it comes to running
many WebGL shaders. Just tried Firefox, and it runs that shadertoy blob demo
just fine (albeit at a meager 27 fps on my setup).

Post a reply to this message

On Fri, 24 Jul 2015 21:31:27 +0200, Samuel Benge <stb### [at] hotmailcom>  
wrote:

> "Samuel Benge" <stb### [at] hotmailcom> wrote:
>> I was able to update the driver today (wasn't sure I could, since it was
>> impossible before a recent major OS update). No crash when I tried the  
>> link this
>> time! But there was nothing to see once I got there, either. Of course,  
>> this
>> isn't the best GPU in the world, so it's not surprising :/
>>
> As it turns out, Internet Explorer is my main problem when it comes to  
> running
> many WebGL shaders. Just tried Firefox, and it runs that shadertoy blob  
> demo
> just fine (albeit at a meager 27 fps on my setup).
>
>

IE, i.e. worst Internet browser ever.

-- 
-Nekar Xenos-

Post a reply to this message