Solved: Affinity hanging on initial splash screen #206
hogar1977
started this conversation in
Show and tell
Replies: 1 comment 1 reply
|
I was having this same problem both with the installer AND the AppImage. The installer recommends Wine 11.12, but the app doesn't launch for me at all under Wine 11. When I finally switched to Wine 10.10 (using the installers "Switch Wine Version" troubleshooting option) and then "Reinstall WinMetadata" it finally launched and runs perfectly! TL;DR; If you are having problems launching, and it hangs on the splash card, try using Wine 10.10 instead of Wine 11. I suspect the problem is that WinMetadata doesn't get installed for Wine 11 (apparently on purpose!?), but is still needed by Affinity. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I installed Affinity natively on Arch linux using the python script. Everything installed perfectly and Affinity was running fine when launched with the button from the script. However, when I would try to run the application through the patched .desktop shorcut it would always hang at the splash screen.
I have modified my .desktop Exec line to following (replace 'yourusername' with your own!):
Exec=env WINEPREFIX="/home/yourusername/.AffinityLinux" WINEDEBUG="-all,fixme-all" WINEDLLOVERRIDES="opencl=" VKD3D_DEBUG="none" VKD3D_DISABLE_EXTENSIONS="VK_KHR_present_id" VKD3D_FEATURE_LEVEL="12_1" VKD3D_SHADER_DEBUG="none" VKD3D_SHADER_MODEL="6_5" DXVK_ASYNC="0" DXVK_CONFIG="d3d9.deferSurfaceCreation = True; d3d9.shaderModel = 1" DXVK_LOG_LEVEL="none" /home/yourusername/.AffinityLinux/ElementalWarriorWine/bin/wine start /b "C:/Program Files/Affinity/Affinity/AffinityHook.exe"
This solved the issue for me. Maybe it helps some of you that have similar issues. It makes sure to bypass wine's opencl override and uses the modifiers that are already implemented in the python script when launching Affinity from it's interface. Its just that the script doesn't for whatever reason include those same modifiers in the .desktop file when it patches it.
All reactions