https://bugs.winehq.org/show_bug.cgi?id=42304
Bug ID: 42304 Summary: Caladrius Blaze shows black screen on title menu Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: fjfrackiewicz@gmail.com Distribution: ---
Created attachment 57028 --> https://bugs.winehq.org/attachment.cgi?id=57028 Wine 2.0 terminal output
When attempting to play the game Caladrius Blaze, I am greeted with a completely black screen.
I've attempted to play the game while using Windows XP & 7 modes.
Any advice on what logs I would need to provide will be greatly appreciated as I can't see anything related to DirectX in the game's terminal output at all...
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #1 from fjfrackiewicz@gmail.com --- Created attachment 57029 --> https://bugs.winehq.org/attachment.cgi?id=57029 Screenshot of the black screen
https://bugs.winehq.org/show_bug.cgi?id=42304
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Caladrius Blaze shows black |Caladrius Blaze, Raiden IV: |screen on title menu |Overkill show black screen | |on title menu
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #2 from fjfrackiewicz@gmail.com --- Raiden IV: Overkill, which uses the same engine as Caladrius Blaze, also shows a black screen on the title menu.
I believe there is a regression here as I've ran Raiden IV before in Wine 1.9.3. I am currently running a regression test as I write this comment.
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #3 from fjfrackiewicz@gmail.com --- I checked again and both games work just fine in Wine 1.7.24 but if I attempt to go any higher, they stop displaying correctly.
I am not sure how to carry out a regression test starting from Wine 1.7.24 since it fails to build...
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to fjfrackiewicz from comment #3)
I checked again and both games work just fine in Wine 1.7.24 but if I attempt to go any higher, they stop displaying correctly.
I am not sure how to carry out a regression test starting from Wine 1.7.24 since it fails to build...
You can try to cherry-pick the patches required to make it build at each step of the bisection, as in bug 42282 comment 8. You might need more / different patches and they might not cherry-pick cleanly but it's probably worth a try.
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #5 from fjfrackiewicz@gmail.com --- (In reply to Matteo Bruni from comment #4)
(In reply to fjfrackiewicz from comment #3)
I checked again and both games work just fine in Wine 1.7.24 but if I attempt to go any higher, they stop displaying correctly.
I am not sure how to carry out a regression test starting from Wine 1.7.24 since it fails to build...
You can try to cherry-pick the patches required to make it build at each step of the bisection, as in bug 42282 comment 8. You might need more / different patches and they might not cherry-pick cleanly but it's probably worth a try.
Hi Matteo,
I actually managed to build the 1.7 series of Wine without the need to cherrypick by downgrading flex to an earlier version :) The regression test is still on-going as I write this comment.
https://bugs.winehq.org/show_bug.cgi?id=42304
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
--- Comment #6 from fjfrackiewicz@gmail.com --- I ran a regression test with Wine 1.8 as the bad Wine and Wine 1.7.24 as the good Wine and nothing conclusive came out of the test. The reason I picked Wine 1.8 as the bad Wine is because the games fail to work on Wine 1.8.
The weird thing is that if I use this version of Wine for Arch Linux: https://archive.archlinux.org/packages/w/wine/wine-1.7.24-1-x86_64.pkg.tar.x... both Caladrius Blaze and Raiden IV work as they should but any other version results in the black main menu screen. I can still hear the sounds and all but I can't see anything.
I would be more than happy to donate a copy of either game to anyone willing to look into this issue.
https://bugs.winehq.org/show_bug.cgi?id=42304
Emmanuel Anne emmanuel.anne@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |emmanuel.anne@gmail.com
--- Comment #7 from Emmanuel Anne emmanuel.anne@gmail.com --- I had the same problem, the solution is easy : just install vcrun2013 using winetricks, I used winetricks version 20170316 (the latest). You can run this before or after installing the game, apparently what makes it to work is in the libs overrides. I didn't test raiden4 with this but it probably works too with this.
https://bugs.winehq.org/show_bug.cgi?id=42304
--- Comment #8 from fjfrackiewicz@gmail.com --- (In reply to Emmanuel Anne from comment #7)
I had the same problem, the solution is easy : just install vcrun2013 using winetricks, I used winetricks version 20170316 (the latest). You can run this before or after installing the game, apparently what makes it to work is in the libs overrides. I didn't test raiden4 with this but it probably works too with this.
Thanks for the info, the workaround (vcrun2013) does as you described but it's not a proper solution since using winetricks is considered a workaround :)
https://bugs.winehq.org/show_bug.cgi?id=42304
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Caladrius Blaze, Raiden IV: |Caladrius Blaze, Raiden IV: |Overkill show black screen |Overkill show black screen |on title menu |on title menu (needs native | |vcrun2013)
https://bugs.winehq.org/show_bug.cgi?id=42304
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |msvcrt
https://bugs.winehq.org/show_bug.cgi?id=42304
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |98bc9fdaa431f274fe3a9fc538b | |0b562c6fad981 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Gijs Vermeulen gijsvrm@gmail.com --- Fixed by: 98bc9fdaa431f274fe3a9fc538b0b562c6fad981
I tested Raiden IV.
https://bugs.winehq.org/show_bug.cgi?id=42304
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Component|msvcrt |msvcp
--- Comment #10 from Gijs Vermeulen gijsvrm@gmail.com --- Forgot to add that I tried to find out which commit caused the regression. It brought me to 3888aa4d8d406fce2c63b79e4e8fe164cd549a36, but reverting that commit (had to revert 3b62083443c419d96692985368ff527bbfd98050 as well) did not fix the issue, so I am almost certainly wrong.
https://bugs.winehq.org/show_bug.cgi?id=42304
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.13.
https://bugs.winehq.org/show_bug.cgi?id=42304
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.0.x
https://bugs.winehq.org/show_bug.cgi?id=42304
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.x |---
--- Comment #12 from Michael Stefaniuc mstefani@winehq.org --- Removing the 3.0.x milestone from bugs included in 3.0.3.
-
wine-bugs＠winehq.org