Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

WebGL malfunction in latest version

  • 1 răspuns
  • 1 are această problemă
  • 3 vizualizări
  • Ultimul răspuns de stegu

more options

I have a GLSL tutorial at this address: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial.html With the update to Android 4 and the latest version of Firefox, shaders 5 to 10 stopped working correctly. Everything was fine before, and looked like the desktop version. I really want this to work on FF for Android, but the bug is silent (fatal malfunction without any error message) even though I think I did everything to spec, and like I said, things were fine before the update. Any hints to whether this is a bug or an error on my part? My platform is Android 4 on a Samsung Galaxy Note (N7000). I have no other WebGL capable mobile platform to test this.

I have a GLSL tutorial at this address: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial.html With the update to Android 4 and the latest version of Firefox, shaders 5 to 10 stopped working correctly. Everything was fine before, and looked like the desktop version. I really want this to work on FF for Android, but the bug is silent (fatal malfunction without any error message) even though I think I did everything to spec, and like I said, things were fine before the update. Any hints to whether this is a bug or an error on my part? My platform is Android 4 on a Samsung Galaxy Note (N7000). I have no other WebGL capable mobile platform to test this.

Toate răspunsurile (1)

more options

I have routed around the bug in this somewhat crippled version: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial_mobile.html Still no solution to the original problem, and still no clue to what is wrong. The shader runs, but shows a completely wrong and glitchy pattern. Works fine on desktop version, worked fine in Android 2.3 on the same phone and with the same version of FF.