Alliance Space Guard

[Kabouik]

Compatibility Report

• Name of the game with compatibility issues: Alliance Space Guard
• Steam AppID of the game: not a Steam game, and not released yet, it is only a private test build but I thought I'd investigate that since this is a one-developer game and they probably won't have time to sink into Linux compatibility at this stage

System Information

• GPU: AMD Radeon RX 580 Series
• Driver/LLVM version: POLARIS10 DRM 3.42.0 5.15.26-211.current LLVM 13.0.0
• Kernel version: 5.15.26-211.current # 1 SMP PREEMPT Sat Mar 5 05:12:04 UTC 2022 x86_64 GNU/Linux
• Full system information report as Gist
• Proton version: Experimental

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

It took me some time to realize that Steam launch options have no effect on non-Steam games, and the environment variables have to be set beforehand when launching Steam itself. I got two distinct results depending on whether I used PROTON_USE_WINED3D=1, see below:

• With just PROTON_LOG=1 steam, steam-15066880814979481600.log I am sorry, I am not sure I am able to show the content of this window at this stage even though there's nothing fancy in there, so better safe than sorry. In any case; it's a pre-launch game settings window and it seems to work as expected, except for an audio issue and most importantly this "D3D < 11" issue. There is a field to select the GPU, with two choices: my AMD dGPU, and my Intel iGPU, but I get the same issue with both.

• With PROTON_USE_WINED3D=1 PROTON_LOG=1 steam, steam-15066880814979481600.log The game settings window doesn't show up.

The first case was quite encouraging because I got to the game's settings window, but unfortunately it detects a version of DirectX below 11 and greys out the launch button. The game actually requires DirectX 11.0. Seeing that, I tried to use PROTON_USE_WINED3D=1 which led me to this second issue, which I think is related to SharpDX (SharpDX is used to connect .NET and DirectX).

I am not sure which of those two is the closest to launching the game actually, which is why I'm presenting both.

Reproduction

Adding the game as a non-Steam game and running it with Proton Experimental (same with Proton 7) pretty much reproduces this all the time. As stated above, launch options have to be set as environment variables when running Steam from terminal for them to be taken into account for non-Steam games. Unfortunately, this won't be easy for others to reproduce because the game is in a private testing phase and can't be accessed by many players. I know this means it won't be easy to solve, but I was thinking reporting the logs wouldn't hurt, and perhaps someone can understand the errors better than I did.

[Blisto91]

@Kabouik The launch options not working for non steam games should be fixed on the steam beta branch so you could try that. Dunno when it's gets pushed to stable steam. Does it behave any differently if you launch with this? (omit the %command% part if you are not using the steam launch options)

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

[Kabouik]

Thanks @Blisto91 for the answer. I can confirm that launch options seem to work as expected in the Beta branch, thank you.

With the launch option you recommended, I get the same first result (game settings window) as above, except thise time only my AMD GPU is offered as a choice in the GPU selector in that window. However, it still reports D3D < 11.

Since the game uses .NET and SharpDX, I guess this could be one way to investigate?

On 2022-04-04 11:17 Blisto91 @.***> wrote:

@Kabouik The launch options not working for non steam games should function on the steam beta branch so you could try that. Does it behave any differently if you launch with this? (omit the %command% part if you are not using the steam launch options)

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/sha
re/vulkan/icd.d/radeon_icd.x86_64.json %command%

--
Reply to this email directly or view it on GitHub: https://github.com/ValveSoftware/Proton/issues/5747#issuecomment-10873 13575 You are receiving this because you were mentioned.

Message ID: @.***>

[Blisto91]

If you launch it with this from steam does it show a dxvk overlay in the settings app?

DXVK_HUD=1 %command%

I would guess not, but just as a test.

[Kabouik]

Hey @Blisto91. I see no overlay with this launch option.

[Blisto91]

Roger just wanted to make sure if it wasnt running through dxvk

[Kabouik]

Some new results:

• Deleted my Steam Proton prefix (rm -rf ~/.steam/steam/steamapps/compatdata/3172619714)
• Set compatibility layer in Steam to Proton-6.9-GE-2
• Launched once to create the prefix
• Ran protontricks --gui and selected ASG in the list
• Selected default prefix, then "Install a Windows DLL or component"
• Selected dotnet48 and installed it; I don't think it succeeded but moved to the next step anyway
• Launched the game again, observed the Settings window now throws an exception every time I click on a field (that's new)
• Set compatibility layer to Proton Experimental
• Launched the game again and noticed the D3D < 11 issue is not there anymore and the launch button no longer is greyed out, although there's no green message stating that the dependency is satisfied either (there is one on Windows); also the "Graphics quality" field is not populated anymore
• Clicked the launch button and got the error in the second screenshot

[Blisto91]

Gj Oh yea since it's not a native steam title yet it doesn't include it's own first time setup so anything extra besides a clean windows install needs to be done manually.

[Kabouik]

From the developer, after he read the above message:

The problem is possibly with .NET: the code is compiled on the fly so an app may start seemingly correctly but then fail when unable to manage a new section because of compatibility issues.

I don't know yet what else can be tried at this stage. Although, again, I had the impression that the installation of dotnet48 did not go perfectly well; this may be one of the first things to solve.