Crash on level start when using digital distribution versions #11
Comments
|
General note for switching between the Steam and CD-ROM versions: Whenever Jedi Knight is launched from Steam, it will try to install a compatibility shim that affects all other Jedi Knight installations but not itself. I haven't dug into exactly what this compatibility shim is doing, but at minimum it's forcing some bad compat options (like requiring admin privileges). You can uninstall the shim by running this in an administrator command prompt from your Steam JK directory: |
The Steam version was modified to periodically call ChangeDisplaySettingsA inside menu rendering functions. Ostensibly this is to force the game to show the menu in fullscreen on modern computers, but since JkGfxMod already handles this it is more annoying than anything. The call is just being suppressed for now. This change also adds a configuration option, "log_path", which is useful for turning on logging when it is inconvenient to change environment variables. Comment #11
|
Current status: JkGfxMod can inject into the Steam version by the following process:
The intro cutscene and main menu appear correctly. The Steam overlay notification appears, but won't pop over when Shift+Tab is pressed (does this even work in the native version?). Getting JkGfxMod working with the Steam version and overlay does seem possible, if not feasible. The game crashes to desktop after loading a level. This happens shortly after Jedi Knight calls IDirect3D::Initialize with too few arguments, which is something that doesn't happen in the CD-ROM version of Jedi Knight. I'm not sure why they would have added this; IDirect3D::Initialize does nothing according to the SDK docs. The Steam version also seems to crash with an access violation when there's a debugger attached, so I'm not having much luck investigating this crash so far. |
|
Steam can be used as a launcher by following these steps:
This makes Jedi Knight run with JkGfxMod, with the Steam overlay fully working, and even with the Steam soundtrack fix. This isn't a real solution, but at least it demonstrates the problem isn't Steam. I think there's something very wrong with the JediKnight.exe that Steam ships. |
Steam automatically passes the -windowgui command line option as a Windows compatibility workaround. If you're using JkGfxMod this really isn't what you want, and it causes the game to behave poorly if you're using a non-Steam executable launched under Steam. inject.exe now filters out the -windowgui command line option if fullscreen is enabled in the configuration file. I've been waffling about this change for a while, since if non-Steam users do specify -windowgui on the command line they are probably doing it for a good reason. However, this is the cleanest workaround for the majority of Jedi Knight players. Comment #11
|
Are those EXEs supported? I tested them, but it's hard to tell if they work. |
|
Hello @Blackbird88 Unfortunately, I can't guarantee support for unofficial patches. There are too many of them. If they seem to work for you, though, then they're probably fine. |
jdmclark
changed the title
|
#39 suggests this bug may affect the GOG version as well. |
jdmclark
changed the title
Currently, JkGfxMod does not work with the executables that ship with the Steam version. Root cause is currently unknown. This issue tracks investigation and development work related to the Steam version.
The text was updated successfully, but these errors were encountered: