4.6.1 on win7 64bit.
It’s very unstable and crashes very frequently. I spent more than 60 hours developing a prototype and suddenly the editor crashed and it refuses to open my maps. I tried everything including deleting loads of files and delete then re-install the editor but nothing worked. Finally I realized that the editor is taking more than 18GB of RAM out of my 24. When I gave up I reformatted my PC and installed a fresh win7 64bit then updated it to the latest updates and installed only visual studio express then Unreal. Guess what, It crashes AGAIN!!
I have submitted loads of crash reports please find a solution. The last thing any game designer wants is to lose so many hours of work.
Sorry to hear your having problems with the engine, but I have a few things you can try to get it back up and running.
Have you tried using the backup autosaves from your project folder? They can be found in the ProjectName\Saved\Autosaves\Game\Maps folder, try opening the editor and loading an earlier one to see if it is a problem with the latest save file.
That is alarming to say the least… Is this when the editor is idle or while building the lighting? It is normal for building the lighting to take up quite a few gigabytes if you have a larger map, but when the editor is idle I have never seen mine go above 3gb.
If you aren’t able to load the editor, make sure you download and install the DirectX 2010 redistributable package as it is required (and not automatically downloaded by windows update).
I had very much crashes also, and i figured out smth. If you have wrong name or wrong class name in your configs, which doesnt exist anymore or was renamed, then UE4 will crash when you open your project.
To fix this problem you need to manually change configs with proper names.
UE4 has very big problems with renaming. And then it doesnt show you warning message, it crashes instead.
I know! that’s why I took it more serious than just a crash which happens with many other software. By the way, It took 18GB while idle on a simple example map. It wasn’t even my map because I couldn’t open it at all.
I think directX comes with my graphic card. I used UE4 for few months without having to download directX
Thank you. Now I started my project all over again! If it happens again I will report!
Agree, I started to have the problem when I was trying to rename “door” to “door1”. After that even trying to manually rename it back to “door” didn’t help. I noticed that it keeps recreating and extra asset “door1” everytime it crashes and when I start the editor again I find both “door” and “door1” and none of them is accessible.
Indeed, you certainly shouldn’t be having such issues with a stable version of the engine. That’s for sure. Even more so with those system specifications - I’m able to run a stable release on a low end Mac with minimal crashing, for instance (not my main system, obviously!).
So clearly there’s something wrong here. Do post up your crash logs, as aforementioned.
LogLinker:Warning: Asset '../../../**Engine/Content/Functions/Engine_MaterialFunctions03/Procedurals/ComputeFilterWidth.uasset**' has been saved with empty engine version. The asset will be loaded but may be incompatible.
Unknown exception - code 00000001 (first/second chance not available)
Fatal error: [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.6\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformMemory.cpp] [Line: 54]
Ran out of memory allocating 53994222768 bytes with alignment 0
Can you post to the answerhub at http://answers.unrealengine.com so we can better assist you? In your answerhub post. Please post your specific error, steps to reproduce this crash, your dxdiag, and the most recent .dmp and log files located in your saved\logs\ folder (as mentioned above). Thank you!
yeah? Leave it there until it dies or I give up? don’t bother Adam. I will give it a new go and see if it’s going to do the same thing again. If it does will have to unsub unfortunately. I love the system but I left CryEngine, after more than a year, because of the same reason, crashes on simple prototype game.
Mostly you get a really fast answer but atm you have to keep in mind that:
In observance of the holiday season, most of Epic Games will be on vacation from December 22 until January 5th. Some support will still be available during this time. We thank you for your understanding regarding any delays that may occur, and wish everyone the very best during this holiday season."
When you could send us the map/project we can probably help you faster/better.
I guarantee you it wont die and will be investigated, just like every other crash/bug report posted on the site. I was planning on following its progress personally due to an issue I ran into yesterday.
I had nearly the same issue after adding in assets I downloaded from the Community Content forum, I launched the engine and it started eating up ram at an alarming rate (1gb ram every 5 seconds) until it eventually ran out of memory and crashed. I have a feeling it was caused by assets that were created in a different version of the editor, but I need to confirm that with the creator of the assets first (these were just a couple of materials and textures).
If you did something similar to that, I would find the assets and remove them from the content folder, then try launching the engine again. This fixed my issue but once I get more info I will be posting it on AnswerHub for Epic to investigate.