# Path tracer MRQ D3D crash

**URL:** <https://forums.unrealengine.com/t/path-tracer-mrq-d3d-crash/765816>\
**Category:** Rendering\
**Tags:** unreal-engine, crash, Rendering\
**Created:** [February 7, 2023, 6:50pm UTC](https://forums.unrealengine.com/t/path-tracer-mrq-d3d-crash/765816 "2023-02-07T18:50:27Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![UElaci](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@UElaci](https://forums.unrealengine.com/u/UElaci)\
**Post date:** [February 23, 2024, 11:22am UTC](https://forums.unrealengine.com/t/path-tracer-mrq-d3d-crash/765816/7 "2024-02-23T11:22:08Z")

</div>

My guess it’s a memory leak no one cares about as not enough people use PT and also if you stay within low values for spatial sampling and only increase temporal samples it’s ok.

However unlike deffered renderer you can’t just rely on temporal samples all the time…

Anyways I think we get sooner some faster rendering and denoising for PT rather than a fix for this.

---

_[View the full topic](https://forums.unrealengine.com/t/path-tracer-mrq-d3d-crash/765816)._
