@Geez
Hello!
Nope, this happens only on modded run. Unfortunately, there's not much info besides logs I provided. I believe it may be tied to "losing" the mods on second run (another bug, btw):
0. Choose mods in the mod manager menu.

1. Go to Scenarios menu in main menu.
2. Select any scenario (Combat Ops, for example), choose multiplayer hosting option here, you will seee listen server MP settings modal window.
3. Go to Mods tab, notice that mods are not enabled despite that you selected them in the general mod manager menu.
4. Press play, wait until you will see the game world (play starts).
5. Go back to the scenarios, press the very same scenario, select Mods tab in listen server MP settings modal window. Notice that there is no mods at all. Scenarios will appear when you leave the Scenarios menu and revisit it later.

Infamous nvidia crash started to occur for me too (it wasn't like that before or wasn't that frequent):

01:01:19.679 RENDER    (E): Invalid copy queue fence value (complete = -1, expected 1505350), GPU crash is likely
01:01:19.679 RENDER    (E): Render error (-2005270523 = 0x887A0005): The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. The application should destroy and recreate the device.
01:01:19.679 RENDER    (E):   func: m_pD3DDevice->GetDeviceRemovedReason()
01:01:19.679 RENDER    (E):   C:\jenkins\cpu\workspace\continuous_branches_stable_1.3.0\ARGamecode\Enfusion\Enfusion\src\render\enf_rendmainimpl.cpp(3138): enf::RendererImpl::EndFrame
01:01:19.679 RENDER    (E): Device removed, reason: DXGI_ERROR_DEVICE_REMOVED
01:01:19.679 ENGINE    (F): Crashed
01:01:19.716 RENDER       : ----------------------------------------------------------------
01:01:19.716 RENDER       : ----------------------------------------------------------------
01:01:19.716 RENDER       : Rend: Fps:1000000.00 (0.00ms) | Present 0.00ms | Wait4GPU 0.00ms (graphical 0.00 + copy 0.00) | defrag 0.00ms
01:01:19.716 RENDER       : Rend: DP:0000 DPI:0000 DPR:0000 DPID:0000 Tri:00000 Vert:000000 CSRun:00|AllV:00x(00000) AllI:00x(00000) BegV:00x(00000) BegI:00x(00000)|TRes:0206
01:01:19.716 RENDER       : ----------------------------------------------------------------

My log:

Ticket is no longer relevant anymore, could be removed/closed.

Seems that I messed up my NV Control Panel settings. After resetting to default everything is working OK. Close the ticket.

@Arkensor
Thanks for the upcoming fix!😄

Debug tile regeneration 3x3 fixed this problem, so there's something with the patch generation.

@speedwaystar
Yeah, not here, but I'm seeing it too, especially on patrol behaviours.

Yeah, this is why I'm proposing thing from OP. :)
It's an compilable scripting language anyway, so compiler could handle this synthax sugar and unfold it in an ordinary || manner.

In T182389#2629802, @LouMontana wrote:

that's SQF syntax… in Enfusion we do

if (damageContext.damageType & (EDamageType.COLLISION | EDamageType.FIRE | EDamageType.REGENERATION))
     return;

:-)

Can confirm that it also happens in the game itself (1.2.0.70).

Seems to be that at very least Reforger Workbench Experimental fails to read some settings:

Nope, I haven't touched animation graphs at all, and I'm not using any other mods as dependencies.
Honestly, it is kinda self-resolved with 1.2.0.66 update, it no longer crashes for me .

@Geez
It seems to be random and mostly happens in Workbench.
You could try to spawn S1203 vehicle via Game Master in Workbench Play Mode (at very least it's how I got the state of the icon on screenshot from OP).

Seconding this.
I believe that current system fits DayZ (which is close encounters-focused due to it's "Friendly?" nature and need of social interactions between players), but it needs fine tuning to fit Arma.
Reforger's implementation has several problems:

1. It promotes close firefights no further than 100 meters (tbh, I never had even a midrange firefight at this moment), and this is wrong on so many levels as Arma was always about combined arms and actions on a squad/platoon level.
2. Since soldiers become just a few pixels beyond 200 meters, players can't see the result of their shootings, even that Arma 3 jittery hit animation was much better. It's a game, almost no one enjoys bullet-raining trees and bushes for an hour as it happens in real life. This detrimens gunplay a lot.
3. This basically makes any kind of rifle optics is necessary to hit something beyond 200 meters, so all public servers will be just PSO-1/ACOG fest. Humans are able to recognize and hit standing target with naked eye up to 400 meters as it stated, for example, in AK-74's shooting instruction books.

Can confirm - worked for me too. Thank you for posting the solution.

In T158403#2192726, @dedmen wrote:

"Since the DLC came out" or "Since the last Arma update 2.04 came out"
when exactly did that start? So far it doesn't seem to be caused by Arma.

I have the same problem. I had it before 19th May when i was on Steam Beta branch, but since i opted out of it things became good again. Until today.
Error started appearing today again, i guess this Steam Beta update moved into their stable Steam branch.