The problem I am documenting in the video has only come into being with the intro of 1.14 on my computer. I have spent the most of today trying to figure out what is going on with no success. Every map I have tried running in 1.14 is subject to the same problem. Go back to ver. 1.33 __ and run the same maps and the problem never happens. I have uninstalled Ver 1.14 and reinstalled twice leading to no resolution of the problem.

The video shows what happens. If you choose to view the video, you may want to get a drink and some nachos, the process to get from the problem start to the final restoration of the map takes a few blank screens. I must add that the screen restoration does not solve the problem, it will just repeat the process if I try to move any item again.

I think you'll get a lot more views in this thread, for sure. it seemed to be skipped right over in the other one! Like I said in the other thread, it does the same for me, except the editor is still usable upon restore. Hopefully others can recreate it. I don't use F9 edit normally though, I just tried it upon seeing your bug report.

Anybody else?

@Jerry Trimble
Thanks for the Support here. I realize that not everyone uses this GG command but if we are going to be provided with this function then it should work.
I like problem solving but this one has gotten the best of me (it's driving me nuts). I can't give lee enough information for him to use to identify the glitch.

I'm positive that I have never encountered this problem in over 1000 hours of use with any beta version before 1.14 and the included model making stuff. If any one has any pertaining clues please add to this thread for lees benefit not mine. I hope I'm not on a wild goose chase...

I must add that in new maps the problem still exist but is erratic. Sometimes yes sometime no. Sometimes immediate sometimes later in the map development. But sooner than later it happens. Tis a mystery

yes, I verify I have the same issue with the beta. Rolling back to 1.14 and verifying files. if I still get it will roll back to 1.33

[update-ok, it works fine in 1.14 if I use my own map, but on stock maps like GemWorld the issue occurs. Going to roll back to 1.33]
[update2 - GemWorld works fine when in F9 no freeze/crash, now I can't use EBE , but then again I can live without F9 for a while till it's fixed so back to 1.14 ]

Personally I would Email Lee directly with your video ...
When it comes to bug fixes he loves Video's showing the problem ..

This looks similar to what I have seen every now and then as well. I normally get it after working on a map for awhile and put it down to memory issues. This is with older versions as well, as I haven't much used the new one yet, bar a few quick map tests. I've seen it quite often with 1.33 and earlier though, given enough time and tests in a single session. Perhaps the introduction of the EBE and the extra memory it must use has made it more obvious? Not a nice bug, I've lost a bit of work in the past from this, as once it goes wrong I refuse to save the potentially broken map.

Edit - Been testing a bit of coding and got it to crash by forgetting to change == to =. After auto reloading I saw the same issue. It seems when reloading a crashed level it doesn't quite reset properly. It's easily reproduce-able at least

@DVader
It is true in my case also, now that you mention it, time and test in a single session will also cause this problem.

@synchromesh
I have sent the video via email to Lee as suggested.