[Bug 45927] New: Tom Clancy' s TheDivision.exe terminates itself a few seconds after launch
https://bugs.winehq.org/show_bug.cgi?id=45927 Bug ID: 45927 Summary: Tom Clancy's TheDivision.exe terminates itself a few seconds after launch Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: m4ng4n(a)gmx.de Distribution: --- Created attachment 62454 --> https://bugs.winehq.org/attachment.cgi?id=62454 Screenshot message box TheDivision My hardware/software/setup: - AMD FX 8320 - AMD Radeon RX580 - amdgpu open-source driver - openSUSE Tumbleweed 20180926 64-bit - Kernel 4.18.8-1-default 64-bit - Mesa 18.3 with LLVM 8.0 - Plasma 5.13.5 - wine 3.17 (I also tried with 3.17-staging, the results are the same) - uplay client from Thursday, September 27th 2018, running flawlessly and starting Watch Dogs and Splinter Cell Blacklist without problems - all tests on a fresh 64-bit Wine Prefix, only corefonts installed via winetricks (needed by uplay) Hello All, when I start Tom Clancy's The Division with uplay for the first time after downloading it, the launcher installs DX and vcrun correctly and after that it starts TheDivision.exe that terminates itself immediately. At every subsequent launch with uplay or from a terminal TheDivision.exe terminates itself wihtin a few seconds after launch. No logo or window or any kind of lifesign is to be seen. The only feedback I get is when I try to start it from a terminal: /games/Ubisoft/Tom Clancy's The Division> WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 wine TheDivision.exe 00d1:fixme:heap:RtlSetHeapInformation 0x7d0000 0 0x23e830 4 stub 00d1:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 102 00d1:err:seh:setup_exception stack overflow 1760 bytes in thread 00d1 eip 000000007bc63b8a esp 0000000000140f30 stack 0x140000-0x141000-0x240000 I tried to debug it with WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 winedbg TheDivision.exe but all I get is a message box - titled "TheDivision.exe" - that says: "A debugger has been found running in your system. Please, unload it from memory and restart your program." After clicking that message box away I can only quit the debugger. See the attched screenshot. This is my first debugging attempt and I am pretty much lost here. So I decided to create a log file with WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 WINEDEBUG=+relay wine TheDivision.exe as stated here, https://wiki.winehq.org/Wine_Developer%27s_Guide/Debugging_Wine#Debugging_Ti... and hope it is useful. I also managed to do a backtrace, once only, a couple of days ago because the exe is gone too fast to catch it. I do not know if it is of any use but will include it for further investigation. If you need any more debugging information just tell me and I will provide it. Thank you. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #1 from Freigeist <m4ng4n(a)gmx.de> --- Created attachment 62455 --> https://bugs.winehq.org/attachment.cgi?id=62455 TheDivision launch log.txt -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #2 from Freigeist <m4ng4n(a)gmx.de> --- Created attachment 62456 --> https://bugs.winehq.org/attachment.cgi?id=62456 TheDivision backtrace.txt -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Freigeist <m4ng4n(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Anthony Jagers <noonetinone(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noonetinone(a)gmail.com --- Comment #3 from Anthony Jagers <noonetinone(a)gmail.com> --- I'm wondering if DRM is stopping this from running. I get the same experience with this title as the OP. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #4 from Freigeist <m4ng4n(a)gmx.de> --- Revisiting. wine 3.19 The behaviour of TheDivision.exe is unchanged. The error messages when started in a terminal are unchanged. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #5 from Freigeist <m4ng4n(a)gmx.de> --- Revisiting. wine 3.21 and wine 3.21-staging Using the Uplay client the behaviour of TheDivision.exe with wine 3.21 is unchanged. I also tried with wine 3.21-staging. The behaviour is the same as with wine 3.21. Ment as a heads up: I was curious and did some experimenting and installed the windows Steam client in its own fresh 64bit-prefix, together with corefonts and dxvk93, under 3.21-staging and the trial version of The Division in Steam and very much to my surprise it started and worked. It has sound and is somewhat hard to play at first due to some heavy lagging, but it launches and is working. What makes this so surprising is that both installations - the one from the Uplay client and the other one from Steam - seem to be identical, but one of them (Steam) is working with wine and the other one (Uplay) is not and this despite the fact, that both installations run the same Uplay client to launch the game. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #6 from Anthony Jagers <noonetinone(a)gmail.com> --- Well, it's on sale. So, I'll take it rather than leave it. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #7 from Anthony Jagers <noonetinone(a)gmail.com> --- I just finished downloading the steam version and it works. There was some lag and stuttering when the game first starts up, but things will settle down. I ran it with the staging patches & dxvk. I would need to try it with wined3d and with vanilla wine trunk before giving it a gold rating. Right now I give it silver but it's completely playable. I tried the demo version about a month ago and I couldn't get it to work. Maybe the demo is too old to run. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #8 from Freigeist <m4ng4n(a)gmx.de> --- Revisiting. wine 4.01 and wine 4.01-staging Using the Uplay client the behaviour of TheDivision.exe with wine 4.01 & 4.01-staging is unchanged. Trying to run the steam demo with steam for windows stopped working for me. The error message is the same as in comment #1 -> 008e:err:seh:setup_exception stack overflow 1776 bytes in thread 008e eip 000000007bc807aa esp 0000000000140f20 stack 0x140000-0x141000-0x240000 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #9 from Anthony Jagers <noonetinone(a)gmail.com> --- I can't get it to work any more. I think denuvo is stopping the game to run. See Bug 46548. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #10 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Anthony Jagers from comment #9)
I can't get it to work any more. I think denuvo is stopping the game to run. See Bug 46548.
I am not sure about that. How do you come to that conclusion? I did not know about denuvo and did a search and found this wikipedia entry: https://en.wikipedia.org/wiki/Denuvo "The Division" is not listed there. Oth there are roughly a dozen games listed as using denuvo that I own and that run flawlessly with a current wine installation on my machine. Battlefield Hardline and Battlefield 1 being just two examples. I also did not find any clues in my wine-division-prefix hinting about denuvo's presence in the installation. What came to my mind instead is that it might have something to do with the package versions on our systems that are addressed by wine's fake dlls. If these are changing because of an update one or more libraries could stop working the way they used to during the short timespan in which The Division was working. Oth, at least on my machine, there is no hint in the logs about a library not working anymore, so I am still clueless about what might have changed. I do not know what distro you are using but - as I am using openSUSE Tumbleweed, which is rolling - my system has had countless updates/upgrades since the end of november. What about your system? Has it been unchanged since the end of november and only wine itself has been updated to newer versions? Knowing that could give us a hint to probably rule out a system package/library update as a possible reason why The Division stopped working. Other than that I am out of ideas right now. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #11 from Anthony Jagers <noonetinone(a)gmail.com> --- Your error reported in comment 8 is what I get. I don't get any system updates that would break this game since I use a hand cranked Linux from Scratch system. And I don't appreciably alter my wine prefixes(e.g. with winetricks) that would help to explain this. Later on I'll do some more digging and get back to you. You should read my comments at Bug 46548. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #12 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Anthony Jagers from comment #11)
Your error reported in comment 8 is what I get. I don't get any system updates that would break this game since I use a hand cranked Linux from Scratch system. And I don't appreciably alter my wine prefixes(e.g. with winetricks) that would help to explain this. Later on I'll do some more digging and get back to you.
Great, thanks.
You should read my comments at Bug 46548.
I did but forgot to mention that I checked the timestamps on my The Division installations after reading your comments. The results are interesting: 1. Uplay-Installation, I own the game, it never worked, see comment #0 -rwxr-xr-x 1 atze users 29301448 Oct 2 20:22 TheDivision.exe 2. Steam for Windows Installation, Demo version of the game, worked between 26.11.18 and maybe the end of december 2018 (cannot say for sure) -rwxr-xr-x 1 atze users 29301448 Oct 10 20:37 TheDivision.exe Both files have timestamps way before 26.11.18 (comment #5) so they have not changed/were not updated on my system since their respective timestamps. Just as you did I also tried to get The Division working again by installing wine 3.21 and 3.21 staging & dxvk 0.93 via lutris but that did not work either. Maybe using the lutris wine versions here was a mistake. I don't know. I will give it a new try with wine 3.21 and 3.21-staging from winehq as soon as I have some time and get back. Concerning my prefixes - one for the uplay installation, the other for steam for windows, both are testing prefixes for The Division exclusively - I only have corefonts and dxvk installed. This has not changed since my first try to run The Division. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #13 from Anthony Jagers <noonetinone(a)gmail.com> --- I ran md5sum on the executable. d691f47ea7c6919d8c879003fdb44aa5 thedivision.exe Do you get the same? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |isakov-sl(a)bk.ru --- Comment #14 from Sergey Isakov <isakov-sl(a)bk.ru> --- is it possible bug 46601 has the same origin? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #15 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Anthony Jagers from comment #13)
I ran md5sum on the executable. d691f47ea7c6919d8c879003fdb44aa5 thedivision.exe Do you get the same?
TheDivision.exe in the uplay prefix: d691f47ea7c6919d8c879003fdb44aa5 TheDivision.exe TheDivision.exe from the trial installation in the Steam for Windows prefix: d691f47ea7c6919d8c879003fdb44aa5 TheDivision.exe -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #16 from Anthony Jagers <noonetinone(a)gmail.com> --- That err:seh line given in Comment 8 says that the game is in an exception loop that it can't get out of until the stack is exhausted. I found some information on the error on the wine wiki page for Wild Metal Country. There it talks about debugging this to figure out why the first exception occurs. https://wiki.winehq.org/Debugging_Wild_Metal_Country In Comment 8 the finale exhausted exception is in a thread identified by '008e'. The offending thread id changes every time the games is ran. Stepping into that thread, will help us fix this. One problem I ran into is it appears that the debug channel +relay kills the other channels that I need, namely err:seh. Hence, the line in Comment 8 is ommitted in a multithreaded application with the +relay channel. Getting usable +relay console output has been elusive. I've asked for help in the forums. https://forum.winehq.org/viewtopic.php?f=2&t=31987 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #17 from Freigeist <m4ng4n(a)gmx.de> --- Created attachment 63571 --> https://bugs.winehq.org/attachment.cgi?id=63571 TheDivision log excerpt with +relay,+seh -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #18 from Freigeist <m4ng4n(a)gmx.de> ---
One problem I ran into is it appears that the debug channel +relay kills the other channels that I need, namely err:seh. Hence, the line in Comment 8 is ommitted in a multithreaded application with the +relay channel. Getting usable +relay console output has been elusive. I've asked for help in the forums.
WINEDEBUG=+relay,+seh is working for me. It produced a 4.7 Gig logfile. An excerpt is attached. In line 24 the log says 8606.086:00ea:trace:seh:call_handler handler at 0x14634fbf5 returned 1 In line 48 it says 8606.087:00ea:trace:seh:call_vectored_handlers handler at 0x6f266b70 returned 0 8606.087:00ea:err:seh:setup_exception stack overflow 1840 bytes in thread 00ea eip 00007f96c21c6c7a esp 0000000000140ee0 stack 0x140000-0x141000-0x240000 Probably the handler at 0x6f266b70 should not return 0? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #19 from Anthony Jagers <noonetinone(a)gmail.com> --- No Way! The game actually just started working again with Staging 4.2(git)! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #20 from Freigeist <m4ng4n(a)gmx.de> --- wine 4.2 and wine 4.2-staging Using the Uplay client the behaviour of TheDivision.exe with wine 4.2 and 4.2-staging is unchanged. A log excerpt with WINEDEBUG=+seh,+tid,+timestamp,+relay is attached. The steam demo version of The Division is only running with wine 4.2-staging not with wine 4.2. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #21 from Freigeist <m4ng4n(a)gmx.de> --- Created attachment 63611 --> https://bugs.winehq.org/attachment.cgi?id=63611 TheDivision log excerpt with +relay,+seh, wine 4.21-staging -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #22 from Anthony Jagers <noonetinone(a)gmail.com> --- Created attachment 63621 --> https://bugs.winehq.org/attachment.cgi?id=63621 a working log from 4.2 staging This is my +seh log from 4.2 staging. There are no err:seh errors. I tried to get +relay, but after about 18 gigs of lines I shut it off. How did you set up your prefix? Maybe lutris can help. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #23 from Anthony Jagers <noonetinone(a)gmail.com> --- Now I can only tell you about my prefixes and how I put them together. I jump start them by running winetricks steam. Even if you are not running the steam version of Division, winetricks could still give you a better and more viable prefix setting up steam. I have been setting up multiple prefixes and just talking the entire steam folder in "Program Files" with me when I go. If I had to guess what my problem was which 4.2 solved for me was the work done on built-in dll's which are named api-ms-win-crt-*.dll. Remember that I could run it at Thanksgiving but couldn't duplicate my success. I must have imported a bad dll with winetricks since then. It's just a hunch. Below are some note that I could gather about two prefixes which can run the game. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #24 from Anthony Jagers <noonetinone(a)gmail.com> --- Created attachment 63640 --> https://bugs.winehq.org/attachment.cgi?id=63640 Info on my default prefix Excised from the log is any mentioning of XAudio dlls, which are quite numerous. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #25 from Anthony Jagers <noonetinone(a)gmail.com> --- Created attachment 63641 --> https://bugs.winehq.org/attachment.cgi?id=63641 about another backup prefix If there is anyway I can help you or you need any additional info, ask. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #26 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Anthony Jagers from comment #25)
Created attachment 63641 [details] about another backup prefix
If there is anyway I can help you or you need any additional info, ask.
Thank you very much for your help, very much appreciated! To answer your question from comment 22, both of my prefixes have only corefonts and dxvk96 via winetricks installed, everything else is out of the box. I will give the uplay-division prefix a try with your settings and get back here. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #27 from Anthony Jagers <noonetinone(a)gmail.com> --- I took the liberty of bisecting this to determine the first staging commit that would run the game for me. The commit is below: ecc4fe6d6a0809fdebc8e294939a9a1d7b57abe0 which are patch onto wine at commit: f7b3120991df02ecaa975c18c6421fedb48ae731 The previous bad commit is staging: 35f9449641aa3ffe94e3daf765de35c3ab5b119a which patches onto wine commit: 957a1f0216995c14c3a3fe737358578a506af707 The commits on staging side(ecc4) don't look like they would have affected a wine component to get the game running for me. However on the wine side of things. Staging has to rebase to quite an extensive number of commits. They fall on the weekend and go from 77b to 957. The one commit which catches my eye is: 01b8a795952b460189fc1fc91eff8e733c4e053d setupapi: Add stub for CM_Get_Sibling. dlls/api-ms-win-devices-config-l1-1-0 dlls/api-ms-win-devices-config-l1-1-1 ______ I did all of this assuming I actually need to staging patches. I'll dig a little more. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Kikongo Strain <59b_44fc0dyc4okf(a)vermutlich.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |59b_44fc0dyc4okf(a)vermutlich | |.net --- Comment #28 from Kikongo Strain <59b_44fc0dyc4okf(a)vermutlich.net> --- I followed this bug for some time and recently tested it again. I have the uplay version and it never worked for me. With 4.2-staging it doesn't work, too. I tried the Steam Demo but it's the same result (even with 4.2-staging or I'm doing it wrong) Tried multiple (new) prefixes w/ or w/o dxvk, esync or other settings Setup: Intel i5 4210U Nvidia GeForce 840M (415.27) Ubuntu 18.04.2 (64 Bit) Kernel: 4.15.0-46.49 Everything up to date -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #29 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Anthony Jagers from comment #23)
Now I can only tell you about my prefixes and how I put them together.
I installed all the verbs/dlls that you have installed one by one in my division prefix and it did not work. Also, to exclude that it could be possibly DE related (I have Plasma 5.15 installed), I did a test installation of openSUSE Tumbleweed and tested with the following DEs: i3wm, LXQT, XFCE and Gnome. The result is the same as with Plasma 5: err:seh:setup_exception stack overflow 1760 bytes. I also tried in a new prefix to set all api-ms-win-*.dlls which are present in the The Division game directory manually to native, builtin, with the same result. But I finally found a workaround but I did not log it yet. The fact that The Division demo starts but the uplay installation doesn't does not make sense. So I thought it could be related to the fact that the demo version is started by the steam client which then starts uplay and it is! My workaround for those of you that own the uplay version of The Division: 1. Make a separate prefix for The Division only. I called it wine-division-64 2. From now on do every step below pointing wine to this prefix with WINEPREFIX=$HOME/.wine-division-64 (or whatever you called your prefix) 3. Install corefonts and dxvk96 with winetricks 4. Install the uplay client, start it and point it to your existing The Division installation, otherwise download and install The Division. When finished close the uplay client 5. Install Steam for windows in the same prefix and let it run 6. In the Steam client goto "Games" -> "Add a non-steam game to my library" and choose the uplay client 7. Start the uplay client with steam 8. Disable the in-game overlay in the uplay client and in steam. Otherwise the game might crash when it tries to login on the Ubisoft servers 9. Start The Division from the uplay client 10. Play The Division Andreas -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #30 from Freigeist <m4ng4n(a)gmx.de> --- Created attachment 63689 --> https://bugs.winehq.org/attachment.cgi?id=63689 uplay started with steam for windows and The Division working One more thing: 1. When you start Steam from command line and see the following output: 01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub and The Division does not start within 30 to 60 seconds after, then it just hangs somewhere. In this case kill the TheDivision.exe process and start it again with the uplay client. Attached is a log of the terminal output (without any debug channels enabled for now) that contains - Steam for windows start - uplay client start from within steam - The Division start with the uplay client and gameplay for roughly 10 mins -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #31 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to Freigeist from comment #30)
One more thing:
1. When you start Steam from command line and see the following output:
^^^^^This should say: When you start Steam from command line and clicked on "Play The Division" in the uplay client and see the following output:
01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub
and The Division does not start within 30 to 60 seconds after, then it just hangs somewhere. In this case kill the TheDivision.exe process and start it again with the uplay client.
-- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 sahelanthropus <3dw_50ssu16amyn7(a)byom.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |3dw_50ssu16amyn7(a)byom.de --- Comment #32 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- (In reply to Freigeist from comment #30)
1. When you start Steam from command line and see the following output:
01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub
I tried the steps you provided and got further than before. Before I got stuck at the loading spinner in uplay launching The Division, now it finishes the loading, asks me to enable uplay overlay and starts TheDivision.exe Two TheDivision.exe (and their parents x64launcher.exe) get started and after some seconds all turn into Zombie processes. I don't get the error output you mentioned. I added an attachment with the console output I get when clicking the 'Play' button in uplay --- Comment #33 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- Created attachment 63765 --> https://bugs.winehq.org/attachment.cgi?id=63765 wine 4.2-staging uplay with steam for windows and The Division not working -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 sahelanthropus <3dw_50ssu16amyn7(a)byom.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |3dw_50ssu16amyn7(a)byom.de --- Comment #32 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- (In reply to Freigeist from comment #30)
1. When you start Steam from command line and see the following output:
01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub
I tried the steps you provided and got further than before. Before I got stuck at the loading spinner in uplay launching The Division, now it finishes the loading, asks me to enable uplay overlay and starts TheDivision.exe Two TheDivision.exe (and their parents x64launcher.exe) get started and after some seconds all turn into Zombie processes. I don't get the error output you mentioned. I added an attachment with the console output I get when clicking the 'Play' button in uplay --- Comment #33 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- Created attachment 63765 --> https://bugs.winehq.org/attachment.cgi?id=63765 wine 4.2-staging uplay with steam for windows and The Division not working -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #34 from Anthony Jagers <noonetinone(a)gmail.com> --- If the steam client can start the demo version then maybe it will start the retail version if you substitute the uplay games files for the demo in it's place. It already has the same md5sum. Steam won't know the difference. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #35 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- (In reply to Anthony Jagers from comment #34)
If the steam client can start the demo version then maybe it will start the retail version if you substitute the uplay games files for the demo in it's place.
It already has the same md5sum. Steam won't know the difference.
The Steam demo has a similar problem for me, it ain't working. TheDivision.exe starts and takes a one full core 100% for now an hour. All game files are verified. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #36 from Freigeist <m4ng4n(a)gmx.de> --- First things first. Revisiting. wine 4.3 and wine 4.3-staging Using the uplay client I can confirm that with both wine versions the error is gone. It is now possible for me to run the The Division without the workaround in comment 29 with the uplay client directly. For others to test: This is the way that worked for me 1. Make a new separate prefix for The Division only. I called it wine-division-64 2. From now on do every step below pointing wine to this prefix with WINEPREFIX=$HOME/.wine-division-64 (or whatever you called your prefix) 3. Install corefonts and the latest dxvk with winetricks 4. Install the uplay client, start it from the commandline and point it to your existing The Division installation, otherwise download and install The Division. 5. Disable the in-game overlay in the uplay client. Otherwise the game might crash when it tries to login to the Ubisoft servers 6. Start The Division with the uplay client 7. When you start the uplay client from command line and clicked on "Play The Division" and see the following output on the command line and the command line output stops there: 01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub and The Division does not start within 30 to 60 seconds after you clicked on start, then it just hangs somewhere. In this case kill the TheDivision.exe process and start it again with the uplay client. On wine 4.3 this happened to me 3 or 4 times before The Division finally started. 8. Now give it a try on your machines -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #37 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to sahelanthropus from comment #32)
Two TheDivision.exe (and their parents x64launcher.exe) get started and after some seconds all turn into Zombie processes. I don't get the error output you mentioned.
I added an attachment with the console output I get when clicking the 'Play' button in uplay
1. There is this error in your log that got this bug report started in the first place. Look at line 89 of your log: 00e2:err:seh:setup_exception stack overflow 1776 bytes in thread 00e2 eip 000000007bc7d14a esp 0000000000130f20 stack 0x130000-0x131000-0x230000 2. There are also these lines in your log, lines 6, 57 and 97: 007c:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. I don't know if this spells trouble but it should be easy to fix to exclude it as a possible cause for (further) trouble. Open a terminal and enter "ntlm_auth --version". If your version is < 3.0.25 or simply not present update/install winbind with your package manager. 3. Give wine 4.3(-staging) a try instead of using 4.2 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #38 from Freigeist <m4ng4n(a)gmx.de> --- I forgot to mention that occasionally if you quit the division it does not terminate correctly with "017f:err:ntdll:RtlpWaitForCriticalSection section 0x7fc5e3698ec8 "?" wait timed out in thread 017f, blocked by 0114, retrying (60 sec)" showing up in the console. This line gets repeated every 60 seconds. In that case I could only Ctrl-Alt-F2 to a new console and kill the TheDivision.exe process from there. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #39 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- Its working! Installed winbind, wine4.3-staging and now after the second try in uplay The Division starts via uplay + steam windows (In reply to Freigeist from comment #38)
I forgot to mention that occasionally if you quit the division it does not terminate correctly with
"017f:err:ntdll:RtlpWaitForCriticalSection section 0x7fc5e3698ec8 "?" wait timed out in thread 017f, blocked by 0114, retrying (60 sec)"
showing up in the console.
I have this too. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #40 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- Created attachment 63780 --> https://bugs.winehq.org/attachment.cgi?id=63780 wine4.3-staging uplay only Division freeze after some seconds Looks like it's now 'working' without Steam for windows aka uplay only. During the whole game the console displays 'info: Presenter: Actual swap chain properties' (present mode switches between 'VK_PRESENT_MODE_IMMEDIATE_KHR' and 'VK_PRESENT_MODE_FIFO_KHR'), many times more than in Freigeist's log attachment. I attached console output when The Division froze seconds after being ingame. It suddenly either uses a full core at 100% and freezes without any console output or there's 'VK_ERROR_DEVICE_LOST' at the end of the log (see second attachment) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #41 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- Created attachment 63781 --> https://bugs.winehq.org/attachment.cgi?id=63781 wine4.3-staging uplay only Division VK_ERROR_DEVICE_LOST -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #42 from Freigeist <m4ng4n(a)gmx.de> --- (In reply to sahelanthropus from comment #40) Are you identical to the guy in comment 28 who sports the following hardware specs: Setup: Intel i5 4210U Nvidia GeForce 840M (415.27) Ubuntu 18.04.2 (64 Bit) Kernel: 4.15.0-46.49 I am asking because in your logs a Geforce 840M is mentioned. Anyway, it looks like that your hardware does not fulfil the minimum system requirements. Please check this for yourself on the steam page.
I attached console output when The Division froze seconds after being ingame. It suddenly either uses a full core at 100% and freezes without any console output or there's 'VK_ERROR_DEVICE_LOST' at the end of the log (see second attachment)
The problem you have, besides from that your hardware seems to be insufficient to run The Division, looks rather dxvk related. So please open an issue about your problem with the dxvk developer there: https://github.com/doitsujin/dxvk -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Freigeist <m4ng4n(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #43 from Freigeist <m4ng4n(a)gmx.de> --- Since nobody is complaining that this bug still exists I will close this now as 'RESOLVED'/'Fixed' in wine-4.3. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #44 from sahelanthropus <3dw_50ssu16amyn7(a)byom.de> --- (In reply to Freigeist from comment #42)
(In reply to sahelanthropus from comment #40)
Are you identical to the guy in comment 28 who sports the following hardware specs:
I am asking because in your logs a Geforce 840M is mentioned. Anyway, it looks like that your hardware does not fulfil the minimum system requirements. Please check this for yourself on the steam page.
I'm not that person, the only thing that person and I have in common is the graphics card. I know it's under the minimum system requirements but it runs flawless under Windows. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions(a)gmail.com --- Comment #45 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 46548 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 --- Comment #46 from Berillions <berillions(a)gmail.com> --- It does not work for me. I can launch the game but when i want to validate the character creation, the game crashes. I have the demo. @Freigeist : Will you buy The Division 2 ? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45927 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #47 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 4.4. -- 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.
participants (1)
-
wine-bugs＠winehq.org