5.6.1 when
I prefer them to take the time they need.
But next Tuesday is a good candidate.
Except, Epic is not Valve
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.
It should have been yesterday😭
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
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
Hello, can we get fix for broken padding in blueprint editor finally?
(it happens with access specifiers are enabled)
Thanks!
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
thanks, i tried with
<bAllowUBAExecutor>false</bAllowUBAExecutor>
and <bAllowUBALocalExecutor>false</bAllowUBALocalExecutor>
and still the same issue
Can someone please check and confirm this?
I had same problem even without AA, Lumen and Nanite with normal shadows.
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.
I hear people say good things about latest Godot, in regards to standalone VR
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]
/**
* 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.
I wish I knew. We have been using the same template for nearly 2 years. All we do is update the plugins. All of which were approved by FAB. I guess I will have to remove them one by one until I find the conflict. To make things worse it compiles with Zero errors. It is only when you run the shipping build that this error appears and crashes the program.
Well it looks PSO related and if I had to take a guess, it’s probably some issue with HWRT. I remember having issues with this a version or two ago. You might have to delete any caches in your %localappdata%\projectname\
folder. I think anything PSO related should just be in the root directory of it and should have obvious enough file names.
I kind of remember having to change a project setting as well, like disabling this(?)
but it might be unrelated though or might be related to something that has since been fixed.
Bugs after migrating my project:
- Enable Order Independent Transparency (Experimental): Opacity/emissive issue — everything becomes overly bright when this option is enabled. (No problem in 5.5)
- Generate Ray Tracing Proxies: Crashes the game if Nanite is disabled, with the following error:
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File: D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 1067] Array index out of bounds: 2 into an array of size 2