Unreal Engine 5.7 Released

General Announcements
, ,
65

UE4 Projects Failing to Launch since the Launcher update before UE5.7 release (19.0.2 Update Status)

2 Likes
66

Can’t start the editor, I’m getting crash on startup every single time. I tried verifying files and reinstalling this version to no avail. 5.6.1 works just fine. Crashlog:

LoginId:b272149447f152fce9b3ebac5b10cc7d
EpicAccountId:deccaeee99924d5e80cee0fd56c42dad

Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Developer\DerivedDataCache\Private\DerivedDataBackends.cpp] [Line: 208]
Unable to use default cache graph ‘InstalledDerivedDataBackendGraph’ because there are no writable nodes available.Add -DDC-ForceMemoryCache to the command line to bypass this if you need access to the editor settings to fix the cache configuration.

UnrealEditor_DerivedDataCache
UnrealEditor_DerivedDataCache
UnrealEditor_DerivedDataCache
UnrealEditor_DerivedDataCache
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

67

have you been able to fix that cook error?

68

I removed wpo wind from shaders graphs. Also took out also extra detail (material functions), removed shared wrap from texture samples, added set material attritubes with only needed inputs. Quite unknown what was causing the error, but managed to cook without errors.

Cooked build is still running odd. Frame time jumps very high ~25ms, while GPU/GameThread andother hit is only 7-11ms. Also even basic landscape grass dosent appear during play. Wondering if the frame time hit is from those voxel trees. Didnt have that kind of hit in UE5.6 and only updated trees when got in UE5.7. :S Unless niagara data channels are working strange. There is new batch node to write to niagara data channel.

Currently cooking dev build to do testing with unreal insight.

1 Like
69

Got Garbage Collection crash during cooked play. Source Effect Chain causing crash when cue ends. That effect chain have simple delay in it:

Object SoundCue /Game/SaOKStuff/X/Sounds/Modern_Weapons_SFX_Part_I/Construction_Kit/M39_EMR_Marksman_Rifle/M39_EMR_OneShot_4_Cue.M39_EMR_OneShot_4_Cue (0x000001e90bd83620) from cluster SoundCue /Game/SaOKStuff/X/Sounds/Modern_Weapons_SFX_Part_I/Construction_Kit/M39_EMR_Marksman_Rifle/M39_EMR_OneShot_4_Cue.M39_EMR_OneShot_4_Cue (0x000001e90bd83620 / 0x000001e8cbe889d0) is referencing 0x000001e88a324300 SoundEffectSourcePresetChain /Game/SaOKStuff/VoiceActors/SoundDelayChain.SoundDelayChain which is not part of root set or cluster.

image
image898×385 40 KB

70

You have to provide more information such as the related/suspected log lines - saying it failed to launch can be of many unknown reasons. Or any machine spec, o/s.

72

I also had constant crashing issues inside the Editor in 5.7, I fixed it by adding this to the DefaultEngine.ini inside my project files.

[/Script/RHI.RHISettings]
bEnableGPUBreadcrumbs=False
bEnablePixEvents=False

and launching your project with the -vulkan flag through your terminal.

Now its running (mostly) fine, although i don’t work with raytracing in that project, so your experience may vary. UI issues are still present for me (with x11 as well), although it’s only submenus and toolbars popping up on a different monitor, as for now.

I fixed some UI issues on my end by modifying my windowrules (I use Hyprland), so I can’t give any tips on how to solve that Nobara.

1 Like
73

That is unfortunately not possible with my distro without significant breakage of packages.

74

Thanks for the tips, unfortunately in my case it doesn’t seem to help. I’ve noticed that most of the crashing seems to be specific to Nanite foliage, since it’s experimental I guess it may be expected to some extent.

75

Hello, just wanted to share that the current fix is only temporary.

The problem keeps coming back. As soon as you launch an older engine version, like UE 5.6, and then try to go back to 5.7, the crash hits again. This means you have to delete those folders repeatedly every single time you switch between engine versions.

Is there a more permanent solution?

76

I cant use Rider with 5.7 on Linux besides the other problems already mentioned

20:38:25.690: Setting up Unreal Engine project files…
20:38:25.694: /opt/unreal-engine/Engine/Build/BatchFiles/Linux/SetupDotnet.sh: line 50: syntax error near unexpected token fi 20:38:25.694: /opt/unreal-engine/Engine/Build/BatchFiles/Linux/SetupDotnet.sh: line 50: fi
20:38:25.694: /opt/unreal-engine/Engine/Build/BatchFiles/Linux/GenerateProjectFiles.sh: line 35: dotnet: command not found
1 Like
77

