Closed Blisto91 closed 4 months ago
The game apparently expects device lost signaling on alt+tab (as can be seen in the WineD3D trace):
It's worth checking out if @K0bin's d3d9 config option does anything in this case.
Forgot to note i already tried with d3d9.deviceLossOnFocusLoss
and it has the same issue.
Here is trace with it enabled Castlestrike-DeviceLost.trace.tar.gz
Turns out we were not releasing state blocks on calls to D3D8Device::DeleteStateBlock(), rather only removing their references from ye' olde state block set. That kept the D3D9 resources around as well, which caused the issues on device Reset. Should be fixed now in #172.
Confirmed fixed
Alt tabbing in Castle Strike will make you not able to go ingame again. This is likely due to some upstream work from a rebase.
Software information
Castle Strike
System information
Apitrace file(s)
Castlestrike.tar.gz One with d8vk and one with wined3d
Log files
Castlestrike_d3d8.log Castlestrike_d3d9.tar.gz