Unreal Engine Issues

[CrashReport]UnrealEditor-Chaos!Chaos::TEventContainer<Chaos::FCollisionEventData>::DispatchConsumerData() [EventManager.h:214]

Generated from CrashReporter Error Messages:Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 691] Array ind ...

Third Person Character Package imports with linker errors

I was able to encounter these errors on the latest binary for 4.25.3 when doing a repro for a salesforce ticket. Here is the customers description:When importing the C++ ThirdPersonCharacter package ...

Mesh Vertex Painting Broken for Splines

The mesh painting mode appears to no longer work on splines, as the vertexes seem to have all vertex colors at 1, 1, 1, 1 by default, and can't be removed or painted anything else. ...

DestructibleMesh does not correctly effect vertex color of material.

Destructible Mesh does not correctly affect vertex color. ...

FLinearColor ignores Blue in slate code

When FLinearColor is used inside slate code, the third vector value is ignored. This causes FLinearColor(1,1,1) to produce the same color as FLinearColor(1,1,0). This also causes FLinearColor::Blu ...

Error launching onto HTML5: "Expression (0) failed in \Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:428!"

This is launching on to Firefox 53.0.2 (64-bit) and also occurs in Main. Error message:uncaught exception: ASM_CONSTS<@blob:http://localhost:53501/4354ee7b-de4a-419b-b0bc-5d58ff557ed2:1:38655 _emsc ...

Projects crash when launching onto Firefox 64-bit

QAGame crashes when it launched onto Firefox. The following exception occurs with the error message:*Expression (0) failed in D:\UE4_Dev-Rendering\Engine\Source\Runtime\Core\Private\Async\TaskGraph ...

When adding the UIRenderer to the Movie Render Queue, the rendering output is a difference in PIE and MRQ.

UI rendering in PIE and UIrenderer rendering in MRQ produce different output results. This is because when dealing with fades in the UI, the rendering results should not be different.  Workaround ...

Using the "Keep World" scale rule can result in incorrect relative location when attaching actors

This seems to happen due to a precision error when calculating the relative transform between the socket and the component being attached. Occasionally, one of the transforms will have a scale of (0 ...

Inserting before a FSlateImageRun twice will cause crash