Both "Create Instance" and "Load Level Instance" nodes always cause a "same GUID" load error. How to avoid?
The level I am instancing contains just a landscape, but whenever I create more than one instance of it, it works but I get load errors complaining that the second landscape instance has the same GUID as the first, and it wants me to save it as a separate file (defeating the purpose of instancing?)
The error message:
Landscape_1 Landscape Landscape_1 of /Game/Maps/UEDPIE_0_A0_LevelInstance_29 has the same guid as Landscape_1 of /Game/Maps/UEDPIE_0_A0_LevelInstance_30. /Game/Maps/UEDPIE_0_A0_LevelInstance_30.Landscape_1 has had its guid automatically changed, please save /Game/Maps/UEDPIE_0_A0_LevelInstance_30!
Here is an example of a script that will produce this error:
I've tried every method of level instancing, with and without World Composition, level blueprints vs actor blueprints, playing Selected Viewport vs Standalone, etc. I can't find any way to not get this error.
Any idea how I should proceed? Or any way to confirm whether this is working as intended and it is safe to build on a foundation that throws out these errors?
Hey guys drag Get World Asset Package FName of the Create Instance function and then use that name to call Load Stream Level
answered Oct 14 '18 at 12:52 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here