So this is a bit of a wierd one, though it’s happened twice today with subtractive geometry. The first time happened when I was moving a brush’s position, whilst the second occurred for another object using Undo. I didn’t save a screenshot, but did keep a copy of the call stack error which is the same in both instances:
633e1cd810d12f95d214bb9cf547935
I save my work regularly outside of Autosave so it’s not much of a problem for me, but I thought I should report it, in case others are experiencing the issue.
We have attempted to recreate the bug in 4.1 and have been unsuccessful. If you could provide the information asked for in the following post, that would be great:
I can say it is intermittent yet, over the past couple of days, it happens mostly when undoing several changes (perhaps more than 6); this would seem to suggest the problem is related to the History. You should try undoing/redoing changes quickly to see if this creates the conditions necessary for the crash…
I don’t have the information on hand about system specs or the current build I’m using, but will post them tomorrow.
Sorry Hyncharas, those are the wrong log files. We’d need to take a look at the Editor’s log file. It should be in your project’s /Saved/Logs/ folder and will be called something like MyProject.log.
System Specs
Dell M1730 | Intel Core 2 Due Extreme X9000 2.8GHz | Dual NVIDIA GeForce GTX 9800M 2GB | 8192MB RAM | Windows 7 Ultimate SP1 64-Bit
I’ve also attached a copy of the latest crash log and DxDiag in a zipfile…
If there are any other users experiencing crashes when undoing changes to their levels, please post here; the more Epic knows, the better they will be able to weed out the issue.
The reason I sent you the CrashReport and DxDiag stuff was because that other thread suggested I do so, though I confess I didn’t send a project-specific log that recorded the error… consequently, that is attached to this comment.
Can someone also explain to me why I can’t upload .TXT documents unless they are in a zipfile?
Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.
If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.