Please attach your dcs.log for when the bug is experienced
Describe the bug
Currently, in DCS, the following is observed:
Scenario A: A LURX DRX call indicates an overshoot before the groove (1NM starts)
Scenario B: A LURX DRX LULX DLX call indicates an overshoot inside the start of the groove (1NM) OR if the player calls in before they are on centerline.
Scenario C: A LURX with no DRX appears to indicate a genuine lineup right.
Scenario D: A LULX with no DLX appears to indicate a genuine lineup left.
Currently in LSO BOT Scenario A is not evaluated differently, Scenario B writes the grade to LURX DRX , Scenario C/D do not need additional evaluation.
Desired behavior
When LURX DRX appears with a LURIM, this should be evaluated as OS
When LURX DRX appears with no LURIM, this should be evaluated as OSCB
When LURX DRX LULX DRX appears with a LURIM , this should be evaluated as TTS OS (?)
When LURX DRX LULX DRX appears with no LURIM, this should be evaluated as TTS OSCB (?)
Please attach your dcs.log for when the bug is experienced
Describe the bug
Currently, in DCS, the following is observed:
Scenario A: A
LURX DRXcall indicates an overshoot before the groove (1NM starts)Scenario B: A
LURX DRX LULX DLXcall indicates an overshoot inside the start of the groove (1NM) OR if the player calls in before they are on centerline.Scenario C: A
LURXwith noDRXappears to indicate a genuine lineup right.Scenario D: A
LULXwith noDLXappears to indicate a genuine lineup left.Currently in LSO BOT Scenario A is not evaluated differently, Scenario B writes the grade to
LURX DRX, Scenario C/D do not need additional evaluation.Desired behavior
When
LURX DRXappears with aLURIM, this should be evaluated asOSWhen
LURX DRXappears with noLURIM, this should be evaluated asOSCBWhen
LURX DRX LULX DRXappears with aLURIM, this should be evaluated asTTS OS(?)When
LURX DRX LULX DRXappears with noLURIM, this should be evaluated asTTS OSCB(?)