cryinkfly / Autodesk-Fusion-360-for-Linux

This is a project, where I give you a way to use Autodesk Fusion 360 on Linux!
https://github.com/cryinkfly/Fusion-360---Linux-Wine-Version-/wiki
MIT License
1.79k stars 115 forks source link

Various graphical glitches *solved* #212

Closed bishboshin closed 1 year ago

bishboshin commented 2 years ago

Describe the bug Graphical glitches:

To Reproduce Steps to reproduce the behavior:

  1. Start the Fusion 360
  2. See the glitches

Expected behavior no graphical glitches

Screenshots 2022-04-04_21:45:51 2022-04-04_21:45:13 2022-04-04_21:44:58

Laptop Asus UX533FD:

Additional context

Console output: Intel: https://gist.github.com/bishboshin/c280e4afdfababa513cb1c50e154a477 Nvidia: https://gist.github.com/bishboshin/1c3bdbc0e02e1e91550591e8045a6b91

Edited: added console output for two GPUs: intel and nvidia

cryinkfly commented 2 years ago

Please check this post here: https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/213 🙂

bishboshin commented 2 years ago

Added the console output for two GPUs to the top post. "sudo sysctl dev.i915.perf_stream_paranoid=0" makes the "MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0" message go away, but the glitches stay, unfortunately.

bishboshin commented 2 years ago

I figured out the reason of one graphical glitch: it was just a picom making dark background of all the floating objects. After killing the picom, Fusion window started to look better: Unsaved Image 2 Unsaved Image 1 However, some glitches persist:

I tried to install Fusion 360 from lutris repo - same performance. I also have the #9 but it does not bother me as much as the glitchy sprites. =(

cryinkfly commented 2 years ago

I have also now these glitches (DXVK & OpenGL) with the newest graphics drivers and Wine version:

OS: openSUSE Tumbleweed Kernel: 5.17.1-1-default DE: Xfce 4.16 WM: Xfwm4 Wine: 7.6-1444.1 Mesa: 22.0.1-306.1

Fusion 360: 2.0.12670

Bildschirmfoto_2022-04-13_12-37-51

cryinkfly commented 2 years ago

Okay I was just experimenting with the rendering of Wine itself and figured out that there might be a bug there!

This problem now occurs when I set this with the help of winetricks:

renderer=vulkan

Bildschirmfoto_2022-04-13_14-50-33

Link for more information:

Bildschirmfoto_2022-04-13_15-05-50

bishboshin commented 1 year ago

Update: everything is solved by installing a proton package and disabling shadows in picom as follows:

...
shadow-exclude = [
    "name = 'fusion360.exe'",
    "class_g = 'fusion360.exe'",
...

not sure which one of these lines worked, but it worked. =) Regarding the proton: For this particular application, off course, it's bloated. It might be not the most elegant solution, but it works, as it installs many things needed for optimal wine performance. I still have some minor glitches, but that's already a different topic =) To be continued... This topic can be marked as "SOLVED" at this point.

cryinkfly commented 1 year ago

@bishboshin Can you can describe the steps, please?

cryinkfly commented 1 year ago

I have found these posts here:

bishboshin commented 1 year ago

@bishboshin Can you can describe the steps, please?

Well, I did two things: 1. installed the proton package, 2. disabled picom for the Fusion 360.

  1. The proton package is available in AUR for Arch-based systems: https://aur.archlinux.org/packages/proton In my case, I used the yay-helper to install it: yay -S proton This helped to get rid of this kind of glitches: image To my opinion, installing proton is far from being an elegant solution. Because proton is installing a lot of stuff. It's a very big package. Probably, it is possible to tweak some Wine settings or to install some smaller packages instead of the bloated proton, but it worked for me. Probably, when I need to install it another time, I will try to figure out what worked exactly. Maybe it was just one of the libraries from the proton dependencies (can be seen on the link above), that caused things to work properly. I'm not sure at this point yet.
  2. Unwanted shadows like here: image were fixed by making an exception for picom, which I use in my setup for some fancy transactions and transparency in my qtile windows manager. It's also described on the picom Arch wiki page how to do that. In my case, I needed to add some lines to the ~/.config/picom.conf file under "shadow-exclude" section:
    ...
    shadow-exclude = [
    "name = 'fusion360.exe'",
    "class_g = 'fusion360.exe'",
    ...

    you can see the class and the name of the Fusion 360 window by running xprop and clicking on it's window when it is running. The output is a bit cryptic, but you only need to look for the variables called "...NAME..." or "...CLASS...". In my case it was "fusion360.exe" as described above. Maybe, specifying just name of just class_g would also work, but I'm too lazy to test that =) It works as is and I'm fine with that. Let me know if there are any other questions. I'll update this topic if I will need to reinstall it another time and get better understanding of the issue.

bishboshin commented 1 year ago

I have found these posts here:

* https://superuser.com/questions/1554422/disable-font-smoothing-in-wine

* https://www.wine-reviews.net/2009/03/how-to-enable-font-anti-aliasing-in.html

It can easily be, that during the proton installation, these settings are set in the proper way and that causes the problem to go away. Next time I will try these two first.