I have a blueprint which seems to be stuck continously loading iteself after the game saves. Heres the log:
LogFileHelpers: Saving map 'ImportSHPIntoCesiumTEST' took 0.051
LogFileHelpers: InternalPromptForCheckoutAndSave took 86.916 ms (total: 190.545 ms)
LogContentValidation: Display: Starting to validate 1 assets
LogContentValidation: Enabled validators:
LogContentValidation: /Script/DataValidation.DirtyFilesChangelistValidator
LogContentValidation: /Script/DataValidation.EditorValidator_Localization
LogContentValidation: /Script/DataValidation.WorldPartitionChangelistValidator
LogContentValidation: Display: Validating asset /Game/ImportSHPIntoCesiumTEST.ImportSHPIntoCesiumTEST
AssetCheck: /Game/ImportSHPIntoCesiumTEST Validating asset
LogAssetEditorSubsystem: Opening Asset editor for Blueprint /Game/SpawnBuilding.SpawnBuilding
LogSlate: Took 0.006052 seconds to synchronously load lazily loaded font '../../../Engine/Content/Slate/Fonts/Roboto-Italic.ttf' (157K)
LogBlueprintEditor: Perf: 2.9 total seconds to load all 9 blueprint libraries in project. Avoid references to content in blueprint libraries to shorten this time.
LogBlueprintEditor: Perf: 2.7 seconds loading: /Landmass/Landscape/BlueprintBrushes/Libraries/LandscapeBrushLibrary
LogSlate: Took 0.004196 seconds to synchronously load lazily loaded font '../../../Engine/Content/Slate/Fonts/Roboto-BoldCondensed.ttf' (158K)
LogGeometry: Warning: GeometryScriptError: AppendSimpleExtrudePolygon: PolygonVertices array requires at least 3 positions
LogGeometry: Warning: GeometryScriptError: CreateNewStaticMeshAssetFromMeshLODs: LOD 0 has no triangles
LogBlueprintUserMessages: [SpawnBuilding_C_0] Error When Converting to Static mesh on
LogGeometry: Warning: GeometryScriptError: AppendSimpleExtrudePolygon: PolygonVertices array requires at least 3 positions
LogGeometry: Warning: GeometryScriptError: CreateNewStaticMeshAssetFromMeshLODs: LOD 0 has no triangles
Those warnings continue (Currently on SpawnBuilding_C_53500) with no signs of stopping. This has happened a couple of times now and seeming started after I told the blueprint to destroy itself. Does anyone know whats causing this and how to stop it?