Describe the bug
Trying to launch Plutonium with protontricks-launch --appid 202990 /chonker/SteamLibrary/steamapps/compatdata/202990/pfx/drive_c/users/steamuser/AppData/Local/Plutonium/bin/plutonium-launcher-win32.exe results in a successful launch of the Plutonium launcher, but launching Black Ops 2 from it results in the wineserver terminating. Launching Plutonium with protontricks gui, selecting the Black Ops 2 MP prefix, and running the Plutonium exe arbitarily results in successful launch of Plutonium followed by a successful launch of Black Ops 2.
To Reproduce
Steps to reproduce the behavior:
1a. Open terminal and run protontricks-launch --appid 202990 /chonker/SteamLibrary/steamapps/compatdata/202990/pfx/drive_c/users/steamuser/AppData/Local/Plutonium/bin/plutonium-launcher-win32.exe.
2a. Plutonium will correctly launch, select Black Ops 2, and attempt to launch. (this step requires you have set up the game's path in the Plutonium launcher)
3a. After a few moments the wineserver will terminate.
1b. Launch protontricks gui from terminal or your choice of gui methods.
2b. Select the Black Ops 2 prefix, then default prefix, then run arbitrary executable.
3b. Select the Plutonium executable described above and run. It will launch correctly.
4b. Select Black Ops 2 and launch.
5b. It launches and runs perfectly fine. The wineserver does not terminate until the game is closed.
Expected behavior
Both methods should handle the wineserver the same instead of one terminating and the other keeping it.
System (please complete the following information):
- Distro: Fedora 44
- Protontricks installation method:
sudo dnf install protontricks
- Protontricks version: 1.14.0
- Steam version: Beta 1783717985
Additional context
Plutonium's installer and executable are a bit silly, the installer requires itself to be inside the prefix before it can be run correctly, and the executable requires a typical install directory for Black Ops 2. The former is achievable with just copy/pasting the installer exe into the downloads folder inside the prefix's virtual C drive, the latter requires you make a symlink to Black Ops 2's root folder into C:\Program Files (x86)\Steam\steamapps\common\, make sure the symlink is named exactly how the original folder is named.
Also -vv doesn't help as the moment the wineserver terminates so does my terminal.
Describe the bug
Trying to launch Plutonium with
protontricks-launch --appid 202990 /chonker/SteamLibrary/steamapps/compatdata/202990/pfx/drive_c/users/steamuser/AppData/Local/Plutonium/bin/plutonium-launcher-win32.exeresults in a successful launch of the Plutonium launcher, but launching Black Ops 2 from it results in the wineserver terminating. Launching Plutonium with protontricks gui, selecting the Black Ops 2 MP prefix, and running the Plutonium exe arbitarily results in successful launch of Plutonium followed by a successful launch of Black Ops 2.To Reproduce
Steps to reproduce the behavior:
1a. Open terminal and run
protontricks-launch --appid 202990 /chonker/SteamLibrary/steamapps/compatdata/202990/pfx/drive_c/users/steamuser/AppData/Local/Plutonium/bin/plutonium-launcher-win32.exe.2a. Plutonium will correctly launch, select Black Ops 2, and attempt to launch. (this step requires you have set up the game's path in the Plutonium launcher)
3a. After a few moments the wineserver will terminate.
1b. Launch protontricks gui from terminal or your choice of gui methods.
2b. Select the Black Ops 2 prefix, then default prefix, then run arbitrary executable.
3b. Select the Plutonium executable described above and run. It will launch correctly.
4b. Select Black Ops 2 and launch.
5b. It launches and runs perfectly fine. The wineserver does not terminate until the game is closed.
Expected behavior
Both methods should handle the wineserver the same instead of one terminating and the other keeping it.
System (please complete the following information):
sudo dnf install protontricksAdditional context
Plutonium's installer and executable are a bit silly, the installer requires itself to be inside the prefix before it can be run correctly, and the executable requires a typical install directory for Black Ops 2. The former is achievable with just copy/pasting the installer exe into the downloads folder inside the prefix's virtual C drive, the latter requires you make a symlink to Black Ops 2's root folder into
C:\Program Files (x86)\Steam\steamapps\common\, make sure the symlink is named exactly how the original folder is named.Also
-vvdoesn't help as the moment the wineserver terminates so does my terminal.