https://bugs.winehq.org/show_bug.cgi?id=46612
Bug ID: 46612 Summary: wine-staging 4.1 breaks all Battlefield Versions Product: Wine-staging Version: 4.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: llenort@aol.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Wine 4.1 breaks all Battlefield Versions tested.
BF 3, BF 4, BF 1, BF 5
downgrade to Version 4.0 fix all versions. When 4.1 is installed all BF Versions simply not start. The Version shows no unexpected output for me. So i don't know where the problem is.
My context:
HW: Ryzen 7, NV RTX 2080, 16 GB SW: Linux OS Opensuse 15, wine-staging, dxvk 0.96
Thank you for your outstanding work on wine and wine-staging! lle
https://bugs.winehq.org/show_bug.cgi?id=46612
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia@gmail.com Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- Is it known which Staging patches are necessary for Battlefield to run? Can someone try to perform a bisect between upstream Wine 4.0 and 4.1 by applying the necessary staging patches on each iteration?
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #2 from lle llenort@aol.com --- Hi,
i try to install a fresh wine 4.1 (not wine-staging) and want to start the Origin Client to test BF Titles. But i can‘t login. Origin start and then the OriginWebHelperService.exe crash.
Try to cancel but the OriginWebHelperService.exe will restart by wine an crash immediately over and over again. So can‘t test the BF game with wine 4.1. I mean the WebHelper will use the Qt5 Framework so maybe we need the vcrun2017 ?! But this would be strange because i don‘t installed the vcrun2017 Version in 4.0 wine-staging and can start Origin and any BF Title without any Problems?!
Maybe we don‘t have a staging problem here? Has somebody successfully installed and played any BF (4,1,V) Title with wine version 4.1 or even 4.1 Staging?!
Again, thanks for any Help and Support. lle
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- Another kind user has graciously agreed to do a regression test, and come up with https://github.com/wine-staging/wine-staging/commit/7a2d7b751df3ee2bdcf0337e... as the breaking point.
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hans@meelstraat.net
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |7a2d7b751df3ee2bdcf0337e9f7 | |ac6f469b49555
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #4 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Zebediah Figura from comment #3)
Another kind user has graciously agreed to do a regression test, and come up with https://github.com/wine-staging/wine-staging/commit/ 7a2d7b751df3ee2bdcf0337e9f7ac6f469b49555 as the breaking point.
Based off this commit, then a +bcrypt log would help.
https://bugs.winehq.org/show_bug.cgi?id=46612
Anthony Jagers noonetinone@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |noonetinone@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #5 from Anthony Jagers noonetinone@gmail.com --- I was wondering why BF5 quit working.
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |bcrypt Product|Wine-staging |Wine
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- The requisite commits are in Wine now, so let's move this to the Wine product.
https://bugs.winehq.org/show_bug.cgi?id=46612
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|7a2d7b751df3ee2bdcf0337e9f7 | |ac6f469b49555 |
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #7 from Anthony Jagers noonetinone@gmail.com --- Do you still need a +bcrypt log? If so then I'll get back to you in 4 hours.
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |73b695f059740715ebd3ea0ce3c | |e88477977e628
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- (In reply to Anthony Jagers from comment #7)
Do you still need a +bcrypt log? If so then I'll get back to you in 4 hours.
Yes, if it's still broken with latest wine master that would probably be helpful.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #9 from Anthony Jagers noonetinone@gmail.com --- Created attachment 63585 --> https://bugs.winehq.org/attachment.cgi?id=63585 requested bcrypt log
The requested +bcrypt log. Origins output comes first. No problems with that but I kept it in anyway. The game starts at line 50434.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #10 from Hans Leidekker hans@meelstraat.net --- (In reply to Anthony Jagers from comment #9)
Created attachment 63585 [details] requested bcrypt log
The requested +bcrypt log. Origins output comes first. No problems with that but I kept it in anyway. The game starts at line 50434.
Does the game start if you revert to the commit before 73b695f059740715ebd3ea0ce3ce88477977e628?
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #11 from Anthony Jagers noonetinone@gmail.com --- Yes it would start if I tried. I already compiled a 4.1 staging build skipping earlier gcrypt work. The game was fine.
Those two staging commits which first break bfv are: d25f4cf2e21617a5eb2551c775a09b8f854f96d2 7a2d7b751df3ee2bdcf0337e9f7ac6f469b49555
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #12 from Hans Leidekker hans@meelstraat.net --- (In reply to Anthony Jagers from comment #11)
Yes it would start if I tried. I already compiled a 4.1 staging build skipping earlier gcrypt work. The game was fine.
Those two staging commits which first break bfv are: d25f4cf2e21617a5eb2551c775a09b8f854f96d2 7a2d7b751df3ee2bdcf0337e9f7ac6f469b49555
How about plain Wine?
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #13 from Anthony Jagers noonetinone@gmail.com --- I see what you need. A log from 4.2 might different that the earlier one that was based off of bcrypt work from staging.
I'll get you one.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #14 from Anthony Jagers noonetinone@gmail.com --- plain wine
Origin need some staging patches. I don't know which specific ones are needed.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #15 from Anthony Jagers noonetinone@gmail.com --- Congrats to you Hans!
The game indeed does start with Wine 4.2 Staging! I did not alter the wine source. other than apply the staging patches.
You deserve a raise! This bug needs closing.
https://bugs.winehq.org/show_bug.cgi?id=46612
lle llenort@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #16 from lle llenort@aol.com ---
Hello and yes, congrats to Hans Leidekker. Can confirm all BF Titles start with wine staging 4.2
Seems this bug is history :-) Many thank to all of you for your amazing work!
All the Best lle
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Ever confirmed|0 |1 Resolution|FIXED |---
--- Comment #17 from Zebediah Figura z.figura12@gmail.com --- Another user reports that Battlefield currently does not work with Staging 4.2. Reverting to the commit before 73b695f059740715ebd3ea0ce3ce88477977e628 doesn't help, reportedly because those changes were necessary to get Battlefield to work in the first place.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #18 from Anthony Jagers noonetinone@gmail.com --- I don't know what to tell you. It works.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #19 from lle llenort@aol.com --- Hi,
has the other user some more information. Did he use dxvk and the nvapi64 workaround? Maybe this will be the problem?
I tested the following BF Versions 3, 4, 1 and 5. Not only starting the game. Playing online and solo missions. Works very well.
Here some more Information on my setup.
- Wine-staging 4.2 64 Bit Prefix - opensuse Leap 15.0 - deintalled nouveau and use nvidia beta vulkan drivers (current 418.30) - kernel version 4.20.10.x - mesa 18.3.4 - dxvk 0.96
dllOverride
"*d3d10"="native" "*d3d10_1"="native" "*d3d10core"="native" "*d3d11"="native" "*d3dcompiler_46"="native" "*d3dcompiler_47"="native" "*dxgi"="native" "*nvapi64"="" "*x3daudio1_0"="native,builtin" "*x3daudio1_1"="native,builtin" "*x3daudio1_2"="native,builtin" "*x3daudio1_3"="native,builtin" "*x3daudio1_4"="native,builtin" "*x3daudio1_5"="native,builtin" "*x3daudio1_6"="native,builtin" "*x3daudio1_7"="native,builtin" "*xapofx1_1"="native,builtin" "*xapofx1_2"="native,builtin" "*xapofx1_3"="native,builtin" "*xapofx1_4"="native,builtin" "*xapofx1_5"="native,builtin" "*xaudio2_0"="native,builtin" "*xaudio2_1"="native,builtin" "*xaudio2_2"="native,builtin" "*xaudio2_3"="native,builtin" "*xaudio2_4"="native,builtin" "*xaudio2_5"="native,builtin" "*xaudio2_6"="native,builtin" "*xaudio2_7"="native,builtin"
- using a dxvk.conf file with:
# graphic card id (rtx2080). Will be different on other Versions like gtx 970/1080 ... dxgi.customDeviceId = 1E87 # This will be the same for nvidia cards dxgi.customVendorId = 10DE
Maybe this will help.
All the Best lle
https://bugs.winehq.org/show_bug.cgi?id=46612
Tk ti3nou@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ti3nou@gmail.com
--- Comment #20 from Tk ti3nou@gmail.com --- I'm the user Zebediah was talking about.
Here are more details about my issue: BF3, BF4 and BF1 are working perfectly fine with staging 4.0 4f5ec55. The following staging commit, 7a2d7b7 (based on the same wine commit, 152cda3), breaks all of them.
While trying to run the game with 7a2d7b7 I get an error message asking to verify the game. Doing so has no effect of course. I can still run both games fine with 4f5ec55 afterwards. I'm assuming that issue was bcrypt related and is now fixed.
However on staging 4.2 release (or master), none of these games are running (the process dies on itself instantly on launch) and no error message shows up. I have tried on a new prefix as well with no difference. As soon as I switch back to 4f5ec55 they are all able to run again.
No other game seems to be affected and I can run my other Origin games with no issue. It doesn't seem to be a dependency or configuration issue as it's running absolutely fine on 4f5ec55.
I'm on Arch with the usual nvapi/nvapi64 disabled, DXVK master etc.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #21 from Anthony Jagers noonetinone@gmail.com --- You can start by verifying the games files. There was a massive 8 gig patch released last week. I have to let the Origin client just sit there for four seconds are pressing 'Play'. I don't know what its doing but the BFV windows will pop up.
The breakage of staging commit,7a2d7b7 , mirrors my experience and I just simply backed up one commit until the 4.2 release.
Some console output would be nice.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #22 from Tk ti3nou@gmail.com --- The log output looks uninteresting as is, but I don't know what to search for as +bcrypt showed nothing of interest to Zebediah. Game exe dies instantly and I can spam it as much as I want, the outcome is always the same.
This is the whole output when trying to launch, in this case, BF1.
0009:fixme:netprofm:list_manager_GetConnectivity 0x13e52510, 0x33c060 008e:fixme:file:ReplaceFileW Ignoring flags 2 008e:fixme:file:ReplaceFileW Ignoring flags 2 0009:fixme:netprofm:list_manager_GetConnectivity 0x14e11b98, 0x33c060 0009:fixme:netprofm:list_manager_GetConnectivity 0x14c0c098, 0x33c060 0009:fixme:netprofm:list_manager_GetConnectivity 0x13d6ced0, 0x33c060 008e:fixme:file:ReplaceFileW Ignoring flags 2 0009:fixme:netprofm:list_manager_GetConnectivity 0x14ba9d80, 0x33c060 0009:fixme:netprofm:list_manager_GetConnectivity 0x8aafd68, 0x33c060 0009:fixme:netprofm:list_manager_GetConnectivity 0x14a952b0, 0x33c060 0009:fixme:netprofm:list_manager_GetConnectivity 0x13e37790, 0x33c060 0043:fixme:file:FindFirstFileExW flags not implemented 0x00000002 warn: D3D11Texture2D::QueryInterface: Unknown interface query warn: f8fb5c27-c6b3-4f75-a4c8-439af2ef564c warn: D3D11Texture2D::QueryInterface: Unknown interface query warn: f8fb5c27-c6b3-4f75-a4c8-439af2ef564c 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:ntdll:server_ioctl_file Unsupported ioctl 110004 (device=11 access=0 func=1 method=0) 0009:fixme:wbemprox:client_security_SetBlanket 0x73072958, 0x13d44390, 10, 0, (null), 3, 3, (nil), 0x00000000 0009:fixme:wbemprox:client_security_Release 0x73072958 opened using SMOID 104 00d6:fixme:wbemprox:client_security_SetBlanket 0x7c2d9958, 0x1693d8, 10, 0, (null), 3, 3, (nil), 0x00000000 00d6:fixme:wbemprox:client_security_Release 0x7c2d9958 00d5:fixme:msvcrt:__clean_type_info_names_internal (0x6105f890) stub 00d5:fixme:msvcrt:__clean_type_info_names_internal (0x1113b488) stub 00d5:fixme:msvcrt:__clean_type_info_names_internal (0x6411ada4) stub 00d5:fixme:msvcrt:__clean_type_info_names_internal (0x658dad74) stub 00d5:fixme:msvcrt:__clean_type_info_names_internal (0x672bbe9c) stub 00d3:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 00d3:fixme:msvcrt:__clean_type_info_names_internal (0x669aa8) stub 00d3:fixme:msvcrt:__clean_type_info_names_internal (0x1800deff8) stub 0009:fixme:netprofm:list_manager_GetConnectivity 0x13e37790, 0x33c060 warn: D3D11Texture2D::QueryInterface: Unknown interface query warn: f8fb5c27-c6b3-4f75-a4c8-439af2ef564c warn: D3D11Texture2D::QueryInterface: Unknown interface query warn: f8fb5c27-c6b3-4f75-a4c8-439af2ef564c 0009:fixme:shell:propertystore_SetValue (0x8914e08)->(0x2e09e70 0x33bd0c): stub 0009:fixme:shell:propertystore_Commit (0x8914e08): stub 0009:fixme:shell:SHAddToRecentDocs Unsupported flags: 6 opened using SMOID 100 00e3:fixme:wbemprox:client_security_SetBlanket 0x7c1ff958, 0x169368, 10, 0, (null), 3, 3, (nil), 0x00000000 00e3:fixme:wbemprox:client_security_Release 0x7c1ff958 00dd:fixme:ntdll:NtQueryInformationJobObject stub: 0xa94 1 0x12adfdc4 48 (nil) 00e6:fixme:file:FindFirstFileExW flags not implemented 0x00000002 00df:fixme:msvcrt:__clean_type_info_names_internal (0x6105f890) stub 00df:fixme:msvcrt:__clean_type_info_names_internal (0x1113b488) stub 00df:fixme:msvcrt:__clean_type_info_names_internal (0x6411ada4) stub 00df:fixme:msvcrt:__clean_type_info_names_internal (0x658dad74) stub 00df:fixme:msvcrt:__clean_type_info_names_internal (0x672bbe9c) stub 00db:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 00db:fixme:msvcrt:__clean_type_info_names_internal (0x669aa8) stub 00db:fixme:msvcrt:__clean_type_info_names_internal (0x1800deff8) stub 0009:fixme:netprofm:list_manager_GetConnectivity 0x9462fc0, 0x33c060
https://bugs.winehq.org/show_bug.cgi?id=46612
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|73b695f059740715ebd3ea0ce3c | |e88477977e628 |
--- Comment #23 from Hans Leidekker hans@meelstraat.net --- (In reply to Tk from comment #20)
I'm the user Zebediah was talking about.
Here are more details about my issue: BF3, BF4 and BF1 are working perfectly fine with staging 4.0 4f5ec55. The following staging commit, 7a2d7b7 (based on the same wine commit, 152cda3), breaks all of them.
While trying to run the game with 7a2d7b7 I get an error message asking to verify the game. Doing so has no effect of course. I can still run both games fine with 4f5ec55 afterwards. I'm assuming that issue was bcrypt related and is now fixed.
However on staging 4.2 release (or master), none of these games are running (the process dies on itself instantly on launch) and no error message shows up. I have tried on a new prefix as well with no difference. As soon as I switch back to 4f5ec55 they are all able to run again.
You could try a regression test on wine-staging:
https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #24 from Tk ti3nou@gmail.com --- (In reply to Hans Leidekker from comment #23)
You could try a regression test on wine-staging:
For that "verify game file" prompt I guess? I fear I know more or less where that one breaks as well, but I'll have to confirm it. Let's give it a run.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #25 from Tk ti3nou@gmail.com --- I decided to rebuild the whole series and here are the results, for staging, still trying BF1 (I don't have BF5) :
4f5ec55 : The game works fine.
7a2d7b7 : The game can't start anymore (process dies). Instead, I'm greeted with an error message telling me the game install needs to be repaired. I can see "GnuTLS error: The request is invalid." in the logs. "Repairing" the game has no effect.
d25f4cf : Same behavior as 7a2d7b7. fd3b0a7 : Same behavior as 7a2d7b7. 785d3c2 : Same behavior as 7a2d7b7. 0f48c0c : Same behavior as 7a2d7b7. 1edb7d5 : Same behavior as 7a2d7b7. 3dab9e5 : Same behavior as 7a2d7b7, possibly taking a bit longer time before the error message to show (it seemed to be consistent).
ca3bfa2 : The error message doesn't show up and "GnuTLS error: The request is invalid." doesn't appear in the logs anymore. The game still won't start and dies on launch.
This last behavior is unchanged up to latest master.
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #26 from Zebediah Figura z.figura12@gmail.com --- Hmm, this could be related to recent loader changes. Have you been testing in a clean prefix?
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #27 from lle llenort@aol.com --- Hi,
please try to uninstall the vc runtime versions and reinstall the versions with the ones that came with the game:
...Battlefield 1/__Installer/vc/vc2013/redist/vcredist_x64.exe ...Battlefield 3/__Installer/vc/vc2008sp1/redist/vcredist_x64.exe ...Battlefield 4/__Installer/vc/vc2012Update3/redist/vcredist_x64.exe
I install the 32bit versions too but i'm sure this isn't necessary :-)
Please make sure to uninstall the old ones. The repair action only make a simple check of the game file content. The Repair will not reintstall and maybe some setup files will be missing on your wine prefix profile.
When this not help, please try to make a 'fake' reinstall of the game:
- quit origin - move/rename the game install directory - start origin - go to inventory and install game - wait some seconds (the initial install/download files will be created in the new install folder. - quit Origin over the file menu - move the complete game content of the old Install directory in the new install folder. Override any existing files. - start origin, download continues, wait until origin end the download - quit origin - start wine (winefile, explorer) and change to the _-installer/vc/.. and install the x64 runtime - quit wine and make sure all wine processes ends (wineserver -k) - try to start wine/origin and the game
All the Best lle
https://bugs.winehq.org/show_bug.cgi?id=46612
--- Comment #28 from Tk ti3nou@gmail.com --- Thanks to both your comments, lle and Zebediah, I was finally able to fix it.
Here's what I did: To begin with, I have created a first fresh prefix with "last known working" 4f5ec55. Then I have set overrides to disable nvapi/nvapi64 and installed DXVK. Installed Origin. Set my game dir path in Origin, and let it find/refresh installs for both BF3/BF4/BF1. I didn't install any of the vc runtimes manually nor xact, and didn't add any additional override. The games are all starting just fine at this point.
Then I have created a second fresh prefix, with current master, and followed the exact same steps. Guess what? The games are all starting just fine as well.
Next I have created a third fresh prefix with "last known working" 4f5ec55, followed all the same steps as above then switched to current master to actually start the games. Same behavior as before, the games won't work. Switching back to 4f5ec55 and the games are working again.
As a follow up, I have created a fourth fresh prefix with current master, same steps as above then switched to "last known working" 4f5ec55 to start the games. Same behavior as before, the games won't work. Switching back to current master, however, didn't help the games to start in that configuration (strangely?).
At last (as I had high suspicions), I decided to install a couple vc runtimes from winetricks (namely 2012, 2013 and 2017) on the first and second prefixes. Games wouldn't run anymore after that.
Kinda funny the BF games were the only ones affected in my whole collection, but yes, it's fixed, and the error was on my side.
Thanks again to lle and Zebediah.
https://bugs.winehq.org/show_bug.cgi?id=46612
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID
--- Comment #29 from Zebediah Figura z.figura12@gmail.com --- (In reply to Tk from comment #28)
At last (as I had high suspicions), I decided to install a couple vc runtimes from winetricks (namely 2012, 2013 and 2017) on the first and second prefixes. Games wouldn't run anymore after that.
Hmm, I just checked and all of those winetricks verbs seem to install to the correct locations. I guess maybe there's something about native msvcrt that doesn't work with the game.
https://bugs.winehq.org/show_bug.cgi?id=46612
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #30 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org