Hey guys,
Whenever I select or clic on my ‘makepostprocesssettings’ node, it makes me crash. (it’s in my level blueprint, if it helps).
Tested on multiple computers, always windows 8.1.
All the best,
Mael
Hey Elseware,
I have recreated the steps leading up to the the crash you are experiencing. What I would like for you to do is to send me your machine ID. After the crash a grey report box should have popped up saying “hey unreal has crashed for this reason.” On that list should be a machine ID. If you have sent that error off I can look up specifically your logs and figure out where the issue is.
If you didn’t submit that report, please recreate what you have done and then grab that number for me and send it to me.
Thanks,
Hey , thanks for the quick answer.
Well in fact, just hovering my mouse over the node makes it crash. But It doesnt ask for sending a report. It freezes until I stop the process and I can’t seem to make it crash so I can send you this report…
Hey Elseware,
To clarify what version of the launcher are you using? Is this the launcher that you have installed off of the Unreal sight or the compiled version from github?
1.) Can you reproduce this in another project? Use a blank project with no starter content.
a. create cube
b. change to movable
c. recreate your steps in your first question
2.) Send me your logs and your DirectX Diagnostic Tool.
After all of this, I should be able to narrow down where the issue is.
Well my version is the one from the unreal website. Am not using the github one.
Will do what you asked ! 
Hey Elseware,
I have attempted to recreate what you have experienced and cannot replicate the same result. I thought it might have been your graphics card or your OSX but that is not the case. Can you create a new blank project with nothing else besides the Post Processing node in the Level Blueprint?
If you can and it doesn’t crash then it may be the way you are setting your blueprint up.
If it does crash then send me that test project and I’ll see exactly whats occurring.
Hey Elseware,
This is just a followup to your issue. There are a few troubleshooting options before drastic options :).
1.) Make sure you have no add-ons installed for UE4.
2.) Make sure all of your files are installed in the right spot and there is no logs or documents in your documents or common folders.
3.) Last option is to completely uninstall the editor and do the previous steps.
Hopefully that will do the trick,
You have the specs on your machine to run UE4, so on paper this should be working correctly.
Hi,
I’m experiencing exactly the same issue.
It used to work fine, now I’ve upgraded to Window 10, and to UE 4.9 and everytime I get my mouse over a post process node it freeze the engine.
Before updating my OS and the engine, I notice a huge text box (showing all the parameters), the box was stretch and not rendered properly, but the engine was not freezing.
To me it sounds like a graphic card problem.
Is there anything to fix the issue ?
Many thanks.
This could possibly be a graphics card issue. I have been attempting to recreate this issue on my end without success. If you would open a new post with MakePostProcessingNode with windows 10 as it’s title and link that here I will look into this issue further.
Exactly the same thing for me on Windows 10 running 4.9 and 4.10, managed to break out the node a couple of times and attempt to set it but now if I try and do it again in my level blueprint i just crash, was also crashing on my player controller on the camera
Hi,
I found what was causing the freeze and found a way to avoid it on a forum.
It’s coming from the tooltip, makes the engine freeze when he try to display it.
Hiding tooltips in the editor prevent the freeze.
To disable tooltips just type “Slate.AllowToolTips 0” without quotes in the console and “Slate.AllowToolTips 1” to enable it.
Hope this help in the meantime we get a fix.
Cheers.
From what I can tell, this occurs any time there is too much information for a tooltip box to show. Post Process Settings is the obvious candidate since it stores so much information in just itself, but I’ve managed to cause it with custom structs (I’m working with a Time of Day blueprint that has an array of structs that itself contains several structs, which also causes this issue. Amusingly one of those structs is PostProcessSettings, though it still happens if I remove it). Generally I’m assuming it’s freaking out since there’s not enough space to show everything, rather than simply not showing it or showing a generic error. A really annoying bug, it crashes me out easily once every 10 minutes as I accidentally mouse over the output to a node that triggers this.
temporary fix works though, which is great, but naturally comes with the downside of not being able to quickly mouseover nodes to check values.