When I launch the game using "wine cmd /c launcher.bat", the game is consistently stuck at the "prepare to load data" at 0% and the screen completely froze (while the music plays on). It's after the game successfully checks for updates but before the door is even shown. So I cannot play at all.
I know my setup works as I was able to play when launching via launcher.exe. This approach worked till today because launcher.exe suddenly thinks the game is not even installed (the yellow Launch button is replaced with a "Get Game" button).
Help! Let me know what additional info you need.
When I launch the game using "wine cmd /c launcher.bat", the game is consistently stuck at the "prepare to load data" at 0% and the screen completely froze (while the music plays on). It's after the game successfully checks for updates but before the door is even shown. So I cannot play at all.
I know my setup works as I was able to play when launching via launcher.exe. This approach worked till today because launcher.exe suddenly thinks the game is not even installed (the yellow Launch button is replaced with a "Get Game" button).
Help! Let me know what additional info you need.
It seems MHY changed something about their launcher, as the old version and game download links are no longer working. Maybe you should try to update the launcher?
It seems MHY changed something about their launcher, as the old version and game download links are no longer working. Maybe you should try to update the launcher?
Thanks Alex! Your instinct was right! I installed with a new launcher and sure enough the problem went away, and everything worked as before.
The launcher.bat is still stuck somehow, so I'm curious about the differences between the two ways of launching.
Thanks Alex! Your instinct was right! I installed with a new launcher and sure enough the problem went away, and everything worked as before.
The launcher.bat is still stuck somehow, so I'm curious about the differences between the two ways of launching.
You're always supposed to run the game through launcher.bat because it does some additional security checks prior starting the game.
To figure out what's going wrong, run wine cmd /c launcher.bat from the terminal or check the output log if you're using Lutris. It might be related to an earlier reported issue where certain utility programs (find.exe) are not included in some Wine packages.
You're always supposed to run the game through `launcher.bat` because it does some additional security checks prior starting the game.
To figure out what's going wrong, run `wine cmd /c launcher.bat` from the terminal or check the output log if you're using Lutris. It might be related to an earlier reported issue where certain utility programs (`find.exe`) are not included in some Wine packages.
It's a great idea to ensure /etc/hosts is correct (out of curiosity, is this the only concern here?) We all want your great work to continue.
The lockup I experienced is related to stdout somehow. The game plays without a glitch if wine stdout is redirected: wine cmd /c launcher.bat > /dev/null
Ideas?
It's a great idea to ensure /etc/hosts is correct (out of curiosity, is this the only concern here?) We all want your great work to continue.
The lockup I experienced is related to stdout somehow. The game plays without a glitch if wine stdout is redirected: wine cmd /c launcher.bat > /dev/null
Ideas?
launcher.bat also prepares the service and marks it as running within the registry, in case the game ever checks for it.
Regarding the lockup, you could try to append the Unity argument -nolog in the last line of launcher.bat. I've noticed a similar issue on older Wine builds (~ 5.17) but it vanished after either a newer DXVK build or Wine 6.0 (stable).
if wine stdout is redirected: wine cmd /c launcher.bat > /dev/null
...but Wine logs to stderr, which would be 2> /dev/null. If you're sure that Wine is causing it, you can customize the output using the environment variables:
WINEDEBUG=-all wine ...args... or respectively
DXVK_LOG_LEVEL=none wine ...args... for DXVK messages
`launcher.bat` also prepares the service and marks it as running within the registry, in case the game ever checks for it.
Regarding the lockup, you could try to append the Unity argument `-nolog` in the last line of `launcher.bat`. I've noticed a similar issue on older Wine builds (~ 5.17) but it vanished after either a newer DXVK build or Wine 6.0 (stable).
> if wine stdout is redirected: wine cmd /c launcher.bat > /dev/null
...but Wine logs to stderr, which would be `2> /dev/null`. If you're sure that Wine is causing it, you can customize the output using the environment variables:
* `WINEDEBUG=-all wine ...args...` or respectively
* `DXVK_LOG_LEVEL=none wine ...args...` for DXVK messages
-nolog (should this be the default?) solved it. So Unity is not playing well with stdout in my env? I'm using Wine 5.19-staging. Would you recommend 6.0 stable?
You're the man Krock!
-nolog (should this be the default?) solved it. So Unity is not playing well with stdout in my env? I'm using Wine 5.19-staging. Would you recommend 6.0 stable?
Sorry, I don't know what's causing it but will update TROUBLESHOOTING accordingly. I also gave (stock) Proton 5.13 some tries, and that issue did not occurr to me again.
Feel free to test other Wine logging levels (-all for example), turn off DXVK outputs or upgrade DXVK. There's nothing I can do without a reliable way to reproduce it.
EDIT: Workaround found. If you find an explanation for this, or a more reliable solution, please answer below.
Sorry, I don't know what's causing it but will update TROUBLESHOOTING accordingly. I also gave (stock) Proton 5.13 some tries, and that issue did not occurr to me again.
Feel free to test other Wine logging levels (`-all` for example), turn off DXVK outputs or upgrade DXVK. There's nothing I can do without a reliable way to reproduce it.
EDIT: Workaround found. If you find an explanation for this, or a more reliable solution, please answer below.
When I launch the game using "wine cmd /c launcher.bat", the game is consistently stuck at the "prepare to load data" at 0% and the screen completely froze (while the music plays on). It's after the game successfully checks for updates but before the door is even shown. So I cannot play at all.
I know my setup works as I was able to play when launching via launcher.exe. This approach worked till today because launcher.exe suddenly thinks the game is not even installed (the yellow Launch button is replaced with a "Get Game" button).
Help! Let me know what additional info you need.
I'm hoping this is something trivial, i.e., some missing launch parameters? Is there a quick way to figure this out?
It seems MHY changed something about their launcher, as the old version and game download links are no longer working. Maybe you should try to update the launcher?
Thanks Alex! Your instinct was right! I installed with a new launcher and sure enough the problem went away, and everything worked as before.
The launcher.bat is still stuck somehow, so I'm curious about the differences between the two ways of launching.
You're always supposed to run the game through
launcher.batbecause it does some additional security checks prior starting the game.To figure out what's going wrong, run
wine cmd /c launcher.batfrom the terminal or check the output log if you're using Lutris. It might be related to an earlier reported issue where certain utility programs (find.exe) are not included in some Wine packages.It's a great idea to ensure /etc/hosts is correct (out of curiosity, is this the only concern here?) We all want your great work to continue.
The lockup I experienced is related to stdout somehow. The game plays without a glitch if wine stdout is redirected: wine cmd /c launcher.bat > /dev/null
Ideas?
launcher.batalso prepares the service and marks it as running within the registry, in case the game ever checks for it.Regarding the lockup, you could try to append the Unity argument
-nologin the last line oflauncher.bat. I've noticed a similar issue on older Wine builds (~ 5.17) but it vanished after either a newer DXVK build or Wine 6.0 (stable)....but Wine logs to stderr, which would be
2> /dev/null. If you're sure that Wine is causing it, you can customize the output using the environment variables:WINEDEBUG=-all wine ...args...or respectivelyDXVK_LOG_LEVEL=none wine ...args...for DXVK messagesYou're the man Krock!
-nolog (should this be the default?) solved it. So Unity is not playing well with stdout in my env? I'm using Wine 5.19-staging. Would you recommend 6.0 stable?
Sorry, I don't know what's causing it but will update TROUBLESHOOTING accordingly. I also gave (stock) Proton 5.13 some tries, and that issue did not occurr to me again.
Feel free to test other Wine logging levels (
-allfor example), turn off DXVK outputs or upgrade DXVK. There's nothing I can do without a reliable way to reproduce it.EDIT: Workaround found. If you find an explanation for this, or a more reliable solution, please answer below.