The frame appears to be getting skipped entirely, but the timing for the frames on either side of them is correct, ie: if frame 10 is skipped, frame 9 and 11 still match the working case, so the ove ...
Calling PlayQuantized on an asset set to Force Inline crashes editor:Assertion failed: SoundWaveDataPtr->GetLoadingBehavior() != ESoundWaveLoadingBehavior::ForceInline [File:D:\SMoyls_UE5_Release-5. ...
The cursor position is no longer updated during drag and drop, so drag-over events cannot respond correctly. Commenting out the following code in WindowsCursor.cpp works as a workaround ( the behavi ...
Parameter names do not update on custom functions that are already called in event graph after compiling blueprint. ...
If a blueprint has "Simulate Physics" active on a component, it will not render when running standalone game. ...
If a "Destroy Component" has a target of self within a blueprint component, the "Destroy Component" node will not trigger. ...
Collapse to Function creates a ReturnNode that cannot be deleted. When creating a new Function, the ReturnNode is not mandated like this, so this seems inconsistent. Included is a screenshot of thi ...
In a State Machine, deleting a state and hitting undo causes any transitions that were attached to that state to become broken. They appear as the circular transition node icons, but aren't connect ...
Edit MattK: This probably has nothing to do with FBX. The object has a mass of 28 million kg so it would appear that the calculation of mass/physics asset is busted which is causing the flickering ...