Crash with a specific groom asset in editor only, if applyed on an actor on a level.
When the user move the editor camera around, the editor crash.
It happen rarely when the user start a play in editor session (for some users, it’s 100%, others it happen rarely).
There are no problem on the cooked game, everything work fine.
On the attached callstack,
- Section.PositionBuffer is not null only on the first Section, triggering the check on all the other secions.
- The LODIndex == 2, and it’s coherent with the crash, the asset work fine when the editor camera is near the actor.
I think there are a problem with our groom asset, but i can’t find why, if i open the groom asset, it look fine and no explicite error is displayed. And an editor crash is not a normal behavior on any situation.
[Attachment Removed]
Steps to Reproduce
We use the 5.7.1 version from P4, the attached project is on 5.7.4 from the launcher and the problem is the same.
In the attached project, open a level.
Place the actor /Game/Proto/CharacterTest on the level.
Move the camera a little. Moving far away or turning in a way to not have the actor on the camera is usualy enought.
At this point, the editor crash.
[Attachment Removed]
Hi Nicolas,
Thanks for reporting this issue. I was able to reproduce the crash, so I have created a Jira ticket with the engine team: https://issues.unrealengine.com/issue/UE\-371068\. Are you urgently blocked on this issue? I can imagine crashing in the editor all the time can be a bit of a pain, so maybe we can look for a workaround.
[Attachment Removed]
We have currently removed this asset, and use a simpler placeolder groom that does not crash (or bald npc), until we find a solution.
I think the art team have already made a new version, but i don’t know if this one is fine or have the bug.
[Attachment Removed]
Ok, thanks for the info. Since you are not urgently blocked, I will close out the ticket. Please keep an eye on the issue tracker and reach out again if you don’t see any timely updates.
[Attachment Removed]