Unreal Engine Issues

Insufficient stack size in async MediaCapture thread

Reported from our partner Babooblab: The UDN Customer does not give any detailed information to reproduce the issue. However they specify the kind of issue (stack overwflow) and give a possible sol ...

EnhancedInput Chorded Actions do not work on higher priority mappings

Reported from Prismatic: It appears that the Add Mapping Context function currently prioritizes low numbers over high numbers, which seems inconsistent with the function description and some parts ...

Static Mesh cooking: Bad mesh description should not crash the cooker

FStaticMeshRenderData::Cache has the assertion: checkf(Owner->IsMeshDescriptionValid(0), TEXT("Bad MeshDescription on %s"), *GetPathNameSafe(Owner)); This assertion can be triggered by data erro ...

Nanite mesh is shown with player collision

Optimize FActorFolders when there's level streaming in PIE.

This will need more investigation, but at least in PIE (to check if we can do the same in editor), when a level is streamed-in, we should only add the new missing folders for this level and when str ...

[AI] BT cooldown decorator fails on initial startup

BT cooldown decorators are failing on starting a game either via PIE or Standalone regardless of the fact their branches have not yet run. This is true for if the cooldown decorator checks its value ...

SlateScriptingCommands plugin loads too late to receive MainFrame RegisterCommandList broadcast

This was reported on UDN. TL;DR: A user has reported that a custom command cannot be added to the "MainFrame" context in the UUICommandsScriptingSubsystem from their plugin. The problem seems to b ...

[Quartz] - Playing a Force Inline SoundWave asset with PlayQuantized crashes editor

Calling PlayQuantized on an asset set to Force Inline crashes editor:Assertion failed: SoundWaveDataPtr->GetLoadingBehavior() != ESoundWaveLoadingBehavior::ForceInline [File:D:\SMoyls_UE5_Release-5. ...

When Sweeping a sphere over a heightfield or trimesh when the sphere is in initial overlap we don't get the exact correct hitpoint. It seems to be the nearest vertex to the hitpoint instead

drag the progress bar in level sequence would crash in debug editor

it seems in FSequencerTimeSliderController::ComputeFrameTimeFromMouse the CursorPos is -nan ...