The crash can be worked around by modifying FFoliageISMActor::Serialize as following code : void FFoliageISMActor::Serialize(FArchive& Ar) { #if WITH_EDITORONLY_DATA if (!Ar.IsCooking()) // ...
a fix was proposed in the UDN but it needs to be tested and revised ...
Workaround: Construct the DefaultSubobject with ... = CreateDefaultSubobject<UMassAgentComponent>(TEXT("MASS"), true); The issue appears to be that the DefaultSubobject holds a pointer to the CDO ...
Resaving the level using ResavePackagesCommandlet is a workaround. ...
Reported by multiple users. When in a networked session a GameplayEffect is automatically removed due to:a tag being added that's not allowed, or (TargetTagRequirements.RemovalTagRequirements.MustHa ...
Referece to the source level should be fixed by FReplaceObjectRefsArchive, but it is not working because ArIsModifyingWeakAndStrongReferences is not set. It can be fixed by setting the flag.class FR ...
Collision build at runtime for LiDAR point cloud does not apply. This applies to Editor and Standalone. If you do not allow collision builds at runtime, this module should not be available at runtim ...
When changing the tangent value, the last value is sometimes not 1.0 [Reproduce sample project] [Link Removed] ...
We had some code using the CA_VALID_POINTER and CA_CHECK_RETVAL annotations which had been working fine up until the 5.3 engine release. In 5.3, we started getting the following compile errors in a ...