Created attachment 57029 [details]
Screenshot of the black screen

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.

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...

(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.

(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.

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.xz 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.

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.

(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 :)

Fixed by: 98bc9fdaa431f274fe3a9fc538b0b562c6fad981

I tested Raiden IV.

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.

Closing bugs fixed in 3.13.

Removing the 3.0.x milestone from bugs included in 3.0.3.