Closed Bug 881264 Opened 7 years ago Closed 7 years ago
JS renderer is black
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release) Build ID: 20130605070403 Steps to reproduce: visit http://threejs.org/examples/webgl_buffergeometry_particles.html Actual results: webgl three js renderer not show
in android 4.0.3 on acer iconia tab A100
[11:13:41.063] NS_ERROR_FAILURE: Failure @ http://threejs.org/build/three.min.js:418 The demo requires an extension not currently supported in Firefox for Android: compressed texture S3TC. http://www.doesmybrowsersupportwebgl.com/
needinfo to bjacob regarding status of mobile + S3TC
(In reply to Aaron Train [:aaronmt] from comment #2) > [11:13:41.063] NS_ERROR_FAILURE: Failure @ > http://threejs.org/build/three.min.js:418 > > The demo requires an extension not currently supported in Firefox for > Android: compressed texture S3TC. > > http://www.doesmybrowsersupportwebgl.com/ but in beta ? the demo is fonctional
Component: General → Canvas: WebGL
Product: Firefox for Android → Core
Version: Firefox 24 → Trunk
Someone could repro on an Atrix 4G, confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
S3TC is supported by the browser on Android too wherever the GPU supports it... the problem is that the majority of mobile GPUs do /not/ support S3TC! Specifically, as far as I know (used to be true at least around last year), the only mobile GPUs supporting S3TC are NVIDIA Tegras, and the reason why they do is that they are essentially cut-down versions of NVIDIA desktop GPUs. Unfortunately there is no compressed texture format that is universally supported on all current mobile GPUs. We support S3TC, ATC and PVRTC at the moment, which covers most of the market (we miss some ARM Mali's I think, but most of the current ones do not support _any_ compressed format _with alpha_ --- ETC1 lacks alpha, which makes it largely useless). In the future, the mobile world is set to converge to a universal format like ETC2 or ASTC, but until the majority of mobile GPUs in the real world support those, we won't have any good solution.
...wait, the device in comment 4 *is* a Tegra. If this doesn't support S3TC, then I don't know why --- could we have a regression? We definitely used to have S3TC working on Android Tegra devices even recently.
Can we please get a regression window?
I did all the maj until Friday, Saturday and Sunday I was not working I made the shift available today around 14h
(In reply to Aaron Train [:aaronmt] from comment #2) > [11:13:41.063] NS_ERROR_FAILURE: Failure @ > http://threejs.org/build/three.min.js:418 > > The demo requires an extension not currently supported in Firefox for > Android: compressed texture S3TC. > > http://www.doesmybrowsersupportwebgl.com/ I now think that that's a red herring: go to about:config, set webgl.disable-extensions to true, retry: the demo still works on my desktop. So it doesn't rely on any WebGL extensions like S3TC textures. We need to understand where that NS_ERROR_FAILURE is actually coming from.
this 2013-06-09-03-12-30-mozilla-central-android/ 09-Jun-2013 05:17 http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2013-06-09-03-12-30-mozilla-central-android/fennec-24.0a1.multi.android-arm.apk is functionnal the lasted nigtnly is not functional for me having looked into the code of three will have a js error detection Operation with the pixel ratio for canvas you change something in the detection of the screen size or canvas size ?
2013-06-10-03-11-47-mozilla-central-android/ 10-Jun-2013 05:24 bug latest-mozilla-central-android/ 10-Jun-2013 04:30 bug
On Windows: [14:48:55,237] NS_ERROR_FAILURE: Failure @ http://threejs.org/build/three.min.js:418 No error in 23.0a2 and below.
Probably related to bug 881681.
passing it on to :dz to help with investigation as this could be related to the landing in Bug 881681 . Please feel free to reassign if needed.
I can't reproduce this. Is it still an issue?
Excellent work, this seems to be resolved now. I've tested a few of AlteredQualia's demos without running into the bug.
You need to log in before you can comment on or make changes to this bug.