https://bugs.winehq.org/show_bug.cgi?id=41745
Bug ID: 41745 Summary: Killing Floor 2: Missing text Product: Wine Version: 1.9.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs@winehq.org Reporter: roman@hargrave.info Distribution: ---
Killing Floor 2 is now _functioning_ in that it is /navigable/ by human.
That being said, currently text is missing in all manner of locations, and this is possibly related to the following FIXME's in d3d11_immediate_context_OMSetBlendState
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented. fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}.
https://bugs.winehq.org/show_bug.cgi?id=41745
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3dx11 |-unknown Severity|major |normal
https://bugs.winehq.org/show_bug.cgi?id=41745
--- Comment #1 from roman@hargrave.info roman@hargrave.info --- Addend: these notes are also printed on each frame during gameplay.
https://bugs.winehq.org/show_bug.cgi?id=41745
acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acescopezz@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=41745
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #2 from Adam Bolte abolte@systemsaviour.com --- All text in KF2 is now rendered correctly. Previously the text of many menu options were not visible, but I am unable to reproduce that now.
For reference, tested using Wine 2.6 using a Fury X, Mesa 17.0.1 and the HCU/Software/Wine/Direct3D/MaxVersionGL REG_DWORD 0x00040005 (242149) registry key set (as indicated over at https://www.winehq.org/wwn/404#Direct3D%2011%20development). The game was launched using the -dx10 game launch option.
I tried setting the graphics options to Low, Medium, High and Ultra, and each of these rendered all in-game text fine. I even tried playing the game at Low and Ultra details, and completed a Normal length solo survival match on each. I briefly saw slight graphical corruption on one of the enemies at one point - everything else ran flawlessly. Frame rate was a little low for my liking, but quite playable. The Steam overlay wouldn't show for some reason so am not sure what FPS I was getting, but it felt around 25-30 at Ultra detail (at 2560x1440).
Without the -dx10 option, in game graphics are very corrupted making the game unplayable, but even then the menus and menu text is all rendered correctly. I believe this bug has been fixed and can be closed.
https://bugs.winehq.org/show_bug.cgi?id=41745
roman@hargrave.info roman@hargrave.info changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #3 from roman@hargrave.info roman@hargrave.info --- A/O (probably prior to) 2.9 the issue is no longer reproducible in any configuration using the Staging branch, and probably mainline.
https://bugs.winehq.org/show_bug.cgi?id=41745
roman@hargrave.info roman@hargrave.info changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WORKSFORME
--- Comment #4 from roman@hargrave.info roman@hargrave.info --- Changing to WFM - it seems more appropriate since I'm the only observer so far.
https://bugs.winehq.org/show_bug.cgi?id=41745
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=41745
--- Comment #6 from Ken Sharp imwellcushtymelike@gmail.com --- (In reply to roman@hargrave.info from comment #3)
probably mainline.
Testing is the only way to find out.