# Unreal engine 5.7.1 Map generation Bug?

**URL:** <https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485>\
**Category:** World Creation\
**Tags:** unreal-engine, bug-report, editor, question\
**Created:** [December 20, 2025, 3:26am UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485 "2025-12-20T03:26:18Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![DragonSoupStudio](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dragonsoupstudio/32/1136450_2.png) [@DragonSoupStudio](https://forums.unrealengine.com/u/DragonSoupStudio)\
**Post date:** [December 20, 2025, 3:26am UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/1 "2025-12-20T03:26:18Z")

</div>

Hello fellow dev’s, I have a question; When I try to load a heightmap as world map in unreal engine 5.7.1 it keeps only rendering 1 corner of the heightmap and repeating it as a tile rather then loading the full heightmap.

I tested the same heightmap on engine 5.4 and it worked fine, backloading and then updating the file to 5.7 destroys that map for some reason.

the dimensions I am working with are 4096x4096

I am trying to implement a 10x10KM map with 3K height, Are my calculations incorrect?  
I use 10000x100/4096 for the X/Y axis and 3000x100/512  
These same calculations worked fine in older engines so i’m not sure if this is the problem or if it is a bug with unreal engine 5.7.1

Any advice?

 ![2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/2/7/f2737fd0ef23940d6d6f91679530bfcda3d43626.jpeg)

 ![1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/8/b/f8b1c77fdb7311a18a177b935eed4e4cc9478b06.png)

---

<div class="post-metadata">

**Author:** ![Ya\_delic](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Ya\_delic](https://forums.unrealengine.com/u/Ya_delic)\
**Post date:** [December 21, 2025, 3:25pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/2 "2025-12-21T15:25:11Z")

</div>

Same here.

---

<div class="post-metadata">

**Author:** ![DragonSoupStudio](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dragonsoupstudio/32/1136450_2.png) [@DragonSoupStudio](https://forums.unrealengine.com/u/DragonSoupStudio)\
**Post date:** [December 26, 2025, 9:50pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/3 "2025-12-26T21:50:36Z")

</div>

While not a longterm solution as it’s not a fix to this problem;  
What ended up working for me was starting a project in engine 5.4, implementing the map in that version with the same calculations; Loading the landscape partitions, doing a bit of work like setting up a landscape material on the landscape; painting a bit; setting up some scene lighting and whatnot; the usual stuff you do early on.  
And then opened up engine 5.7, loaded the project up on that version as a new copy of the project.  
So far, that has been the only way for me to get the full 10x10km map to load normally on 5.7.  
Hope it works for you too until a better solution comes along!

---

<div class="post-metadata">

**Author:** ![TruthPhoenix](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@TruthPhoenix](https://forums.unrealengine.com/u/TruthPhoenix)\
**Post date:** [March 13, 2026, 11:14am UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/4 "2026-03-13T11:14:03Z")

</div>

Yup me too. I created a 8129x8129 landscape with normal settings in World Creator and saved as an R16 file. Been doing this in previous versions of UE and worked fine. But 5.7 is broken when I use Landscape Mode to import the heightmap. I get the same result as you. A quarter sized tile repeated in 4 x 4 pattern. ☹

---

<div class="post-metadata">

**Author:** ![CrazedMoe](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@CrazedMoe](https://forums.unrealengine.com/u/CrazedMoe)\
**Post date:** [March 17, 2026, 1:48pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/5 "2026-03-17T13:48:19Z")

</div>

Same issue here as well. I cannot load any map without this now strange issue.

---

<div class="post-metadata">

**Author:** ![QuickkBee](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@QuickkBee](https://forums.unrealengine.com/u/QuickkBee)\
**Post date:** [March 19, 2026, 10:18pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/6 "2026-03-19T22:18:56Z")

</div>

Has a bug been filed for this? The quality control is abysmal. They didn’t even know world partition was borked.

---

<div class="post-metadata">

**Author:** ![Aten](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Aten](https://forums.unrealengine.com/u/Aten)\
**Post date:** [April 18, 2026, 9:06pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/7 "2026-04-18T21:06:27Z")

</div>

Just come back to terrain after a 2 year break, excited to see if anything has been improved. First thing I find is I can’t even import a heightmap, it’s unbelievable!

EDIT: Tried it in 5.7.4 and managed to get it working. It came in wrong at first but just redid the import and it corrected itself 😕

---

<div class="post-metadata">

**Author:** ![Dagwood2000](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Dagwood2000](https://forums.unrealengine.com/u/Dagwood2000)\
**Post date:** [June 18, 2026, 9:58pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/8 "2026-06-18T21:58:32Z")

</div>

Just wanted to chime in. Was stuck trying to create terrains myself. What works is to create a Third Person project and then create a new level - choose basic. Then the terrain import works!

---

<div class="post-metadata">

**Author:** ![CrazedMoe](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@CrazedMoe](https://forums.unrealengine.com/u/CrazedMoe)\
**Post date:** [June 29, 2026, 10:41pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/9 "2026-06-29T22:41:33Z")

</div>

Same bug in the newer version 5.8 not sure on how to fix it other than the listed work arounds this is a pretty big issue.

---

<div class="post-metadata">

**Author:** ![QuickkBee](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@QuickkBee](https://forums.unrealengine.com/u/QuickkBee)\
**Post date:** [July 9, 2026, 5:28pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/10 "2026-07-09T17:28:10Z")

</div>

What a garbage platform. They’ve had months to fix a bug that literally breaks World Partition, their “solution” to large open worlds. It’s like they don’t even care what they ship these days

---

<div class="post-metadata">

**Author:** ![oniregoc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@oniregoc](https://forums.unrealengine.com/u/oniregoc)\
**Post date:** [August 27, 2026, 3:17am UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/11 "2026-08-27T03:17:55Z")

</div>

I completely agree! It’s incredible that this crucial aspect of open-world creation still hasn’t been fixed a year later. I wonder how long AAA studios will put up with a situation like this. I also tried reverting to version 5.6, but there’s a memory bug that prevents converting the landscape to Nanite within the World Partition system. It maxes out the memory and causes a crash. (And I have 256 GB of RAM, too.)

---

<div class="post-metadata">

**Author:** ![skidz](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/skidz/32/1081394_2.png) [@skidz](https://forums.unrealengine.com/u/skidz)\
**Post date:** [September 3, 2026, 1:33am UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/12 "2026-09-03T01:33:11Z")

</div>

In 5.7 the only way I have been able to get around this with reasonable speed is to:

- In the new landscape section, click Import
- Select your height png, it will conform the settings to it. If not, press the “fill with data” button or whatever beside import so the settings update.
- Click new instead of import at the top, this will take you back to the new section but with the settings from import. Create the landscape.
- A flat landscape conforming to the height map size will be created
- Now in the landscape tools you can import the height png ontop of this flat landscape. It will import correctly, no repeated height sections.

Epic, please fix this issue. I know you only care about Fortnite UE6 and slop games, but if you kill the trust of the community by letting the current engine rot or go unfixed, people will think twice about using Unreal for their next games.

Cheers, hope this helps.

---

<div class="post-metadata">

**Author:** ![MostHost\_LA](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mosthost_la/32/907035_2.png) [@MostHost\_LA](https://forums.unrealengine.com/u/MostHost_LA)\
**Post date:** [September 3, 2026, 4:26pm UTC](https://forums.unrealengine.com/t/unreal-engine-5-7-1-map-generation-bug/2686485/13 "2026-09-03T16:26:21Z")

</div>

The issue isn’t the garbage epic releases, but rather the fact that everyone is still attempting to use said garbage when for at least the last 6 years it has been a known fact…

They aren’t going to fix this. In fact, they made it worse many times over. I think they compete with one another internally over who screws the system up worse…

Move on. Use meshes. Live happy.
