STAR WARS™ Jedi Knight - Jedi Academy™

protonopen appid 6020Whitelist Request

ValveSoftware/Proton#1744 · opened 2018-10-15 by dreamer · updated 2019-03-19 · 2 comments · github · game page · search this game

Ddreamer 2018-10-15 github

Compatibility Report

Name of the game with compatibility issues: STAR WARS™ Jedi Knight - Jedi Academy™
Steam AppID of the game: 6020

GPU: Intel® HD Graphics 3000
Driver/LLVM version: 3.0 Mesa 18.0.5
Kernel version: 4.18.12
Link to full system information report as Gist: https://gist.github.com/dreamer/4f3773020ded88d4612e41de4dd67b7e
Proton version: 3.16-1 Beta

Game crashes on start. Happens on any modern system.

Run using following launch options:

NVIDIA: __GL_ExtensionStringVersion=17700 %command%
Intel/AMD: MESA_EXTENSION_MAX_YEAR=2003 %command%

I tested if contoller is causing crash as in #1732 and it does not. Game starts normally (both singleplayer and multiplayer).

Aaeikum 2019-02-18 github

Hello. With Proton 3.16-7, you can now use the PROTON_OLD_GL_STRING runtime option instead of the Mesa- or Nvidia-specific environment variables.

Ddreamer 2019-03-19 github

[x] that pressing the Play button in the Steam client is sufficient.
[x] that runtime config options are necessary to run the game.
[x] that no workarounds other than PROTON_* env variables are necessary (PROTON_OLD_GL_STRING=1)

[ ] I haven't experienced any issues.
[x] There are no issues left open for this game.
[x] Although I consider the gaming experience equal to Windows there are remaining issues:
- Multiplayer version does not download server list - this seems to be common issue judging by questions on various forums. It's still possible to create and play multiplayer match. Behaviour is the same on Windows 10 in the same network. When I wrote original compatibility report, multiplayer worked fine, so I think it's likely not a Wine problem, but rather a server problem.

Tested also alt-tabbing behaviour (perfect) and if game crashes when controller is plugged in (it doesn't).