ValveSoftware / ValveSoftware/Proton

Myst: Masterpiece Edition (63660)

Open
#2,138 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial overlay
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: Myst: Masterpiece Edition
  • Steam AppID of the game: 63660

System Information

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-63660-taking-screenshot.log
steam-63660-open-overlay-and-alt-tab.log

Symptoms

1st problem:
Taking a screenshot makes the game permanently dark until its restart.

Before taking the screenshot:
20181225153133_1
After taking the screenshot:
20181225153138_1

2nd problem:
The mouse cursor is invisible when Steam overlay is open.

3rd problem:
The mouse cursor is invisible when alt-tabbed to desktop.

Reproduction

1st problem:
Launch the game, use the key to take a screenshot in Steam (default F12). The game will become dark after that.

2nd problem:
Launch the game. Press Shift+Tab to open Steam overlay. The mouse cursor will be invisible while the overlay is active.

3rd problem:
Launch the game. Press Alt+Tab to switch to desktop. The mouse cursor will be invisible while alt-tabbed.

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 with the attached steam-63660-taking-screenshot.log and steam-63660-open-overlay-and-alt-tab.log, then reproduce the three symptoms with Proton 3.16-1. Verify whether current Proton still shows the screenshot-darkening and invisible-cursor behavior. The report names no source file or test, so a completed fix and regression coverage would first require identifying the relevant subsystem.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.