You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Honestly not sure if it's a bug or just wrong usage, but it definitely should be handled either at compile time or runtime in one way or another.
Having a return; inside fragment or vertex methods would cause shaders to break, as it would exit before outputs are properly assigned. I'd suggest making it a compile time error if return; statement is used inside entry-point methods.
Honestly not sure if it's a bug or just wrong usage, but it definitely should be handled either at compile time or runtime in one way or another.
Having a
return;
insidefragment
orvertex
methods would cause shaders to break, as it would exit before outputs are properly assigned. I'd suggest making it a compile time error ifreturn;
statement is used inside entry-point methods.Source: Haxe#Heaps Discord message by kevansevans
Shader code
-D shader_debug_dump
dump: 5_dump.txtProduced fragment shader:
The text was updated successfully, but these errors were encountered: