Switching wine version makes Fusion 360 usable again #598
Replies: 3 comments
-
|
Bummer - didn't work for me. I was using Fusion, with I guess 10.14 (should've paid closer attention 🙃) and then it stopped working on 10.15. Black screen. Switching to 9.2 (I didn't find a 9.22 on the Kron4ek repo) gives me this: |
Beta Was this translation helpful? Give feedback.
-
|
I've got very similar issues with recent wine versions (I tried 10.14, 10.15, 10.18) with both Xorg and Wayland on an NVidia RTX3000. My issues are:
And also for me, using wine 9.22 seems to resolve most or all of these issues. Performance seems to be much worse, though. |
Beta Was this translation helpful? Give feedback.
-
|
The latest version of Wine that has been working for me is 10.11 - Everything above has all of the above issues. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
I’ve been running Fusion 360 on Linux for a while now, and recently I hit a ton of weird bugs that made it borderline unusable. After weeks of pushing through a buggy mess, I finally found a solution that completely fixed it for me. Hopefully this helps someone else too!
Some of the issues I was having:
I was originally running some version of Wine 10, and an upgrade to Wine 10.15 broke Fusion entirely, it wouldn’t even launch. That’s what led me to this fix.
The fix: use Kron4ek’s Wine 9.22 build
Go to:
https://github.com/Kron4ek/Wine-Builds/releases
Download wine-9.22 and extract it somewhere, for example
~/.local/wine-kron4ekCheck if it runs:
~/.local/wine-kron4ek/bin/wine --versionThen make it your default Wine version:
for bash/zsh: echo 'export PATH="$HOME/.local/wine-kron4ek/bin:$PATH"' >> ~/.bashrcfor fish: set -U fish_user_paths $HOME/.local/wine-kron4ek/bin $fish_user_pathsThen confirm kron4ek 9.22 is now the default:
Beta Was this translation helpful? Give feedback.
All reactions