OODA Value Impact

[TitaniumTrout]

I'm working with the OODA field in the Unit wrapper, https://commandlua.github.io/#wrapper_Unit. I have three values to work with, Detection, Evasion, and Targeting.

Code: Select all

unit.OODA = {detection = 900, evasion = 900, targeting = 1}

This gives me a ship that doesn't evade incoming missiles but almost instantly targets the incoming strike. Evasion and targeting have impacts to what I'd expect to see.

What is detection doing? I've manipulated it big, small, in between, and the incoming strike is detected at approximately the same point every time. I've tested it on aircraft and see no impact. Am I missing something to use it properly?

[KnightHawk75]

Detection may be just its default time detection/scan-time for sensory on the 'unit', I don't think it applies to sensor-specific-scantimes (that can't be changed) though which is why you might not noticed a difference,ie your radars and such that have their own setting continue to use their own hardcoded settings. I wonder how much it's actually used anymore, for instances minedetector sensors I think still pull their scan time from this default, but other than that not sure what else. Question for devs perhaps.

[rneum]

Has anyone looked at a distraction function? Some of the news reports from the current crisis seem to indicate a crew can get focused on one thing and another is missed. I read an article that seems to indicate the Moskva was overly focused on one threat when another came in from a different direction.

[blu3s]

I'm working with the OODA field in the Unit wrapper, https://commandlua.github.io/#wrapper_Unit. I have three values to work with, Detection, Evasion, and Targeting.

Code: Select all

unit.OODA = {detection = 900, evasion = 900, targeting = 1}

This gives me a ship that doesn't evade incoming missiles but almost instantly targets the incoming strike. Evasion and targeting have impacts to what I'd expect to see.

What is detection doing? I've manipulated it big, small, in between, and the incoming strike is detected at approximately the same point every time. I've tested it on aircraft and see no impact. Am I missing something to use it properly?

I have been doing some tests and detection affects, as the name implies, the detection by the unit. For example with a CG 57 against a B-52 flying in the direction of the CG57 with an angle of 225 degrees. With a detection OODA of 15s the B-52 is detected at 249nmi 45º. With the detection time at 500 the B-52 is detected at 222.2nmi 45º. Taken to the extreme, with a detection time of 5000, the detection range is 100nmi at 225º when the B-52H has already overflown the CG. So with a detection of 0 you have the exact instant when the sensor detects the unit.