https://bugs.winehq.org/show_bug.cgi?id=41310
Bug ID: 41310 Summary: World in Conflict can't get past loading screen in tutorial Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: alex3kov@zoho.com Distribution: ---
Created attachment 55640 --> https://bugs.winehq.org/attachment.cgi?id=55640 Log with WINEDEBUG=+d3d9
1.0.1.1 version of the game from gog.com. After Alt-Tabbing or switching to another desktop workspace I can't get back into the game. Starting missions gets stuck in the same way.
According to setup manual here https://appdb.winehq.org/objectManager.php?sClass=version&iId=20703 I've set d3d10 to "Disabled", replaced dxdiagn with native and set it to "Native" in winecfg - so the game uses DX9.
Log with WINEDEBUG=+d3d9 is attached. It turned out to be 10Mb, so I gzipped it. These lines look suspicious: fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT! fixme:d3d:debug_d3dformat Unrecognized 0x41415353 (as fourcc: SSAA) WINED3DFORMAT!
I can provide more logs, test patches etc.
https://bugs.winehq.org/show_bug.cgi?id=41310
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #1 from winetest@luukku.com --- Alt+tabbing from application and it hangs seems to be somekind of regression I seem to have it too (with lot of apps, all?). Can you try virtual desktop and default output when trying to start the game?
https://bugs.winehq.org/show_bug.cgi?id=41310
Alex alex3kov@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alex3kov@zoho.com
--- Comment #2 from Alex alex3kov@zoho.com --- Created attachment 57199 --> https://bugs.winehq.org/attachment.cgi?id=57199 Trace on 2.0
This is a standard trace from Wine 2.0
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #3 from Alex alex3kov@zoho.com --- Enabling virtual desktop in winecfg produces the same result.
https://bugs.winehq.org/show_bug.cgi?id=41310
Alex alex3kov@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.18 |2.0
https://bugs.winehq.org/show_bug.cgi?id=41310
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |directx-d3dx9
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com ---
From the logs:
err:d3dcompiler:compile_shader HLSL shader parsing failed.
Installing a native d3dcompiler DLL should workaround it. One way to do that is with "winetricks directx9".
https://bugs.winehq.org/show_bug.cgi?id=41310
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #5 from fjfrackiewicz@gmail.com --- (In reply to Matteo Bruni from comment #4)
From the logs:
err:d3dcompiler:compile_shader HLSL shader parsing failed.
Installing a native d3dcompiler DLL should workaround it. One way to do that is with "winetricks directx9".
Another way is "winetricks d3dcompiler_43" :)
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #6 from Alex alex3kov@zoho.com --- (In reply to Matteo Bruni from comment #4)
From the logs:
err:d3dcompiler:compile_shader HLSL shader parsing failed.
Installing a native d3dcompiler DLL should workaround it. One way to do that is with "winetricks directx9".
After winetricks directx9 I'm getting "Critical error: DirectX9.0b must be installed to run WiC." Wine mentioned dx11 in the log, so I also installed d3dx11_42 d3dx11_43 (same result). Attaching trace.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #7 from Alex alex3kov@zoho.com --- Created attachment 57201 --> https://bugs.winehq.org/attachment.cgi?id=57201 Trace with installed directx9 d3dx11_42 d3dx11_43
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #8 from Alex alex3kov@zoho.com --- So with winetricks dxdiagn I can now enter tutorial. I'll play with it a bit more tomorrow and probably close this.
https://bugs.winehq.org/show_bug.cgi?id=41310
Alex alex3kov@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.0 |1.9.18
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #9 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to fjfrackiewicz from comment #5)
Another way is "winetricks d3dcompiler_43" :)
That only works if the game directly uses exactly d3dcompiler_43 or any of the d3dx9 dlls. Which is probably the case here, so for this game it's probably fine too.
(In reply to Alex from comment #8)
So with winetricks dxdiagn I can now enter tutorial.
That sounds like winetricks is broken somehow (or not up to date, I guess)
I'll play with it a bit more tomorrow and probably close this.
This is just a workaround, the bug is still valid.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #10 from Alex alex3kov@zoho.com --- (In reply to Matteo Bruni from comment #9)
I'll play with it a bit more tomorrow and probably close this.
This is just a workaround, the bug is still valid.
You mean WINE's d3d should be able to handle that without winetricks? If you come up with patches - I can test them on my WiC copy.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #11 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Alex from comment #10)
You mean WINE's d3d should be able to handle that without winetricks?
Yes, that's the idea.
If you come up with patches - I can test them on my WiC copy.
I won't have anything in the short term I'm afraid... Still this is something we want to fix eventually.
https://bugs.winehq.org/show_bug.cgi?id=41310
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #12 from Adam Bolte abolte@systemsaviour.com --- The Complete Edition (v1.0.1.1) is currently free from Ubisoft until the 12th December 2017 from here: https://www.ubisoft.com/en-au/event/world-in-conflict-giveaway/
I completed the entire tutorial without issue. I tried alt-tabbing to see if I could make it crash. I couldn't. I did notice there was about a 3 second delay before the game would resume, but it did not crash.
It was downloaded into a clean 32-bit wineprefix via Uplay and Wine Staging 2.21 (since Wine stable can't run Uplay). I then switched to Wine (non-staging) 2.22 to test the game by invoking wic.exe directly (after editing the config to switch to DirectX 9 mode).
At no point did I use winetricks or any DLL overrides. Tested on a Fury X using the AMDGPU Pro 17.40 "hybrid" driver stack under Xfce on Ubuntu 16.04.3 LTS. I think this bug is fixed.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #13 from Alex alex3kov@zoho.com --- Will Uplay work in 2.23? Currently fails on 2.20/2.21/2.22 with "A Ubisoft service currently not available."
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #14 from Alex alex3kov@zoho.com --- GOG.com version fails to start on 2.22 (clean win32 prefix, nothing added by winetricks). Attached wic_2.22.log.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #15 from Alex alex3kov@zoho.com --- Created attachment 59876 --> https://bugs.winehq.org/attachment.cgi?id=59876 Trace with WINEDEBUG=+d3d9 on 2.22, GOG version
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #16 from Adam Bolte abolte@systemsaviour.com ---
Will Uplay work in 2.23?
No. I used wine-staging 2.22 to get Uplay to work. No winetricks or DLL overrides or anything else.
Once downloaded, I switched the prefix over to using a clean Wine 2.23 build for testing.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #17 from Rafał Mużyło galtgendo@o2.pl --- wrt. gog version: given the lines: 01c6:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithDataSegs 01c6:fixme:faultrep:ReportFault 0x43fde64 0x0 stub
it might be that the game should be crashing here after writing a dump, which isn't implemented yet.
Perhaps it's some kind of hardware limitation, that isn't hit till the actual gameplay is about to start.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #18 from Rafał Mużyło galtgendo@o2.pl --- ...well, damn...
This is a bit more tricky than the previous comments suggest, mainly cause of high risk of a false positive on problem being solved.
It seems the only dll override needed is d3dx9_31.dll. The false positives come from caching.
In the same dir as "Game Options.txt" there's 'Shadercache' dir. Once it's filled by the override, on subsequent runs things work without the override...as long as that dir isn't removed, then 'rinse, rise, repeat'.
So, Alt-Tabbing is just a symptom, wine's lib is waiting for something to end (related to writing those cached shaders), that never does.
https://bugs.winehq.org/show_bug.cgi?id=41310
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.18 |1.6 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Component|d3d-util |hlsl Product|Wine |vkd3d
--- Comment #19 from Gijs Vermeulen gijsvrm@gmail.com --- I get a red screen when the game launches with wine-8.0rc2. Tested the GOG version. Forced d3dcompiler_43 and 47 to builtin.
https://bugs.winehq.org/show_bug.cgi?id=41310
--- Comment #20 from Gijs Vermeulen gijsvrm@gmail.com --- Created attachment 73787 --> https://bugs.winehq.org/attachment.cgi?id=73787 +d3dcompiler
https://bugs.winehq.org/show_bug.cgi?id=41310
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|World in Conflict can't get |World in Conflict crashes |past loading screen in |due to missing 'lit' |tutorial |handling
--- Comment #21 from Gijs Vermeulen gijsvrm@gmail.com --- Current problems:
0024:err:d3dcompiler:D3DCompile2 <anonymous>:31:8: E5005: Function "lit" is not defined.
-> this bug
0024:err:d3dcompiler:D3DCompile2 <anonymous>:20:16: E5005: Function "tex2D" is not defined.
-> bug 33979
0024:err:d3dcompiler:D3DCompile2 <anonymous>:7:1: E5017: Aborting due to not yet implemented feature: SM1 "cast" expression.
-> filed bug 54372
https://bugs.winehq.org/show_bug.cgi?id=41310
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d86db8bcbe5d0e2593d39864c7e | |5215bd643008f Resolution|--- |FIXED Status|NEW |RESOLVED
--- Comment #22 from Nikolay Sivov bunglehead@gmail.com --- lit() is now implemented, https://source.winehq.org/git/vkd3d.git/commit/d86db8bcbe5d0e2593d39864c7e52....
https://bugs.winehq.org/show_bug.cgi?id=41310
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Nikolay Sivov bunglehead@gmail.com --- Closing bugs fixed win 1.7.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla