I am new to Unreal Engine. Spikes instead of hills or mountains come about despite the brush type being circular while editing after creating Landscape.
Thanks in advance.
Hey there @TankutZeytinoglu! Welcome to the community! Iāve seen this issue before and it can stem from a number of things. Often the issue is either that graphics drivers jumbling up the vertexes of the landscape when the memory changes. Sometimes this could be because VRAM is being topped off (which is not the case in your example).
What are your specs and which version of the engine is this in?
First, letās back up your project and then weāll try something.
After editing the landscape this way, can we try saving and closing the project and relaunching? If it looks normal afterwards, we will know our culprit a bit better.
$ lspci | grep -i --color āvga|3d|2dā gives this output :
00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
00:17.0 SATA controller: Intel Corporation Device 43d3 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Ti Mobile] (rev a1)
Unreal Engine version is 5.3.0
My OS is Debian 12 (bookworm)
āAfter editing the landscape this way, can we try saving and closing the project and relaunching? If it looks normal afterwards, we will know our culprit a bit better.ā
I tried it yet the result didnāt changed.
Thanks
So, thats a corrupted heightmap.
Not sure what is causing it or how since the engine is literally doing it for you butā¦
Before you loose your mind figuring things out, try to use one of the reccomended landscape sizes to see if it works on those (google āue4 landscape reccomended sizeā) and it should pull up the docs with relevant info.
At the very least, try the 2x2 component setting which is more often used.
Assuming none of that will work, then there must be a problem with the linux release in the way the landscape writes the heightmap or similar.
Note that because you are on linux it could be the write to disk is failing altogether due to write permissions or file size restrictions.
A safe way to test this is to use a custom 16bit PNG with actual input data.
If you see the preview deform and work, then you know the issue isnt the file.
If editing the file causes issues anyway, then you also know that the write process is failingā¦
Ahhh thatās definitely going to be a fun one to work with. Do any of the tests MH recommended change the outcome? Iāve only got data on height maps information being read incorrectly or completely corrupted in this manner when thereās a GPU side problem.
If possible, can you create a new level from the default open world template that has terrain built in? If that is distorted when it comes in, it should provide more information. If its not, try editing it and see if it distorts this way as well.
Does this occur on terrain with edit layers turned off?
I mean, considering he is on linux this is 100% still possible.
Particularly with Nvidia its sometimes hard to get drivers on Windows that work right;
They had me jumping hoops at the studio through most of 2022 where the drivers would not work correctly for multi-monitor setups causing all sorts of issues with all sorts of programs (thankfully they got their act together now it seems).
Anyway Iām sure that the linux driver avaliability and consistency is iffy at best, so I can totally see the drivers being the root cauae of this as wellā¦