1.Pasting the content of OutlinerCrash.txt into the Outliner will inevitably cause a crash.
2.Pasting the content of SequenceCrash.txt into the Sequence will inevitably cause a crash, but my tests on version 5.6 suggest the crash has been fixed. Please verify.
重现步骤
Hello [mention removed]
Thank you for reaching out and bringing these issues to our attention.
I was able to reproduce the Sequence crash using the text from SequenceCrash.txt. I’ll investigate some more and get back to you.
Regarding the OutlinerCrash.txt text, I was not able to crash my Editor. Here, pasting the text into the Outliner only created a Folder called grass:
[Image Removed]Let me know if there are any missing steps to reproduce this crash.
All the best,
[mention removed]
Pasting the content of OutlinerCrash.txt into the Outliner will inevitably cause a crash.
Regarding this issue, I tried versions 5.52, 5.5, and 5.6, and they all crashed. However, I did miss some preconditions—my apologies!
Please open the provided test case: open the project UE5_UDN_Cases, then open /Script/Engine.World’/Game/FoliageTest.FoliageTest’. Pasting into this level will cause a crash. I’ve also attached a crash log. Additionally, I’d like to add another question: Why does the engine ignore the characters after “grass” when I paste a folder named “grass mesh”? Can this be improved as well?
Crash Log
Hello [mention removed]
Thank you for the added context and for providing a repro project, but still, pasting the contents of OutlinerCrash.txt into the Outliner, or anywhere inside the Editor, while having the FoliageTest open, did not cause a crash in my system; it just kept creating more folders:
[Image Removed]
Regarding your question, I was able to check that if you want the folder to be called grass mesh, you need to enclose the whole text in “”, like so:
Begin FolderList Folder="grass mesh" End FolderListLet me know if you can think of anything else that might trigger the crash.
All the best,
[mention removed]
Hi, I’m still able to consistently reproduce the crash even after clearing the DerivedDataCache and Intermediate folders. I’m not sure if it’s related to my hardware configuration (AMD CPU & RTX 3090), but the issue doesn’t occur on my other Intel-based computer. Here’s the crash log for your reference.（UE5_UDN_Cases_v03.log）
BTW，The grass mesh was copied manually—why isn’t it automatically enclosed in quotation marks? This could cause the “mesh” folder to be lost during pasting. Are there plans to optimize this?
[Image Removed]
Hello [mention removed]
I’m yet to reproduce the crash you described.
Maybe it’s an encoding issue?
What language is your system running on?
Here, I use International English for both my OS and Unreal.
Although I was not able to reproduce your crash, I was able to pinpoint where the double quotes are missing:
`FString SSceneOutliner::ExportFolderList(TArray InFolders) const
{
FString Buffer = FString(TEXT(“Begin FolderList\n”));
for (auto& FolderName : InFolders)
{
Buffer.Append(FString(TEXT(“\tFolder=”)) + FolderName.ToString() + FString(TEXT(“\n”)));
}
Buffer += FString(TEXT(“End FolderList\n”));
return Buffer;
}`I’ll make an issue report for the missing double quotes.
While you wait for a fix to be incorporated into the engine, you can change the code at that point, and your folders with spaces should be treated correctly.
If you don’t want to rely on engine changes, I suggest trying a different naming strategy for your folders. For instance, by using a character to differentiate between names, like grass_mesh or grass-mesh.
All the best,
[mention removed]
Hello [mention removed]
I was testing your other report regarding the Sequencer crash.
Previously, I was able to reproduce the crash by pasting that shared text on the Sequencer of UE5.6 Preview, but after updating to 5.6.0-43139311, the release version, the crash stopped.
I get two warnings, and those look tied to a missing reference from your project:
LogProperty: Warning: ObjectProperty /Script/Sequencer.MovieSceneCopyableBinding:SpawnableObjectTemplates.SpawnableObjectTemplates: unresolved reference to '"/Script/Engine.RectLight'/Game/Levels/Release/SystemLevel/HeroChoose/NewLevelSequence1.NewLevelSequence1:MovieScene_0.RectLight_1'"' LogProperty: Warning: ObjectProperty /Script/Sequencer.MovieSceneCopyableBinding:SpawnableObjectTemplates.SpawnableObjectTemplates: unresolved reference to '"/Script/Engine.RectLight'/Game/Levels/Release/SystemLevel/HeroChoose/NewLevelSequence1.NewLevelSequence1:MovieScene_0.RectLight_1'"'Would it be possible for you to check if the same applies to you?
Does the crash still happen after updating to the release version?
If that’s the case, it would be great if you could provide a minimal project where the issue manifests itself.
Let me know.
All the best,
[mention removed]
Hello [mention removed]
Regarding the missing double quotes, I’ve made a JIRA report to be added to the Unreal issue tracker website (https://issues.unrealengine.com).
Please note that Epic ultimately determines whether the issue will be made publicly accessible, and the process can take a few days; therefore, the tracking link may not be immediately accessible.
Once available, you will be able to track the resolution at Unreal Engine Issues and Bug Tracker (UE\-295686)
I’ll be waiting for your reply regarding the Sequencer issue.
All the best,
[mention removed]
Hi, regarding the folder paste crash, I’ve discovered critical evidence and confirmed it’s reproducible across all machines. It was extremely difficult to pinpoint. When all three panels (Light Mixer, Env. Light Mixer, View Changes) are simultaneously open, creating a new level, then creating a new folder > copying the folder > pasting will consistently crash the editor. I haven’t investigated further since other combinations of these three windows might also cause crashes. Please reproduce using the provided Layout config file:
Reproduction Method: Place CrashLayout.ini in C:\Users\XXX\AppData\Local\UnrealEngine\5.6\Saved\Config\Layouts. Launch UE5.6, load this Layout, create a new level, and follow the video operations to reproduce the crash.
I’ve provided two reference videos: The non-crash video shows only two of the windows open, while the crash case has all three windows open.
Regarding the Sequencer issue, as I initially stated, it no longer exists in 5.6. If you also can’t reproduce it, clearly the bug has been resolved.
Thank you for your patience – together we’ve pinpointed the issue.
Hello [mention removed]
Thank you for the time you dedicated to pinpointing this insidious bug!
During my tests, I noticed that while both Light Mixer and View Changes were open, pasting a folder into the Outliner would generate a crash on a newly created scene, as well as a scene that was not the one the engine opens by default - the Project Default scene did not crash upon pasting a folder, and this might be used as a workaround: set your working scene as the one the engine opens by default.
I’ve made another JIRA report to be added to the Unreal issue tracker website (https://issues.unrealengine.com).
Please note that Epic ultimately determines whether the issue will be made publicly accessible, and the process can take a few days; therefore, the tracking link may not be immediately accessible.
Once available, you will be able to track the resolution at Unreal Engine Issues and Bug Tracker (UE\-296010)
As I believe we have addressed the issues you reported, I’ll close the case.
However, please feel free to reply if you have anything else to add.
All the best,
[mention removed]