Note: This issue persists even after applying the fix from //UE5/Main CL 45797729, which addressed a related issue.

We've encountered a crash in UWidgetAnimation::CreateDirectorInstance when repeatedly switching resolutions. We've had it for a while but it's not until recently that we've found a consistent repro.

Our understanding is that it's a lifetime issue. Sequence of events:

1. Viewport resizing triggers Slate to rebuild its widgets
2. Some widget with an active animation gets destroyed/marked for delete
3. UMGSequenceTickManager::ForceFlush is called
4. During Flush MovieSceneEventSystem::TriggerEvents fires
5. Consequently CreateDirectorInstance is called on UWidgetAnimation
6. GetPlaybackContex() returns null
7. CastChecked LogFatal (crash)

One suggested fix would be to detect zero scale and clamp it to some very small nonzero value. Note, though, that almost immediately below the scale factor calculation, there is a comment in the code warning about the drift that may be caused by the current method.

I’ve found an issue with the visualization of PlayerCollisions when using LandscapeSplineMesh with a mesh that has Nanite enabled. The Chaos collisions shown in the Chaos Visual Debugger are correct. It therefore seems to be an Editor issue where the deformation is not applied when Nanite is turned on. If I disable Nanite, the collisions are displayed correctly.

Is this a known issue? Will there be a fix in upcoming versions?

The showFlag.CollisionVisibility 1 cvar is a viewport visualization mode that highlights which Actors will block visibility. The showFlag.CollisionPawn 1 cvar is a Player Collision viewmode which highlights assets that collide with a character or Pawn. In these modes, only the respective collisions are rendered in the viewport.

Problem

The licensee noticed that setting `showFlag.CollisionVisibility 1` in one of their production levels seemed to omit most collision geometry in a Development game build, with `showFlag.CollisionPawn` also exhibiting the same issue. Everything seems to work fine in PIE and when the licensee tried a test level everything seemed fine at first, but then they noticed a select few assets were indeed missing in the collision view. Most of the test level is composed of simple block-out meshes which do not have Nanite enabled, but the pieces with no collision drawn (they do have collision) were production assets with Nanite enabled.

It is the licensee's understanding that the `showFlag.CollisionVisibility` and `showFlag.CollisionPawn` views should work in Development builds of the game, but this doesn't seem to be happening for StaticMesh assets that have Nanite enabled. Since nearly all of their production assets are going to have Nanite enabled this is going to make the collision views in game builds entirely unrepresentative.

Additional Notes

[Link Removed]

Adding a Delay task instead will allow this to work if the delay is greater than that used in Level 2a. If you remove the task from Level 1c, it will also transition to Level 2b as expected. Adding an empty parent state to Level 1c with no changes in tasks also works.

Root cause is in UMovieSceneSkeletalAnimationSection::GetAutoSizeRange (MovieSceneSkeletalAnimationSection.cpp:337). It calls InnerToOuterTransform.TryTransformTime(InnerEndTime).Get(InnerEndTime), and when the inverse transform fails to map InnerEndTime to an outer time (because the value is outside the Inner Clamp or Inner Loop range), the .Get(InnerEndTime) fallback returns the raw inner-tick value. That value is then used as if it were an outer-tick value in GetInclusiveStartFrame() + (OuterEndTime - OuterStartTime).FrameNumber, mixing inner-tick and outer-tick values and producing a negative or otherwise invalid length. SetRange then refuses the range and Auto Size has no effect.

This behavior was introduced by CL 40829088 ( [Link Removed] Closed , fixed in 5.6), which replaced the previous TOptional check with a .Get(fallback) pattern.

The issue occurs regardless of what kind of points and data are coming in, how many iterations you add, or any other settings. The results are always a crash.

When reproducing this issue, the editor will crash with the following error:
Assertion failed: IsRotationNormalized() [Link Removed] [Line: 1307]

WORKAROUND:

Unchecking and rechecking the Custom Items and Inventory setting will re-apply the change to the currently loaded Island Settings object. Be sure to save!

After getting the below message

LogTextStoreACP: Verbose: GetTextExt - From 33 to 34

A line break past that range is inserted. However, when typing Korean, the correct range is not selected. Instead, it remains fixed at 'From 33 to 34' , which prevents Korean input.

Additional Notes

Even after the bug occurs, Korean input still works when typing before position 33. ([Link Removed])

The same issue also occurs in the default Editable Text and Editable Text (Multi Line) widgets

See also the attached video demonstrating the bug