In T189923#2806100, @ad.HD wrote:

DFW-4-2C-18, 09.05 2025 19:27:23
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7694fbfb0 at 0x8

Class: 'A6_MK12'
Entity id:3055486

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

In T189923#2804591, @nachoooo wrote:

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

Which weapon pack is the A6_AK104 in? Also you may want to look at any crashes that are occuring seconds before the WeaponFSM crash as being the culprit. For instance I sometimes get a crash when the CarePackage mod cleans up old care packages, this is because its trying to delete something thats already been deleted so it gets a NULL pointer or illegal read operation
\

Yeah send me your logs, most likely its a bugged player, desync, or a buggy weapon/mod. I may include debug messages with the players name attached to the log so you can see if its one player in particular causing the issue. I have seen corrupted player profiles and cheaters causing memory corruption issues.

In T189923#2802844, @TWINKLE.Play wrote:

In T189923#2802687, @nachoooo wrote:

Updated ctx checking and sync intervals, appears to be more stable. WeaponFSM Fix

If the problem is fixed by Dayz, can we see a stable version of the fix for the problem with weapons from you at 1.28?

Updated ctx checking and sync intervals, appears to be more stable. WeaponFSM Fix

In T189923#2802029, @ad.HD wrote:

In T189923#2801943, @nachoooo wrote:

I'm going to make a couple tweaks to the current_state_id and see if that helps, most likely I'll upload later tonight when pop dies down

Not sure if this is helpful or not, but I'm now getting an fsm crash that calls out your mod:

---

DFW-4-2C-18, 01.05 2025 19:44:05
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff75ec79864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:5

SymGetSymFromAddr:487, addr:0x7ff75ec79864
SymGetSymFromAddr:487, addr:0x7ff75ee441ef
SymGetSymFromAddr:487, addr:0x7ff75ee5db62
SymGetSymFromAddr:487, addr:0x7ff75ee45bcf
SymGetSymFromAddr:487, addr:0x7ff75ee42d75
SymGetSymFromAddr:487, addr:0x7ff75ee479e2
SymGetSymFromAddr:487, addr:0x7ff75ee4324f
SymGetSymFromAddr:487, addr:0x7ff75f0788b4
[CDPInitServer]: ??? addr:0x7ff75f2314f9
[CDPInitServer]: ??? addr:0x7ff75f21de38
[CDPInitServer]: ??? addr:0x7ff75f21bdd3
[CDPInitServer]: ??? addr:0x7ff75f21e1ff
[CDPInitServer]: ??? addr:0x7ff75f22b1c0
[CDPInitServer]: ??? addr:0x7ff75f21d52c
[CDPInitServer]: ??? addr:0x7ff75f23bcda
[CDPInitServer]: ??? addr:0x7ff75f21d7c0
[CDPInitServer]: ??? addr:0x7ff75f22f031
SymGetSymFromAddr:487, addr:0x7ff75ee6514c
SymGetSymFromAddr:487, addr:0x7ff75ee65c57
SymGetSymFromAddr:487, addr:0x7ff75ee6654b
SymGetSymFromAddr:487, addr:0x7ff75ee6f94a
SymGetSymFromAddr:487, addr:0x7ff75ee6f989
[BaseThreadInitThunk]: ??? addr:0x7ffdeff24ed0
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b

Uploaded new version to check current_state_id = 0 as empty as defined in scripts\4_world\entities\firearms\fsm\states\weaponstablestate.c

I'm going to make a couple tweaks to the current_state_id and see if that helps, most likely I'll upload later tonight when pop dies down

Thats a bummer, I personally haven't had any crashes. Obviously its not a permanent fix but at least it will stop crashes 4-5 times a day. The main issue is the lack of sanity checks in the DayZ code and the short-circuit coding. As of this last update, Enfusion engine doesn't appear to properly handle && operator logic.

Happy to help out the community! @Gooon I'd like to have a chat with you, https://discord.gg/killerz

I found that in addition to ctx being NULL, the WeaponDebugger and current_state_id can also cause crashing. I've added error checks for those and also redid the overrides from prefix to modded overrides which should prevent any crashing. I'm uploading the new version now. WeaponFSM Fix

I've added a NULL Pointer check to the vanilla code to prevent server crashes. More specifically I've added NULL pointer checks on the variables ctx, state, and m_fsm in the modules weapon_base.c and weaponfsm.c. I've published this as a workshop item WeaponFSM Fix . Keep in mind this hardcodes these two modules with 1.27 code so it may break when 1.28 is released. Please remember to remove this mod when 1.28 is released.