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.

on 1.,26 all be good, after update to 1.27 server start random crash with that error

Program: D:\DayZServer4\DayZServer_x644.exe
Reason: Access violation. Illegal read by 0x7ff611825d71 at 0xa8

4 years and no response?

The RoadTripNG mod is the easiest to test this issue. The only dependency that it has is the CF mod
https://steamcommunity.com/sharedfiles/filedetails/?id=2354568600

Hello RedFalcon.
We will need the exact car mod where this issue is reproducible.
We also need as few as possible mods dependent on it so we can easily reproduce the issue.

Any update to this?

I was trying to spawn a new Player with Man man = g_Game.CreatePlayer(ident, old.GetType(), old.GetPosition(), 0, "NONE");, then kill the old player in the DB and select the new player and move all items and stats over to the new player. The problem is, that I now get an error when saving the new player, because the playerID and charID is not set when the player was created like this. When I respawn, it works fine, so there must be something, that is executed in the engine to set the playerID and the charID on respawn, which doesn't seem to happen anywhere in the scripts.