It’s in the video and its all over UDN its a launcher issue as I outline with the unrealselector.exe pointing to the wrong path for UE4. I’ve provided multiple workarounds…. just look into the like 5 forum post covering this issue or look up the UDN issue.

1 Like
78

Fix: Restore Lumen support for D3D Shader Model 5 (DX11/DX12 SM5)

Unreal Engine 5.7 broke Lumen on D3D SM5 due to StochasticLighting shader
requiring 8 UAVs (hardware limit: 4 UAVs). This commit restores full Lumen
functionality with a fallback path that combines UE 5.6’s simpler approach
with 5.7’s compatibility requirements.

Key Changes:

  • StochasticLighting.cpp: D3D SM5 detection, simplified 2-UAV depth/normal copy
  • Created LumenTileBitmask with all tiles marked (0xFF) for 5.7 compatibility
  • LumenScreenProbeGather.cpp: Fixed GI temporal validation (check data not pointer)
  • LumenReflectionDenoiserTemporal.usf: Conditional depth read for D3D SM5
  • New shader: StochasticLightingDenoising.usf (5.6-style history storage)

Result:
:white_check_mark: Full Lumen GI + Reflections working on DX11 and DX12 SM5
:white_check_mark: DX11 SM5 with Lumen SWRT is fastest performing Lumen path
:white_check_mark: Quality identical to SM6+, no tile culling optimization
:white_check_mark: Production ready, tested across multiple scenarios

Files Modified:

  • StochasticLighting.cpp (fallback path + LumenTileBitmask creation)
  • LumenScreenProbeGather.cpp (temporal validation fix)
  • LumenReflections.cpp (D3D SM5 comment)
  • LumenReflectionDenoiserTemporal.usf (depth consistency)
  • LumenScreenProbeGatherTemporal.usf (PackedPixelData validation)
  • StochasticLightingDenoising.usf (new 5.6-style shader)
  • DeferredShadingRenderer.h (function declaration)
  • LUMEN_D3D_SM5_FIX_SUMMARY.md (comprehensive documentation)

https://github.com/EpicGames/UnrealEngine/compare/release...uno1982:UnrealEngine:5.7-Lumen-D3D-SM5-Fix

Update: PRs Open for both Main and Dev for those on that branch who want to put it through the paces.
Main - https://github.com/EpicGames/UnrealEngine/pull/14056
Dev-5.7 - https://github.com/EpicGames/UnrealEngine/pull/14055

6 Likes
79

Thank you so much for your work on the source to regain SM5 functionality! I found the github commit from epic for the irradiance field gather method that was added to the main branch; which did not make it into 5.7 release. It looks like it may be viable enough in its current state. I may merge it with the additions made to SM5 branch, for a pretty good perf boost on top. Here is the link to the github commit if anyone is interested in adding it in:

https://github.com/EpicGames/UnrealEngine/commit/fead0b4f3cfc6262371837867d16e8aea3345481

1 Like
80

I have hundreds of plugins and content from the Fab store. Nothing is compatible and nothing works with 5.7 paid or otherwise. Nothing will install from the Epic Launcher. 90% of my plugins are compatible up to 5.4

Not even Epic plugins that are in the tutorials for how to use content in 5.7 You still tell us to use plugins from within Fab that are not compatible for 5.7 but it’s in the Epic tutorials! Either update your plugins or fix your tutorials or allow us to install content and plugins for previous versions again!

Most of them are just model packs and simple content. Why are we no longer allowed to import models from Fab into our projects if they are no longer marked compatible for the specific engine we are working with? Having to redownload another version of the engine and manually copy files over is such a waste of time. Not being allowed to install or use my paid for plugins and content is a total scam!

Where has the support gone for these forums? 5.7 has broken everything and nobody seems to have any answers.

4 Likes
81

Tricky that GrassMaps_SampleWorldPos in PCG HLSL have rotation offset if landscape have rotation offset e.g. -90 degrees. My farmfield crops dont appear in right places. :frowning:

Tryed to use GrassMaps_Sample, but it dosent seem to return any data. Are the texturecoordinates 0 to 1 or something else?

image
image1084×837 483 KB

EDIT: Maybe getting it working by counting grid cell center from bounds and using it for position after GrassMaps_SampleWorldPos. Could rotate all points around that center.

82

VR is broken again in this release. If you disable “Forward Shading” the right eye renders differently than the left eye.

4 Likes
83

landscape layers broken. otherwise (best engine release since 5.4)

1 Like
84

SM5 on Android broken again?

85

Please Add possibility for 5.7.x to generate files with source version on Visual Studio 2026. All the best ;)!