https://bugs.winehq.org/show_bug.cgi?id=40207
Bug ID: 40207 Summary: Bioshock CSMT crash Product: Wine-staging Version: 1.9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: hadrien.lacour@openmailbox.org CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ArchLinux
Created attachment 53720 --> https://bugs.winehq.org/attachment.cgi?id=53720 crash backtrace
Playing Bioshock (via Steam), when loading the "Medical Pavillion" area, if CSMT is enabled, it crashes with the following backtrace. Without CSMT, it works correctly.
https://bugs.winehq.org/show_bug.cgi?id=40207
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
--- Comment #1 from Robert Walker bob.mt.wya@gmail.com --- (In reply to q3cpma from comment #0)
Created attachment 53720 [details] crash backtrace
Playing Bioshock (via Steam), when loading the "Medical Pavillion" area, if CSMT is enabled, it crashes with the following backtrace. Without CSMT, it works correctly.
Could you check if this is an issue with a 32-bit Wineprefix as well?
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #2 from q3cpma hadrien.lacour@openmailbox.org --- Jus tested it, it doesn't crash. Just to precise, I reproduced it like 5 times with the same backtrace on the 64bit one, so it's not a coincidence.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #3 from q3cpma hadrien.lacour@openmailbox.org --- Sorry, CSMT wasn't enabled. It happens too.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #4 from q3cpma hadrien.lacour@openmailbox.org --- Created attachment 53721 --> https://bugs.winehq.org/attachment.cgi?id=53721 crash_backtrace_32bit
Here's the backtrace for the 32bit prefix.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #5 from Sebastian Lackner sebastian@fds-team.de --- Does this issue still occur with Wine Staging 1.9.10+?
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #6 from q3cpma hadrien.lacour@openmailbox.org --- Sorry, I'm on Gentoo now and have to compile wine (again) because the staging USE flag isn't set, and download Bioshock again too before testing again. If I test it again, it won't be exactly now.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #7 from Robert Walker bob.mt.wya@gmail.com --- (In reply to q3cpma from comment #6)
Sorry, I'm on Gentoo now and have to compile wine (again) because the staging USE flag isn't set, and download Bioshock again too before testing again. If I test it again, it won't be exactly now.
If you dump your Bioshock saved game file "somewhere" on the inter-webs - from near the problematic area. I can have a play with it. I just don't have any saved games from Bioshock floating around just now... (Unless the crash happens early in the Medical Pavillion level - then I can just play it through.)
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #8 from q3cpma hadrien.lacour@openmailbox.org --- Actually, I can't even reach the main menu since updating to 1.9.11 staging, CSMT or not (backtrace provided). Should I make a seperate bug?
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #9 from q3cpma hadrien.lacour@openmailbox.org --- Created attachment 54651 --> https://bugs.winehq.org/attachment.cgi?id=54651 Bioshock crash with 1.9.11 staging
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #10 from Sebastian Lackner sebastian@fds-team.de --- (In reply to q3cpma from comment #8)
Actually, I can't even reach the main menu since updating to 1.9.11 staging, CSMT or not (backtrace provided). Should I make a seperate bug?
Yes, please open a separate bug report for this issue (if there is no similar bug report yet). Please also test if you can also reproduce it with the development version of Wine.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #11 from Robert Walker bob.mt.wya@gmail.com --- (In reply to q3cpma from comment #8)
Actually, I can't even reach the main menu since updating to 1.9.11 staging, CSMT or not (backtrace provided). Should I make a seperate bug?
I can't reproduce that with wine-1.9.11-112-gd864119 (Staging)... Have you disabled the d3d10 & d3d11 libraries - with winecfg?
I'm still waiting to hear (cough!!) ... How early (in the game) the CSMT enabled Wine crashes with Wine-Staging. Then I'll attempt to reproduce that failure!
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #12 from q3cpma hadrien.lacour@openmailbox.org --- I've applied the "DirectX 10.0 support" thingie from https://appdb.winehq.org/objectManager.php?sClass=version&iId=17740&... before. Also, the moment is precised in the first post: when loading "Medical pavillion", after the cutscene with the projected message about spying.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #13 from Robert Walker bob.mt.wya@gmail.com --- (In reply to q3cpma from comment #12)
I've applied the "DirectX 10.0 support" thingie from https://appdb.winehq.org/objectManager. php?sClass=version&iId=17740&iTestingId=87778 before. Also, the moment is precised in the first post: when loading "Medical pavillion", after the cutscene with the projected message about spying.
If your graphics card supports DirectX 11.x - then you also need to disable d3d11 support in winecfg (sorry I've still got to add that info to the Bioshock page)... It's a fairly recent Wine change that the detection hardware support leads to these code pathways being enabled.
Sorry - but just double checking about the area where your crash occurs... I'll try playing through that area (time permitting!!)
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #14 from q3cpma hadrien.lacour@openmailbox.org --- Tried with d3d11 disabled (I suppose the 7970 supports dx11), with and without CSMT: no change. I'll try to build it from source now.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #15 from q3cpma hadrien.lacour@openmailbox.org --- Well, unless I get around the "wine version mismatch" thing, someone else is gonna have to test it with git.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #16 from Erich E. Hoover erich.e.hoover@wine-staging.com --- (In reply to q3cpma from comment #15)
Well, unless I get around the "wine version mismatch" thing, someone else is gonna have to test it with git.
Run "wineserver -k".
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #17 from q3cpma hadrien.lacour@openmailbox.org --- (In reply to Erich E. Hoover from comment #16)
(In reply to q3cpma from comment #15)
Well, unless I get around the "wine version mismatch" thing, someone else is gonna have to test it with git.
Run "wineserver -k".
Thanks, but it did nothing (as expected, since I looked manually if it was running). The error message says "or you have and older one somewhere in your PATH", which is the case.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #18 from Erich E. Hoover erich.e.hoover@wine-staging.com --- (In reply to q3cpma from comment #17)
... Thanks, but it did nothing (as expected, since I looked manually if it was running). The error message says "or you have and older one somewhere in your PATH", which is the case.
Where are you running wine from? Did you "make install" it before running it?
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #19 from q3cpma hadrien.lacour@openmailbox.org --- (In reply to Erich E. Hoover from comment #18)
(In reply to q3cpma from comment #17)
... Thanks, but it did nothing (as expected, since I looked manually if it was running). The error message says "or you have and older one somewhere in your PATH", which is the case.
Where are you running wine from? Did you "make install" it before running it?
No, since I don't want to clutter my system. I just wanted to run it from the build dir.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #20 from Robert Walker bob.mt.wya@gmail.com --- (In reply to q3cpma from comment #19)
No, since I don't want to clutter my system. I just wanted to run it from the build dir.
I thought you said you were running Gentoo though? Why not just build the live version of Wine, install system-wide and then revert back. If you don't want to run that version of Wine all the time? Personally I'm always on Wine-Staging git these days :-) Otherwise you'll have to make sure all the library path variables are set correctly (e.g. by changing the build prefix).
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #21 from q3cpma hadrien.lacour@openmailbox.org --- Here's the other crash bug for those interested. https://bugs.winehq.org/show_bug.cgi?id=40759
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #22 from q3cpma hadrien.lacour@openmailbox.org --- So I was able to test it with 1.9.11 staging (CSMT enabled). Crash even earlier than before, during the first level (the one after you get out the submarine-elevator) when going through the plane's tail in the water tunnel. I have a backtrace, but I should recompile wine to have a real one.
https://bugs.winehq.org/show_bug.cgi?id=40207
q3cpma hadrien.lacour@openmailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.3 |1.9.11
https://bugs.winehq.org/show_bug.cgi?id=40207
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.11 |1.9.3
--- Comment #23 from Sebastian Lackner sebastian@fds-team.de --- Please do not change the version (see bug reporting guidelines). It is sufficient to mention that the issue is still present.
https://bugs.winehq.org/show_bug.cgi?id=40207
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #24 from winetest@luukku.com --- (In reply to q3cpma from comment #22)
So I was able to test it with 1.9.11 staging (CSMT enabled). Crash even earlier than before, during the first level (the one after you get out the submarine-elevator) when going through the plane's tail in the water tunnel. I have a backtrace, but I should recompile wine to have a real one.
Could you retest with 2.x series of wine? There has been no response to this over 6 months and it's a lot of time in wine development.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #25 from q3cpma hadrien.lacour@openmailbox.org --- Sorry, I don't have Wine nor Steam+Bioshock installed at the moment. If I test it again, it won't be now.
https://bugs.winehq.org/show_bug.cgi?id=40207
--- Comment #26 from Robert Walker bob.mt.wya@gmail.com --- (In reply to winetest from comment #24)
(In reply to q3cpma from comment #22)
So I was able to test it with 1.9.11 staging (CSMT enabled). Crash even earlier than before, during the first level (the one after you get out the submarine-elevator) when going through the plane's tail in the water tunnel. I have a backtrace, but I should recompile wine to have a real one.
Could you retest with 2.x series of wine? There has been no response to this over 6 months and it's a lot of time in wine development.
I've tested extended gameplay from the very start of the game. With, or without, CMST enabled - I didn't have a single crash.
Nvidia GeForce GTX 970M with 378.13 drivers Wine Staging 2.2
So I can't reproduce this bug...
https://bugs.winehq.org/show_bug.cgi?id=40207
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #27 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine(3.20)?
-
wine-bugs＠winehq.org