Adding Decal Component Crashes Editor [4.14]

Hi Guys,

My editor is crashing when I attempt to add a decal component to a Character Blueprint. As soon as you click to add the decal component the whole editor crashes and doesn’t allow me to send a bug/error report.

It also doesn’t allow me to drag and drop a decal into the Character Blueprint.

Cheers,

I am having the same issue. The problem only exists on one machine. I can add decals on a mac and two other PC’s but not the third PC. There isn’t much of a scenario but here are the specs from dxdiag:

MacPro6,1 (late 2013 running Windows 10 through bootcamp)
Intel Xeon CPU E5-1650 v2 @ 3.5HGz (12 CPUs), ~3.5GHz
64GB RAM
DirectX 12
Dual AMD FirePro D700 (FireGL V) 6GB
Driver Version for graphics cards: 15.301.2101.0

The graphics card driver is the max I can go using the apple software update tool. ATI has a block on installing newer drivers directly on this hardware so it’s either Apple update or nothing. There is a way to install hacked versions of the drivers but first I want to know if this can be fixed with what I currently have.

The Steps: Create a new project → add a decal → crash and if the decals were added from the other machines the steps are: Open project from .uproject or launcher → instant crash

Both of these do not give me the usual popup asking to send crash info to Epic, just the windows crash window that asks if I want to find a solution online. Oh, and it crashes on 4.13 and 4.14 on the said pc.

Any help would be appreciated.

P.S. On the rare occasion that it does load, if I move the view with right-click/move mouse it crashes.

Hi Kinthamen,

Could you provide your Machine ID or a screenshot of the callstack that pops up when the engine crashes? I need that info to look up your specific crash to investigate what is going on.

,

I don’t get a stack on crash but here are the logs and dxdiag info.link text

“Both of these do not give me the usual popup asking to send crash info to Epic”. That was a little convoluted but I meant that I didn’t get the window you are asking about. I just get these windows error:

https://padletuploads.blob.core.windows.net/prod/88587568/6e6e9d8c6a122f35bc36bca539f82f97/UE4StoppedWorking.png

https://padletuploads.blob.core.windows.net/prod/88587568/3374d05493e6534d69a1aea23af1ad68/UE4StoppedWorkingDebug.png

for the help by the way. :slight_smile:

It looks like it’s my ATI graphics drivers. No fix yet but I will post if I find the exact solution.
Event Viewer:
Faulting application name: UE4Editor.exe, version: 4.14.1.0, time stamp: 0x5847b772
Faulting module name: atidxx64.dll, version: 8.17.10.648, time stamp: 0x56baa01e
Exception code: 0xc0000005
Fault offset: 0x00000000006ce1e4
Faulting process id: 0x34e0
Faulting application start time: 0x01d266d81a5d604f
Faulting application path: C:\Program Files (x86)\Epic Games\4.14\Engine\Binaries\Win64\UE4Editor.exe
Faulting module path: C:\WINDOWS\SYSTEM32\atidxx64.dll
Report Id: 819a7e6a-680c-46ec-802a-312da3a46b1c
Faulting package full name:
Faulting package-relative application ID:

I don’t have the settings as this post but it explains a few things:
https://www.armedpineapple.co.uk/tag/atidxx64-dll/

Why it only happens in projects with decals is a mistery to me though.

I found a fix for the issue. So far, I no longer get the instant crash or the crash when moving around in the viewport if I luckily get past the instant crash. As I mentioned above, the issue was the graphics drivers. Just as a notice, this is for a MacPro late 2013. The fix was to run the AMD Cleanup Utility that comes with newer, albeit unsupported, drivers for the FirePro D700. Then delete “c:\windows\system32\atidxx64.dll”. Once that is done, install the modded drivers from https://www.mxdriver.com/ per the instructions provided.

I think the core issue might be that the UE4 Editor is using some methods or classes in the new dll that didn’t exist in the old driver’s dll I had.

Regardless, for the help! Hope this helps others who might be in the same situation.

Cool, I’m going to accept your answer and delete the unnecessary information that is clogging up this post so others can find the answer more easily. for clarifying that the crash window won’t open.

We that a silent crash and usually that indicates a problem outside the engine just for future reference (like outdated drivers or hardware issues for example).