UE 5.3 Memory out of bounce on landscape to nanite conversion ?

After converting my 5.2 project to and 5.3 and on converting my landscape (13x6km 1m resolution, about 80 Million vertices) to Nanite, the operation eats up my full 192 GB Ram then crashes. Scene is World partition, so landscape is in about 350 Streaming chunks. So UE should convert them one by one without problems right?

Anyone converted their big landscape to nanite with 5.3?

2 Likes

64GB + 100GB of virtual memory wasn’t enough to get an 8k landscape converted, just processes for 20 min and then crashes. At this point there must be a memory leak or something, because how an operation like this can suck up so much resources I have no idea. I guess unless they expect all developers to have a terabyte of memory laying around or something.

Same here, I was trying to convert a bunch of landscape proxies at a time, to see if that works, instead of converting the whole landscape (which should also work). 44 proxies were done in a few seconds. But then when I go to save it, UE eats up ALL the RAM and crashes. Can’t save a Nanite Landscape it would seem. This is broken. My landscape is 8x8 km.
Ryzen 9 3900x
64 GB DDR4 Dual Channel
Radeon RX 6700XT 12 GB
Running from a Crucial SSD 550 Mb/s

2 Likes

This wasn’t an issue in pre-release 5.3 … what have they done!?!

Same problem here with an 8k landscape.
Tried building a few landscape streaming proxies at a time and then save. Eats up 100% memory then crashes.

A 4k landscape imported with no problem and RAM usage peaked at 50GB.

13900k
96gb DDR5 RAM
RTX 4090
2TB Samsung Pro 980

I recently have samiliar issue, 13900k + 4090 seems to be a bad combination some how. But I kinda found a work around, goto th Intel website and download “Extreme Tuning Ulitily”, then set p-core and e-core down a little bit, and the crashes and blue screens never showed again. Just give it a try.
I see a lot of people reporting problems like this, all related to 4090+13900k. I m guessing the hardware development is too fast for the dev team to experiment every combination.

Sadly I have a AMD 7950x3d and not an Intel. It isn’t Intel related.

Same issue with 248 chunks: more than 100GB of ram in use and crash.
My solution: select a few chunks, rebuild nanite, save, repeat…

1 Like

Confirmed on W11 Pro 23H2, Ryzen 5900X, 204GB free memory available for the editor, 24GB VRAM also sometimes runs out while working with landscape.

Nanite System Requirements

  • The Gibson
  • 2 Flux Capacitors₁
  • 16YB Storage (quantum storage crystals recommended)

₁28 required to enable lighting :slight_smile:

2 Likes