wine-8.7-staging-tkg-amd64

[mksaleem]

Hi,

Thank you for wine 8.7 update I am having some problem running wow using [wine-8.7-staging-tkg-amd64.tar.xz] but it runs fine using [wine-8.7-staging-amd64.tar.xz] Following is the error in the log file: wineserver: using server-side synchronization. [0513/204008.037:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0 [0513/204008.251:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0 [0513/204008.254:ERROR:dxva_video_decode_accelerator_win.cc(1405)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E) Initial process has exited (return code: 256) Monitored process exited. Exit with return code 256

Update 15/05/23: Tried wine-8.8-staging-tkg-amd64.tar.xz with the same issue as 8.7

Kind Regards

[Kron4ek]

Hi,

Is this latest World of Warcraft from Battle Net, or some older version (like 3.3.5a)? Does it work with staging-tkg 8.6?

Edit. Ok, i tried to run Battle Net with staging-tkg 8.7 and can't even install it, it crashes at the installation. But it works with staging-tkg 8.6, which means this is a regression in staging-tkg 8.7. Don't know how to fix it though, so i suggest you to use staging-tkg 8.6 or staging 8.7 for now.

[mksaleem]

It is latest World of Warcraft I didnt check Does it work with staging-tkg 8.6, but working perfectly fine with Does it work with staging-tkg 8.5 I will try 8.6, thanks :)

[mksaleem]

wine-8.10-staging-tkg-amd64 fsync: up and running. [0616/220913.118:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0 [0616/220913.324:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0 [0616/220913.346:ERROR:dxva_video_decode_accelerator_win.cc(1405)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E) Initial process has exited (return code: 256)

[Etaash-mathamsetty]

Hi,

Is this latest World of Warcraft from Battle Net, or some older version (like 3.3.5a)? Does it work with staging-tkg 8.6?

Edit. Ok, i tried to run Battle Net with staging-tkg 8.7 and can't even install it, it crashes at the installation. But it works with staging-tkg 8.6, which means this is a regression in staging-tkg 8.7. Don't know how to fix it though, so i suggest you to use staging-tkg 8.6 or staging 8.7 for now.

I think it's something do you with the way you are building it or userpatches that you have added, I built a default wine-tkg-git on my system and it works fine :/ maybe it's time to start making my own builds :p

[Kron4ek]

The thing is there is no difference in patches and building process between 8.6-staging-tkg and 8.7-staging-tkg (except for proton-vr which i doubt has anything to do with this), and nonetheless BattleNet does not work with the latter (and newer versions). It's a regression in some of the already used patches or in how Wine interacts with them, i think.

[Etaash-mathamsetty]

The thing is there is no difference in patches and building process between 8.6-staging-tkg and 8.7-staging-tkg (except for proton-vr which i doubt has anything to do with this), and nonetheless BattleNet does not work with the latter (and newer versions). It's a regression in some of the already used patches or in how Wine interacts with them, i think.

What if proton-vr does have something to do with this? Also I'm not saying that you added a patch between 8.6 and 8.7, im saying that there is a patch that stopped working properly after 8.6 that isn't part of the default wine-tkg-fsync build (a userpatch maybe).

[Etaash-mathamsetty]

ok first of all: proton-win10-default.patch -- ( Enforce win10 as default wine version ) is not needed (wine 8.3+ use windows 10 as the default version)

proton-tkg-staging.patch -- ( Using Steam-specific Proton-tkg patches (staging) 2/3 )
proton-tkg-additions.patch -- ( Using additional Proton-tkg patches )
proton-cpu-topology-overrides.patch -- ( Enable Proton's CPU topology override support )
proton-vr.patch -- ( Enable Proton vr-related wined3d additions )

Applied hotfix remove_hooks_that_time_out2.mypatch
Applied hotfix winex11.drv_Add_a_GPU_for_each_Vulkan_device_that_was_not_tied_to_an_XRandR_provider.mypatch

are not in my stock builds

1. proton-vr is not needed, it modifies wined3d, which nobody uses for gaming (the patches are older than dxvk :/) so you should (probably) IMMEDIATELY disable it
2. all the others seem fine I think

[Kron4ek]

Ok, will try to build with _protonify disabled next time.

proton-win10-default.patch -- ( Enforce win10 as default wine version ) is not needed (wine 8.3+ use windows 10 as the default version)

Although Wine sets Windows 10 by default now, it reports older Windows 10 build than required for some games, so the patch is still useful (https://github.com/Frogging-Family/wine-tkg-git/commit/3d3535b1a3a4ae29b9353e45ddf1d043ff65f50d).

[Etaash-mathamsetty]

Ok, will try to build with _protonify disabled next time.

proton-win10-default.patch -- ( Enforce win10 as default wine version ) is not needed (wine 8.3+ use windows 10 as the default version)

Although Wine sets Windows 10 by default now, it reports older Windows 10 build than required for some games, so the patch is still useful (Frogging-Family/wine-tkg-git@3d3535b).

Upstream reports 18362 build number, this patch is 18683, more or less the same thing, so that patch is outdated (wine 8.3 also has a Windows 11 mode that reports 22000 I think)

[Kron4ek]

This patch reports 19043, not 18683.

[Etaash-mathamsetty]

This patch reports 19043, not 18683.

it's still the old number in kernel32's resource file, but I should have read the commit's message mb

[Etaash-mathamsetty]

Works perfect now, thanks so much!

I guess it's time to slowly add back the patches and test which one is causing issues :)

[Kron4ek]

Works for me too now, so _protonify was the issue indeed.

@mksaleem Try 8.11-staging-tkg.

[mksaleem]

Works perfectly now, thanks for sorting it out.