I am having the same issue. Has anyone found any info on this?

I would also like to ask for add delay before ejection seat be killed. I'm talking about this function: BIS_fnc_planeEjection (a3\functions_f_jets\functions\ejection\fn_planeejection.sqf)
line 188

This is a great place to be. Many thanks to everyone who put in their time, energy, effort and time. This is an excellent resource. I'll be sharing the wonderful aspects of this site in my classes.
https://www.twitch.tv/danciesmith/about
https://about.me/pain-management

The site that the business uses is a good template for my own. I've recommended this website to family members and friends who are close to me. It's a fantastic site, and I'll recommend it to friends and acquaintances.

I have done a clean install of Windows 11 Pro and reinstalled Steam and Arma 3with no other programs installed or running. I get the same result and same error message. Please help!

In T167438#2384358, @Ron4Swat wrote:

I did some more testing on a new dedicated server installation on a different system and could reproduce the issue there with just vanilla Arma3.

After some testing it seems i found the culprit in the server config file.

The entry

class Missions {
     class ARMA3 {
         template = "MP_COOP_m02.Stratis";
         difficulty = "Regular"; 
     };
};

created the problem. When removing it from the config file it solves the problem.

This configuration is there for ages, but did not create any issues until more recently.

1. I'd leave Fired and FiredMan untouched for backwards compatibility
2. getShotParents and objectParent working with lasers could be a good idea if laser entity stores this stuff
3. I'd make it easy and just do a global MEH, something like LaserCreated and ensured Deleted works with laser entity, so you can track when its deleted

Additional optional parameter, useFuseDistance, choose whether to apply the projectile's config arming distance or not

Problemo. As usual backwards compat bites back.
Missions tend to spawn Missiles/Rockets/Bombs to cause explosions, by spawning them directly inside the target, expecting it to explode immediately (because it hit something).
For example YAAB benchmark is broken by this, it spawns R_60mm_HE rockets and Bo_GBU12_LGB bombs, both of which have a fuseDistance of 50. So after this change, they just don' t explode anymore.

However it works without the High Command module loaded

Update: game now starts when I disabled profiling

This issue is still a problem. I cannot speak in multiplayer. The issue has persisted for years now.

This is file for crash when mods are turned off

2.20 and next prof

These glasses for armed ones do not exist at all, at least Fire Geometry is completely gone

?

Hackers Suk

Not exactly sure, but the issue is either with extDB3 directly or with callExtension, as return value suggests some issues with getting the data. As there are no slow callExtension warnings in log, i guess its extDB3 issue so in that case Ticket could get closed.