Unreal Engine 5.5 Released

[IronicParadox]

@IronicParadox

RayTracingDevice->CreateStateObject(&Desc, IID_PPV_ARGS(Result.GetInitReference())) failed 
 at D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12RayTracing.cpp:663 
 with error E_INVALIDARG

Still getting these errors when launching a DX12 SM6 packaged game for the SECOND time when HWRT(r.Lumen.HardwareRayTracing or the “Use hardware raytracing when available” in the project settings) is enabled or gets enabled during runtime.

Just to be clear: The game will launch fine on the FIRST launch, but then crashes with that error on the SECOND or any further attempts to launch it after that. The culprit is the _PCD3D_SM6.upipelinecache file located in the %localappdata%/GAMENAME/SAVED folder. If that file gets deleted, the game will launch correctly again for a first time, but will again, crash every time after that.

Windows 11 23H2
13600kf
2080FE+566.14 drivers

I also tested on a similar system with an AMD 7900xt and it did the same thing. I also tested using Vulkan SM6 and it doesn’t have this issue.

5.5.2 fixed this issue. Before, the workaround was to uncheck the “share material shader code” option in the project->packaging settings. I re-enabled it, packaged the project and it doesn’t crash any more.

[nande]

Which branch should i use to get 5.5.2?

i’m currently on branch “5.5”, i just went to Help> About and it says “Version: 5.5.2-0+UE5” so i guess it’s 5.5.2.
but when i did git pull it only changed one file with very little changes.
i’ve noticed @Tina_Wisdom shown a ton of changes.

If i go to github and compare release with 5.5 it shows more than 5K+ commits

if i compare 5.5 with the tag 5.5.2-release i also get 5K+

if i compare the tag 5.5.2-release to release branch there are no differences

i don’t want to stay on release since i don’t want it to update to 5.6 automatically one day.
and staying on the tag is uncomfortable since sometimes i want to update to 5.5.3 if it comes.

but in any case, i’m not sure now if 5.5 has 5.5.2 or not, or whether i should stay on those types of branches to get the latest 5.5.x (or when 5.6 is out would i get 5.6.x on the 5.6 branch?)

i have heard epic uses a custom set up for their cvs, so maybe that’s what’s going on.

i’m confused with this. does anyone from epic knows what’s the best?

[Amanda.Schade]

Hey everyone!

Our team is aware of a critical issue impacting existing overrides on Skeletal Mesh Assets when updating a project from 5.5.X to 5.5.2.

Background:
If an Actor within the Level Viewport has a Blueprint-added Skeletal Mesh Component where the Skeletal Mesh Asset has been overridden, the overridden value will be lost after the update. It will appear simply that the mesh on the Actor has changed after the update. This does not affect Actors that have natively added Skeletal Mesh Components, i.e. C++ classes like Character are not affected.

If a project has already been updated, the overridden values cannot be recovered. The overrides will either need to be set manually or fixed via a script or Blueprint Editor Utility.

Next steps:
To quickly address this critical issue, we are backing out code that fixed an issue causing Skeletal Meshes to not update on Blueprint construction. If you’re planning to update your project, we recommend holding off until the 5.5.3 Hotfix. This does not impact new projects created in 5.5.2.

ETA on the Hotfix:
Look for that update in a Hotfix in the coming days—apologies for any disruptions in the meantime.

[mostapenko]

Weeks of work lost because of a sporadic bug where I cannot save a certain file (hangs at 0%, no its not the referenced master material related). This is not present in 5.3.2. One of the worst releases I’ve ever used. Cannot recreate it, and cannot fix it in the solution where work needs to be done. Chased it down to a lock that is waiting for an (editor ui) frame to be rendered…