protonscr

Broken Sword 2 - the Smoking Mirror: Remastered

protonopen appid 33600Game compatibility - Unofficial
ValveSoftware/Proton#6202 · opened 2022-10-02 by venky1989 · updated 2022-10-05 · 7 comments · github · game page · search this game
Vvenky1989 2022-10-02 github

Compatibility Report

  • Name of the game with compatibility issues: Broken Sword 2 - Remastered
  • Steam AppID of the game: 33600

System Information

  • GPU:
  • Driver/LLVM version:
  • Kernel version:
  • Link to full system information report as Gist:
  • Proton version:

I confirm:

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

Symptoms

My BS2 (Broken Sword 2) game - Remastered version was working well until my system crashed in the morning. When I tried playing the same in the evening, it is crashing. I tried with other Proton versions but not working. BS1 is working fine (Hence my system might not be the issue here). I have attached the error log. Please check it out. Waiting for a helpful response.
P.S:- I use a Ubuntu 18.04 system.

Reproduction

I played BS2 and finished 29% of the game. My system crashed due to power cut. I restarted my system and tried launching the game. It is trying to launcha nd crashing everytime. BS2 Original is opening but in a small window and very buggy. BUt BS2 remastered is crashing everytime.

Kkisak-valve maintainer 2022-10-02 github

Hello @venky1989, in your Proton log, these look like some lines of interest:

err:steamclient:create_win_interface Don't recognize interface name: SteamController008
err:steamclient:create_win_interface Don't recognize interface name: SteamInput006

SteamController008 looks like it was added with Steamworks 1.51 (Proton 6.3+), and SteamInput006 is from Steamworks 1.53 (Proton 7.0+) and you're using Proton 5.13 with this game. Please retest with Proton 7.0-4.

Vvenky1989 2022-10-04 github

Hi Kisak, Thank you for the Prompt reply. I have tried to launch the game with Proton 7.0-4 but the result is the same. I am attaching the error log again. Can you please take a look at it?
steam-33600.log

P.S:- Uodate: Using Proton 7.0-4 (In STeam Settings) and Auto in Game Settings, I am able to now start and play its Original Version but the Remastered version is Crashing as usual. It used to work well for a few days (I completed 29% of the game) but crashing now. What could it be?

Kkisak-valve maintainer 2022-10-04 github

A header only Proton log usually hints that something went wrong before the actual game got a chance to start. If you completely close Steam, then run Steam from a terminal, are there any hints in the terminal spew when you tell Steam to start the game?

Vvenky1989 2022-10-05 github

HI Kisak,

WHen I do that, I am getting an error.

64418568, installed version 1664418568, existing pending version 0
[2022-10-05 14:58:27] Nothing to do
[2022-10-05 14:58:27] Verifying installation...
[2022-10-05 14:58:27] Performing checksum verification of executable files
[2022-10-05 14:58:35] Verification complete
vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
BInit - Unable to initialize Vulkan!
vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
BInit - Unable to initialize Vulkan!
chdir /home/thedarklord/SteamLibrary/steamapps/common/Broken Sword 2

This same error is repeating for starting the game as well.

Kkisak-valve maintainer 2022-10-05 github

I don't understand why that would prevent Proton from trying to run the game, but regardless, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please check if a more substantial log is generated with PROTON_LOG=1 now.

Vvenky1989 2022-10-05 github

Hi Kisak,

Here is the Gist file attached. The Proton error log file is still the same with just the Header.

P.S:- The game used to run well a week back, the system crashed once, and from then on it never launched successfully again.
https://gist.github.com/venky1989/a6276c319334f24a537871fffb67fc5f

Kkisak-valve maintainer 2022-10-05 github

So, that at least tells us that you're on a Sandybridge generation Intel chipset, which because that generation doesn't support Vulkan makes it unsupportable by Proton in general. However, it looks like the game is a DirectX 5 game and that goes through wined3d to OpenGL and the Vulkan bits are most likely not touched at all. This means we're back to no real hints to ponder.

Proton versions

Launch options