Unreal Engine 5.6 Released

General Announcements
,
166

Also the Steam Subsystem has been broken for the last few versions. This needs to be fixed..

167

I found a few issues in 5.6 that make VR unusable:

  1. MegaLights no longer work in VR, It renders incorrectly in the right eye. This was working fine in 5.5.

  2. Disabling forward shading and using lumen causes severe smearing of the image being rendered to the headset. As you look around the smearing/ghosting becomes worse.

168

5.6.1 when

1 Like
169

I prefer them to take the time they need.

But next Tuesday is a good candidate.

3 Likes
170
171

Except, Epic is not Valve :sweat_smile:

172

Mouse navigation controls in the Collab Viewer and FPS template are not working in both the editor and the built project when using versions 5.6 and 5.7 from Git source.
In 5.6 Preview 1, everything works perfectly.

Please fix this.

173

It should have been yesterday😭

174

I can confirm this bug. The broken 3D Text Plugin is a blocker and I even refactored the whole project one long day to replace the e.g. “set” nodes with “set text” and so on.
And after I fixed all compiler errors ( blueprints only project ) some blueprints with the 3D text component even crash the Editor when I try to simply open them… oO
Tried to delete my custom fonts that don’t seem to be supported by 5.6.0 - still crashing. Play - also crashing. Wow.. Dx

1 Like
175

NANITE DISPLACEMENT BUG

If you add displacement under Nanite on a Landscape (without World Partition) part of it become invisible! Nanite Skirt Enable reduce this but give erro again when you save… Displacement effects seem total broken…

Antonio De Lorenzo
Unreal Engine Authorized Istructor

Screenshot 2025-07-10 152734
Screenshot 2025-07-10 1527342382×1492 153 KB

1 Like
176

Hello, can we get fix for broken padding in blueprint editor finally?
(it happens with access specifiers are enabled)

p10
p10373×143 13.9 KB

p2
p2759×193 51.8 KB

Thanks!

2 Likes
177

Does anyone know where the “Simulation Options” have gone in Unreal 5.6? It only shows “Simulate” and no option to disable gravity as shown in the manual: Testing Physics Assets in Unreal Engine | Unreal Engine 5.6 Documentation | Epic Developer Community

178

thanks, i tried with

		<bAllowUBAExecutor>false</bAllowUBAExecutor>

and         <bAllowUBALocalExecutor>false</bAllowUBALocalExecutor>

and still the same issue

179

Can someone please check and confirm this?

180

I had same problem even without AA, Lumen and Nanite with normal shadows.

1 Like
181

Having ‘Instanced Stereo’ and ‘Virtual Texture support’ both enabled generates hundred of errors in a packaged game and hangs on black screen when running in VR.
Reproducible in a blank project.
Bug also submitted.

It’s a shame that VR support has been sidelined so much so that even the most basic features and optimizations don’t work anymore. Guess we are doomed to stay in 4.27.

1 Like
182

I hear people say good things about latest Godot, in regards to standalone VR

183

(post deleted by author)

184

I’m tired of waiting for the point release. Does anyone know what I need to change to get rid of this error?

Assertion failed: !“Enclosing block should never be called” [File:D:\build++UE5\Sync\Engine\Source\Runtime\RenderCore\Public\VertexFactory.h] [Line: 693]

185 
/**
	* Can be overridden by FVertexFactory subclasses which have EVertexFactoryFlags::SupportsPSOPrecaching set - this function will only be called when that flag is set
	*/
	static void GetPSOPrecacheVertexFetchElements(EVertexInputStreamType VertexInputStreamType, FVertexDeclarationElementList& Elements) { checkNoEntry(); }

And the error comes from Engine/Source/Runtime/Core/Public/Misc/AssertionMacros.h#L291:

	/**
	 * Denotes code paths that should never be reached.
	 */
#ifndef checkNoEntry
	#define checkNoEntry()       check(!"Enclosing block should never be called")
#endif

What are you trying to do that’s triggering this? It looks like something you’re doing is trying to access somewhere that isn’t supposed to be reached.