Reloaded-Project
[Granblue Relink: User is stuck after loader successfully loads in its entirety]
I've been stuck in this window for a long time, what should I do to fix it?
I seriously need to buy this game and see what happens here. This is strange.
Would you be able to provide more information about your system? I bought this game but have trouble replicating this.
This is also strange, in that I've never seen the modloader fully initialize before, but the end user be stuck.
Things that come to mind:
- Anything that can overlay/read/alter game visuals (e.g. ReShade, Special K, Video Capture Software)
- This includes anything that renders ontop of the game such as 'Nahimic Audio Driver' which comes preinstalled on some prebuilt/OEM machines.
etc. Anything that would be useful in trying to replicate your setup.
Anything that
Would you be able to provide more information about your system? I bought this game but have trouble replicating this.
This is also strange, in that I've never seen the modloader fully initialize before, but the end user be stuck.
Things that come to mind:
* Anything that can overlay/read/alter game visuals (e.g. ReShade, Special K, Video Capture Software) * This includes anything that renders ontop of the game such as 'Nahimic Audio Driver' which comes preinstalled on some prebuilt/OEM machines.etc. Anything that would be useful in trying to replicate your setup.
Anything that falls under the above @basterzero
im having the same problem now. I was able to use reloaded before and it has the same problem now. I did not add any new mods and it will only startup when all my mods turned off(but the mods are still on). This might happen because I updated the reloaded app, or maybe I forced quit once.
Normally this is printed while loading a code mod. Hmm, actually. Wait, is something trying to be loaded after Steam DRM Bypass?
What's your enabled mod list?
Enabled mod list doesnt matter. Game won't start even if I only enable the GBFR mod manager.
Enabled mod list doesnt matter. Game won't start even if I only enable the GBFR mod manager.
My concern was maybe there was a deadlock in the mod itself, causing it to get stuck on boot; since I only print when mods actually finish loading, not when they start.
Does it happen without any mods enabled at all?
It won't happen without any mod. However, all my mods are loaded even I disabled all of them.
Is the problem specific to GBFR ModManager mod then?
Try loading something generic like 'Reloaded File Monitor', I presume that works OK?
I'll look in ModManager mod source code then, to see if anything stands out. Gimme a while, I gotta finish up some unrelated work
Actully it doesn't work as expected. if I activate reloaded file moniter in the game page, the command window pops up and exit in 1 sec then the game won't boot. However, If I activate the reloaded file moniter in the manage mods page, in the game page the enable/disable box for reload file moniter is a filled red box(I assume that means enabled), and the game boot normally
Hmm, weird, gimme a while, I'll be back later. Will build some debug versions of mods.
I have reloaded the monitor file. What happens is that when it reaches this screen, it bounces back to the program.
And I tried to remove GBFR Manager, it appears that it can run the game normally, but it cannot run the mods.
I have reloaded the monitor file. What happens is that when it reaches this screen, it bounces back to the program.
And I tried to remove GBFR Manager, it appears that it can run the game normally, but it cannot run the mods.
Are you saying that it runs correctly in this situation then?
Unfortunately, I just run into the same problem and I wonder if there is already a solution now.
I successfully run the game with mods in it at first but failed on the second attempt.
I am just stuck in this window and it cannot run the game again.
I can manually start the game with these mods in it even if I disabled all of them, which is just the same situation as above.
I'm not very good at English, and I'm sorry if I can't describe this situation clearly.
I could probably try debugging it myself but I'd suggest asking the current project maintainer ( @Nenkai ) in case this is a common situation / known problem.
It seems that utility manager is stuck deadlocked on boot.
I've seen this problem very rarely from various people, but never personally I'm not sure. There should be enough error messages during and after initialization, which aren't being fired at all
Maybe it is stuck during the loader's logic somewhere, but I wouldn't know where without an exact setup to reproduce
I've seen this problem very rarely from various people, but never personally I'm not sure. There should be enough error messages during and after initialization, which aren't being fired at all
Maybe it is stuck during the loader's logic somewhere, but I wouldn't know where without an exact setup to reproduce
I'd usually try doing the following:
- Check for any async code (check for anything that waits).
- Check for any silent exceptions tied to async code.
If nothing else, just add log lines all over the place and grab someone who's affected by the issue. Should make things easier.
Apologies for the very delayed reply,
As far as I know we are not using any async code here but i've added further logging in the newest version to at least know whether the loader's entrypoint is even being hit - every errornous phase should've already been logged before this though, maybe third party lib code deadlocking, hard to tell.
Thanks for the suggestions!