-
Notifications
You must be signed in to change notification settings - Fork 2
Description
This is an old wine "issue". The executable directory where the executable run is the current working directory (the folder that you run protonlaunch from) and some applications cant access their assets because of that.
This is probably a deliberated behaviour since you dont want to change your cwd but since running Windows applications on Linux is a special situation the behaviour that i've notices is the follow:
The times where you dont switch the directory break more apps than the times where you do switch the directory. 90% of the applications are coded correctly and that change dont make difference.
So one solution would be to add a flag to enable auto chdir, although i would prefer to set the default to change the directory that would have an unexpected behaviour on applications where you don't expect the CWD to change and make troubleshoot worse. So a flag that explicitly enable that feature can be added.