Using the Ctrl+W Shortcut when duplicating a material node occasionally causes a crash, this can also occur after the node has been duplicated and you try to connect it.
I’ve seen this issue posted multiple times here already but it keeps being closed (not useful!) I get the following callstack error:
!Id:c87a4f3d7a5d659fb91c8aa4bafe74fd
We apologize for the inconvenience.
Please send this crash report to help improve our software.
I’ve seen the other answerhub posts asking for DXDIAG and other log files, where can I find those? I suspect this crash is also related to another one I posted (that has been fixed but not yet implemented by a community member) here:
The Logs are found in the project folder → saved → Logs. It is best to include the most recent log file after the crash. The DXDIAG can be found by navigating to this folder:
C:\Users\USER.NAME\AppData\Local\UnrealEngineLauncher\Saved\Logs
Also, to help with the investigation, which nodes are you using that you have seen cause this crash?
Thanks , I’ll try and get it to happen again today and post the logs.
As for the nodes, it seemed to happen sporadically. I thought initially it might only be nodes that have an existing shortcut, but in fact it seemed to happen with all the following if I remember rightly.
Constant Bias Scale
Add
Subtract
Texture Sampler
Frac
I’m wondering if perhaps it’s caused when you have a node connected, disconnect it and duplicate it? The issue with the dynamic parameter was something to do with the node not refreshing or being ‘recreated’ IIRC
Here is the network I was building (from left to right) that was causing the crash. Interestingly, I also got a completely different crash when connecting the succesfully Duplicated Texture Sampler to the emissive channel instead of Previewing the node. It seems that there is a certain point where the material is unstable, and after that regardless of what nodes are deleted, it still has the potential to crash the engine.
So as predicted it happened again, duplicating a ‘Component Mask’ node certainly seems to cause it regularly.
Callstack:
!Id:c87a4f3d7a5d659fb91c8aa4bafe74fd
We apologize for the inconvenience.
Please send this crash report to help improve our software.
I’ve attached ALL of my logs and dump-files for the crashes the UE4 has generated in this project, the most recent ones are the ones highlighting this problem. (See: Logs.Zip)
It helps to know how long something like this has been affecting users. The developers are aware of this issue and are working on a solution that should come out in a future update to the engine. If you continue to see this issue in current versions of the engine then let us know and I can add any information you can provide to the bug tracker.
Does anyone know if this is supposed to be fixed in 4.6.1. I’m still experiencing it. We have done a lot of customization to the engine, so I’m not sure if it’s us or stock UE4.
