4096er terrains

[imported_cajomi]

A super simple typo causes a heavy problem:

After swichting to project panel, the datas of all levels are lost.
This only happens with 4096er terrains.
This bug causes, that using the brush after switching to projectpanel and back to terrain panel (on a 4096er terrain) give no sensful results. The brush uses the level data, but because there are now, he uses the last data in the level cache. This bug causes no crash, but disfunction.
Also this bug causes, that in a stored project the level date are missing.

This bug will be fixed in the first update.

I recommand to use max. 2048 terrains, if you want to use the brush.
This bug has no effect on storing the projectsettings. So you can still work on 4096er projects.
The level protection also uses the level data, so this also will give wrong results with 4096er terrains, after switching between project and terrain panel.

[Darthmagus]

I tried to reproduce your bug and I get another.

4096 terrain:
After loading a simple preset, I used the brush.
No disfunction with the brush.
I wanted to clear the preset in the terrain shape and I get the following message.
I tried to reproduce it but the bug didn't appear again.

[Darthmagus]

After swichting to project panel, the datas of all levels are lost.
This only happens with 4096er terrains.
This bug causes, that using the brush after switching to projectpanel and back to terrain panel (on a 4096er terrain) give no sensful results. The brush uses the level data, but because there are now, he uses the last data in the level cache. This bug causes no crash, but disfunction.
Also this bug causes, that in a stored project the level date are missing.


I tried to reproduce your bug and I get this following screenshot. Is it your bug?

[imported_cajomi]

yes, that is caused by the bug.
I have found as workaround, to work on 2048er, and at last step, direct before exporting, change to 4096.

I will have also a look, whether the bug you find is caused by the same typo.

Johannes

[imported_cajomi]

to your bug: I also can not reproduce it so far. But I think, it will appear again in another situation and then it is getting more clear.