4.15.2 crash on draw material to rendertarget

After updating to 4.15.2 I noticed my project containing the draw material to rendertarget function crashes at runtime. I was suspicious since this project ran fine before the update, so I tested with the content examples. The draw material to rendertarget example also seems to crash at runtime, although less consistently (it seemed to take longer sometimes, while crashing instantly other times).

Hey kokiri-

Are you calling Draw Material to Render Target in code or through blueprints? Can you provide reproduction steps and/or a screenshot of the setup you’re using? What exactly did you do to test the crash in Content Examples?

It’s being called from blueprint. As far as sequence of calling goes, I load up dynamic material instances and rendertargets in the construction script,
then clear the rendertargets on EventBeginPlay.
once Draw Material to Render Target is called, the editor crashes. No crash if it isn’t called.

with the content examples, I believe their calling sequence is similar, except their rendertargets aren’t dynamically created. they still get cleared at beginplay, and still crash eventually (sometimes this crashes immediately, sometimes times when I get close to the water demo, sometimes it crashes after playing with the demo for a short time, very rarely it won’t crash at all).

(album showing blueprints http://imgur.com/a/PrjOR)

When you open Content Examples, what level are you opening and what exactly are you doing to trigger the crash? When I open the “Blueprint Render To Target” level and test interaction with the objects in the level I do not get a crash.

It’s the blueprint to render target level that crashes for me. I’m positive it hasn’t been edited, but I’m going to try it with a fresh project shortly.

as far as what I’m doing to make it crash, I’m really not sure. Sometimes it crashes as soon as I click play, other times it crashes when I turn the camera towards the demos. I’ve recorded the crash happening, if it’s any help error report crash - YouTube

I’m really stumped by this, since I never had a crash like this before the update, and now it happens to multiple projects. (I have verified my engine files in the unreal launcher, too)

Just thought I’d jump in here and say, hey me to! The crash started after the 4.15.2 update on a project which previously worked fine. I was in the process of elimination to work out what was going on and came across your post on here. I only need to hit play and it will crash pretty much instantly each time.

The crash reporter text looks identical to what you posted on youtube. I’ve been submitting the reports to epic via the reporter.

right, so I made a fresh project, to test with.
I’m creating a fresh dynamic rendertarget in the construction script.
clearing it to black on begin play.
drawing noise to it on tick.
and using a material with that rendertarget as a texture parameter.
and it all seemed to work perfectly… until I restarted the editor.
when I reloaded the project, it crashes instantly when I hit play.

Hey guys-

Can you provide your DXDiag please? A report was filed for this crash (Unreal Engine Issues and Bug Tracker (UE-44742) ) however it still has not been reproduced internally. I was able to find crash in our system - if you provide your EpicID or MachineID we can look up your crash as well) Having the DXDiag would provide additional information on top of the crash info submitted.

Sure thing

link text

Small update, I tested my project with 4.16.0 preview 2, and didn’t encounter any crash. As far as I can tell it seems exclusive to 4.15.2

Hey kokiri-

Thank you for testing this in 4.16 as well. I have updated the report to include the extra information. I am marking this as resolved now that a report has been entered for tracking. If you have further information or questions about this issue, feel free to add a comment to reopen the post.

Cheers

Hi thanks for looking into this one.
My LoginID: 6769a78e495d27505e012aa31c29254b
DxDiag

Also having this issue. My project is heavily dependent upon Render Targets and now having a single Draw Material to Render Target Blueprint call crashes the project.

LoginId:134733bf4aa1b6efa463128806bedd31
EpicAccountId:823ce9da15ae4c3095da16d99589e2d0

Access violation - code c0000005 (first/second chance not available)

UE4Editor_Core!FName::ToString() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\uobject\unrealnames.cpp:901]
UE4Editor_Engine!TEnqueueUniqueRenderCommandType<`UKismetRenderingLibrary::DrawMaterialToRenderTarget'::`12'::BeginDrawEventCommandName,<lambda_006f723da97008118d513539c16ed84f> >::DoTask() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\rendercore\public\renderingthread.h:190]
UE4Editor_Engine!TGraphTask<TEnqueueUniqueRenderCommandType<`UKismetRenderingLibrary::DrawMaterialToRenderTarget'::`12'::BeginDrawEventCommandName,<lambda_006f723da97008118d513539c16ed84f> > >::ExecuteTask() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\public\async\taskgraphinterfaces.h:883]
UE4Editor_Core!FNamedTaskThread::ProcessTasksNamedThread() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:954]
UE4Editor_Core!FNamedTaskThread::ProcessTasksUntilQuit() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:701]
UE4Editor_RenderCore!RenderingThreadMain() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:325]
UE4Editor_RenderCore!FRenderingThread::Run() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:459]
UE4Editor_Core!FRunnableThreadWin::Run() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]

Hey mindridellc-

This was recently reproduced internally using latest NVidia drivers (382.05). Older drivers were not showing the crash. You can try reverting to a previous driver to see if the crash still occurs. We are still investigating the full extent of this crash

Just downgraded to the previous driver from 4/17/17 and was still getting the crash.