[Bug 44250] New: Star Wars KOTOR Knights of the Old Republic (GOG): Crash trying to enter Black Vulkar base
https://bugs.winehq.org/show_bug.cgi?id=44250
Bug ID: 44250 Summary: Star Wars KOTOR Knights of the Old Republic (GOG): Crash trying to enter Black Vulkar base Product: Wine Version: 3.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs@winehq.org Reporter: kirinn@mooncore.eu Distribution: ---
Created attachment 60045 --> https://bugs.winehq.org/attachment.cgi?id=60045 Wine log output and backtrace
Knights of the Old Republic 1, version 2.0.0.3 from GOG. Archlinux x64 kernel 4.14.8 Open-source Radeon, tried both xf86-video-ati 1:7.10.0 and xf86-video-amdgpu 1.4.0 (hardware: R7 240, a GCN 1.0 card) Mesa 17.3.1 -----------------
The game crashes when you try to enter the Black Vulkar base through the sewers on the first planet.
The crash backtrace for this appears identical to the crash that happens when you have Frame Buffer Effects enabled and try to enter Stealth mode at any time. However, even with the setting disabled, the Black Vulkar base can't be entered.
To reproduce, play through the game normally, passing through the Undercity and the sewers. Rescue the wookiee, then find the Vulkar base elevator. Enter the elevator. A loading screen comes up, and the game crashes when loading is complete.
The crash happens both using hardware and software rendering. (LIBGL_ALWAYS_SOFTWARE=1 wine swkotor.exe)
The bug was first brought up here: https://www.reddit.com/r/kotor/comments/7mc682/kotor_1_game_crashes_when_ent...
https://bugs.winehq.org/show_bug.cgi?id=44250
--- Comment #1 from kirinn@mooncore.eu --- Created attachment 60047 --> https://bugs.winehq.org/attachment.cgi?id=60047 Save game in front of crashing elevator
Attached a save game for easy reproduction. Unzip this in your Kotor/saves directory. It'll overwrite your first save slot, so make a backup first if you want to preserve your save.
Start the game, load the "Black V Base" save, and you're in front of the Vulkar base elevator. Take a short step forward (WASD movement) to trigger the loading screen and crash. (If your FPS is very low, the character may jump ahead too far and miss the trigger point; just move back and forth a bit and it should take.)
https://bugs.winehq.org/show_bug.cgi?id=44250
kirinn@mooncore.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=44250
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #2 from Béla Gyebrószki gyebro69@gmail.com --- Created attachment 60049 --> https://bugs.winehq.org/attachment.cgi?id=60049 backtrace (nouveau/mesa 17.3.1)
I can reproduce the crash with nouveau/mesa 17.3.1, but not with the proprietary drivers 387.34.
OpenGL vendor string: nouveau OpenGL renderer string: NV106 OpenGL core profile version string: 4.3 (Core Profile) Mesa 17.3.1 OpenGL core profile shading language version string: 4.30
wine-3.0-rc3-24-g72ab2d5b07
https://bugs.winehq.org/show_bug.cgi?id=44250
andrew@alshain.org.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@alshain.org.uk
--- Comment #3 from andrew@alshain.org.uk --- Same here with Steam version using Arch linux fully up to date as of 31/12/2017:
linux 4.14.9 wine 3.0rc4 mesa 17.3.1
open source amdgpu drivers and radeonsi.
This is with a RX460 graphics card. Occasional transient crashes up to that point, but the entrance to the Black Vulkar base crashes constantly no matter how I tweak the graphics settings.
https://bugs.winehq.org/show_bug.cgi?id=44250
--- Comment #4 from andrew@alshain.org.uk --- I managed to copy my savedgames to a laptop with a AMD A6 processor (mullin GPU), also using the amdgpu driver and this crash doesn't occur. It's running a slightly out-of-date antergos distribution based on Arch:
kernel: 4.13.8-1-ARCH mesa: 17.2.3-1 wine: 2.19.1
I can save the game on the level that causes the crash, copy that savedgame back to the machine producing the crash, and loading the savedgame instantly crashes with the same error and suspicious register value. Loading the same savedgame on the laptop works fine.
This is not the only part of game that results in a repeatable crash. Two other locations that spring to mind that on entering result in the same crash are the hunting lodge on Tatooine, and on leaving the airlock to walk outside to get to the bridge on the Leviathan. Loading those savedgames on the laptop works with no problems.
It is possible to continue playing after that level on the machine that experiences the crash, but as mentioned there are other instances of that (presumably the same) bug occuring on later levels.
https://bugs.winehq.org/show_bug.cgi?id=44250
--- Comment #5 from kirinn@mooncore.eu --- This is still occurring with Wine 3.2 + Mesa 17.3.5. No notable difference in callstack compared to before.
https://bugs.winehq.org/show_bug.cgi?id=44250
kirinn@mooncore.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #6 from kirinn@mooncore.eu --- This is no longer occurring on Wine 3.6 + xf86-video-ati 1:18.0.1 + Mesa 18.0.1, on my AMD graphic card.
It is now possible to enter the Vulkar base without crashing, and the stealth frame buffer effect works as well.
Can one of the kind people who've added comments confirm the crash is fixed for them too?
https://bugs.winehq.org/show_bug.cgi?id=44250
--- Comment #7 from A andrew@alshain.org.uk --- Wine 3.6 and mesa 18.0.1
I no longer have the save from outside the Vulkar base, but I tried it with a later save outside the Rakatan base which crashed with the same error and it's now working. So it does look like it's now been fixed.
https://bugs.winehq.org/show_bug.cgi?id=44250
--- Comment #8 from kirinn@mooncore.eu --- Excellent. Thank you!
https://bugs.winehq.org/show_bug.cgi?id=44250
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTOURBUG
--- Comment #9 from Béla Gyebrószki gyebro69@gmail.com --- This was most probably fixed in Mesa, not in Wine so the correct resolution for this bug should be NOTOURBUG. I can confirm that the crash doesn't occur with Mesa 18.0.1. I tried Wine 3.0 and 3.2 and now they don't crash the game.
https://bugs.winehq.org/show_bug.cgi?id=44250
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=44250
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #11 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
https://bugs.winehq.org/show_bug.cgi?id=44250
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Béla Gyebrószki from comment #9)
This was most probably fixed in Mesa, not in Wine so the correct resolution for this bug should be NOTOURBUG. I can confirm that the crash doesn't occur with Mesa 18.0.1. I tried Wine 3.0 and 3.2 and now they don't crash the game.
Fixed upstream, closing.
-
wine-bugs＠winehq.org