Hi
I’ve been using the development editor and had a problem switching to debug editor a few days ago. I solved the problem by regenerating the UE4 project files, rebuilding the editor. I switched back to development editor (in a different project), then switched to debug editor in that project. I got the same problem. I get a message saying that a “64 bit operation is taking longer than expected”. This time, however, I’ve tried regenerating the project files, rebuilding the ue4 solution in debugeditor mode etc. Nothing works. If I leave VS running with the message, it crashes.
Would love to try and get this problem sorted! Thanks
Hi ,
Could you please provide a little more information about where and when you are running into this issue (which version of the Editor and Visual Studio are you using)? Are you able to reproduce this issue in a new project created from a template? If so, can you provide the steps that you take from creating the project to seeing the issue occur?
Hi, I’m using 4.2.1 and VS pro 2013. As far as I remember the project was always 4.2.1. Infact another project that has been affected in the same way is the CodeTutorial project (also starts from a third person template). I had the same problem on the CodeTutorial project and fixed it by regenerating the project files and rebuilding UE4. Now it doesn’t seem to want to go into debug mode either. I’ll try starting a new project and get back to you…
Looks like a new project won’t work in DebugGame Editor either. It builds, but I then right click on the project in the solution window and try and start an instance, or use the drop down menu at the top, and I get the 64 bit process message…
Could you provide a screenshot of the error message?
Is your Solution Platform set to Win32 or Win64?
It’s Win64. Funnily enough, I just relaunched VS and opened the CodeTutorial project and it ran an instance straight away, when I tried to replicate the error message. I’m going to rebuild my main project in debugeditor mode and then close VS, reopen it and try and launch an instance. Incidentally, I’m shortly going to be upgrading to 4.3, which will hopefully iron things out anyway. I’ll let you know if relaunching VS fixes it for the other project…
It might also be worth mentioning, I switched the machine off in between, I wonder if that would make a difference. Normally I just put it to sleep, often with VS open.
Well thats interesting! It worked without me even shutting down VS and restarting it. Considering that VS has actually crashed, I must have closed and reopened VS before. I’m thinking the significant difference is having switched the machine off and back on again.