Issues related to standalone game

[nkdtr]

Thank you for a great plugin!

During game development, I encountered the following issues in StandaloneGame:

1. Failed to exit the map (moving to another map or using RestartLevel)
2. Failed to start map when using the Dungeon Sub Level Database.

I confirmed this behavior in UE5.4, UE5.6, and the latest plugin version for them.

[shun126]

Thank you for contacting us.
I have tried to think of a situation where the glitch could occur, but could not come up with one.
Could you give us some more details about the situation?
For example, what steps are causing the problem, and what error message, if any, is displayed?

[nkdtr]

Clearing the Dungeon Sub Level Database allows the game to start, but executing the RestartLevel command causes CrashReporter to output the following call stack:

Assertion failed: GEditor [File:D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorActorFolders.cpp] [Line: 56]

UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_DungeonGenerator!ADungeonGenerateBase::DestroySpawnedActors() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\DungeonGenerator\Source\DungeonGenerator\Private\DungeonGenerateBase.cpp:326]
UnrealEditor_DungeonGenerator!ADungeonGenerateBase::Dispose() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\DungeonGenerator\Source\DungeonGenerator\Private\DungeonGenerateBase.cpp:390]
UnrealEditor_DungeonGenerator!ADungeonGenerateBase::EndPlay() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\DungeonGenerator\Source\DungeonGenerator\Private\DungeonGenerateBase.cpp:202]
UnrealEditor_Engine
(...)

[shun126]

We are really sorry for the inconvenience. Thank you very much for sending us the report.
We have tried to reproduce the problem by creating what we believe to be the same environment, but it never crashed.

1. Enable DungeonGenerator in a new blank project
2. Clear sublevel designations in DGP_Sample
3. Open the Demonstration map in the plugin and start StandaloneGame

Would the same phenomenon occur with this procedure?

[nkdtr]

I apologize for the confusion, but I am reporting two separate phenomena.

case A

1. Enable DungeonGenerator in a new blank project
2. Open the Demonstration map in the plugin and start StandaloneGame

case B

1. Enable DungeonGenerator in a new blank project
2. Clear sublevel designations in DGP_Sample
3. Open the Demonstration map in the plugin and start StandaloneGame
4. "RestartLevel" with the console command

[shun126]

I tried to recreate the same issue by creating a blank project in UE5.6, but it didn't work. There's one thing I'm concerned about: I opened the following file in a text editor...

D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\DungeonGenerator\Source\DungeonGenerator\Private\SubLevel\DungeonSubLevelDatabase.cpp:131

bool IsTryingToLoadCurrentlyEditedMap(const FString& targetMapPackageName)
{
	if (const auto* editorWorld = GEditor->GetEditorWorldContext().World())
	{
		if (editorWorld->PersistentLevel)

Will it crash if I change the above part to the following?

bool IsTryingToLoadCurrentlyEditedMap(const FString& targetMapPackageName)
{
	if (GEditor)
	{
		if (const auto* editorWorld = GEditor->GetEditorWorldContext().World())
		{
			if (editorWorld->PersistentLevel)

[nkdtr]

Thank you for your confirmation.

I modified the source code and built it, but it still seemed to crash.
(In case A, the crash position appears to have changed.)

It's strange that you're not experiencing any issues in your environment.
Could it be dependent on the environment, such as the compiler?

Since building the plugin locally this time produced a more detailed call stack, I've attached it for your reference.

case A

Assertion failed: false [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\UnrealEngine.cpp] [Line: 16496]

UnrealEditor_Core!FDebug::CheckVerifyFailedImpl2() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Misc\AssertionMacros.cpp:728]
UnrealEditor_Engine!HandleInvalidWorldContext() [D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\UnrealEngine.cpp:16496]
UnrealEditor_Engine!UEngine::LoadPackagesFully() [D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\UnrealEngine.cpp:16372]
UnrealEditor_Engine!UGameInstance::CreateGameModeForURL() [D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\GameInstance.cpp:1582]
UnrealEditor_Engine!UWorld::SetGameMode() [D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\World.cpp:5679]
UnrealEditor_DungeonGenerator!UDungeonSubLevelDatabase::Convert() [C:\UEProjects\DungeonTest\Plugins\DungeonG25833380f055V12\Source\DungeonGenerator\Private\SubLevel\DungeonSubLevelDatabase.cpp:171]
UnrealEditor_DungeonGenerator!UDungeonSubLevelDatabase::Build() [C:\UEProjects\DungeonTest\Plugins\DungeonG25833380f055V12\Source\DungeonGenerator\Private\SubLevel\DungeonSubLevelDatabase.cpp:90]
(...)

case B

Assertion failed: GEditor [File:D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorActorFolders.cpp] [Line: 56]

UnrealEditor_Core!FDebug::CheckVerifyFailedImpl2() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Misc\AssertionMacros.cpp:728]
UnrealEditor_UnrealEd!FActorFolders::FActorFolders() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorActorFolders.cpp:56]
UnrealEditor_UnrealEd!FActorFolders::Get() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorActorFolders.cpp:88]
UnrealEditor_DungeonGenerator!ADungeonGenerateBase::DestroySpawnedActors() [C:\UEProjects\DungeonTest\Plugins\DungeonG25833380f055V12\Source\DungeonGenerator\Private\DungeonGenerateBase.cpp:326]
UnrealEditor_DungeonGenerator!ADungeonGenerateBase::Dispose() [C:\UEProjects\DungeonTest\Plugins\DungeonG25833380f055V12\Source\DungeonGenerator\Private\DungeonGenerateBase.cpp:390]
(...)

[shun126]

Thank you. I was able to find the cause from this log. I will fix it as soon as possible, so please give me some time. Until then, please try using PIE.

[nkdtr]

Thank you for your cooperation!

[shun126]

Version 1.7.6 has been released. DungeonGeneratorDemo has also been updated accordingly.

A known issue is that if you enable the Actor property "Cooking" > "Is Editor Only", it will crash when running "Standalone". We are still investigating how to fix this. "Is Editor Only Actor" can be used without any issues.