Eagle GPU acceleration

[itrashCBCWM]

Dear support!

I would like to ask you a question about GPU acceleration in Linux Eagle version. I'm still using the older version (x86 7.2.0) because newer versions have some gpu delays. I have also tried the newest version (9x), but the same results, even if I changed the xcb->xcb_egl platform.

Eagle versions:

• 7.2.0 - OK
• 7.5.0 - ERR
• 7.7.0 - ERR
• 8.x - ERR
• 9.x - ERR

So what was changed between 7.2.0 and 7.5.0? How the solve this problem?

I didn't try the 7.3.0 and 7.4.0.

Thank you,

Andy

[jorge_garcia]

Hi @itrashCBCWM,

I hope you're doing well. The issue isn't so much that the GPU support has changed but rather there are features in the newer versions of EAGLE that are more intensive on the renderer. Since those features aren't going to be removed, this can be considered a normal behavior.

Let me know if there's anything else I can do for you.

Best Regards,

[itrashCBCWM]

Hi @jorge_garcia !

Thank you for your answer.

I have made some more "measurements". I have installed version 7.3.0 and 7.4. to distinguish exact version. So version 7.3.0 is working fine, but 7.4.0 has the mentioned problem. So is there any changelog for version 7.4.0 available? Or what is the dramatic/problematic change there?

Thank you,

Andy

[jorge_garcia]

Hello @itrashCBCWM,

I hope you're doing well. The changelog's are included in every installation of EAGLE you'll find it in the installation directory doc folder.

I don't remember off the top of my head what changed it could've been but if I had to guess it may have been the introduction of the board shape feature, or the orthogonal move feature.

Please let me know if there's anything else I can do for you.

Best Regards,

[didrik.madheden]

I'm using Eagle on Linux as well and I've been struggling with this. Out of interest, what's your GPU? Or more specifically, what does glxinfo report? (You may need to install it using a command like "sudo apt-get install mesa-utils" if it doesn't exist on your system.)

One partial solution I've found is to install the Windows version of Eagle in Wine. For me, this makes panning and zooming buttery smooth (even for newer 9.x versions) although instead it introduces some other slight graphical performance issues, for example when moving a component. Maybe you will have better luck. At least, this tells me that this is not simply an issue of lacking hardware, but a software issue somewhere that should be addressable. (Even if the issue might be in the graphics driver or Linux libs and essentially outside Autodesk's control.)

Here are a couple of commands to tweak graphics settings when launching Eagle. None of them really did anything for me, but they might help you:

env LIBGL_ALWAYS_SOFTWARE=1 ./eagle

env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 ./eagle

[itrashCBCWM]

Hello Jorge and Didrik!

First, thank you for your answers.

@jorge_garciaWhich feature is the dramatic from here https://www.element14.com/community/thread/45683/l/eagle-version-74-released?displayFullThread=true?

@didrik.madhedenI tried your suggestions.

1. mesa-utils is installed as well
2. LIBGL_ALWAYS_SOFTWARE=1 ./eagle
   • Same results as before
3. LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 ./eagle
   • Give me some errors due to x64 version
   • So I used the x86 version, LD_PRELOAD=/usr/lib/i386-linux-gnu/libxcb-dri3.so.0.0.0 ./eagle
     • but there are the same "delays" results
4. glxinfo | grep "Device"
   • Device: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) (0x116)
5. cat /etc/os-release
   • NAME="Ubuntu"
   • VERSION="18.04.4 LTS (Bionic Beaver)"

So maybe I can  try to use wine, but I would like to still use a native version.

Regards,

Andy

[itrashCBCWM]

Hello again,

After some time, I have made some more measurements.

I have tested the version 7.4.0 over wine, and it works without any "delays". So there should be definitely changed something in the Linux part. As I said, I would like to still use the native version.

I have also compared ldd outputs between 7.3.0 and 7.4.0. Exactly the same libraries are linked, but on different addresses. Is it somehow possible to check, what is wrong/was changed between those versions?

Regards,

Andy

[itrashCBCWM]

Hello @jorge_garcia ,

Is there any progress here? Do I have to think, that this is solved now?

Regards,

Andy