If by "terraforming" you means the heightmap - the terrain, in your old (broken) project it will be one of the *.v4d files, but we don’t know exactly which one to use, since it varies from project to project.

Hello Geez,

Hello,
You can try creating a new project (with the same parameters and heightmap) and gradually import all the template libraries from the old project.
Once that's done,you should close Terrain Builder and then add the object layers from the old project to the new one as well, and try loading the new project.

@Geez any updated?

Looks to be fixed. I had to make sure reset="1" to see my changes, without waiting.

In T191227#2796473, @Geez wrote:

We have noticed you do not have it enabled in this line:

<weather reset="0" enable="0">

Could that be the issue?

We have noticed you do not have it enabled in this line:

Hello FreaknPwNed.
With the config you have provided we have foggy weather on our testing server. Is there something else that could be wrong?

Hello LBmaster.
One of them seems to be a memory crash and the other one is possibly related to inventory. Nonetheless both are related to the modded content.
Regards,
Geez

Or move it all to Object.

@Geez Any news on this due to patch 1.28?

glad to see a lot of these suggestions made it to 1.28. I could not test the new FIX-Me warnings yet, but the changes in the code look very promissing

when using the FindFreeLocationFor method from the GameInventory, I get a valid location back, which also checks for flipped items, but I would like to avoid spawning the item to use this method

tiez tak nejako, nebolo by zle keby to generovalo nahlady, lebo skusat na slepo je dost zdlhave

Giving this a bump. Would like to see this fixed.

In T190710#2786149, @Geez wrote:

Hello kazeka4.
Could this be caused by some external software you are running or outdated/corrupted driver?

Chiming in here, because this has been an issue for literal YEARS.
It has absolutely NOTHING to do with external software or outdated/corrupted drivers. It most likely has to do with the fact that DayZ still runs on DirectX11 - as this issue can be almost entirely eliminated by running DayZ on a Vulkan API (I and many others have tested this firsthand).
AMD GPUs have had these issue worse than Nvidia for the last few years, but ever since 1.26, the issue is just as noticeable on Nvidia GPUs as it is AMD.
Most AMD GPU users have had to run specific drivers from May 2020 to get slightly better performance due to changes in how AMD GPUs handle DX11. Reported this one years ago.
I bought an Nvidia 4060 JUST to "fix" these issues back in September of 2024, and it genuinely did fix my frame issues until 1.26 was implemented. But let's get down to specifics about this issue, since I know for a fact I'm not the only one in you lot's ears about it right now:

Same problem here.

Hello kazeka4.
Could this be caused by some external software you are running or outdated/corrupted driver?

pls i wanna play fix it thnks

The function is being called from GesturesMenu.CloseMenu publicly, instance.OnMenuRelease(); with instance being static GesturesMenu instance;. Which somehow bypasses the access modifier.

I forgot to mention, this only happens on the prod version of DayZ exe. Diag exe will swallow the compile error.

Resolved in 1.28

Update:
It happens on the specific mapframe settings and also causes often crashes with packed map into pbo and testing on local server.