3
things.
First. World comp can crash a Titan if you don’t know what to do.
The leading issue?
Leaving the “mini map” open.
Many times it’s just there in its own window or UI panel. When importing tiles landscapes it is absolutely necessary to make quadruple sure nothing else in the engine is open.
No extra tabs, no extra windows, and most definitely not the mini map visualizer.
Closing it out if you have it open could potentially solve your problem.
-
4gb of vram is nothing. You can’t expect to be able to develop on such a low amount regardless of what engine you use.
It’s literally barely enough to get games to run… I’m surprised you haven’t ran into a ton of other engine issues. -
if you aren’t under NDA, you could probably post your tile files and ask for someone to test and see if the tiles are the problem.
Hint: they probably aren’t. It’s the import process that’s failing for you.
Let’s add 4 too.
With 4gb of Vram you’ll barely be able to open up 4 tiles at the same time when they are empty at 2017px per tile. I think that’s the size you mentioned.
On a 1080ti you can barely load 9 tiles of 8km each.
You should really update the gfx even if it’s definitely not the best time to do so considering there’s nothing good avaliable on the market… consider investing in a pre-built with a 3080…
Let’s also add 5…
Instead of importing the tiles all together. Go one by one.
Create the first landscape. Import the height map. Add the adjacent tile. Import the heightmap and continue on that way.
Painful, but its a solution nonetheless.