ValveSoftware / ValveSoftware/Proton

Visual Basic no longer installed after steam deck updates.

Open
#6,149 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues: Anything that uses Visual Basic.
  • Steam AppID of the game: Multiple games

System Information

  • GPU: Whatever is in a Q3 Release Steam Deck
  • Driver/LLVM version: Whatever the current steam deck update as of 9/11/22 uses
  • Kernel version: Whatever the current steam deck update as of 9/11/22 uses
  • Proton version: Experimental, 7.XX, and all others I have tested.

I confirm:

  • [Y] that I haven't found an existing compatibility report for this game.
  • [Y] that I have checked whether there are updates for my system available.
Virtual environment boots normally, which means log is unlikely to show any signs of problems (Aside from that Virtual Basic doesn't exist and an error window is spawned by the game, as tested in Mechwarrior 5 in particular) - My experience with diagnostic logs is that this kind of issue does not show up on them, period.

Symptoms

Steam Deck update was rolled out on 9/11/22 and now any game that uses Visual Basic no longer functions, giving an error window instead.

Reproduction

Update the steam deck, then launch any game that requires Microsoft Visual Basic to run, via proton. Tested versions were Experimental and 7.X. Last game tested was Mechwarrior 5, which ran perfectly fine prior to the update. Last time this occurred I had to factory reset the steam deck and start over (which is now happening once a week due to this exact bug) to fix.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure after a Steam Deck update with a Visual Basic-dependent game through Proton Experimental or 7.X, as described in the report. Compare the affected behavior with the previously working state and collect the requested Proton log where possible. Done means identifying the update-related cause and restoring launch for affected games without a factory reset.

Written by the indexing model from the issue text.

Assessment

Tech stack
visualbasic
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.