This sounds legit. Anyone mess with the if node recently? There seems to be a regression where existing content is broken. This should be fixed ASAP and patched into 4.6. https://forums.unrealen ...
Major performance drop with instanced meshes since PhysX 3.4 upgrade Regression: YES Worked: 3172292 (4.13.2) Broken: 3249277 (4.14.3) For me, my results were: 4.8 through 4.13 No Collision - ...
REGRESSION: Yes, did not occur in 4.22 In the Content Examples Niagara map, the emitters at display 3.4 are not rendering when at runtime. There were some fixes for this (or a similar issue) for V ...
Projects that worked normally in 4.18, failures occurred in 4.19. Resolve by replacing the contents of the LevelSequence that is the cause of the problem with the new asset.Perhaps a problem has occ ...
Some users are experiencing a crash when converting their project from 4.7 to 4.8. From user reports it appears to be affecting those who have added code to their projects and created blueprints bas ...
Any material that already exists in 4.11p1, with tessellation enabled, causes assigned geometry to disappear. Any material created within 4.11p1, with tessellation enabled and a base color, causes t ...
This is a regression in behavior between 4.14.1 and 4.14.2! The editor will crash when importing FBX meshes that have multiple material ID assignments. If it's a single material ID it will import w ...
When using any of the Set Linear Limit nodes (X/Y/Z) and converting a project from a previous version of the engine, the nodes get their Constraint Type value reset to Free. I tested this with proje ...
Upgrading a project to version 4.24.1 results in a loss of functionality that worked from 4.20 to 4.23.1 without having made any changes. Test Project: [Link Removed] Tested: 4.25 CL: 11062379 ...
Converting a project from 4.8.3 to 4.10.4 causes external reference spam in the message log>map check window. Seems directly related to [Link Removed]. Making new jira on request. ...