It’s an editor preference, ”Enable the PCG Editor Mode Toolkit”.
Be prepared for it to crash frequently.
You are right, it seems to be an experimental feature, get a crash after click ‘Draw Spline‘
1 Like
LoginId:57458bc746540fac14889394de3fd02b
EpicAccountId:d8dda0a8099a404ca5b1a8696ead6c53
Fatal error: [File:D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12DescriptorCache.cpp] [Line: 733]
Missing uniform buffer at slot 1, stage SF_Vertex. Please check the high level drawing code. Hashes: Vertex: 15FBF792F84DE5CC59972B485241B7D98345D982, Pipeline: D5ABD36AE137D11E56DAA9017EEA167F8F87AEF3.
UnrealEditor_D3D12RHI!FD3D12DescriptorCache::SetRootConstantBuffers() [D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12DescriptorCache.cpp:733]
UnrealEditor_D3D12RHI!FD3D12StateCache::ApplyState() [D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12StateCache.cpp:618]
UnrealEditor_D3D12RHI!FD3D12CommandContext::RHIMultiDrawIndexedPrimitiveIndirect() [D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Commands.cpp:1316]
UnrealEditor_D3D12RHI!FD3D12CommandContext::RHIDrawIndexedPrimitiveIndirect() [D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Commands.cpp:1334]
UnrealEditor_Renderer!FRHICommand<FRHICommandDrawIndexedPrimitiveIndirect,FRHICommandDrawIndexedPrimitiveIndirectString2186>::ExecuteAndDestruct() [D:\build\++UE5\Sync\Engine\Source\Runtime\RHI\Public\RHICommandList.h:1620]
UnrealEditor_RHI!FRHICommandListBase::Execute() [D:\build\++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:542]
UnrealEditor_RHI!FRHICommandListExecutor::FTranslateState::Translate() [D:\build\++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:1096]
UnrealEditor_RHI!`FRHICommandListExecutor::FSubmitState::Dispatch'::`10'::<lambda_1>::operator()() [D:\build\++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:1043]
UnrealEditor_RHI!FRHICommandListExecutor::FTaskPipe::Execute() [D:\build\++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:740]
UnrealEditor_RHI!TGraphTask<TFunctionGraphTaskImpl<void __cdecl(enum ENamedThreads::Type,TRefCountPtr<FBaseGraphTask> const &),0> >::ExecuteTask() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:696]
UnrealEditor_RHI!UE::Tasks::Private::FTaskBase::TryExecuteTask() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Tasks\TaskPrivate.h:518]
UnrealEditor_RHI!LowLevelTasks::TTaskDelegate<LowLevelTasks::FTask * __cdecl(bool),48>::TTaskDelegateImpl<`LowLevelTasks::FTask::Init<`UE::Tasks::Private::FTaskBase::Init'::`2'::<lambda_1> >'::`13'::<lambda_1>,0>::CallAndMove() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Async\Fundamental\TaskDelegate.h:171]
UnrealEditor_Core!LowLevelTasks::FTask::ExecuteTask() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Public\Async\Fundamental\Task.h:627]
UnrealEditor_Core!LowLevelTasks::FScheduler::ExecuteTask() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:397]
UnrealEditor_Core!LowLevelTasks::FScheduler::WorkerLoop() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:757]
UnrealEditor_Core!`LowLevelTasks::FScheduler::CreateWorker'::`2'::<lambda_1>::operator()() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:220]
UnrealEditor_Core!FThreadImpl::Run() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\Thread.cpp:69]
UnrealEditor_Core!FRunnableThreadWin::Run() [D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:159]
I have this crash in 5.5, 5.6 and now 5.7. It’s easy to replicate. Just add a new project based on the virtaual reality template. Then add a Niagara System with the Confetti Burst emitter. Open that system in the editor and the editor will crash. It does not crash when I add that system to the level. If I disable instanced stereo it will also not crash.
Thank you for letting us know! We’ve noted the problem & will investigate!
1 Like
Thank you! I’ve passed along both notes to the MetaHuman team!
1 Like
Thank you for bringing this up! I’ve made a note and will let the team know!
1 Like
Interesting! I’ll do some testing to see which version this seemed to pop up in and let them know - thank you for pointing it out!
2 Likes
With this release does that mean that 5.6 is getting no more point releases or is that still in the cooker? I was hoping for a bug fix on the the Text3D plugin making it work again.
Usually. When a new “Preview” is released, the previous version is no longer updated.
The hair issue should be now fixed on latest 5.7. The extreme SSS as well.
4 Likes
Hello 
Thanks for taking the time to report this issue. I see you’ve raised this issue as well in the Lumen GI and Reflections thread. Would you mind creating and passing along a small repro project so I can get our engineers to take a look? Any information would be helpful of course!
1 Like
Nanite still broken on terrain since at least 5.5 : Is Nanite Tessellation broken on terrain in 5.6 ? - #3 by HIsevaly
Virtual Textures still flicker since at least 5.4 : Why are Streaming Virtual Textures flickering ?
2 Likes
Hello, I compiled the UE 5.7 preview on Arch Linux with KDE Plasma on Wayland and I noticed that the engine natively uses Wayland now but there are huge issues. If there is any tooltip or submenu on screen then you cannot click anything, for example if you click file then while that menu is up you can’t click anything and will have to use the keyboard. If you go to package your project and that little notification pops up at the bottom right then you have to wait for it to finish because it won’t let you click anything or use the keyboard. I don’t know if this is only affecting KDE Plasma on Wayland or how widespread this issue is but it is quite severe. For context I am also using an Nvidia GPU.
5 Likes
Thank You for 5.7 improvements.Think gonna skip HLOD 
. All the best!
2 Likes
My Pleasure 
!
i just sent you a message with project link: https://forums.unrealengine.com/t/test-project-for-ray-traced-refraction-issue/2659612?u=ibtesam_sadiq
1 Like
Hey, I have a question. Since the preview of 5.7 is out. Is it okay to use substrate on the metahumans?. Because I know that y’all said that’s gonna be more fixed and stable for the full release of 5.7 from the metahuman forum 5.7 preview that I had read. And I really do wanted to tryout the 5.7 preview with that feature. But I’m too scared to use it. And plus I know I’m gonna be having a hard time trying to be patient to wait for the full release of 5.7 in order to do that type of stuff. I’m very curious about it. And just was really excited for that feature that’s finally production ready. Because I haven’t tried using substrate feature before yet. And plus also did was curious about the new nanite foliage voxel that I was excited about it too. But um yeah. Oh and sorry if I’m saying too much. Just been feeling alittle bummed lately. And curious. That’s all. But still excited for it tho whenever the full release comes
Thanks for pointing this out @Ibtesam_Sadiq. This is indeed a regression and is a bug in 5.6 as well. I’ve filed Unreal Engine Issues and Bug Tracker (UE-334308) which will be publicly viewable soon. We’ll have a fix for it by the time 5.7 releases, but if you’re using the preview at the moment and need a workaround, you can always use the Set Key Time menu item in the right click menu of the key.
2 Likes
@Max.Chen
Thanks, looking forward to it.
This error appeared in 5.7 and occurs when using Wayland. I’m on Fedora, GNOME, and everything is exactly the same, but if I start a session through Xorg, then 5.7 works. The same error also occurs in 5.8.
Version 5.6 works without this problem on both Xorg and Wayland.
1 Like
Amazing news, seems inline raytracing works for Mac M3+ silicon. Is there full pathtracer support planned as well for apple silicon HWRT?
2 Likes