Closed Bug 661399 Opened 13 years ago Closed 13 years ago

Impossible to get webgl active in firefox 4 nvidia gtx570 and latest (270.61) Nvidia drivers

Categories

(Core :: Graphics: CanvasWebGL, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mathieu.recchia, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

I tried to visit a page with a WEBGL component but it still remains inactive.
Here's a copy of my about:support page http://pastebin.com/Rm4PR8Nb


Reproducible: Always
Component: Graphics → Canvas: WebGL
QA Contact: thebes → canvas.webgl
In about:config, what are the values of webgl.disabled and are there any non-default (printed in bold font) values under gfx.blacklist.* ?

Does it work if you go to about:config and set webgl.force-enabled=true ?
--> if that still doesn't work, that means something is seriously wrong with your graphics driver.
Webgldisabled is set a false and al gfx.blacklist are set with default values

I tried to set webgl.force-enabled=true and visit this URL : http://www.nihilogic.dk/labs/webgl_musical_solar_system/ but i have this error message : "No WebGL found!
You need a canvas- and WebGL-enabled browser to view this demo.
See this blog post for details on how to obtain one - or watch this YouTube video if that works better for you. "

for information i use these drivers from Nvidia site : http://www.nvidia.fr/object/win7-winvista-64bit-270.61-whql-driver-fr.html
What is the value of the preference webgl.prefer-native-gl? Does it make a difference when you change it?
Also, can you start with a clean profile using

  firefox.exe -no-remote -P
Well, there's no change when i modify webgl.prefer-native-gl from false to true.
With a clean profile "firefox.exe -no-remote -P" all is ok.
(In reply to comment #5)
> With a clean profile "firefox.exe -no-remote -P" all is ok.

Ah, then let's close this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.