... I'm guessing you'll need to revise your debrief window to read some like this:
600' - AR; 1500' - IC; 2300' - IM; 3100'-3600' - X; 4000' - BC; 5000' - BR
And instead of a solid lines for the start, use dashed lines. This would make the start variable, a window, as it should be for each pass.
Fair enough. However, my suggestion slightly differs:
600' - AR; (1/4 nm) 1500' - IC; (1/2 nm) 3000' - IM; 4000 - X, BC; (3/4 nm) 4500' - BR
My guess is that the Start is where the pilot starts calling the ball, right? Given the approach speed of 145 kts, we'll have some 16 sec in the groove, and at 130 kts groove time will be exactly 18 sec...
And it's ok to add some randomization, or a window. But currently no dashed lines, sorry
...Once you pass the IC point you shouldn't get a waveoff for a deviation that falls into the "a little" category, i.e. "(LO) A Little Low", or "(HI) A Little High". Since the cone has shrunk considerably by the time you get to the IC point, corrections for (LO) or (HI) are easily and safely done with small power adjustments...
You can adjust the waveoff limits in the [Locus.GS] section of the vLSO.ini file:
; The glideslope locus.
; This is a boundary which represents the locus of points in the vertical plane from which
; the aircraft will reach an on-glideslope condition at the ramp.
; Distances are measured in feet from the touchdown point.
;--- Dist Up Down
Pos.0 = 5200, 1.30, -1.60
Pos.1 = 2500, 0.75, -0.77
Pos.2 = 2200, 0.68, -0.72
Pos.3 = 2000, 0.66, -0.71
Pos.4 = 1600, 0.57, -0.60
Pos.5 = 600, 0.45, -0.55
Last two numbers are the glideslope deviations, up and down respectively. Generally, 'a little' area starts from 0.3 degree up to some 0.8 degree...