# Unreal Engine 5.6 Released **URL:** \ **Category:** Announcements\ **Tags:** unreal-engine, Released\ **Created:** [June 3, 2025, 1:50pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952 "2025-06-03T13:50:06Z")\ **Posts on this page:** 20\ **Page:** 4
**Author:** ![Uno1982](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/uno1982/32/982436_2.png) [@Uno1982](https://forums.unrealengine.com/u/Uno1982)\ **Post date:** [June 7, 2025, 2:17pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/63 "2025-06-07T14:17:18Z")
SM5 Lumen is Back Baby! [![](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/3/b/63b4a60299e06e62a94a623c0eb6e9567b9b3bcc.jpeg "UE5.6 - DX11 & 12 SM5 Lumen Support is Back!!!!") ](https://www.youtube.com/watch?v=Nw8gn7Vih8I) ---
**Author:** ![jakubhaluszczak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jakubhaluszczak/32/1071790_2.png) [@jakubhaluszczak](https://forums.unrealengine.com/u/jakubhaluszczak)\ **Post date:** [June 7, 2025, 2:47pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/64 "2025-06-07T14:47:23Z")
I’ve found a workaround when it comes to HW lumen not working on foliage with WPO. Idk why, but it works. r.RayTracing.Geometry.NaniteProxies.WPO 0 ![image1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/a/1/aa10bc3178698059ff057aa9734e5a4696252105.png) ---
**Author:** ![an1y](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@an1y](https://forums.unrealengine.com/u/an1y)\ **Post date:** [June 7, 2025, 11:29pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/65 "2025-06-07T23:29:20Z")
The whole functionality just disappeared in 5.6 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/d/1/a/d1a6cbc98541f844fbd8c9b1fdeb41aa4410f0e6.jpeg) ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/d/1/a/d1a8b63e777fa29590329245ec910d2e5faf2966.jpeg) ---
**Author:** ![Robyn](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Robyn](https://forums.unrealengine.com/u/Robyn)\ **Post date:** [June 8, 2025, 11:38am UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/66 "2025-06-08T11:38:43Z")
MacOs and Linux users need a dedicated area for Epic to detail all non-compatible features. Current documentation does not do this sufficiently. Also, please can Epic start being explicit in the main UE Release notes and Tech presentations when there are new features that are not compatible with macOS / Linux? We understand that achieving feature parity between Windows and macOS can take time, however more could be done to prevent users losing time from trying to access features that won’t work on their device. MetaHumans have cross-industry appeal, however Epic failed to mention that the 5.6 “fully embedded” in-engine MetaHuman creation feature was for Windows only, in key communications on the topic. The one-sided marketing around this will only serve to alienate new comers to the engine, who are using an alternative platform and unable to reference once source of truth for non-compatible features. The Tech talks at Unreal Fest discussed widening access for MetaHumans through other platforms, so it’s ironic that there was no mention of the feature not yet being available on macOS. If Epic truly wants to embrace cross industry workflows then there needs to be an approach that refers to the engine in context to all its platforms, so users who don’t use Windows aren’t mislead. MacOs users are asking about MetaHuman integration and Hardware Raytracing Support etc. Please allow us to have one place to see where these things are still classed as in progress for each UE release. Access to the latest MetaHumans for 5.6 is not possible to macOS users, and the lack of communication from Epic around this feels like another FAB launch gone wrong scenario. Please talk to us, let us know what’s happening. To other macOS / Linux users please write a comment to Epic to share your experiences. ---
**Author:** ![mageaster](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@mageaster](https://forums.unrealengine.com/u/mageaster)\ **Post date:** [June 8, 2025, 1:45pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/67 "2025-06-08T13:45:17Z")
> [@Robyn](#): > > MacOs and Linux users need a dedicated area for Epic to detail all non-compatible features. Disagree. EG should not announce a feature unless it is fully supported on all available platforms. > [@Robyn](#): > > Access to the latest MetaHumans for 5.6 is not possible to macOS users BTW, there is mention that only Windows supported. You know where? On the Metahuman site! I’ve never even bothered to visit it! ---
**Author:** ![Robyn](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Robyn](https://forums.unrealengine.com/u/Robyn)\ **Post date:** [June 8, 2025, 2:31pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/68 "2025-06-08T14:31:16Z")
I did see the Hardware Requirements in the MetaHuman documentation, only after I had tried to install the plugins. The page isn’t in an ideal location, hence my request for these details to also be put in the main UE Release notes and be acknowledged in marketing communications generally. Epic move fast, so it’s inevitable some features may only be supported on Windows when they first come out. That said, it was disappointing for them to announce the new updates as being available in Unreal Engine 5.6, as if users of other platforms aren’t part of that equation. ---
**Author:** ![TheKJ](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TheKJ](https://forums.unrealengine.com/u/TheKJ)\ **Post date:** [June 8, 2025, 9:26pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/69 "2025-06-08T21:26:01Z")
* * * Profiler 2.0 is a complicated mess with very little explanations on the basic stat gpu graph. A good workflow is important for profiling. I watched all 3 live streams, many people found the way GPU profiler sorted the data easy to fast to use. It’s not our fault Epic has to keep track of their async bs to get anything running for a show. The profiler needs to come back, disable async on capture if needed. This is ridiculous. If it’s somewhere in the 5.6 docs, then Epic needs to fix the keyword search. * * * Not a single UE developer has answer my question about this 5.6 issue: [UE5.6 Is Terrible-No profiler, Rendering Nanite Geo Twice (Hardware Basepass still present)](https://forums.unrealengine.com/t/ue5-6-is-terrible-no-profiler-rendering-nanite-geo-twice-hardware-basepass-still-present/2541315) Why do none of the timings transfer from the HW basepass to the Nanite basepass? Now anyone use 5.6 will have two bloated basepass timings and this was even shown the in Witcher 4 demo. ---
**Author:** ![SaOk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SaOk](https://forums.unrealengine.com/u/SaOk)\ **Post date:** [June 8, 2025, 10:00pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/70 "2025-06-08T22:00:44Z")
How to get Niagara Data Channels work in packaged game? Still crashing for me in UE5.6, but no issues when playing in editor. Instant crash when “write to niagara data channel” is used. ---
**Author:** ![ruminaire](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ruminaire](https://forums.unrealengine.com/u/ruminaire)\ **Post date:** [June 8, 2025, 10:24pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/71 "2025-06-08T22:24:13Z")
Hi, I also got this error when testing migrate from 5.5.4 to 5.6.0 You could try to do Find All node GetEnumeratorNameAsString used in all BP in original project 5.5.4, then remove them temporarily, then recreate the node in 5.6.0 Idk why but it causing that error crash, at least that’s what happen in my project and removing them temporary is fixed the crash. * * * Other than this error, I got the other one which is from Nanite skeletal mesh, I’m not sure if it’s related or not, but if you’re using Nanite skeletal mesh you could try to disable them. I think 5.6.0 is missing Nanite skeletal mesh from 5.5.1+, iirc it was causing error in 5.5.0 ---
**Author:** ![Maenavia](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Maenavia](https://forums.unrealengine.com/u/Maenavia)\ **Post date:** [June 9, 2025, 12:10am UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/72 "2025-06-09T00:10:34Z")
A new GPU profiler is planned : [https://x.com/TimHobsonUE4/status/1930632625854505453](https://x.com/TimHobsonUE4/status/1930632625854505453) It also seems that the return of the old profiler is planned likely as a temporary solution until the new one is ready as shown by this merge on the dev-5.6 branch (probably 5.6.1 ?): [https://github.com/EpicGames/UnrealEngine/commit/c9008ee2954d97efec8b52107b6080eea1c53075](https://github.com/EpicGames/UnrealEngine/commit/c9008ee2954d97efec8b52107b6080eea1c53075) Nonetheless, for accurate and high-quality performance profiling, Unreal Insight remains the only reliable solution for conducting proper analysis within a fully packaged build. ---
**Author:** ![TheKJ](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TheKJ](https://forums.unrealengine.com/u/TheKJ)\ **Post date:** [June 9, 2025, 12:49am UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/73 "2025-06-09T00:49:27Z")
> Nonetheless, for accurate and high-quality performance profiling, Unreal Insight remains the only reliable solution for conducting proper analysis within a fully packaged build. We already had tools for this. HW API inspectors. Again, no UE dev is addressing how broken Nanite in 5.6 > [@UE5.6 Is Terrible-No profiler, Rendering Nanite Geo Twice (Hardware Basepass still present)](https://forums.unrealengine.com/t/ue5-6-is-terrible-no-profiler-rendering-nanite-geo-twice-hardware-basepass-still-present/2541315): > > When items in the basepass are converted to Nanite, those material shading rates are transferred into the Nanite base pass. The basepass will only have a timings for items shaded as non-nanite With 5.6, items are not transferred and it’s behaving like the hardware geo pass is still running all the LODs along with the nanite material evaluation. This is ridiculous and UE didn’t behave this way in 5.6 preview. Happens in build version too. 5.6 also had a profiler, instead … ---
**Author:** ![Avytus](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Avytus](https://forums.unrealengine.com/u/Avytus)\ **Post date:** [June 9, 2025, 10:28am UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/74 "2025-06-09T10:28:16Z")
Has anyone figured out how to retarget characters with version 5.6? Automatic retargeting no longer works (IK Retarget bone chain, Root, was unable to be normalized. Chain too short.) When trying to fix this with the skeleton edit, creating a root is no longer possible either. We can add the bone, but each time we validate, it ignores our changes and parent it in the wrong place. For now, the only solution I’ve found is to export these assets to Blender and add them manually. You have to add it to position 0 of the viewport on the 3D cursor, then parent the armature to it. It really bothers me because all the changes made to this version are really exciting. ---
**Author:** ![Tina\_Wisdom](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tina_wisdom/32/1073211_2.png) [@Tina\_Wisdom](https://forums.unrealengine.com/u/Tina_Wisdom)\ **Post date:** [June 9, 2025, 1:53pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/75 "2025-06-09T13:53:00Z")
Thank you, this should be fixed now! ---
**Author:** ![Tina\_Wisdom](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tina_wisdom/32/1073211_2.png) [@Tina\_Wisdom](https://forums.unrealengine.com/u/Tina_Wisdom)\ **Post date:** [June 9, 2025, 1:54pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/76 "2025-06-09T13:54:11Z")
Thank you, I believe this should be fixed now - let me know if you see any additional errors! ---
**Author:** ![Tina\_Wisdom](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tina_wisdom/32/1073211_2.png) [@Tina\_Wisdom](https://forums.unrealengine.com/u/Tina_Wisdom)\ **Post date:** [June 9, 2025, 1:55pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/77 "2025-06-09T13:55:01Z")
Oh interesting! Thank you, I’ll pass this along to the template team! 😄 ---
**Author:** ![Maenavia](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Maenavia](https://forums.unrealengine.com/u/Maenavia)\ **Post date:** [June 9, 2025, 2:03pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/78 "2025-06-09T14:03:31Z")
I encountered a rather annoying issue in 5.6: the ConsoleHelp.html only returns a very limited list of CVars. It’s quite inconvenient when trying to look up system-specific CVars and their descriptions, as it only displays around a hundred entries and nothing more 🤨 ---
**Author:** ![motorsep](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/motorsep/32/918698_2.png) [@motorsep](https://forums.unrealengine.com/u/motorsep)\ **Post date:** [June 9, 2025, 2:54pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/79 "2025-06-09T14:54:16Z")
GPULM is a broken mess again. VLMs are broken. While baked lighting looks okay’ish (with a ton of artifacts) in the Editor and various preview modes, when building .apk for Meta Quest 3 and running it on the device, level appears pitch black. It’s not the case when using dynamic lighting with “Force No Precomputed Lighting” or when baking lighting with CPULM (yes, I “fixed” it in 5.6.0 thanks to one of the UE devs and his AI buddy 😅 ). ---
**Author:** ![geverk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@geverk](https://forums.unrealengine.com/u/geverk)\ **Post date:** [June 9, 2025, 5:03pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/80 "2025-06-09T17:03:05Z")
HI, I have some idea what was causing it, It’s about the screen proportion, it becomes visible only on my main screen, That is 2560x1440; On 1920x1080 is ok ---
**Author:** ![Tina\_Wisdom](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tina_wisdom/32/1073211_2.png) [@Tina\_Wisdom](https://forums.unrealengine.com/u/Tina_Wisdom)\ **Post date:** [June 9, 2025, 6:12pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/81 "2025-06-09T18:12:03Z")
This was not intended & is being investigated\* - \* editing for some additional context, this is officially a bug with a planned fix for an upcoming hotfix! ---
**Author:** ![kotlet](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kotlet](https://forums.unrealengine.com/u/kotlet)\ **Post date:** [June 9, 2025, 8:45pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952/83 "2025-06-09T20:45:26Z")
Found solution. It was caused by default UV channel created by CubeGrid tool. Redoing AutoUV again fixes it. Apparently AI claims that even with world position mapping you still need correct UVs for DDX/DDY mip loading. Still gonna leave it here as solution for someone in the future. * * * I have main shader that uses DDX and DDY for texture mips because reasons. In 5.6 it does not load highest mip (4k) on floors however it does on walls because in (fps view) I can get closer to a wall. Worked fine before. Here is the interesting part though. If I create second material with the same non loading texture but using regular texture sampler and put it on a static mesh 100 meters away it will force the mips to work correctly on the floor that I am standing on and uses DDX DDY shader. Also simply disabling streaming for textures instantly fixes mips. Even having same texture thumbnails in the content browser fixes mips. So streamer seem bugged in 5.6. By the way this requires engine restart, because once you force higher mip with lets say r.texturestreaming 0 and switch to 1 it perma fixes until restart. TLDR. Highest mip do not load correctly when using DDX/DDY. [Previous page](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952.md?page=3) [Next page](https://forums.unrealengine.com/t/unreal-engine-5-6-released/2538952.md?page=5)