Can't login in Battlenet with Proton-tkg
Closed this issue · 19 comments
Hi! Everything works fine with the inbuilt Steam's vanilla Proton Experimental. But with TKG the LOGIN button never appears, instead all I see is an infinitely long time spinning Battlenet logo signifying loading. This behaviour happens if I use FSYNC. But no logo even rotates if I try to use NTSYNC, because then the Battlenet application always hangs completely.
last_build_config.log
prepare.log
battlenet_log.txt
Maybe you can try applying this patch proton_battleye.patch. Oops nevermind. Wrong thing.
Looks like ntdll-WRITECOPY patch stop working properly on newer version. I tested and this occurs regardless of the synchronization method selected, including server-side. I also tested standard wine and wine-staging from arch linux repository and same thing
wine-tkg-userpatches.zip
Try these patches. download them and extract them into the wine-tkg-userpatch folder. Also set _protonify=false and clean the prefix
wine-tkg-userpatches.zip Try these patches. download them and extract them into the wine-tkg-userpatch folder. Also set _protonify=false and clean the prefix
@Artewar67 I have just tested with your patches and fresh prefix, but have not changes, it have not helped.
I found out that me have to clean the prefix before testing. Now wine from arch linux repository no longer has this bug and I'm trying to figure out what wine-tkg patch is causing it
I found out that you have battle.net crashing and you need staging patches for that. You need to set _use_staging=true. I have also if do not apply staging, it crashes on installation at 45% and at startup if i install it with wine-staging before that.
wine-tkg-userpatches.zip Try these patches. download them and extract them into the wine-tkg-userpatch folder. Also set _protonify=false and clean the prefix
You also don't need this patchset. I thought the ntdll-WRITECOPY patch was broken until I tried cleaning the prefix
I found out that you have battle.net crashing and you need staging patches for that. You need to set _use_staging=true. I have also if do not apply staging, it crashes on installation at 45% and at startup if i install it with wine-staging before that.
@Artewar67
- If everything is as you say is true, then why does this problem not exist if I use vanilla Proton from Steam?
- Unfortunately, I had to stop using Staging because it causes a regression in Mass Effect Legendary Edition when using Winewayland. When mouse pointer moving over menu items, they should be highlighted, but they are not, causing menu items to have to be clicked twice if I want to choose it. Also when selecting weapons or abilities during combat, I also have to double-click to make it work. I'm going to write about this bug on the Wine's website.
If everything is as you say is true, then why does this problem not exist if I use vanilla Proton from Steam?
Proton may contain changes taken from staging but also a bunch of code modifications that are not found in standard wine. For example I had to play one game through Proton-GE because videos don't work in wine and it has its own Bug report in Wine Bugzilla: https://bugs.winehq.org/show_bug.cgi?id=50277
winegstreamer has been heavily modified in proton and also contains a new media_source implementation. The developers tried to implement this in standard wine but it was rejected.
If everything is as you say is true, then why does this problem not exist if I use vanilla Proton from Steam?
Proton may contain changes taken from staging but also a bunch of code modifications that are not found in standard wine. For example I had to play one game through Proton-GE because videos don't work in wine and it has its own Bug report in Wine Bugzilla: https://bugs.winehq.org/show_bug.cgi?id=50277
And so, what we should to do next now?
I'll try to find the staging patches need for Battle.net.
I found out that it was a bug in the ntsync5 patch for mainline and protonify. This commit should fix it
@Artewar67 now Battlenet hang no more happens with NTSYNC since cadda7e, but I still can't login.
0011-kernelbase-Handle-NULL-old_prot-parameter-in-Virtual.txt
Try this patch (rename format to mypatch and put file in wine-tkg-userpatch)
0011-kernelbase-Handle-NULL-old_prot-parameter-in-Virtual.txt Try this patch (rename format to mypatch and put file in wine-tkg-userpatch)
@Artewar67 with this patch now i can login easy, but now appear a new issue - Battlenet want to install itself update everytime, but have not installed it if I press a button to install it and restart BN, then every time I see a update available. Should I open a new separate issue?
With this commit you no longer need special patch for battle.net
@Artewar67 with this patch now i can login easy, but now appear a new issue - Battlenet want to install itself update everytime, but have not installed it if I press a button to install it and restart BN, then every time I see a update available. Should I open a new separate issue?
I think yes you can open a new issue since we have solved the main problem of this issue.
With this commit you no longer need special patch for battle.net
@Artewar67 with this patch now i can login easy, but now appear a new issue - Battlenet want to install itself update everytime, but have not installed it if I press a button to install it and restart BN, then every time I see a update available. Should I open a new separate issue?
I think yes you can open a new issue since we have solved the main problem of this issue.
@Artewar67 OK, thank you. But I think we will have solved the main problem of this issue when your patch will bee added to this repo etc.