Pressing Ctrl Z (undo) in blueprint after editing value causes freeze.
This bug seems to be pretty persistent.
I set the Walk Speed in a blueprint and immediately after typing in the numeric value (before pressing any return, or clicking) I tried to cancel my changes with Ctrl Z which resulted in a freeze.
I have changed the walk speed in 4.7.2 and I have not had any issues with the editor freezing or crashing. I also was able to Ctrl+Z to undo a previous change in a blueprint and didn’t run into any errors either.
So I’d like to know the exact steps
you took to receive this outcome?
Could you please provide me with the
version of the Editor that you’re on?
If you’re receiving any error ,
could you include those within your
next reply?
Can you also provide the DxDiag from your computer? You can get these by going to the Start Menu and searching for ‘dxdiag’ and running the ‘dxdiag.exe’ program and clicking the ‘save all information’ button.
I haven’t been able to reproduce on a clean project, but I have had this happen several times on various projects while using Undo (Ctrl + Z). This always seems to happen after I’ve been in the blueprint for 5+ minutes.
I’m on 4.7.2.
are not produced because the engine freezes and never actually crashes.
Thanks for providing me all of the information I asked for. I tried to replicate this issue again. Unfortunately, I was unsuccessful in doing so. I had a project open for a few hours which I attempted this on however, it was a project made from 4.7.2 (created today). Were the projects that you’re experiencing the freeze on created in an earlier version of the engine?
The projects were all created in 4.7.2. What does it take for UE4 to create a crash log? I can let it sit frozen for awhile the next time it happens if that might trigger a crash log. This occurs to me fairly frequently when I use several undos. I’ll do my best to replicate the issue.
I’ve had a few guys in-house test this issue out as well, none of us have been able to reproduce this issue. I’ll try again later in the day, once I have a project open for quite a few hours.
In the meantime, if you have the time, let it sit for 5 to 10 minutes while frozen, and see if it crashes out. A crash reporter should appear after the crash happens. If you force a crash on the editor, it’s not going to give proper .
Are you running anything extensive on your system when you’re working within the editor? The editor itself takes a lot of CPU in general, and that could cause your machine to lag and freeze the editor.
Also, have you tried verifying your version of the Editor? You can do this by going into the Epic Launcher, select ‘Library’ and then use the drop-down arrow under 4.7.2 and select ‘verify’. Verifying the Editor could take approximately 15 minutes or so to complete.
Let me know if that helps any, or if you’ve been able to get the crash reporter to appear.
I’m running a fairly basic version of Windows. Nothing special about it. No firewalls, MSE but the real-time scanner is disabled. 4.1 hexacore, 8GB 1800 of RAM, Radeon HD 7700. Running UE4 doesn’t seem to really bog my system.
Also, recently I actually installed UE4 to an entirely different hard than what I initially had it on. This problem has occured on both installations.
The only other bit of data that I might of left out is that the freeze occurs on a paper2d character controller blueprint.
Would you be able to provide me the steps that you’ve taken to get the editor to freeze on a paper2d character controller blueprint? If you’re not sure of what exactly you were doing, that’s ok. Feel free to update this at any point if you notice a specific pathway to a crash in the editor.
I haven’t heard from you in quite some time. For tracking purposes, I must close this thread at this time. If you have any further questions regarding this specific topic, please feel free to respond here. If you have a question on any other topic, please submit a new AnswerHub question.
I am facing the exact same issue can someone please help resolve the issue. I even tried deleting the engine and download a previous version but the same issue occured.