Trouble in lunching Package generator in Eagle 8.7.1

Trouble in lunching Package generator in Eagle 8.7.1

Anonymous
Not applicable
33,554 Views
61 Replies
Message 1 of 62

Trouble in lunching Package generator in Eagle 8.7.1

Anonymous
Not applicable

Dear developers,

 

I have a problems in lunching Package generator in My Managed library to create a 3D package. At web site, there isn't  such a problem, but in application  it shows me "Error: There is a problem running WebGL on this machine".  When I follow link on error message the web page  tells me: "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." I do checked my drivers and they are all up to date.  Is there someone else who has such a problem or is it just me?

PackGenError.png

Reply
Reply
0 Likes
33,555 Views
61 Replies
Replies (61)
Message 2 of 62

Anonymous
Not applicable

Hi there, a few people have this issue aswell, and so far, autodesk has only told us to update our video drivers.

 

see here: https://forums.autodesk.com/t5/eagle-forum/eagle-8-7-parametric-2d-amp-3d-model-generation-library-i...

 

even after forcing the latest drivers to install, i cant get webgl to work in eagle.

Reply
Reply
Message 3 of 62

andrii.anpilogov
Alumni
Alumni

HI @Anonymous @Anonymous

 

The issue is definitely there. But we are struggling with reproducing it.

It seems like mostly old Intel graphics cards are affected by latest Intel drivers that don't have proper OpenGL support.

I suspect that Chrome and Firefox fall back to software rendering.

 

Could you try this two workarounds?

 

1) Press Win+R and type cmd (open command line window):

  cd "c:\EAGLE 8.7.2"

  set QTWEBENGINE_CHROMIUM_FLAGS=--enable-webgl-software-rendering

  eagle_SW_OpenGL.bat

 

2) Press Win+R and type cmd (open command line window):

  cd "c:\EAGLE 8.7.2"

  set QTWEBENGINE_CHROMIUM_FLAGS=–disable_chromium_framebuffer_multisample

  eagle.exe

 

 

Reply
Reply
Message 4 of 62

Anonymous
Not applicable

Hi and thanks for replay!

 

I have already solved this problem, 🙂 Just set my preferred graphics card to be NVIDIA instead Intel graphics.

 

Thank you for suggestions!

Reply
Reply
0 Likes
Message 5 of 62

andrii.anpilogov
Alumni
Alumni

Hi @Anonymous

 

I glad to hear you solved the problem!

Hope you could find few minutes to switch preferable graphics card back and try above workarounds.

We can't reproduce it without your help.

You will help us localize the issue and fix this issue for other users who also could meet this nasty issue.

 

Regards

Reply
Reply
0 Likes
Message 6 of 62

Anonymous
Not applicable

Hi!

I have completed the steps you've prescribed, and things worked out even with automatic graphics card choices. Thanks!

 

I hope this fix will be useful for other designers with such a problem .

 

Thank you!!!

Reply
Reply
0 Likes
Message 7 of 62

andrii.anpilogov
Alumni
Alumni

Hi @Anonymous

 

Thank you for help!

 

Just to be sure I understand correctly, you tried both workarounds and they worked for you, right?

 

Regards 

Reply
Reply
0 Likes
Message 8 of 62

Anonymous
Not applicable

Hi!

 

Yes! I've tried both workarounds and they works for me.

 

Best wishes!

Reply
Reply
Message 9 of 62

Anonymous
Not applicable

Hi andrii,

 

i tried both workarounds, the first on worked, but the second one doesn't work for me.

 

Thanks

Reply
Reply
Message 10 of 62

andrii.anpilogov
Alumni
Alumni

Thank you @Anonymous @Anonymous !

Kudos and solutions are much appreciated!

Reply
Reply
0 Likes
Message 11 of 62

jorge_garcia
Autodesk
Autodesk

Hi All,

 

Here's is on that worked for me. It's in EAGLE readme file for Windows but it should be included here for completeness.

 

