[Bug 24063] World in conflict fails to start in DX10 mode
wine-bugs at winehq.org
wine-bugs at winehq.org
Wed Dec 6 06:00:32 CST 2017
https://bugs.winehq.org/show_bug.cgi?id=24063
Adam Bolte <abolte at systemsaviour.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abolte at systemsaviour.com
--- Comment #5 from Adam Bolte <abolte at systemsaviour.com> ---
Created attachment 59875
--> https://bugs.winehq.org/attachment.cgi?id=59875
WINEDEBUG="+d3d10" wine wic.exe (Wine 2.22)
This game is currently free from Ubisoft until the 12th December 2017 from
here:
https://www.ubisoft.com/en-au/event/world-in-conflict-giveaway/
Once downloaded, it does not require or launch Uplay to function and can be
started directly.
D3D10 mode is toggled by editing "My Documents/World in Conflict\Game
Options.txt" and setting "myDX10Flag" to 1. This seemed to be the default when
I tried it.
Still an issue in Wine 2.22 and Wine Staging 2.21. No DLL overrides are
required for D3D9 mode (which seems to work perfectly as is for what little I
tested), and when running in D3D10 mode there is no stack trace generated when
the game fails to launch - the game does nothing and finally exits cleanly.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list