You can try to add it to your .bash_profile. export WINEARCH=win64
Log out and back in.
The thing is MHWD should have installed the video-hybrid-intel-nvidia-prime for your laptop, and not the video-nvidia
so, wine should use the prime-run … same as this
I wanted to update but the post was closed: that isn’t necessary. That’s not true, prime-run is needed, but running Wine with it doesn’t fix the problem.
Also, it doesn’t work when using intel, I’ll try NVIDIA in a minute (didn’t work).
Driver Version: 470 doesn’t work, I get the same error
And DaVinci Resolve doesn’t recognise the GPU, it’s the same version that I had then
Isn’t there a way to install version 495?
Sorry for being so annoying, please don’t slap me
Yeah, that is why you should always run the latest supported driver by the system and for your GPU.
To me, that means there is something else with your wine config that is off.
If in doubt, use Play On Linux, create different wine prefixes, either 32 or 64 bit installers and test them out. You can remove them if not working, also you can backup them, set fixed wine versions …
I would have mentioned it. That driver became the 510 one … There is always a way to manually fiddle things from older sources. Is not worth the effort.
Okay, sorry about that.
It turned out that the error only happens with specific applications when they call specific…methods, or functions I guess…
i.e. some apps work flawlessly, and some work until I press button x, and some crash while starting up.
I fixed it by removing and recreating the prefix, then re-installing wine, the changing the windows version from Windows 7 to Windows 10.
I think that changing the Windows version was what solved it.
Thank you @bogdancovaciu for your time, patience and help.