-
-
Notifications
You must be signed in to change notification settings - Fork 1
Issues
You cannot use scripts when running Playnite inside Wine due to it not being able to run PowerShell scripts. Functionalities affected:
- Loading script-based extensions
- Game scripts
- Application scripts
- Emulation scripts and startup scripts
- Emulation import scripts
In the future, I might try to reimplement for example, the pre- and post-launch scripts by making it run Bash scripts, but most of the mentioned features will not be fixed.
There are many reasons why this might happen, such as:
- you're running Playnite using Proton/ProtonGE
Don't use Proton/ProtonGE for running Playnite. Use regular Wine instead.
- missing script permissions
It's possible that the Linux script has not been assigned proper permissions. Use the following commands to assign them manually.
# Checks the execution permissions for the script
ls -al <wine_prefix_path>/drive_c/users/<user>/AppData/Roaming/Playnite/Extensions/Yalgrin_WineBridgePlugin/Resources/run-in-linux.sh
ls -al <wine_prefix_path>/drive_c/users/<user>/AppData/Roaming/Playnite/Extensions/Yalgrin_WineBridgePlugin/Resources/open-file-picker.sh
# Sets the execution permissions for the script
chmod a+x <wine_prefix_path>/drive_c/users/<user>/AppData/Roaming/Playnite/Extensions/Yalgrin_WineBridgePlugin/Resources/run-in-linux.sh
chmod a+x <wine_prefix_path>/drive_c/users/<user>/AppData/Roaming/Playnite/Extensions/Yalgrin_WineBridgePlugin/Resources/open-file-picker.shThe game launches from the terminal, but the same command doesn't work from Playnite (emulator/play action/tool)
Might be an issue caused by running Wayland on your main system. Try adding the following environment variable to the specific command:
XDG_SESSION_TYPE=wayland
So for example, RPCS3 emulator command would look like this:
XDG_SESSION_TYPE=wayland /home/user/Downloads/rpcs3-v0.0.39-18708-3e49c32c_linux64.AppImage
This is most likely caused by invalid tracking expression. Launch the game and manually find it using
ps -aux | grep "<search term>" command. If it returns nothing, then you will need to adjust the tracking expression.
This is most likely caused by invalid tracking expression. Launch the game and manually find it using
ps -aux | grep "<search term>" command. If it returns anything other than the game process, then you will need to
adjust the tracking expression.