# DX12 and/or Ray Tracing causes editor to crash when opening a new viewport/material/mesh viewer

**URL:** <https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858>\
**Category:** Rendering\
**Tags:** unreal-engine, Ray-Tracing, dx12, question\
**Created:** [April 8, 2019, 4:25pm UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858 "2019-04-08T16:25:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_1dafbe0f](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1dafbe0f](https://forums.unrealengine.com/u/anonymous_user_1dafbe0f)\
**Post date:** [April 8, 2019, 4:25pm UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/1 "2019-04-08T16:25:17Z")

</div>

I’ve been trying to use UE 4.22 with Ray tracing turned on for a few days but every time I open the project it crashes when I open a new window/tab with a render preview window in it, the editor locks up completely.

This doesn’t happen in 4.22 projects that don’t use the -dx12 start line.

When I use DX12 I see an error in the log repeated saying:

LogD3D12RHI: Display: Root signature created where the root parameters take up 18 DWORDS. Using more than 12 DWORDs can negatively impact performance depending on the hardware and root parameter usage.

The editor doesn’t seem to lock up when I’m just running DX12 but when I turn on Ray Tracing and try to open a material to edit or something similar it locks up.

From what I can see the Ray tracing is working fine in the viewport. I can see the reflections and I can see the GI or AO updating if I move the camera, but if I open another tab with a render window it locks up immediately.

Does anyone have any ideas whats going wrong?

---

<div class="post-metadata">

**Author:** ![xaviprz](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@xaviprz](https://forums.unrealengine.com/u/xaviprz)\
**Post date:** [April 10, 2019, 4:20am UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/2 "2019-04-10T04:20:28Z")

</div>

I have the same problem  
RTX 2060

---

<div class="post-metadata">

**Author:** ![estudiobarrera](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@estudiobarrera](https://forums.unrealengine.com/u/estudiobarrera)\
**Post date:** [April 16, 2019, 7:46am UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/3 "2019-04-16T07:46:44Z")

</div>

Hi!.

I have exactly the same problem. After a few seconds the motor closes with that error.

---

<div class="post-metadata">

**Author:** ![tahayaki](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@tahayaki](https://forums.unrealengine.com/u/tahayaki)\
**Post date:** [April 16, 2019, 8:03am UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/4 "2019-04-16T08:03:15Z")

</div>

Is there a chance that its a similar issue?

Try opening the editor on an extra monitor if you are on a laptop.

> **[UE4 Freezes when ran with -DX12 arg on laptop running 2080 MaxQ without...](https://forums.unrealengine.com/questions/876099/view.html)**
>
> UE4 Freezes when ran with -DX12 arg on laptop running 2080 MaxQ without secondary screen. It works fine when I launch it on a secondary screen as primary/sole screen. I'm running a RTX 2080 Max-Q Design on the Razer 15, with the 418.91 drivers....

And also this is what I posted on another topic

"Ok, I finally found a workaround, which is not the best but at least it lets you to work on any project if you dont have a monitor around.

Normally if you disable intel card from device manager before opening ue4, the engine doesnt work, but if you open the project with the intel card enabled and as soon as engine starts you should minimize the engine without clicking anything, its important that you minimize it, otherwise the video card crashes, then after minimizing go to the device manager and disable the intel card, then the editor should work."

Another workaround is enabling editor debugging symbols, but it crashes large projects.

---

<div class="post-metadata">

**Author:** ![estudiobarrera](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@estudiobarrera](https://forums.unrealengine.com/u/estudiobarrera)\
**Post date:** [May 10, 2019, 11:48am UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/5 "2019-05-10T11:48:46Z")

</div>

I have the same problem with gtx 1080ti. Driver nvidia= 430.64

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_1dafbe0f](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1dafbe0f](https://forums.unrealengine.com/u/anonymous_user_1dafbe0f)\
**Post date:** [May 10, 2019, 3:03pm UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/6 "2019-05-10T15:03:01Z")

</div>

I’ve got a bug report! Vote for it if you’re still having this issue guys, projected fix is 4.22.2!

> **[The Unreal Engine Issues and Bug Tracker](https://issues.unrealengine.com/issue/UE-74075)**
>
> Welcome to the Unreal Engine Issue and Bug Tracker. You can check the status of an issue and search for existing bugs. See latest bug fixes too.

---

<div class="post-metadata">

**Author:** ![aquelChiflo](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@aquelChiflo](https://forums.unrealengine.com/u/aquelChiflo)\
**Post date:** [July 22, 2019, 1:47pm UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/7 "2019-07-22T13:47:41Z")

</div>

I had exactly the same error, try to find some solution and it was very complicated, epic already knows about the error and according to a thread probably solve it in version 4.23

I have version 4.22.3 and 4.23 preview and recently I started having that error when starting a project on anyone using DXR.

My PC  
Rtx2080 oc  
Amd Ryzen7 2700x

After seeing in many forums and trying all the supposed solutions, I found something simple that finally fix my problem.

I entered the Nvidia Geforce Xperience panel and in the graphics update screen (top left) in the option “Choose your driver preference” eleji driver for study, I updated the drivers cleanly.

Then I started the engine and that’s it, I have not had that mistake again, I hope it helps.

---

<div class="post-metadata">

**Author:** ![OzMomotaro](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@OzMomotaro](https://forums.unrealengine.com/u/OzMomotaro)\
**Post date:** [September 8, 2021, 3:53am UTC](https://forums.unrealengine.com/t/dx12-and-or-ray-tracing-causes-editor-to-crash-when-opening-a-new-viewport-material-mesh-viewer/446858/8 "2021-09-08T03:53:16Z")

</div>

Just a quick note - 1080ti’s are not RTX gpus, so by default they cannot do ray-tracing in UE4 (as it is hardware based, not software based).
