|
New epoqe by epoqe [web]
[nfo]
|
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|||||||||||||
|
popularity : 49% |
|||||||||||||
alltime top: #34585 |
|
|||||||||||||
|
||||||||||||||
added on the 2024-05-13 17:01:49 by NinjaKoala  |
||||||||||||||
popularity helper
comments
Could be done in 256b
added on the 2024-05-13 18:33:47 by TomCatAbaddon 
nice, bookmarked dat shadertoy url. ;)
nice logo!
(& typography)
Beautiful, but why is "pi = 3.1415925" instead of "pi = 3.1415926"?
@TomCatAbbadon: Yeah, probably. But i wanted to use our usual workflow and tools. I wanted to see if it's possible to do an 1k with the current state of our compression linker (the answer is: not really).
Also i wanted people to see we have a new logo and publish it as glsl if people want to greet us.
@R0XX0R: There's a history of which pi digits i use in shaders ^^
At first i used a LOT of digits (better safe than sorry).
Then i thought: i don't need all those digits and went for something really short like 3.1416. But with some shader i had glitches with that due to some corner cases. I started to use the output of pi.n(24).str() in sage, which outputs a decimal representation of a 32 bit floating point approximation of pi. The last few digits of that don't correspond to the decimal digits of pi, but in the floating point representation it is the same. However, sometimes i mistakenly use pi.n(23).str() which happened here xD
Also i wanted people to see we have a new logo and publish it as glsl if people want to greet us.
@R0XX0R: There's a history of which pi digits i use in shaders ^^
At first i used a LOT of digits (better safe than sorry).
Then i thought: i don't need all those digits and went for something really short like 3.1416. But with some shader i had glitches with that due to some corner cases. I started to use the output of pi.n(24).str() in sage, which outputs a decimal representation of a 32 bit floating point approximation of pi. The last few digits of that don't correspond to the decimal digits of pi, but in the floating point representation it is the same. However, sometimes i mistakenly use pi.n(23).str() which happened here xD
clean
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 !