Just discovered that the place where it uses x as an iterator is actually using it as a y coordinate in the texture.
Show this thread
Looking at some shader code that starts with "const int i = 32768;" As a coder this completely breaks my mind that someone would do this. All variables are 1 or 2 letters, iterators are h, t, x, and it ... I have no idea what is going on but am determined to figure it out.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
haha that's wild
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
was it ported from matlab? All the matlab code I see looks like that
-
Possibly; I suspect this is a mathemetician or at least a very math oriented person that wrote it
- Show replies
New conversation -
-
-
I'd start by copying it into notepad++ and find replacing the variable names
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is it minimized?
-
Aren't shaders precompiled? Of course the code might be intentionally obfuscated, but my bet is on just plain old bad coding practices.
- Show replies
New conversation -
-
-
avant garde
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's an overflow for a short int and would be - 1. Maybe they're using it as a bit mask? Or to multiply by - 1 quickly? Or to like... Reverse iteration? Idk
-
It appears to be used as a bit shift... since it's a shader you divide by 32768 and it's like shifting right by 15. It's storing a 45-bit number as floats and then getting them back again for more precision
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.