Thanks for the clarification. That was totally it. Based on what you said I was able to track down the problem to my context created by GLFW. I was missing a build flag to enable WebGL2: -s USE_WEBGL2=1. ES3 is up and running on Emscripten for me!
Hai On Monday, November 30, 2015 at 5:20:39 PM UTC-8, キャロウ マーク wrote: > > > > On Dec 1, 2015, at 3:56 AM, Hai Nguyen <[email protected] > <javascript:>> wrote: > > > > Hi Mark, > > > > Thanks for the explanation. Very helpful. I just recently tested this on > Canary Chrome as well. Pretty much the same exact issue. Was curious about > how GLSL ES3 gets translated into GLSL WebGL2? I didn't realize that > varying was still used in GLSL WebGL2. > > Sorry for my lack of clarity. The bare “2.0” I mentioned referred to > OpenGL ES 2.0 where, of course, GLSL 1.00 uses only varying and #version > must be 100. > > The answer to your question is, it is and it isn’t. WebGL 2.0/OpenGL ES > 3.0 support both GLSL 1.00 and GLSL 3.00. If you are using GLSL 1.00 then > “varying" must obviously still be used. However if you use GLSL 3.00 > “varying" is an error and “in” or “out” must be used. > > Regards > > -Mark > > > > > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
