Hi, i don’t know very much about this process so i hope that someone can help me. I’ve downloaded high resolution heightmaps as GeoTiff formats, then imported to QGIS. I want it to be exported as 16 bit grayscale png so i can use it in UE5.
The problem is that the result turn out blocky like on the picture and i don’t want to blur it out since i would lose alot of details.
I’ve tried several ways in QGIS, merging the layers into int 16 format, raster convertion into int 16 format. It still turn out this way. And when i import it to Gimp and change it to grayscale and 16 bit integer, it still turns out blocky/terraced in Unreal and Gaea. It works just fine from Gaea to Unreal with smooth terrain, but i need it to be right when exporting from QGIS.
Manually sample and check the height values on the map to see if that is indeed the case or if you are doing something wrong.
You can also calculate slopes on this. If the data is incorrect it will show a crisp line instead of a constant slope.
Unless Gaea blurs it for you, thats either not possible, or you are selecting a wrong file format during the import/export in Qgis.
Terracing like shown commonly happens when some asshat passed the heightmap into a non-compatible processor of some kind and changed the values out of 16bit into whatever other format. The result can be extreme (256 colors) or not as extreme (15bit+1) but its still a change in data that conpromised the data entierly.
I don’t think Gaea has anything built in to recover out of this state - but maybe it does?
Anyway, both sampling the data and builsing a slope map will help you determine if the data you have in QGIS is the problem itself or not.
Go from there.
Qgis has several different export settings to it as well. Its possible you aren’t acrually exporting 16bit out of it.
You have to check/share your export process for that to be verified.
It would, not sure why they are in a 32bit format when the standard is 16bit.
If used correctly more data will not corrupt the values however.
32bit can store from 0 to 65535 just as well as 16bit can.
Assuming QGIS is updated and works ok with 32 bit formats it shouldnt be problematic in theory.
In practice, if you do any operations at all that change the values you could have problems and cause terracing again… like with any datum changes…