Upgrading a project from 4.11 to 4.12 causes Class Default nodes to disconnect their output pins from other nodes. If the node is reconnected and saved, it will disconnect again when the project is ...
This issue appears to be a continuation of [Link Removed]. Hot reloads work successfully in projects that were created in 4.15 or 4.16 and are still using the same Engine version that they were crea ...
According to information from the licensee, the else clause was added to "FSkeletalMeshLODModel::(GetClothMappingData()" at CL 4437969 , but if it is the cloth data existing from 4.20 or earlier, it ...
User has encountered an exception opening their project when they updated from 4.25.3 to 4.25.4. No repro, log or test project is given at the time. ...
Converting a 4.10 project that includes the Substance Plugin to 4.11 will fail to compile. Workaround: Disabling / removing references to the plugin will allow the project to convert successfully. ...
When upgrading a 4.19.2 project to 4.20 Preview 3 the Nav Area Class is changed to None instead of the value it was before the upgrade. Upgrading from 4.18.3 to 4.19.2 works as expected. This was t ...
Licensee reported that when updating from 4.16.1 to 4.17.2 the value of a function input Boolean is being reset. It is checked as True in 4.16, but when switching to 4.17, it is no longer checked. ( ...
There seems to be a noticeable difference with the temporal AA sharpness in 4.13. This was confirmed by setting Temporal Sample count and sharpness with the same settings in a 4.12 project. A side b ...
Decals are not spawning correctly when spawning based on a rotation value from the hit normal. There is a difference in how this is handled from 4.10.4 to 4.11 and even 4.12. See attached image fo ...
When converting a project from 4.10/4.11 to 4.12(or later) the relative scale of the sockets on skeletal meshes will be changed to 1,1,1 regardless of the previous settings. ...