General Category > Unofficial F/A-18 Acceleration Pack board

vLSO Beta release

<< < (66/282) > >>

Paddles:
No, the waveoff lights on FSX carriers are triggered only if you're beyond the limits of the 4.0 glidepath (too high or too low). No lineup deviations whatsoever. It's a feature of FSX FLOLS, not a bug  ;D

Sludge:
Serge...

I would recommend making "groove time" start approx. 3500' regardless of ball call range, IF the ball call has been made beforehand. I would also re-designate your LSO debrief page to have a BR (Ball Request; case I/II/III) as the starting (rightmost) designation at 5000' vice 5200'. This will coincide with the 0.8 TCN that the IFLOLS flashes for Case I. Then have the pilot "ball call" (auto) at 4400', as this gives the pilot time to respond. Then the LSO responds at 3900', finishing at 3500', and thats when the pass starts (X) when grading is based upon.

** Notice on my pic: I flew a really solid pass and only got a fair. If I fly the same pass and the ball call is made closer to the BC area, I get an OK.

This is the real world video I'm basing this on... and I've flown the numbers and they seem to work well for ball call and groove time.
(the LSO finishes w/"roger ball, hornet, 38 knots port" at 3:27 and the Hornet hits the deck at 3:45 for an 18 sec approach... which conforms to most videos I've seen.)


Whether we are missing some real world piece of the puzzle to make FSX match the real world "groove time", I think this is a good FSX fix 'til we have an exact answer.

Also, what distance do you have setup for proper abeam? I keep getting "too close abeam" when I'm at 1.3 TCN on JRs "Realistic HUD". Now, I remember you said we shouldnt use that, but if we don't, what do we use in FSX? Only the VRS SuperBug can use the "HSI wingtip on the boat at 10 NM expansion" method... we (Sludge fliers, Combat Hornet, JR/Printz HUD users) have to rely on the HUD TCN, so what TCN distance will get us at the right distance abeam?

Later
Sludge

 

Sludge:
Serge...

Since I got a good night's rest, I'm revising my request. Instead of always starting the groove at 3500', I'd say start the "groove time" counter once the pilot has rolls wings level within 5-10 deg of final bearing IF they have already called the ball (manual or auto). I'll fly some passes and find out what HUD TCNs correllate (for FSX fliers) and their approximate display on your debrief screen in feet (so you can build a window). Tonight, I'll fly passes, saving an FSX screen shot and the accompanied vLSO debrief window for each pass. Then we can work out a "groove time" 15-19 secs that will ALLOW for the user to get an OK pass if they roll wings level onto final bearing in that 15-19 sec window.

Once that "groove window" gets figured out, 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.

Here's another video that adds to what I'm saying:
(you see just after 5000', Paddles gives a BR (ball request)... pilot answers at 4000' and LSO final reply finishes at 34-3300'.. and thats and 0:10 secs... he hits the ramp at 0:27)

(granted this video and the video I used before are CASE III approaches, but they show when the LSO goes out for a BR, when the pilot responds, LSO final reply and the start of grading. So transposing, Case I, ZIP LIP, the vLSO BC should be around 4400' and the grading should start ["roger, ball"] when the pilot rolls wings level and approximately on final bearing.)

I'd also add, if you don't already have it (I think you do)... if the pilot rolls wings level onto final bearing and doesnt have a ball (too high/too low to be visible), they get a "waveoff, pattern". As well, once all this "groove time" stuff is worked out, you can add "waveoff, pattern" (Case I) if the pilot doesnt roll wings level inside that "groove window".

Later
Sludge

MikeB54:
There is one thing I would like to see incorporated in the program.  This is something that Chris mentioned to me when he flew with vLSO.  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.  The attached image is a perfect example.

Mike

tgiesige:
Well, here is some more short clips flying VRS Super Hornet using the latest VLSO link "FSXNavyPilot". Not working well with the Bug, Now the exact opposite, getting called high when in fact right on the glide slope and in the groove as per debrief window. Constant "Don't Settle" from LSO ! Why? Is there some sort of parameters that needs to be tweaked by me in order to get the call right? watch the altimeter in the HUD on the approaches as you can see I am on the glide slope but getting called high.
I would really like to get this to work with the VRS Superbug. I am also using auto throttle control on approaches. At any rate not sure how to tweak or what to do to the configuration settings file.  ??? Thanks for your time, I am such a tard at times LOL.
VC97g&index=1&feature=plcp

Navigation

[0] Message Index

[#] Next page

[*] Previous page