-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webgl demo not working(webgl in general) in win7?? #185
Comments
I'll try it out on mac & linux tomorrow, and will post what i get there.. |
it should be related to the difference on blacklist between the browser and content shell. Will look into this. Thanks for reporting. |
In the meantime you could try with this switch '--ignore-gpu-blacklist', as documented here: https://github.com/rogerwang/node-webkit/wiki/Command-line-switches |
thanks for the quick response! :) nw.exe --ignore-gpu-blacklist webgl |
You mean get.webgl.org works in node-webkit on win7 but your webgl code doesn't? |
no, get.webgl.org works within chrome.(so the graphics card supports webgl). within node-webkit however, get.webgl.org says webgl ist disabled |
I see. We are able to reproduce it here. Will fix this soon. Thanks for reporting. |
@aremes , could you please provide these details of the non-working platform: gfx chip model Thanks |
still haven't gotten around to running it on linux.. thanks for all the work! |
We believe copying d3dx9_43.dll and d3dcompiler_43.dll from the Chrome browser install files to the directory of node-webkit will fix this. Will ship the DLLs in the next release. |
Just tested on one workstation which had the same problem, and above solution worked like a charm! thank you very much! ill go ahead and try it on a few other systems today and if successful I'll close that issue. |
We may not be able to just ship the DLL with our distribution, please see this: http://stackoverflow.com/questions/265376/directx-redistributable-package-breakdown |
i understand. well, maybe this whole thing could be documented though, maybe in the readme.md? i'll see if i can figure out some eula compliant way of shipping the dlls with an app.. thanks for the info! |
google chrome ships with those dlls.. doesnt seem to care |
good point, will doc it in the wiki -------- Original Message -------- i understand. well, maybe this whole thing could be documented though, maybe in the readme.md? i'll see if i can figure out some eula compliant way of shipping the dlls with an app.. thanks for the info! Reply to this email directly or view it on GitHub: |
I have been hit with this problem, in one of the testing computers, and adding those files don't seem to solve it. The page http://get.webgl.org/ seems to work in chrome (26.0.1410.12 dev-m) but not in node-webkit while saying:
My The computer has the following:
Any idea how I can find what is the problem? |
Some evolution on this topic? |
Seems the problem was Windows XP (or the drivers?). After upgrading to a newer OS it works fine after copying |
where exactly should i copy those d3dx9_43.dll and d3dcompiler_43.dlll files to ? Should they be in the same folder as libEGL.dll ? |
@Stefdv Yes, all *.dll files should be in the same directory as the node-webkit executable. |
win7下汉字不能正常显示,有的系统没有问题,有的系统存在问题,特别是32位的系统出现该情况的问题比较多一点,后经过再页面上将字体的字号写成18px以上,或者字体加上bold式样以后能正常显示,请问这该如何处理 |
I've been trying to get node-webkit to show any support for webgl under win7, but i've failed terribly.
Both systems i've tried on (7 Home, and 7 Pro) support webgl using chrome(testing done using both get.webgl.org as well as a custom html that just tries to get the experimental-webgl context from a canvas node)
trying to run the webgl demo or the custom html file described above doesn't work in node-webkit.
specifically, it says webgl disabled
i installed all the latest graphics drivers on both systems. no change.
graphics hardware is intel HD 945gm and ati radeon mobility hd4330 none of which show up under chrome's unsupported devices list.
btw, i've tried all of this with 0.3.3 and 0.3.2. --> same result.
The text was updated successfully, but these errors were encountered: