MartinCo

Right - but this is pin point accurate after turning them off immediately after launch from more than 30nm without much time to evaluate and refine the target and reduce the CEP I just downgraded to the previous patch (DCS 2.9.17.12034) and they all missed, both in HAS, POS/EOM etc. which is very different to the current patch

It was the AGM-88D that got upgraded to have GPS and ability to engage targets after turning off their radar - not our AGM-88C (which to my knowledge only used radar homing) Just tested in POS/EOM just toggle launch too - ripple them all within a few seconds and then turn off the emitters - still precise hits from 35+nm This does make all IADS systems / Skynet etc. a bit pointless (since if the harm will hit anyhow, no point going silent) - and didn't used to be the case (else these projects wouldn't have existed!)

Thank you for the fix in DCS 2.9.18.12722!

Hi ED, Since the introduction of Dynamic slots and the "All spawn/parking slots are occupied" pop up message, it would be really great if we could return a tuple on onPlayerTryChooseSlot like onPlayerTryConnect so that we can customize the message to avoid confusion. At present, we must send the player a chat message, and hope they have the window open to explain why the slot block is in effect. Reproduction Ideally, we could use a hook as follows (which allows for backwards compatibility) in Server\Scripts\Hooks to return the tuple: DCL_HOOKS = {} DCL_HOOKS.cb = {} DCL_HOOKS.cb.onPlayerTryChangeSlot = function(playerID, side, slotID) -- If we try spawn a huey at FARP1, fail else we bubble local slot_name = DCS.getUnitProperty(slotID, DCS.UNIT_NAME) if string.sub(slot_name, 1, 11) == "FARP1_UH-1H" then net.send_chat_to("Blocked access to UH-1H at FARP1", playerID) return false, "Blocked access to UH-1H at FARP1" end return nil, nil end DCS.setUserCallbacks(DCL_HOOKS.cb) Launch Mission on Server: SlotBlock-Blocked.miz Try slotting in UH-1H at FARP1 Thanks, Martin

Hi ED, With the most recent patch HARMs are pin point accurate even when the radars are set to enableEmission false, setOnOff false, or the alarm state green after a launch. I have rolled back to DCS 2.9.17.12034 and this behavior was not present. I believe this is true in the 18 as well (based on earlier thread) and a general HARM issue. DCS Version: DCS 2.9.18.12722 Reproduction: * Set up HAS for BB, SD, P, HK * Launch one harm at each target at > 30nm * setEmission Off via F10 menu * Note that RWR indications are removed as they are off * HARMs continue and precisely hit all 4 targets It seems the HARMs have the precise coordinates immediately and INS rather than radar homing Video: Please find mission/track: Mission: harms.miz Track File: harm-emission-off-tracking.trk Thanks, MartinCo

Tested again with DCS 2.9.18.12722 and the issue remains

Thank you so much for the speedy reply, really appreciate it!

Hi @BIGNEWY Is there any update on this ? I see it was marked as fixed internally a few patches ago but it seems like it may not have reached release as of today's patch. Thanks for all the hard work! Kind Regards, Martin

Hi @BIGNEWY I got excited seeing the change note for DCS 2.9.17.11733 Unfortunately - it seems that this only works if you are the MP server host - and it is not synchronized to connected clients Using the attached mission file If you start MP from the Multiplayer menu, jump into the truck, use the F10 menu to spawn the farp, we can see that the FARP is created, and the dynamic spawn menu is activated and populated with our new farp. If we run the same mission on a dedicated server - once the FARP is created - it is shown on the map, we can have the server query the warehouse content but the dynamic spawn menu remains unavailable If we add debugging to `Scripts\UI\MultiplayerSelectRoleMap\MultiplayerSelectDynamicDialog.lua` we can see that neither the FARP name, nor DCS.getDynamicSpawnSettings response is synchronized to the client showing the farp has no name, and the settings do not allow dynamicSpawn / hotspawn LuaGUI (Main): --dbg-- farps:90210 LuaGUI (Main): --dbg-- farps:90210 => y => 501000 LuaGUI (Main): --dbg-- farps:90210 => x => -499000 LuaGUI (Main): --dbg-- farps:90210 => name => LuaGUI (Main): --dbg-- farps:90210 => coalition => blue LuaGUI (Main): --dbg-- farps:90210 => type => FARP LuaGUI (Main): --dbg-- addFunc - dynamicSpawnAvailable => false LuaGUI (Main): --dbg-- addFunc - allowHotSpawn => false Here is a video showing both of the above routes This patch has also impacted the previous workaround of pre-creating warehouse entries in the "warehouses" file within the mission - and this workaround no longer works Track file as client running the server: server-20250622-145021.trk Track file from client of server: farp-sync-bug-20250622-145058.trk Example Mission FIle: farp-sync-bug.miz Thanks, Martin

Just to say this is still happening - I spent about half a day trying to get it to reproduce without much luck joy trying all sorts of things to get the missile to destroy itself and in the process the unit, most often it's happening with Roland ADS the last 3 crashes we have had have all been exactly the same scenario as the first post Unfortunately it's a 1.5 hour track on the latest one so haven't added it and will think of how i can try reproduce it DCS/2.9.13.6818 dcs.20250302-233535.log-2025-03-02 23:35:34.452 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=1945,targetMissionID=1002676,target_ws_type1=2,initiator_object_id=17076993,target=Roland ADS,target_object_id=17076993,targetPilotName=Roland ADS,type=kill,target_unit_type=Roland ADS,t=4846.232,initiator_unit_type=Roland ADS,event_id=1947,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1002676,initiator_coalition=2, dcs.20250302-233535.log-2025-03-02 23:35:34.452 INFO Scripting (Main): event:type=score,initiatorPilotName=Roland ADS,t=4846.232,linked_event_id=1947,initiator_unit_type=Roland ADS,event_id=1948,initiator_object_id=17076993,amount=-15,comment=ground,initiator_coalition=2,initiator_ws_type1=2,initiatorMissionID=1002676, dcs.20250302-233535.log-2025-03-02 23:35:34.452 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=0,targetMissionID=1002676,target_ws_type1=2,initiator_object_id=17076993,target=Roland ADS,target_object_id=17076993,targetPilotName=Roland ADS,type=bda,target_unit_type=Roland ADS,t=4846.232,initiator_unit_type=Roland ADS,event_id=1950,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1002676,initiator_coalition=2, dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): # -------------- 20250302-233535 -------------- dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): DCS/2.9.13.6818 (x86_64; MT; Windows NT 10.0.20348) dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 0000564300000000 00:00000000 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\dcs\server\bin;', symOptions: 532, UserName: 'sdcs' dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): OS-Version: 10.0.20348 () 0x110-0x3 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x0000564300000000 ((module-name not available)): (function-name not available) + 0x0 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x000000000011f182 (Weapons): wStowage::stopRearm + 0x1762 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x00000000001532e8 (Weapons): woMissile::doExplode + 0x1C8 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x00000000001219e8 (Weapons): weaponInitRandomSeed + 0x1C08 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x00000000000807ac (edCore): Mail::Reader::stream + 0x13FC dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x0000000000d13d84 (DCS_server): SW + 0x6FE7D4 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x0000000000d28bd6 (DCS_server): SW + 0x713626 dcs.20250302-233535.log-2025-03-02 23:35:34.476 INFO EDCORE (Main): 0x0000000000d3478e (DCS_server): SW + 0x71F1DE dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x0000000000a68511 (DCS_server): SW + 0x452F61 dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x0000000000a228f4 (DCS_server): SW + 0x40D344 dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x0000000000a24023 (DCS_server): SW + 0x40EA73 dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x000000000272ad88 (DCS_server): AmdPowerXpressRequestHighPerformance + 0x1263D84 dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x00000000010ad88e (DCS_server): SW + 0xA982DE dcs.20250302-233535.log-2025-03-02 23:35:34.477 INFO EDCORE (Main): 0x0000000000014cb0 (KERNEL32): BaseThreadInitThunk + 0x10 2025-02-07 DCS/2.9.12.5336 dcs.20250207-034601.log-2025-02-07 03:46:00.652 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=3213,targetMissionID=1000722,target_ws_type1=2,initiator_object_id=16882433,target=Roland ADS,target_object_id=16882433,targetPilotName=Roland ADS,type=kill,target_unit_type=Roland ADS,t=10334.83,initiator_unit_type=Roland ADS,event_id=3215,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1000722,initiator_coalition=2, dcs.20250207-034601.log-2025-02-07 03:46:00.652 INFO Scripting (Main): event:type=score,initiatorPilotName=Roland ADS,t=10334.83,linked_event_id=3215,initiator_unit_type=Roland ADS,event_id=3216,initiator_object_id=16882433,amount=-15,comment=ground,initiator_coalition=2,initiator_ws_type1=2,initiatorMissionID=1000722, dcs.20250207-034601.log-2025-02-07 03:46:00.653 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=0,targetMissionID=1000722,target_ws_type1=2,initiator_object_id=16882433,target=Roland ADS,target_object_id=16882433,targetPilotName=Roland ADS,type=bda,target_unit_type=Roland ADS,t=10334.83,initiator_unit_type=Roland ADS,event_id=3218,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1000722,initiator_coalition=2, dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): # -------------- 20250207-034601 -------------- dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.20348) dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 0000564300000000 00:00000000 dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\dcs\server\bin;', symOptions: 532, UserName: 'sdcs' dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): OS-Version: 10.0.20348 () 0x110-0x3 dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): 0x0000564300000000 ((module-name not available)): (function-name not available) + 0x0 dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): 0x000000000011f0c2 (Weapons): wStowage::stopRearm + 0x1762 dcs.20250207-034601.log-2025-02-07 03:46:00.675 INFO EDCORE (Main): 0x0000000000152488 (Weapons): woMissile::doExplode + 0x1C8 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000121918 (Weapons): weaponInitRandomSeed + 0x1BF8 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x00000000000807ac (edCore): Mail::Reader::stream + 0x13FC dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000be5ca4 (DCS_server): SW + 0x6F91B4 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000bfad86 (DCS_server): SW + 0x70E296 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000c068ae (DCS_server): SW + 0x719DBE dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x000000000093a501 (DCS_server): SW + 0x44DA11 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x00000000008f4a94 (DCS_server): SW + 0x407FA4 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x00000000008f61c3 (DCS_server): SW + 0x4096D3 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000002266183 (DCS_server): AmdPowerXpressRequestHighPerformance + 0x11D117F dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000cd5eb2 (DCS_server): SW + 0x7E93C2 dcs.20250207-034601.log-2025-02-07 03:46:00.676 INFO EDCORE (Main): 0x0000000000014cb0 (KERNEL32): BaseThreadInitThunk + 0x10 2025-01-03 Roland ADS dcs.20250103-043509.log-2025-01-03 04:35:08.927 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=1374,targetMissionID=1000973,target_ws_type1=2,initiator_object_id=16923137,target=Roland ADS,target_object_id=16923137,targetPilotName=Roland ADS,type=kill,target_unit_type=Roland ADS,t=3664.691,initiator_unit_type=Roland ADS,event_id=1376,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1000973,initiator_coalition=2, dcs.20250103-043509.log-2025-01-03 04:35:08.927 INFO Scripting (Main): event:type=score,initiatorPilotName=Roland ADS,t=3664.691,linked_event_id=1376,initiator_unit_type=Roland ADS,event_id=1377,initiator_object_id=16923137,amount=-15,comment=ground,initiator_coalition=2,initiator_ws_type1=2,initiatorMissionID=1000973, dcs.20250103-043509.log-2025-01-03 04:35:08.928 INFO Scripting (Main): event:weapon_type=6496868,initiatorPilotName=Roland ADS,target_coalition=2,linked_event_id=0,targetMissionID=1000973,target_ws_type1=2,initiator_object_id=16923137,target=Roland ADS,target_object_id=16923137,targetPilotName=Roland ADS,type=bda,target_unit_type=Roland ADS,t=3664.691,initiator_unit_type=Roland ADS,event_id=1379,weapon=XMIM-115 Roland,initiator_ws_type1=2,initiatorMissionID=1000973,initiator_coalition=2, dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): # -------------- 20250103-043509 -------------- dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): DCS/2.9.11.4686 (x86_64; MT; Windows NT 10.0.20348) dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 0000564300000000 00:00000000 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\dcs\server\bin;', symOptions: 532, UserName: 'sdcs' dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): OS-Version: 10.0.20348 () 0x110-0x3 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000564300000000 ((module-name not available)): (function-name not available) + 0x0 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000122a02 (Weapons): wStowage::stopRearm + 0x1752 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000155d48 (Weapons): woMissile::doExplode + 0x1C8 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000125258 (Weapons): weaponInitRandomSeed + 0x1BF8 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x00000000000807ac (edCore): Mail::Reader::stream + 0x13FC dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000be3e34 (DCS_server): SW + 0x6F7364 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000bf8f16 (DCS_server): SW + 0x70C446 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000c04a3e (DCS_server): SW + 0x717F6E dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000939a21 (DCS_server): SW + 0x44CF51 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x00000000008f3fb4 (DCS_server): SW + 0x4074E4 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x00000000008f56e3 (DCS_server): SW + 0x408C13 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000002265047 (DCS_server): AmdPowerXpressRequestHighPerformance + 0x11D2043 dcs.20250103-043509.log-2025-01-03 04:35:08.951 INFO EDCORE (Main): 0x0000000000cd4182 (DCS_server): SW + 0x7E76B2 dcs.20250103-043509.log-2025-01-03 04:35:08.952 INFO EDCORE (Main): 0x0000000000014cb0 (KERNEL32): BaseThreadInitThunk + 0x10

Thanks for the update @Flappie - work has gotten in the way of me testing it - but looks like you managed to! Thank you I was super impressed with the quick turn around, and a persisting artifact client side is certainly preferable to a server crash that affects all!

Thank you @Flappie for the super fast repro and report!

DCS Version: 2.9.12.5336.1 Steps to reproduce: - Host attached mission on MP server - Spawn in with HUEY - F10 -> Spawn Crate - Hook Crate - F10 -> Destroy Crate (`crate_object:destroy()`) Server crash (not client) - This does not occur in single player Server Track attached heredcs.log-20250215-180654.zip Mission file: sling-destroy.miz

Thank you so much for the fix! I can remove some messy remove inventory / re-add inventory now when new players join the server / spawn etc. Fixed in `DCS 2.9.12.5336`

Hi ED, Did a search and didn't find this reported. Since 2.9.10.4160 (or possibly the prior patch) messages sent to players (trigger.action outText etc) are clipped behind the F10 map, this makes it particularly easy to miss messages, especially for those in Combined arms and forcing people to view the message history to confirm they haven't missed something First image: one can see the F10 menu title cut off Second image: you can see the message background clipped Third Image: by opening up the comms menu, we can force the message to be moved to below the menu in order to view it Please find attached track: outTextIssue.trk nullReproduction: - Enter TACCOM slot to get to the map view (or enter 16 and press f10) - F10 Menu -> Other -> outText - observe the message being clipped by top menu - Open Comms Menu, confirm the text message is shown nullnull

Issue persists with DCS 2.9.10.4160 Now i'm glad i decided to make the Airbase version that did get fixed with the patch as a different thread: https://forum.dcs.world/topic/365453-airbase-warehouses-not-syncronized-on-player-join-since-29103948/ Thanks, Martin

I have verified this Airbase issue seems to be resolved with DCS 2.9.10.4160 as per the patch notes

Hi ED This behavior change was introduced with 2.9.10.3948; Tracks, Video below from stock DCS with no scripts/mods Before 2.9.10.3948 if you had a MP mission with 1000 weapons in the warehouse (within the miz file - eg: airbase -> full info -> eqp -> clear -> set GBU38 to 1000), and you removed weapons via scripting (`Airbase.getByName("Batumi"):getWarehouse():setItem()`), these were reflected to clients on join. Since 2.9.10.3948, it seems this is not dispatched to new clients - only deltas that added as such players not online when the removal occurred can join and get however many weapons were originally in the miz file. Video of Issue: Plain Miz file: - warehouse-sync.miz Server Track: - server-20241207-121212.trk Client Tracks (related to multiple connections above): - warehouse-sync-20241207-121218-part1.trk - warehouse-sync-20241207-121301-part2.trk - warehouse-sync-20241207-121349-part3.trk This is possibly related, though different enough that I felt it was a different issue rather than adding to the existing one that was only (at the time) related to dynamically spawned FARPs/Warehouses Workaround: Given the behavior above I believe a workaround of removing all the weapons one wants to control from the warehouses embedded in the miz file and then only adding via the warehouse API should make this work as expected so that's what i'll do now to hopefully avoid this scenario

Issue persists with DCS 2.9.10.3948 New tracks for DCS 2.9.10.3948 Server Track: server-20241204-153723.trk Client Track Session 1 (spawning farp, set 10 rockets, showing rearm with 10, disconnect): farp-warehouse-issue3-20241204-153728.trk Client Track Session 2 (reconnect, rearm showing 0, set 15, rearm showing 5 (not 15), disconnect):farp-warehouse-issue3-20241204-153822.trk Thanks, Martin

This specific crash reproduction does not occur on DCS 2.9.9.2280 (I will monitor for more)

Hi @Flappie This (I'm pretty sure) resolved at one point (or at least, the terrain in this area updated that it was not causing a problem) however, this looks to have regressed and we're back to the same stack trace crashing the dedicated server as well as SP (as shown in the track), kicking players out from MP sessions. DCS: 2.9.8.1214 Steps: - Load Miz - Select Gepard - Set route to the grassy area NW of Bassal Runway (z: 42150 x: +5530 - pretty much anywhere in that area causes the crash) - Crash Please find new track file attached: -20241012-134510.zip 2024-10-12 13:45:10.255 INFO EDCORE (55720): # -------------- 20241012-134510 -------------- 2024-10-12 13:45:10.257 INFO EDCORE (55720): DCS/2.9.8.1214 (x86_64; MT; Windows NT 10.0.22631) 2024-10-12 13:45:10.259 INFO EDCORE (55720): E:\DCS\DCS World\bin-mt\edterrain4.dll 2024-10-12 13:45:10.261 INFO EDCORE (55720): # C0000005 ACCESS_VIOLATION at 00007ff923e07987 00:00000000 2024-10-12 13:45:10.262 INFO EDCORE (55720): SymInit: Symbol-SearchPath: 'E:\DCS\DCS World\bin-mt;', symOptions: 532, UserName: 'Martin' 2024-10-12 13:45:10.264 INFO EDCORE (55720): OS-Version: 10.0.22631 () 0x100-0x1 2024-10-12 13:45:10.266 INFO EDCORE (55720): 0x0000000000077987 (edterrain4): buildMaxEdgeLengthUVSet + 0x1767 2024-10-12 13:45:10.268 INFO EDCORE (55720): 0x000000000024001c (edterrain4): landscape5::navGraph5File::findPath + 0x97C 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x000000000026f8c1 (edterrain4): navGraphPath2::save + 0x2861 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000270042 (edterrain4): navGraphPath2::save + 0x2FE2 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x000000000002435c (edterrain4): ITerrainImpl4::createPathCB + 0x14C 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000206c21 (Transport): wcRoute::createRouteWORoad + 0x91 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x00000000000ac28c (Transport): RouteManager::clear + 0xC7C 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000033b58 (edCore): ed::SyncTaskQueue::push_task + 0x478 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000048b06 (edCore): ed::SyncTaskQueue::push_task + 0x15426 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000032451 (edCore): ed::thread::_get_current_thread_id + 0x71 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2024-10-12 13:45:10.270 INFO EDCORE (55720): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D I have not experienced this on Caucasus or PG however I do feel the underlying ed methods should be more graceful in the event of any topology issues (if that is the trigger / root cause) Thanks, Martin

Hi ED, Since DCS 2.9.8.1214 (It's hard to say if this was also in the main release, but for us it only started experiencing after the hotfix) We have had 4 dedicated server crashes all with the same stack trace below causing significant disruption on our multiplayer servert90-crash.miz 2024-10-05 11:58:00.719 INFO EDCORE (Main): 0x00000000000f7f5b (Weapons): wAmmunitionVikhr::Ny + 0x375B 2024-10-06 12:56:50.884 INFO EDCORE (Main): 0x00000000000f7f5b (Weapons): wAmmunitionVikhr::Ny + 0x375B 2024-10-06 13:16:42.802 INFO EDCORE (Main): 0x00000000000f7f5b (Weapons): wAmmunitionVikhr::Ny + 0x375B 2024-10-06 13:29:01.668 INFO EDCORE (Main): 0x00000000000f7f5b (Weapons): wAmmunitionVikhr::Ny + 0x375B We have managed to reproduce in single player too (Miz file attached) which has just 2 x T90s engaging 1xAbrams with AT-11 whilst you fly in the vicinity and the crash will occur - sometimes it's fast, sometimes slow - could be related to AT-11 missiles vanishing after hitting the buildings. This has occurred whilst flying both the CH47 and AH64 (I didn't try any more modules after confirming two) First track whilst flying CH47, and second track (even faster crash 1545) with the AH64 In the meantime, we have disabled T80/90/ZTZ s etc. just to limit the risk of recurrence. Video: Stack Trace: 2024-10-06 15:45:18.406 INFO EDCORE (Main): # -------------- 20241006-154519 -------------- 2024-10-06 15:45:18.408 INFO EDCORE (Main): DCS/2.9.8.1214 (x86_64; MT; Windows NT 10.0.22631) 2024-10-06 15:45:18.410 INFO EDCORE (Main): E:\DCS\DCS World\bin-mt\Weapons.dll 2024-10-06 15:45:18.411 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffef5c17f5b 00:00000000 2024-10-06 15:45:18.413 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\DCS\DCS World\bin-mt;', symOptions: 532, UserName: 'Martin' 2024-10-06 15:45:18.415 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 2024-10-06 15:45:18.417 INFO EDCORE (Main): 0x00000000000f7f5b (Weapons): wAmmunitionVikhr::Ny + 0x375B 2024-10-06 15:45:18.419 INFO EDCORE (Main): 0x000000000012fc37 (Weapons): wWeaponSystem::getEmissionModeForTarget + 0x1C7 2024-10-06 15:45:18.420 INFO EDCORE (Main): 0x0000000000143230 (Weapons): wWeaponSystemManager::getEmissionModeForTarget + 0x580 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000001159ec (Weapons): wGroupTargetManager::mailToHuman + 0x5C 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x0000000000115ba2 (Weapons): wGroupTargetManager::mailToHumanPlanes + 0xB2 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000000be1d5 (Transport): wcColumn::GetLastWaypointId + 0x1B5 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000000045eb (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x0000000000004c12 (World): wSimCalendar::DoActionsUntil + 0x262 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x000000000090cfba (DCS): SW + 0x421F4A 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x000000000090cc91 (DCS): SW + 0x421C21 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000009325b2 (DCS): SW + 0x447542 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000008ecb04 (DCS): SW + 0x401A94 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000008ee233 (DCS): SW + 0x4031C3 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x00000000022990ad (DCS): AmdPowerXpressRequestHighPerformance + 0x120B0A9 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x0000000000ccde52 (DCS): SW + 0x7E2DE2 2024-10-06 15:45:18.421 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D dcs.log-20241006-152923.zipdcs.log-20241006-154519.zip

Issue persists with DCS 2.9.8.1214 Server Track: server-20241003-125147.trk Client Track Session 1 (spawning farp, set 10 rockets, showing rearm with 10, disconnect): farp-warehouse-issue3-20241003-125212.trk Client Track Session 2 (reconnect, rearm showing 0, set 15, rearm showing 5 (not 15), disconnect): farp-warehouse-issue3-20241003-125316.trk Other clients who were on for both "weapon add events" would have 15 showing in stock (+10 +5)

Draconus, I'm all for a far better global picture mechanic, but that's also significant amount of work to undertake The initial suggestions were (I hoped) a low effort initial tweaks that would yield high returns for a significant number of the community - some movement and improvements are far better than nothing, and easier than asking everything and getting nothing

Hi ED, When using dynamically spawned FARPs and warehouses in multiplayer the item counts do not seem to be syncronized on player join. (FARPs existing within the miz file however, do seem to synchronize content across rejoins) Please see attached video of the following actions: Spawn Invisible FARP Rearm / Refuel menu shows no weapons Add Hydra rockets to FARP Rearm / Refuel menu shows 70 rockets Disconnect Reconnect Rearm / refuel menu shows no weapons Remove Hydra rockets from FARP Add Hydra rockets to FARP Rearm / Refuel menu shows 70 rockets Server Log (not much on) dcs.log Server Track: server-20240915-205728.trk Mission File: farp-warehouse-issue3.miz Edit: Some things I have found out, the above works because i removed them, and added them again with some delay (client sync time) If you run just the add then you will not get weapons in the menu - it appears DCS sends a delta to clients, which makes perfect sense from an eventual consistency perspective with independent client local operations that may occur at the same time as such if you do: warehouse:setItem("weapons.nurs.HYDRA_70_M151", 10) Warehouse shows 10 Disconnect / Reconnect warehouse:setItem("weapons.nurs.HYDRA_70_M151", 10) Warehouse shows 0 warehouse:setItem("weapons.nurs.HYDRA_70_M151", 15) Warehouse shows 5 Mission file including this edit: farp-warehouse-issue3-edit.miz So it does just look like the initial state is missing as part of connection join is absent to correctly apply the series of deltas that occur after join A possible workaround for now is to monitor the time of last sync of your warehouse and if a player is within range and not been synced since they connected then you can remove current inventory making all clients 0 then add the inventory again as required (this may pose a race condition for those actively rearming at that specific location during the "outage") but it's probably better than no weapons