[feature] working properties for rider in linux os (Ubuntu 23.04)

[markaltmaier]

executable won't run because it doesn't use proton to run Bannerlord.exe, and setting it manually doesn't work

[Aragas]

This might a bit out of the scope. I haven't tested debugging via Proton. I do suggest something like ProtonTricks might help with making the exe run with the proper Proton prefix.

[Aragas]

We tried to test executing with Proton a few month ago. It's not possible, from what we're discovered.
You can run the game from Wine\Proton, but Rider is not able to attach to the game process because it tries to attach to the wine/proton process

Here's an example of how to run the game

// launchProperties.json
    "Proton Bannerlord": {
      "commandName": "Executable",
      "executablePath": "%BANNERLORD_PROTON_PATH%",
      "commandLineArgs": "run Bannerlord.exe /singleplayer _MODULES_*$(ModuleId)*Native*SandBoxCore*CustomBattle*Sandbox*StoryMode*_MODULES_",
      "workingDirectory": "$(GameFolder)bin/Win64_Shipping_Client",
      "environmentVariables": {
        "STEAM_COMPAT_DATA_PATH": "%BANNERLORD_STEAM_COMPAT_DATA_PATH%",
        "STEAM_COMPAT_CLIENT_INSTALL_PATH": "%BANNERLORD_STEAM_COMPAT_CLIENT_INSTALL_PATH%"
      }
    },

[huntindeed]

So it's basically impossible to conveniently mod and debug from Linux?

[Aragas]

As far as we know, yes.
The game has the ability to run via .NET (Core), but it uses Win32 API, which requires Wine. Potentially, if we replace and Win32 API library with a Linux API wrapper, it could work, but the game engine is a C++ library compiled for Windows, which makes Wine mandatory. Another issue would be DirectX, but we do have DXVK, which seem to work well