[Bug]: BH3 after game repair using 1.84.3 Preview got "Scene 'GameEntry' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded."

[XiaoMingXD]

Affected Version

1.84.3 Preview

Bug Behavior

after repair the game using 1.84.3 preview version of the Collaps. Start game stuck at the "miHoYo" logo screen.

game log at "C:\Users%username%\AppData\LocalLow\miHoYo\崩坏3" got error bellow.
Scene 'GameEntry' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded.
To add a scene to the build settings use the menu File->Build Settings...
MoleMole.Miscs:LoadScene(String, String, LoadSceneMode)
MoleMole.d__4:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

Expected Behavior

Start the game normaly.

Steps to reproduce

1. update the Collaps to 1.84.3 Preview.
2. run game repair in Collaps of BH3 Mainland China.
3. Start the game.

Related Issues

No response

Screenshot(s)

Additional Information

No response

[neon-nyan]

Hi there,
We have bunch of fixes undergoing for the next version and backport on stable. Can you try this canary build, run Game Repair and see if it fixes your issue?

202606011154-localdev-build_net11_wasdk214-exp8.7z

[XiaoMingXD]

Sure, I'll let you know whether the issue is fixed.
Thanks.

[XiaoMingXD]

I've tried the version you sent.

The good news is that the game is working now after running Game Repair with the new launcher.

At the moment, I haven't been able to reproduce the error I encountered before even using the latest preview.
So it seems the issue has been resolved, although I'm not sure what exactly caused it in the first place.

Thanks for your help.

[neon-nyan]

I've tried the version you sent.

The good news is that the game is working now after running Game Repair with the new launcher.

At the moment, I haven't been able to reproduce the error I encountered before even using the latest preview. So it seems the issue has been resolved, although I'm not sure what exactly caused it in the first place.

Thanks for your help.

Glad it fixed your issue 🎉
We are going to keep this issue open until we shipped the fixes in both new Stable and Preview releases.