EAGLE passes '--ignore-gpu-blacklist' to Chromium by default.
This enables WebGL even on graphics cards / drivers that are known to have problems with it.
If you encounter issues with HTML content including bugs in WebGL then set QTWEBENGINE_CHROMIUM_FLAGS environment variable to “--ignore-gpu-blacklist=false” and run EAGLE:

cd "c:\EAGLE x.x.x" 
set QTWEBENGINE_CHROMIUM_FLAGS=--ignore-gpu-blacklist=false
eagle.exe

You can enter this in command prompt in Windows (Hold windows key and press R, then in the dialog that pops up type cmd followed by enter to get the command prompt) or you can make it part of a batch file.

 

Best Regards,



Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
Reply
Reply
Message 12 of 62

Matthz
Enthusiast
Enthusiast

Hi 

where do you assign the preferred graphic card?

Thanks

Reply
Reply
Message 13 of 62

Anonymous
Not applicable

Hello,

Is there a more permanent solution? The given solution works, however if I close Eagle and then re-open it none of the fixes persist.

I'm on Eagle 9.1.3 if it makes a difference 

Thanks,

Brad

 

Reply
Reply
Message 14 of 62

kd6oji
Enthusiast
Enthusiast

I just created a batch file to use instead of the default shortcut that Eagle provides.
Use notepad or other text editor to create eaglestart.bat

 

cd "c:\EAGLE 9.1.3" << Make sure your eagle folder is here, it will change in future updates
set QTWEBENGINE_CHROMIUM_FLAGS=--ignore-gpu-blacklist=false
start eagle.exe
exit

 

Save that on your hard drive somewhere and create a shortcut to it on your desktop. It is annoying but it works.. By chance what video card are you using? I had an AMD Radeon that was ancient, it never gave me this error, after I upgraded to an Nvidia Geforce 1050ti I get this annoying error trying to do any 3d packages with the default eagle shortcut.

 

 

Reply
Reply
0 Likes
Message 15 of 62

Anonymous
Not applicable

I also have a Nvidia GTX 1050 Ti. I never had this problem at work either, I don't know what that computer had for a graphics card, but I know it wasn't a 1050Ti.

Ill try your batch file approach. I'm sure it will work, but like you said, I'm sure it will get annoying. 

Thanks,

-Brad

Reply
Reply
0 Likes
Message 16 of 62

paulctan
Contributor
Contributor

Here's a step by step solution (in screenshots) on how to permanently put the fix in for Windows 10.  Basically, we are creating a permanent environment variable inside windows, doing the same thing as the suggested patch.

 

Just follow the steps and then close eagle and restart it and it should fix the opengl/webgl problem.

 

Disclaimer:  It worked for my machine, I cannot guarantee that it will work for you.  This is just to save you the steps of typing in the command and/or creating a batch file to launch eagle.  It is not a new fix, just an easier way of doing the fix.

 

Paul Tan.

 

 

 

 

Step1Step1Step2Step2Step3Step3Step4Step4

Reply
Reply
Message 17 of 62

Anonymous
Not applicable

I had this problem on my Nvidia GTX 1050 Ti now and had wireframes instead, my new setup rig is 5x beef up compare to my Toshiba dyanbook laptop having SSD and Intel HD Graphics with it that has same performance I am experiencing with the Nvidia GTX 1050 Ti

Reply
Reply
0 Likes
Message 18 of 62

jarrodFR7AH
Explorer
Explorer

Thanks, this worked for me.  It's ridiculous that this basic problem still exists in 9.3.0

Reply
Reply
Message 19 of 62

tonberryhunter
Advocate
Advocate

This worked!!!  Thank you.  I was like oh come on Autodesk.  Dont you go blaming my GPU and CPU.  They are plenty powerful enough.  I feel like the Autodesk people are a bunch of hipsters with Macbooks.  Like hi any proffesional computer user knows a custom built Windows rig is the best bang for your buck.  Also can we talk about how convoluted the whole 3D package setup is.  The way Eagle handles custom parts and packages in general is a mess.  

Reply
Reply
Message 20 of 62

guizicc
Community Visitor
Community Visitor

It works for my machine.Thanks~

Reply
Reply
0 Likes