Trying to get Starstable to work on my kids computer - I am using Lutris 0.51 with wine as the runner and proton 4.2 as the wine version. Works fine to run the installer which downloads the assets from the star stable site. THEN however, I have to use the option ‘Run EXE inside wine prefix’ to run the real game executable. How do I make a shortcut to this executable inside the wine prefix created for the installer?
I tried copying all the settings of the installer but pointing the executable path to be inside the wine prefix on disk - this causes the game to log me out of my DE (budgie on ubuntu).
…Did you configure the installer as a game shortcut in Lutris? 0_o
Shortcuts are meant to be for games themselves. So the correct way to proceed from here would be to replace Executable path in the Game options tab of shortcut configuration with the path to your game (or put the path to the game directory into Working directory field and executable name into Executable, some games require that).
It would also be a good idea to submit the game into Lutris database; you probably don’t have enough experience to write a functioning installer yet but once someone does it won’t be a problem for anyone else to install it without problems.
A wine game logs you out of your DE? 0_o Didn’t know that was possible. Are you sure you put paths correctly?
…Also, does the game run correctly when you start it via ‘Run EXE inside wine prefix’?
The path seems alright, although using default wineprefix in a Lutris install is probably not the best decision, generally speaking.
Normally, however, you would put the gamedir path in “Working directory” field and have just the executable filename in the “Executable” field. It helps with certain problems (because not all executables support being run from a different folder).
Regardless, I find the idea of a wine process logging you out of X session to be a rather novel concept. I actually doubt it’s a feature supported by Wine (it certainly wouldn’t be of use in general case, and “reboot” button in installers does nothing in Wine). So my best guess would be that you managed to mess up the config, somehow (although how exactly it could lead to a logout is beyond me). Another possibility would be a software problem (like interference from Lutris runtime, which you have to disable in that case), but that seems unlikely as it doesn’t happen when using ‘Run EXE inside wine prefix’…