So... the update_gi.sh script wants config.ini but MiHoYo stores all the GI related settings directly in the Windows Registry, not in a stand-alone file, which breaks this script, even in #948ccb3f75.
If I was inclined, I could probably use WINEREGEDIT to manually save the relevant keys to a file, then format it, but I'd have to do that every time, and that's going to be a huge pain.
Alternatively, I can run the update script from each new patch folder as I grab them from GIT, but then, why have update_gi.sh at all, except as an alternative installer?
Edit: Also, why is the game path being searched for by the script Genshin Impact Game when on every install I've done for friends and on my own live system and VMs, it's always Program Files\Genshin Impact?
So... the `update_gi.sh` script wants `config.ini` but MiHoYo stores all the GI related settings directly in the Windows Registry, not in a stand-alone file, which breaks this script, even in [#948ccb3f75](https://notabug.org/Krock/dawn/commit/948ccb3f75b61c92179c3942c2695cde0955769f).
If I was inclined, I could probably use `WINEREGEDIT` to manually save the relevant keys to a file, then format it, but I'd have to do that every time, and that's going to be a huge pain.
Alternatively, I can run the update script from each new patch folder as I grab them from `GIT`, but then, why have `update_gi.sh` at all, except as an alternative installer?
Edit: Also, why is the game path being searched for by the script `Genshin Impact Game` when on every install I've done for friends and on my own live system and VMs, it's always `Program Files\Genshin Impact`?
config.ini is read by the game itself to determine the its service integration with Epic Games, Google Play, Bilibili or the standard one.
It is also used by the official launcher to determine the currently installed game version. You can test this easily by lowering the setting value of game_version. The launcher will then ask you for updating your "old" game.
Speaking of the official launcher - its default installation directory is C:\Program Files\Genshin Impact and the game is (by default) installed to the subdirectory named Genshin Impact game.
The update_gi.sh script was added because until Wine 8.7 - I will put a note to TROUBLESHOOTING.md soon - winedevice leaked memory, resulting in unacceptable RAM usage while downloading. If you happen to have a recent Wine version, you might as well give the official launcher a try which now works very well. However, the game should still be started from launcher.bat to ensure that crash reports are not sent to their servers.
@EvilSupahFly
`config.ini` is read by the game itself to determine the its service integration with Epic Games, Google Play, Bilibili or the standard one.
It is also used by the official launcher to determine the currently installed game version. You can test this easily by lowering the setting value of `game_version`. The launcher will then ask you for updating your "old" game.
Speaking of the official launcher - its default installation directory is `C:\Program Files\Genshin Impact` and the game is (by default) installed to the subdirectory named `Genshin Impact game`.
The `update_gi.sh` script was added because until Wine 8.7 - I will put a note to TROUBLESHOOTING.md soon - winedevice leaked memory, resulting in unacceptable RAM usage while downloading. If you happen to have a recent Wine version, you might as well give the official launcher a try which now works very well. However, the game should still be started from `launcher.bat` to ensure that crash reports are not sent to their servers.
That's interesting about the location. When I installed the game initially from the Anime Game Launcher (circa patch 238), it installed everything to the launcher folder, and didn't create a new sub-folder, but I was mostly playing it on the PlayStation and would only jump to my PC if my kids wanted to join worlds. It's been a long time since I was actually on the PC version, so when I went to update using the 370 script, after the Anime Launcher failed to update, it complained. I'm going to just nuke the entire thing and start over. I wanted to do it through Lutris, but the only working install script forces WINE to run with a Virtual Desktop, which I didn't want.
Thanks for the update!
That's interesting about the location. When I installed the game initially from the Anime Game Launcher (circa patch 238), it installed everything to the launcher folder, and didn't create a new sub-folder, but I was mostly playing it on the PlayStation and would only jump to my PC if my kids wanted to join worlds. It's been a long time since I was actually on the PC version, so when I went to update using the 370 script, after the Anime Launcher failed to update, it complained. I'm going to just nuke the entire thing and start over. I wanted to do it through Lutris, but the only working install script forces WINE to run with a Virtual Desktop, which I didn't want.
Thanks for the update!
@EvilSupahFlyconfig.ini is only created and used by the official game launcher.
If you don't use it, either create a stub file manually or edit an updater script.
You only need to provide the installed game version.
Honestly I think it's much easier just to download a full ZIP with the client each update using a direct link...
@EvilSupahFly `config.ini` is only created and used by the official game launcher.
If you don't use it, either create a stub file manually or edit an updater script.
You only need to provide the installed game version.
Honestly I think it's much easier just to download a full ZIP with the client each update using a direct link...
So... the
update_gi.shscript wantsconfig.inibut MiHoYo stores all the GI related settings directly in the Windows Registry, not in a stand-alone file, which breaks this script, even in #948ccb3f75.If I was inclined, I could probably use
WINEREGEDITto manually save the relevant keys to a file, then format it, but I'd have to do that every time, and that's going to be a huge pain.Alternatively, I can run the update script from each new patch folder as I grab them from
GIT, but then, why haveupdate_gi.shat all, except as an alternative installer?Edit: Also, why is the game path being searched for by the script
Genshin Impact Gamewhen on every install I've done for friends and on my own live system and VMs, it's alwaysProgram Files\Genshin Impact?@EvilSupahFly
config.iniis read by the game itself to determine the its service integration with Epic Games, Google Play, Bilibili or the standard one.It is also used by the official launcher to determine the currently installed game version. You can test this easily by lowering the setting value of
game_version. The launcher will then ask you for updating your "old" game.Speaking of the official launcher - its default installation directory is
C:\Program Files\Genshin Impactand the game is (by default) installed to the subdirectory namedGenshin Impact game.The
update_gi.shscript was added because until Wine 8.7 - I will put a note to TROUBLESHOOTING.md soon - winedevice leaked memory, resulting in unacceptable RAM usage while downloading. If you happen to have a recent Wine version, you might as well give the official launcher a try which now works very well. However, the game should still be started fromlauncher.batto ensure that crash reports are not sent to their servers.That's interesting about the location. When I installed the game initially from the Anime Game Launcher (circa patch 238), it installed everything to the launcher folder, and didn't create a new sub-folder, but I was mostly playing it on the PlayStation and would only jump to my PC if my kids wanted to join worlds. It's been a long time since I was actually on the PC version, so when I went to update using the 370 script, after the Anime Launcher failed to update, it complained. I'm going to just nuke the entire thing and start over. I wanted to do it through Lutris, but the only working install script forces WINE to run with a Virtual Desktop, which I didn't want.
Thanks for the update!
@EvilSupahFly
config.iniis only created and used by the official game launcher.If you don't use it, either create a stub file manually or edit an updater script.
You only need to provide the installed game version.
Honestly I think it's much easier just to download a full ZIP with the client each update using a direct link...
I assume the question is answered. If there is still something unclear, please let me know.