-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single click launch mode for games using compatibility tools #92
Comments
Please do stop the launching of games after a game is already launched. I accidentally run my games multiple times... |
Multiple games launch at the same time is now blocked. |
This is working in |
For some reason, the single click launch mode is not working for non-native user games. |
@neuromancer seems to work for me. Any info about game and used compat tool? Anything weird in log? |
To reproduce with latest revision (4150ba2):
After that, clicking on the UPlay game will always bring the compatibility layer popup. |
@neuromancer can't reproduce. May it be related to compiler optimizations too? |
I tried without optimizations but it is still an issue. However, it is not a very important one, so feel free to close it. Other users will re-open it if they have the same issue. |
@neuromancer check {
"proton_961940": {
"options": {
"PROTON_NO_ESYNC": false,
"PROTON_NO_D3D11": false,
"PROTON_USE_WINED3D11": false,
"DXVK_HUD": true
}
},
"compat_options_saved": true
} |
The |
@neuromancer try 75a5015. It should be fixed. |
It's fixed. As efficient as always, thanks a lot! |
Possibly fix flatpak errors (tkashkin#15, tkashkin#61) Former-commit-id: 6029659
Once a game was installed with some compatibility mode and (and maybe configured to run properly), it could be nice to offer a single click launch mode to run it. Also, once the game started, it could be a good idea to disable the launch of other games because the compatibility tools can take a little longer to start (e.g. wine) and some impatient users could click several times 😞
The text was updated successfully, but these errors were encountered: