Prince of Persia: The Sands of Time (13600)

[n4ndee]

Compatibility Report

• Name of the game with compatibility issues: Prince of Persia: The Sands of Time
• Steam AppID of the game: 13600

System Information

• GPU: GTX 1050
• Driver/LLVM version: Nvidia 430.50
• Kernel version: 5.0.0-32-generic
• Link to full system information report as Gist: System Information
• Proton version: 4.11-8

I confirm:

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

steam-13600.log

Symptoms

The game starts and runs fine, the widespread fog issue is not present out of the box either, the Hardware.ini file seems to have the fix for it pre applied. However, I do have encountered some other bugs:

Player shadow glitch: The shadow effect under the player starts to behave strangely after jumping, rolling or suddenly changing direction. Two rectangles start to appear gradually and they follow the player's movement. The glitch disappears though, after alt-tabbing out of the game, then back to it. Then it appears again, after jumping around. I've tried all the different Proton versions, and also changing the in-game graphic options. Only turning off all shadow effects fixes it, but that cuts back on the experience. It might not be a Proton specific issue, but I haven't been able to find this bug mentioned anywhere, not on PCGamingWiki, ProtonDB or WineHQ.

No Steam Overlay: Even though Steam Overlay is enabled globally and also specifically for the game, it doesn't work. This means I can't see the current FPS value, but more importantly, I'm not able to use a controller with the game, that I set up with Big Picture Mode's controller options. In BPM, there's also a warning for the game that the overlay is disabled, and controller options won't work.

Reproduction

Just run the game normally. Any help for fixing these issues on my own would be appreciated.

[kisak-valve]

Hello @lnandor, it looks like the Steam overlay is disabled by the game's devs in Steam's database.

[n4ndee]

Hello @kisak-valve, thank you for the information. Then only the shadow bug remains. I've also updated the Imgur album with a video so you can better understand the issue.

[Guy1524]

@lnandor I would try using winetricks or protontricks to install d3dcompiler and d3dx. Trying D9VK is also worth a shot.

[n4ndee]

@Guy1524, thank you very much for the help. I tried installing d3dcompiler and d3dx, but the issue persisted, I might have done something wrong.

Using D9VK however did help, the shadow bug completely disappeared! Strangely enough, it introduced the known fog issue, but that can easily be fixed by editing the Hardware.ini file and making the following changes: ForceVSFog=1, InvertFogRange=0.

The game now runs without any problems whatsoever. Should I close this issue or perhaps make a Whitelist Request?

[kisak-valve]

Hello @lnandor, there's no need for a separate issue report to request the game be whitelisted.

If you're confident that this game runs well, make it explicitly clear that you would like the compatibility report switched over to a whitelist request, your system info (you can re-use the gist you've already made), Proton version used to test, and any PROTON_* env variables that were used.

[n4ndee]

Hello @kisak-valve, all right, then I'd like to ask you to switch over the report to a whitelist request. Here's my System Information, the Proton version used was 4.11-8 and the only env variable needed is PROTON_USE_D9VK=1.

The only other fixes I used were a Widescreen fix, which is only an enhancement, and the Extreme fog fix, which is not OS related.

[springwurm]

does not start with proton 5.0.7.

proton 5.0.7 log: steam-13600_5.0.7.log
proton 4.11-13 log: steam-13600_4.11-13.log

System Info

[kisak-valve]

Hello @springwurm, please verify you have the vulkan-radeon and lib32-vulkan-radeon packages installed.

[springwurm]

yes packages are installed

#pacman -Q | grep vulkan-radeon
lib32-vulkan-radeon 20.0.7-2
vulkan-radeon 20.0.7-2

[kisak-valve]

Does setting the game's launch options to PROTON_USE_WINED3D=1 %command% have an effect?

Also, please update your system information with the extended diagnostics information.

Separately, you could also try using PROTON_FORCE_LARGE_ADDRESS_AWARE=0 %command%.

[springwurm]

PROTON_USE_WINED3D=1 Log: steam-13600.log
PROTON_FORCE_LARGE_ADDRESS_AWARE=0 Log:
steam-13600.log
PROTON_USE_WINED3D=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=0 Log:
steam-13600.log

All three attempts, don´t work.

[friedc]

Works with proton 7.0.

[zixinus]

Hello, the game cannot find a valid display mode when running it off the Steam Deck. I included a log.

steam-13600.log