Service init: 0x1815B6140 (ExitProcess: 0x18161FA50)
Parent^: 0x1815B60D0
Model name string: 0x181979B40
Hash1: 0x181979B5A
Hash2: 0x181979B9E
EDIT by Krock:
2.3.0 patch is done and currently in the testing phase. If there are no severe problems until 2021-11-27, the script will be unlocked.
UnityPlayer.dll md5sum: dbc22b32f297b0e75f658dc10e30969d
Device model getter: 0x180F13740
Hash1 calc: 0x1815A74DE
Hash2 calc: 0x1815A7C0F (target call 0x181046828)
Service init: 0x1815B6140 (ExitProcess: 0x18161FA50)
Parent^: 0x1815B60D0
Model name string: 0x181979B40
Hash1: 0x181979B5A
Hash2: 0x181979B9E
---
EDIT by Krock:
**2.3.0 patch is done and currently in the testing phase.** If there are no severe problems until **2021-11-27**, the script will be unlocked.
As I don't have an access to Windows machine, I can't dump correct hash values and provide full patch. But at least it seems that nothing was changed since 2.2.0, so patch should be relatively straightforward.
As I don't have an access to Windows machine, I can't dump correct hash values and provide full patch. But at least it seems that nothing was changed since 2.2.0, so patch should be relatively straightforward.
I do have access to a windows machine, though I'm not sure what information needs to be extracted or how to do it. While I do have some experience reversing, I wasn't able to get a clear idea of the whole process from the journals and other docs around the repository. But I'd be happy to help with the windows side if you have a clear idea of what needs to be done.
I do have access to a windows machine, though I'm not sure what information needs to be extracted or how to do it. While I do have some experience reversing, I wasn't able to get a clear idea of the whole process from the journals and other docs around the repository. But I'd be happy to help with the windows side if you have a clear idea of what needs to be done.
Hello and thank you for your efforts. I did find more spare time to work on this project than initially expected.
I still cannot provide an exact release date of the 2.3.0 patch, but it can be expected this week. As for the entire patch process: there are no step-by-step instructions, I will only forward mine if the repository ever needs adoption (i.e. lost interest).
General reminder that this repository will be renamed as announced in #215.
Hello and thank you for your efforts. I did find more spare time to work on this project than initially expected.
I still cannot provide an exact release date of the 2.3.0 patch, but it can be expected this week. As for the entire patch process: there are no step-by-step instructions, I will only forward mine if the repository ever needs adoption (i.e. lost interest).
General reminder that this repository will be renamed as announced in #215.
Hm. Today I actually tried running patched 2.3.0 and encountered a very interesing glitch.
Game starts, allows you to login, shows door, displays progressbar of 7 elements...
And then as soon as progressbar fills to 100% game window hides itself. It's just not there anymore. But the game runs: audio plays, stuff happens etc. The only caveat that there's no visible window. Window manager (any) also doesn't see it and doesn't list it.
Even more interesting: window is still there under xdotool search --classname Genshin. And you can send keystrokes to it with xdotool search --classname Genshin key Escape, e.g. Game reacts to them. But you still can't see it.
AFAIK I didn't change anything in my config since 2.2.0, I'll try to play around for a bit and will let you know if I find anything. But it's certainly possible that they might have added some new check somewhere...
UPD: Things I've tried so far:
All Wine versions from 6.18 till 6.21. No luck.
Different window manager settings in winecfg. No luck. (Beware that virtual desktop doesn't work for me for some reason.)
Different window managers (XFMW4, Metacity, ctwm, twm, openbox). No luck.
Hm. Today I actually tried running patched 2.3.0 and encountered a very interesing glitch.
Game starts, allows you to login, shows door, displays progressbar of 7 elements...
And then as soon as progressbar fills to 100% game window _hides itself_. It's just not there anymore. But the game runs: audio plays, stuff happens etc. The only caveat that there's no visible window. Window manager (any) also doesn't see it and doesn't list it.
Even more interesting: window is still there under `xdotool search --classname Genshin`. And you can send keystrokes to it with `xdotool search --classname Genshin key Escape`, e.g. Game reacts to them. But you still can't see it.
AFAIK I didn't change anything in my config since 2.2.0, I'll try to play around for a bit and will let you know if I find anything. But it's certainly possible that they might have added some new check somewhere...
UPD: Things I've tried so far:
- All Wine versions from 6.18 till 6.21. No luck.
- Different window manager settings in `winecfg`. No luck. (Beware that virtual desktop doesn't work for me for some reason.)
- Different window managers (XFMW4, Metacity, ctwm, twm, openbox). No luck.
I'd like to help but I'm not that much of a programmer but I love to tinker into some stuff. I can make one of my backup machines use Windows so please let me know what needs to be done.
I'd like to help but I'm not that much of a programmer but I love to tinker into some stuff. I can make one of my backup machines use Windows so please let me know what needs to be done.
For anyone interested: I was able to properly start and play the game using alternative approach. In this case game doesn't hide it's window. (I won't disclose it yet as it is very tricky to pull and may be unsafe in terms of connecting to official servers.)
So by that I can only assume that they indeed added some extra AC check somewhere.
For anyone interested: I was able to properly start and play the game using alternative approach. In this case game doesn't hide it's window. (I won't disclose it yet as it is very tricky to pull and may be unsafe in terms of connecting to official servers.)
So by that I can only assume that they indeed added some extra AC check somewhere.
Landed here as I'm doing some Honkai research. That said, while I'm not interested in Genshin atm, I can help as I've access to a win machine which is pretty setup for research if you will.
Landed here as I'm doing some Honkai research. That said, while I'm not interested in Genshin atm, I can help as I've access to a win machine which is pretty setup for research if you will.
Thought we were going to migrate the repository only after testing this release, hope we don't lose some testers along the way...
Grabbed the new patch, going to do some initial testing.
Thought we were going to migrate the repository only after testing this release, hope we don't lose some testers along the way...
Grabbed the new patch, going to do some initial testing.
@Alex72 I appreciate your attempts. At least to me, this seems to be an assembly mistake. I did set this project my top priority to stop further stress and headache - by a patch of the usual format.
First version of the 2.3.0 patch is done
Like in all previous patches, please use a testing account to check for issues. If there are any that seem to be patch-related, please report it here.
As noted above, the script unlock will happen on 27 Nov if there are no issues. Thank you for keeping this project "under the hood".
@Alex72 I appreciate your attempts. At least to me, this seems to be an assembly mistake. I did set this project my top priority to stop further stress and headache - by a patch of the usual format.
### First version of the 2.3.0 patch is done
Like in all previous patches, please use a testing account to check for issues. If there are any that seem to be patch-related, please report it here.
As noted above, the script unlock will happen on ***27 Nov*** if there are no issues. Thank you for keeping this project "under the hood".
Seems to be working fine on Gentoo(5.13)+Gnome+Lutris(6.14.4).
@serghidalg Check the INSTALLATION.md file Lutris section.
EDIT: Tried lutris wine 6.21 and it freezes before showing login menu for me.
Seems to be working fine on Gentoo(5.13)+Gnome+Lutris(6.14.4).
@serghidalg Check the INSTALLATION.md file Lutris section.
EDIT: Tried lutris wine 6.21 and it freezes before showing login menu for me.
It seems the game was reacting not to the patch itself, but to the debugger running...
Aargh.
I'm sorry I tend to trigger a false alarm sometimes :)
But now at least there's an alternative way of running the game that doesn't require patching.
Also I have a slip of info that 2.4 comes with a new tracking mechanism. Is it limited to only beta or can be extended to regular releases is still unclear thou.
Patch for 2.3 works like a charm, tnx again @Krock!
OOF, that was very very bad of me.
It seems the game was reacting not to the patch itself, but to the debugger running...
Aargh.
I'm sorry I tend to trigger a false alarm sometimes :)
But now at least there's an alternative way of running the game that doesn't require patching.
Also I have a slip of info that 2.4 comes with a new tracking mechanism. Is it limited to only beta or can be extended to regular releases is still unclear thou.
Patch for 2.3 works like a charm, tnx again @Krock!
if i've read it correcly, patch is fully working and ready to be used, but the script is locked because there's some risk of the game being able to detect the patch and baning us, is that it?
if i've read it correcly, patch is fully working and ready to be used, but the script is locked because there's some risk of the game being able to detect the patch and baning us, is that it?
Wine 6.21 problems are now documented. If the issue persists in 6.22 and future 6.23, please open a new issue providing the exact Wine version and rough system specifications to narrow this issue down so that a Wine Bugzilla issue can be filed.
@Alex72 Question would be whether this alternative approach is easier and more reliable than the current. If 2.4.0 brings patch-relevant changes, I'd appreciate if we could discuss both topics in detail.
@4nizio This and related questions are answered in FAQ.md. In short: Yes.
Wine 6.21 problems are now documented. If the issue persists in 6.22 and future 6.23, please open a new issue providing the exact Wine version and rough system specifications to narrow this issue down so that a Wine Bugzilla issue can be filed.
---
@Alex72 Question would be whether this alternative approach is easier and more reliable than the current. If 2.4.0 brings patch-relevant changes, I'd appreciate if we could discuss both topics in detail.
---
@4nizio This and related questions are answered in FAQ.md. In short: Yes.
Tested with FreeBSD 13-RELEASE + Wine Proton 6.3.2 and Arch Linux + Lutris-GE 6.16. Both works well. Thanks.
Update: To mention, I'm always use both patch and anti_login_crash because after a couple of updates that didn't worked without anti_login_crash, I just apply it anyways.
Tested with FreeBSD 13-RELEASE + Wine Proton 6.3.2 and Arch Linux + Lutris-GE 6.16. Both works well. Thanks.
Update: To mention, I'm always use both patch and anti_login_crash because after a couple of updates that didn't worked without anti_login_crash, I just apply it anyways.
@TwistedSystems , yes to both your questions. Look at PR in the original repo to find Linux-compatible version and build instructions.
BEWARE that safety of this method is UNCLEAR. I only used it to run the game locally. If you decide to try it out with the official server, do it on your own risk.
@TwistedSystems , `yes` to both your questions. Look at PR in the original repo to find Linux-compatible version and build instructions.
BEWARE that safety of this method is UNCLEAR. I only used it to run the game locally. If you decide to try it out with the official server, do it on your own risk.
If 2.4.0 brings patch-relevant changes, I'd appreciate if we could discuss both topics in detail.
We'd have to wait till 2.4 preload anyway, I guess.
@Krock
> If 2.4.0 brings patch-relevant changes, I'd appreciate if we could discuss both topics in detail.
We'd have to wait till 2.4 preload anyway, I guess.
Currently 30 minutes into testing on my alt account. I had an issue with Wine 6.21. It was doing that thing where the game froze right at the login screen but you can still hear the background music playing.
I loaded up Wine GE 6.20 and it loaded up without any issues. I'm on Pop!_OS 21.10 (beta) using Lutris.
EDIT: Playing about 2 hours now. Still using my alt account. Everything seems normal. Will wait for the unlocked version on the 27th before I use my main account.
Currently 30 minutes into testing on my alt account. I had an issue with Wine 6.21. It was doing that thing where the game froze right at the login screen but you can still hear the background music playing.
I loaded up Wine GE 6.20 and it loaded up without any issues. I'm on Pop!_OS 21.10 (beta) using Lutris.
EDIT: Playing about 2 hours now. Still using my alt account. Everything seems normal. Will wait for the unlocked version on the 27th before I use my main account.
EDIT: Nevermind. This seems to be related to a recent system update for Manjaro. I reverted the update using timeshift and the game works fine. now. Sorry for the false alarm.
I'm running into an issue where the game is crashing immediately after the white loading screen when entering the game. I'm using the 5.14.18-1-MANJARO kernel. I generally use wine-ge 6.12, but today I also tried wine-ge 6.20 and wine-staging 6.21, all of them crash. I even tried reinstalling the game.
I'm not seeing any crash logs generated, but I've attached my output_log.txt. Here are the last few lines:
(Filename: E:\WKSPC\2.3Fix\sourceCode\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
[1126/183730.428:ERROR:browser_host_impl.cc(230)] Creating a windowless browser without setting CefSettings.windowless_rendering_enabled may result in reduced performance or runtime errors.
Unloading 5 Unused Serialized files (Serialized files now loaded: 1547)
UnloadTime: 2.081300 ms
Unloading 606 unused Assets to reduce memory usage. Loaded Objects now: 16812.
Total: 282.508800 ms (FindLiveObjects: 0.598900 ms CreateObjectMapping: 0.393100 ms MarkObjects: 279.709000 ms DeleteObjects: 1.806900 ms)
AssetBatchLoader::LoadingProgress0 0.166667
AssetBatchLoader::LoadingProgress0 0.333333
AssetBatchLoader::LoadingProgress0 0.500000
AssetBatchLoader::LoadingProgress0 0.666667
AssetBatchLoader::LoadingProgress0 0.833333
AssetBatchLoader::LoadingProgress0 0.333333
AssetBatchLoader::LoadingProgress0 0.666667
[1126/183737.615:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[1126/183737.863:ERROR:command_buffer_proxy_impl.cc(105)] ContextResult::kTransientFailure: Shared memory region is not valid
[1126/183737.992:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
[1126/183738.002:ERROR:browser_gpu_channel_host_factory.cc(139)] Failed to launch GPU process.
[1126/183738.139:ERROR:audio_context.cc(52)] Create
[1126/183738.139:ERROR:audio_context.cc(130)] AudioContext
[1126/183738.139:ERROR:audio_context.cc(134)] no user gesture
[1126/183738.142:ERROR:audio_context.cc(436)] IsAllowedToStart
[1126/183738.143:ERROR:audio_context.cc(93)] starting
[1126/183738.356:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/183738.825:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/183738.920:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.921:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.922:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.922:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.924:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.925:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.941:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.980:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.987:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.987:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.988:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.988:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.989:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.991:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.992:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.993:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.993:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.996:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
Crash!!!
[1126/183739.363:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
I haven't seen anyone else report anything like this, so I'm not sure if it's directly patch related though. This is my first time testing the patch on this update. 2.2.0 worked perfectly fine for me.
I used the updater script to update the game. I applied both patch.sh and patch_anti_logincrash.sh. Both applied successfully.
EDIT: Nevermind. This seems to be related to a recent system update for Manjaro. I reverted the update using timeshift and the game works fine. now. Sorry for the false alarm.
---
I'm running into an issue where the game is crashing immediately after the white loading screen when entering the game. I'm using the 5.14.18-1-MANJARO kernel. I generally use wine-ge 6.12, but today I also tried wine-ge 6.20 and wine-staging 6.21, all of them crash. I even tried reinstalling the game.
I'm not seeing any crash logs generated, but I've attached my output_log.txt. Here are the last few lines:
```
(Filename: E:\WKSPC\2.3Fix\sourceCode\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
[1126/183730.428:ERROR:browser_host_impl.cc(230)] Creating a windowless browser without setting CefSettings.windowless_rendering_enabled may result in reduced performance or runtime errors.
Unloading 5 Unused Serialized files (Serialized files now loaded: 1547)
UnloadTime: 2.081300 ms
Unloading 606 unused Assets to reduce memory usage. Loaded Objects now: 16812.
Total: 282.508800 ms (FindLiveObjects: 0.598900 ms CreateObjectMapping: 0.393100 ms MarkObjects: 279.709000 ms DeleteObjects: 1.806900 ms)
AssetBatchLoader::LoadingProgress0 0.166667
AssetBatchLoader::LoadingProgress0 0.333333
AssetBatchLoader::LoadingProgress0 0.500000
AssetBatchLoader::LoadingProgress0 0.666667
AssetBatchLoader::LoadingProgress0 0.833333
AssetBatchLoader::LoadingProgress0 0.333333
AssetBatchLoader::LoadingProgress0 0.666667
[1126/183737.615:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[1126/183737.863:ERROR:command_buffer_proxy_impl.cc(105)] ContextResult::kTransientFailure: Shared memory region is not valid
[1126/183737.992:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
[1126/183738.002:ERROR:browser_gpu_channel_host_factory.cc(139)] Failed to launch GPU process.
[1126/183738.139:ERROR:audio_context.cc(52)] Create
[1126/183738.139:ERROR:audio_context.cc(130)] AudioContext
[1126/183738.139:ERROR:audio_context.cc(134)] no user gesture
[1126/183738.142:ERROR:audio_context.cc(436)] IsAllowedToStart
[1126/183738.143:ERROR:audio_context.cc(93)] starting
[1126/183738.356:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/183738.825:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
[1126/183738.920:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.921:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.922:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.922:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.924:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.925:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.941:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.980:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.987:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.987:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.988:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.988:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.989:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.991:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.992:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.993:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.993:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
[1126/183738.996:WARNING:backend_impl.cc(1843)] Destroying invalid entry.
Crash!!!
[1126/183739.363:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED
```
I haven't seen anyone else report anything like this, so I'm not sure if it's directly patch related though. This is my first time testing the patch on this update. 2.2.0 worked perfectly fine for me.
I used the updater script to update the game. I applied both `patch.sh` and `patch_anti_logincrash.sh`. Both applied successfully.
Thank you all for testing. There seem to be no issues. In addition for the first time since 1.2.0, the patch_anti_logincrash.sh script is not mandatory.
Depending on whether this is a mistake of the developers, the patch might be required in a few days, with the next release, or never again.
Until then, have fun and enjoy the Dragonspine event!
Thank you all for testing. There seem to be no issues. In addition for the first time since 1.2.0, the `patch_anti_logincrash.sh` script is not mandatory.
Depending on whether this is a mistake of the developers, the patch might be required in a few days, with the next release, or never again.
Until then, have fun and enjoy the Dragonspine event!
As much as I hoped againt it, it seems that new tracking mechanism made it's way into 2.4.0 release build. And I also had several reports about improved anti-anti-cheat detection mechanism, yet to be confirmed.
As soon as I'll get my hands on 2.4.0 preload I'll try to confirm those things and maybe create a new thread about 2.4.0.
As much as I hoped againt it, it seems that new tracking mechanism made it's way into 2.4.0 release build. And I also had several reports about improved anti-anti-cheat detection mechanism, yet to be confirmed.
As soon as I'll get my hands on 2.4.0 preload I'll try to confirm those things and maybe create a new thread about 2.4.0.
UnityPlayer.dll md5sum: dbc22b32f297b0e75f658dc10e30969d
Device model getter: 0x180F13740
Hash1 calc: 0x1815A74DE
Hash2 calc: 0x1815A7C0F (target call 0x181046828)
Service init: 0x1815B6140 (ExitProcess: 0x18161FA50)
Parent^: 0x1815B60D0
Model name string: 0x181979B40
Hash1: 0x181979B5A
Hash2: 0x181979B9E
EDIT by Krock:
2.3.0 patch is done and currently in the testing phase. If there are no severe problems until 2021-11-27, the script will be unlocked.
As I don't have an access to Windows machine, I can't dump correct hash values and provide full patch. But at least it seems that nothing was changed since 2.2.0, so patch should be relatively straightforward.
I do have access to a windows machine, though I'm not sure what information needs to be extracted or how to do it. While I do have some experience reversing, I wasn't able to get a clear idea of the whole process from the journals and other docs around the repository. But I'd be happy to help with the windows side if you have a clear idea of what needs to be done.
Hello and thank you for your efforts. I did find more spare time to work on this project than initially expected.
I still cannot provide an exact release date of the 2.3.0 patch, but it can be expected this week. As for the entire patch process: there are no step-by-step instructions, I will only forward mine if the repository ever needs adoption (i.e. lost interest).
General reminder that this repository will be renamed as announced in #215.
Hm. Today I actually tried running patched 2.3.0 and encountered a very interesing glitch.
Game starts, allows you to login, shows door, displays progressbar of 7 elements...
And then as soon as progressbar fills to 100% game window hides itself. It's just not there anymore. But the game runs: audio plays, stuff happens etc. The only caveat that there's no visible window. Window manager (any) also doesn't see it and doesn't list it.
Even more interesting: window is still there under
xdotool search --classname Genshin. And you can send keystrokes to it withxdotool search --classname Genshin key Escape, e.g. Game reacts to them. But you still can't see it.AFAIK I didn't change anything in my config since 2.2.0, I'll try to play around for a bit and will let you know if I find anything. But it's certainly possible that they might have added some new check somewhere...
UPD: Things I've tried so far:
winecfg. No luck. (Beware that virtual desktop doesn't work for me for some reason.)Also it's funny that this issue is #230 =)
I'd like to help but I'm not that much of a programmer but I love to tinker into some stuff. I can make one of my backup machines use Windows so please let me know what needs to be done.
For anyone interested: I was able to properly start and play the game using alternative approach. In this case game doesn't hide it's window. (I won't disclose it yet as it is very tricky to pull and may be unsafe in terms of connecting to official servers.)
So by that I can only assume that they indeed added some extra AC check somewhere.
Landed here as I'm doing some Honkai research. That said, while I'm not interested in Genshin atm, I can help as I've access to a win machine which is pretty setup for research if you will.
Thought we were going to migrate the repository only after testing this release, hope we don't lose some testers along the way...
Grabbed the new patch, going to do some initial testing.
@Alex72 I appreciate your attempts. At least to me, this seems to be an assembly mistake. I did set this project my top priority to stop further stress and headache - by a patch of the usual format.
First version of the 2.3.0 patch is done
Like in all previous patches, please use a testing account to check for issues. If there are any that seem to be patch-related, please report it here.
As noted above, the script unlock will happen on 27 Nov if there are no issues. Thank you for keeping this project "under the hood".
All working as usual so far on 2.3.0, will keep testing for a while.
Everything is working fine on my end, arch+lutris
Seems to be working fine on Gentoo(5.13)+Gnome+Lutris(6.14.4). @serghidalg Check the INSTALLATION.md file Lutris section.
EDIT: Tried lutris wine 6.21 and it freezes before showing login menu for me.
Works fine as well. Played for about 30 minutes. Also, wine 6.21 doesn't work
Works fine for me on Pop OS + lutris + wine 6.14 . Played for around 40 mins.
Thanks !
Working fine on Fedora with Wine 6.21. Played around 30 mins. Thank you!
Working on Kubuntu 20.10 x86_64 with wine-6.13. Played for around an hour. Thank you !
OOF, that was very very bad of me.
It seems the game was reacting not to the patch itself, but to the debugger running... Aargh.
I'm sorry I tend to trigger a false alarm sometimes :)
But now at least there's an alternative way of running the game that doesn't require patching.
Also I have a slip of info that 2.4 comes with a new tracking mechanism. Is it limited to only beta or can be extended to regular releases is still unclear thou.
Patch for 2.3 works like a charm, tnx again @Krock!
if i've read it correcly, patch is fully working and ready to be used, but the script is locked because there's some risk of the game being able to detect the patch and baning us, is that it?
Wine 6.21 problems are now documented. If the issue persists in 6.22 and future 6.23, please open a new issue providing the exact Wine version and rough system specifications to narrow this issue down so that a Wine Bugzilla issue can be filed.
@Alex72 Question would be whether this alternative approach is easier and more reliable than the current. If 2.4.0 brings patch-relevant changes, I'd appreciate if we could discuss both topics in detail.
@4nizio This and related questions are answered in FAQ.md. In short: Yes.
Tested with FreeBSD 13-RELEASE + Wine Proton 6.3.2 and Arch Linux + Lutris-GE 6.16. Both works well. Thanks.
Update: To mention, I'm always use both patch and anti_login_crash because after a couple of updates that didn't worked without anti_login_crash, I just apply it anyways.
@TwistedSystems ,
yesto both your questions. Look at PR in the original repo to find Linux-compatible version and build instructions.BEWARE that safety of this method is UNCLEAR. I only used it to run the game locally. If you decide to try it out with the official server, do it on your own risk.
@Krock
We'd have to wait till 2.4 preload anyway, I guess.
patch works successfully. thanks !
Currently 30 minutes into testing on my alt account. I had an issue with Wine 6.21. It was doing that thing where the game froze right at the login screen but you can still hear the background music playing.
I loaded up Wine GE 6.20 and it loaded up without any issues. I'm on Pop!_OS 21.10 (beta) using Lutris.
EDIT: Playing about 2 hours now. Still using my alt account. Everything seems normal. Will wait for the unlocked version on the 27th before I use my main account.
manjaro kernel 5.10.70-1 wine 6.16 with dxvk I'm not yet encounter any problem after finishing 2.3 dragonspine event keep up the good work guys
Played for 1 hour.
Game works fine
Arch Linux x64
Linux 5.15.2-zen
Wine 6.21 + DXVK (forgot the version)
Thanks for your hard work guys!
@TwistedSystems
Yes they did, but there're tools for that too.
Played for an hour, no issues here.
OS: Arch Linux Wine: Wine-GE 6.21 through Lutris (No freezing encountered)
Thank you very much!
Played for 30 minutes, no issues. Thank you!
Linux Mint 19.3 x86_64 / Lutris 0.5.9.1 / Wine: lutris-6.14-4 / DXVK: v1.9.2L
5.10.68-1-MANJARO/lutris-6.10-7/wine 6.16 playing 2nd day, no issue/ban @Krock thank you very for your work
EDIT: Nevermind. This seems to be related to a recent system update for Manjaro. I reverted the update using timeshift and the game works fine. now. Sorry for the false alarm.
I'm running into an issue where the game is crashing immediately after the white loading screen when entering the game. I'm using the 5.14.18-1-MANJARO kernel. I generally use wine-ge 6.12, but today I also tried wine-ge 6.20 and wine-staging 6.21, all of them crash. I even tried reinstalling the game.
I'm not seeing any crash logs generated, but I've attached my output_log.txt. Here are the last few lines:
I haven't seen anyone else report anything like this, so I'm not sure if it's directly patch related though. This is my first time testing the patch on this update. 2.2.0 worked perfectly fine for me.
I used the updater script to update the game. I applied both
patch.shandpatch_anti_logincrash.sh. Both applied successfully.Thank you all for testing. There seem to be no issues. In addition for the first time since 1.2.0, the
patch_anti_logincrash.shscript is not mandatory.Depending on whether this is a mistake of the developers, the patch might be required in a few days, with the next release, or never again.
Until then, have fun and enjoy the Dragonspine event!
As much as I hoped againt it, it seems that new tracking mechanism made it's way into 2.4.0 release build. And I also had several reports about improved anti-anti-cheat detection mechanism, yet to be confirmed.
As soon as I'll get my hands on 2.4.0 preload I'll try to confirm those things and maybe create a new thread about 2.4.0.