| epsilon+=3 waved2 | ||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 53% |
|||||||
alltime top: #28411 |
|
|||||||
|
||||||||
added on the 2016-04-14 03:04:19 by ollj  |
||||||||
popularity helper
comments
I can tell you one mistake you made, this isn't Windows; it's WebGL.
Apart from that, no music, visuals are pretty boring and quite slow. Should save up some of your code and release in a proper prod, or push this out through another medium. A basic test does not a good prod make :)
Apart from that, no music, visuals are pretty boring and quite slow. Should save up some of your code and release in a proper prod, or push this out through another medium. A basic test does not a good prod make :)
this 'belongs' on shadertoy, or in the raymarching thread or make a 1k executable
motivational thumbs.
Another motivational thumb. Always good to see someone new master the art of raymarching!
Now go get a musician and start using it for something that actually has some aesthetic value. :)
Now go get a musician and start using it for something that actually has some aesthetic value. :)
what urs said =)
doesn't work here (Win10, Chrome50, GTX970)
i am still figuring things out here.
somehow 2 of my 2 systems had no webgl problems when i defined a variable integer with the initial value of =400000; and i was dumb enough to assume that other hardware would be just as fine with that but they are not, resulting a shader compiler error. silly oversized integerss constrain compatibility translation and wrapping too much.
ypu may fix it by removing that variable completely from my code, its not important, nearly decapitated condition anyways.
testing glsl on new installed win7 64bit hardware i notice how non-worksave webgl can become and that it can fail to reset on even minor errors, instead assuming "you no longer support webgl because of some random wrapper error, better change relog your OSes user to restart your graphic driver. dissapointed!
somehow 2 of my 2 systems had no webgl problems when i defined a variable integer with the initial value of =400000; and i was dumb enough to assume that other hardware would be just as fine with that but they are not, resulting a shader compiler error. silly oversized integerss constrain compatibility translation and wrapping too much.
ypu may fix it by removing that variable completely from my code, its not important, nearly decapitated condition anyways.
testing glsl on new installed win7 64bit hardware i notice how non-worksave webgl can become and that it can fail to reset on even minor errors, instead assuming "you no longer support webgl because of some random wrapper error, better change relog your OSes user to restart your graphic driver. dissapointed!
Not a bad first attempt.
And to be fair, there are some significantly worse over here.
However, if you compare this to "crème de la crème" - it's not so great.
As others said, but I will second that: sending this as a link to "work in progress" thread accompanied with a screenshot would be more than enough.
Saying that, you are obviously new here, so mistakes happen, and at least I have to admit, you are not just talking/spamming over here. For this, obviously a piggie, but keep it up!
And to be fair, there are some significantly worse over here.
However, if you compare this to "crème de la crème" - it's not so great.
As others said, but I will second that: sending this as a link to "work in progress" thread accompanied with a screenshot would be more than enough.
Saying that, you are obviously new here, so mistakes happen, and at least I have to admit, you are not just talking/spamming over here. For this, obviously a piggie, but keep it up!
download link broken
wrighter: the download links works OK from here in browsers that still support ftp links
you get my thumb up because I value your input to my technology shaders on Shadertoy very much (usually on the mathematical side) and I would love to see you making demos ;) let's go!
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !
I bet I made way to many silly newbie mistakes with it.