ValveSoftware / ValveSoftware/Proton
Lego Indiana Jones: The Original Adventures (32330)
Open
Nobody has claimed this yet.
Game compatibility - Unofficial
Regression
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Whitelist Request
- Name of the game to be whitelisted: Lego Indiana Jones: The Original Adventures
- Steam AppID of the game: 32330
System Information
- GPU: nVidia GTX 1060
- Driver/LLVM version: 4.6.0 NVIDIA 410.73
- Kernel version: 4.19.1.arch1
- Link to full system information report as Gist: https://gist.github.com/sudoman281/98d82e05efae4c4743166c469e893317
- Proton version: 3.7-8
I confirm:
- [ x ] that pressing the
Playbutton in the Steam client is sufficient. - [ x ] that runtime config options
are necessary to run the game. - [ x ] that no workarounds other than the mentioned ones are necessary.
Issues
- I haven't experienced any issues.
- There are no issues left open for this game.
- [ x ] Although I consider the gaming experience equal to Windows there are
remaining issues:
I had a problem with looping a part of the music in the menu, cutscenes, etc. all over again. I had to enable PROTON_NO_ESYNC in user_settings.py in order to make it work. Maybe this was necessary because I use JACK audio server, but I can't tell certainly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Proton runtime configuration and the referenced user_settings.py workaround, then compare behavior with PROTON_NO_ESYNC enabled and disabled. Reproduce the repeated music in the menu or cutscenes using the listed game, Proton version, and JACK audio setup; done means determining whether the looping persists without the workaround and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100