Tested this. For me it didn't crash, however, the performance steadily gets worse and loading times are still very long, still rendering this not worth playing at the moment.I may have found a solution, downloading a game to try out;
You must be registered to see the links
Last post. Its not the same game, but had same problem.
Update: Tested, and its working, had two crashes so far, in ~2 hours window.
So i applied this. Can confirm that the game wont crash after setting this. (At least not about some MaxObjects)I may have found a solution, downloading a game to try out;
You must be registered to see the links
Last post. Its not the same game, but had same problem.
Update: Tested, and its working, had two crashes so far, in ~2 hours window.
Overly simplified but the game basically keeps the stuff you loaded in previous areas, so it's always just in there sitting and you're basically loading everything at the same time constantly.Tested this. For me it didn't crash, however, the performance steadily gets worse and loading times are still very long, still rendering this not worth playing at the moment.
It doesn't fix the inevitable, it just delays it at the cost of consuming more resources.I may have found a solution, downloading a game to try out;
You must be registered to see the links
Last post. Its not the same game, but had same problem.
Update: Tested, and its working, had two crashes so far, in ~2 hours window.
You're missing the point. The game keeps loading more and more objects and none of them ever get unloaded until the engine is using up so much memory that performance degrades until it either crashes or, with that tweak, gets so bad it becomes unplayable.Then remove some zeroes.
Its saying it can have a maximum of 100 Million objects in a scene. Not polygons, but objects.
So drop that down to 100,000 instead. That should still be sufficient numbers to get everything to load, without requiring 100x more RAM.
Do this and your game crashes after about one or two minutesThen remove some zeroes.
Its saying it can have a maximum of 100 Million objects in a scene. Not polygons, but objects.
So drop that down to 100,000 instead. That should still be sufficient numbers to get everything to load, without requiring 100x more RAM.
Yes, it does, forgot to mention about that, but still temporary solution until dev fix this.It doesn't fix the inevitable, it just delays it at the cost of consuming more resources.
You use Mint don't you? Confess! No! You use... Arch...Yes. Update to Windows 10 or Linux![]()
Mint is great until you want to game on it. Being an Ubuntu LTS based means you have 2-years old kernels and drivers which is bad for gaming performance. Slapping some PPAs on top makes your system a Frankenstein mix of fresh and years old drivers and libraries making stability worse. And Ubuntu non-LTS is a complete shit with its never ending "oh no something has gone wrong" unexpected popups. Anything Arch-based is so much better if you can update your system at least once a week (I don't mind doing it daily).You use Mint don't you? Confess! No! You use... Arch...![]()
The problem here is not being amount of RAM consumed, but amount of game objects alive. Error that happens for everyone crashing game doesn't mean "you don't have enough memory". It means "engine can't handle any more objects". Of course you can adjust that limit (as already was posted in this thread) but it will just lead to more RAM and CPU consumption. The game engine should check each object if it can be destroyed and bigger the list - slower it gets. Eventually you still get the same crash, just some time later.But back to the game's topic: Is there anyway to make a garbage collector from outside UE? Since the root of the problem seems to be memory leak, sending the OS a request for memory cleanup could prevent leak to some degree, no?
Oh, ok I get it now, so it's not memory leak. The engine is just being dumb with objects management.The problem here is not being amount of RAM consumed, but amount of game objects alive. Error that happens for everyone crashing game doesn't mean "you don't have enough memory". It means "engine can't handle any more objects".