Hi I was wondering if anyone else was having problems running WebGL in Windows 8 under Chrome.
I'm using Windows 8 Developer Preview x64 and Chrome 18. My video card is a Nvidia 250 GTS.
If I try to run any WebGL page, running though javaScript or NativeClient both fail to load thinking my video card doesn't support it.
I have my own native OpenGL apps that use GL2 and GL3 API features... GL itself is not the issue, unless I don't understand how Chrome uses GLES2 features.
Are there any known bugs about this?? Can't find anything.
EDIT: I just installed 'Windows 8 Consumer Preview x64' and WebGL still does not work... Is there a black list of OS's, kinda like some Intel video cards are black listed?? I have my system dual booted with Arch Linux and WebGL works fine on there?
As a workaround on windows 8 just add --disable-gpu-sandbox (I've checked it on 18 and 19 versions). To check open chrome://gpu/
For more information see chromium issue
Related
Is any one facing issues with remote device debug on Chrome 77 on Mac. I am unable to debug android device on Chrome 77.
A weird but functional solution without having to download an old version of chrome: https://support.google.com/chrome/thread/15368759?msgid=15847043
Download / Open Firefox
Navigate to about:debugging#/setup in Firefox
Disable USB Devices and Enable it again in Firefox
Go to Chrome chrome://inspect/#devices. You will now find your device(s) listed
I too faced the same issue regarding chrome version 77 in windows too.. Kindly download the previous version like 73 or 74..
https://www.neowin.net/news/google-chrome-730368386-offline-installer/
I'm trying to debug an issue in Flash Player that I have managed to fix in Firefox and Internet Explorer, Chrome however refuses to cooperate.
So I'm stuck with tracking down this Chrome specific issue. But as far as I can tell there's no way to get the Flash Debugger working on Chrome for Windows. I've read a few 'solutions' to this problem but most of these were for Mac or were for older versions of Chrome.
I tried disabling the Adobe Flash Player plugin in Chrome's chrome://plugins/ page and installing the Flash Player content debugger for Opera and Chromium based applications – PPAPI plugin, it doesn't seem to install successfully however as it doesn't show up in the plugins list nor am I able to view Flash Player content.
Any help would be greatly appreciated!
I have the same issue, however I was able to have the NPAPI debugger installed for a while. I think the key is the version of player. I found that it is impossible to install the adobe debugger if its version number is lower than the version of chrome flash player. I had the debugger working for about 2 months, but now I'm unable to install it since its version is 21.0.0.197 while chrome has just updated its player to version 21.0.0.213. Also I have found that sometimes I need to run non-personalized version of chrome right after installation. All I can do now is to wait for new version of adobe debugger.
[Edit]
I've found deleting folder with its plugin (the one with version in the name) can help temporary ;) After browser restart I saw debugger in plugins instead.
I have been looking for a way to install the debug version of flashplayer for ie11 or the newer microsoft edge browser under Windows 10. AS far as I understand, the flash plugin is now embedded with both browsers, so there is no way to update it to a debug version.
Using the debug version installer from adobe site (active x version), gives me a pop-up stating that I already have the latest verion which is true, but there seems to be no way to change my version with the debug one.
AS anyone succeed in using the debug version of flash undex one of these browser on Windows 10 (64bits)?
Thanks,
Currently the answer is no, you can not use the Flash debugger in Windows 10 / IE or Edge browsers as they are 'embedded' libraries in the OS now. The options are to use Win 10 & Firefox or use Win 8.1 when debugging Flash.
Via: https://forums.adobe.com/message/7841726#7841726
I have received confirmation that at this time Microsoft does not
support the debuggers on Windows 10. We do not have an estimate as to
when they will support the debuggers, but when they do, the install
links will be added to the Adobe Flash Player Support Center page.
You might do it manually by yourself, the core step is running flash_debugger installation file with switch -install, after a few modification in debugger folder, then you might reach there.
showing the happy result in image following.enter image description here
Download the windows 7 virtual machine for free. I recommend Virtual Box. https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
Once you have Windows 7 running inside Windows 10, install the IE Flash debugger or another of your choice. https://www.adobe.com/support/flashplayer/debug_downloads.html
IE 11 does not support flash player content debugging in windows 10.Fire fox and Chrome browsers however allow for the content debugging in windows 10.
1)Install Flash debugger for Firefox or Chrome:
a) Go to https://www.adobe.com/support/flashplayer/debug_downloads.html
b) For fire fox, Download and install Download the Flash Player content debugger for Firefox - NPAPI
c) For Chrome, Download and install Download the Flash Player content debugger for Opera and Chromium based applications – PPAPI
I have installed Chromium Version 31.0.1650.63 on CentOS release 6.5.
I also have firefox 24.6.0 installed
when I visit a web page in chromium that needs webGL, it says
Uncaught RuntimeError: The browser supports WebGL, but initialization failed.
I have checked the about:flags page the 'disable WebGL' attribute is NOT enabled
I visted
http://get.webgl.org/
Which said: Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.
Visiting that same sight in firefox gave me the nice spinning cube 'success' page.
I visited
chrome://gpu/
and it said
WebGL: Unavailable. Hardware acceleration unavailable
WebGL multisampling: Unavailable. Hardware acceleration unavailable
Which I find hard to square with the same video card providing webgl support in firefox just fine.
Is this truly a video card driver issue or should I look elsewhere?
Most likely this is because Firefox and Chrome use different GPU blacklists.
Please try debugging tips provided here:
WebGL not working for same spec system in chrome. How to fix?
If you have an Intel integrated graphics chip, you might have to enable hardware acceleration (i.e. exposing the GPU functionality directly to certain software) for the X.org server of the X11 window system.
To do this edit or create the configuration file /etc/X11/xorg.conf.d/20-intel.conf and put the following in there:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
Option "DRI" "3"
EndSection
Sources
https://wiki.archlinux.org/index.php/intel_graphics#Configuration
https://bbs.archlinux.org/viewtopic.php?pid=1595276#p1595276
I had this issue after switching from the proprietary Nvidia to the nouveau drivers, a change which does not seem to have been picked up in the chromium GPU config of my profile. The fix is running chromium-browser --single-process once to reset the GPU configuration.
Using info from chrome://gpu and chrome://version
Both on Chrome version: 35.0.1916.153 (Official Build 274914) m
Both using an Nvidia 670 GTX
My driver: 9.18.13.3523
His driver: 9.18.13.4043
My webGL works perfectly, and my driver is slightly behind his. His webGL doesn't work even though in the settings it says all hardware accelerated, webGL enabled etc.
When he goes on page with webGL things they don't work - he can't see them just like you wouldn't see them with old browsers.
Why is this happening? How to diagnose/fix?
Most likely Google has blacklisted the graphics driver because of the bugs.
You need to find out how start Chrome so that it ignores GPU blacklist. On some system it is this command line:
google-chrome --enable-webgl --ignore-gpu-blacklist
... and if it still doesn't work, the relevant console output etc. is needed.
More about blacklist:
http://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists