While the GLSL ES 3.00 (.4) spec says (The GLSL ES 3.1 spec contains
this wording too)
All uniform variables are read-only. They are initialized to 0 at link
time and may be updated through the API.
So I think we're correct in disallowing it.
Ok, fair enough. /me shakes fist at the list
Hi,
Mesa's ast_to_hir.cpp does a check like:
state-check_version(120, 0, initializer_loc,
cannot initialize uniforms);
i.e. it does not allow uniform initializers on GLSL ES 3.00.
Upon my reading of the spec, I can't find any place where that would be
disallowed.
On Wed, May 14, 2014 at 10:00 AM, Aras Pranckevicius a...@unity3d.com wrote:
Hi,
Mesa's ast_to_hir.cpp does a check like:
state-check_version(120, 0, initializer_loc,
cannot initialize uniforms);
i.e. it does not allow uniform initializers on GLSL ES 3.00.
On 05/14/2014 11:52 AM, Matt Turner wrote:
On Wed, May 14, 2014 at 10:00 AM, Aras Pranckevicius a...@unity3d.com wrote:
Hi,
Mesa's ast_to_hir.cpp does a check like:
state-check_version(120, 0, initializer_loc,
cannot initialize uniforms);
i.e. it does not
