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

vLSO Beta release

<< < (219/282) > >>

syn:

--- Quote from: GOONIE on October 09, 2014, 03:23:24 pm ---Couple LSO call questions:

So I am trying to understand when the LSO would say "don't settle" vs. "you're low" vs. "little power", don't they all essentially mean the same thing?

My take is "don't settle" is used when you are trending low on the approach. "you're low" is an informative call used early in the approach (X to IM). "little power" is used when you are going to go below glideslope if power is not added, and is an imperative call used closer to the ramp. Does that sound right?

Same thoughts on following calls: "attitude", "easy with it", "don't go high". I assume "attitude" is used when your nose gets low, slightly flat attitude, and power and attitude (AoA) are not presenting good info to the pilot. "easy with it" means you are overpowered, and fast (AoA red chevron) and is an imperative call used closer to the ramp (IM to IW). "don't go high" is an informative call used early in the approach (X to IM).

Just trying to understand these calls better, when they are used, what they mean, and also wanted to see if this is how vLSO utilizes these calls (logic).

Thanks.   

--- End quote ---

I also think that vLSO should make less advisory calls and more imperative calls as you get closer in. I also miss having more "power"/"easy with it" calls :'(

Taras:
Hi guys
First of all, thanks for vLSO,  great program that brings a lot of reality to carrier ops

Unfortunately for a while I deal with a little problem.  

vLSO is not able to recognized and identified  FCLP airbases,but all carriers are identified and with them vLSO works correctly
I have NAS Meridian KNMM and Fentress KNFE sceneries, all installed properly, according the install instructions (in add-on scenery folder there are the appropriate "tag" files in each of the scenery folders)

Do you have any suggestions what could lead to that problem?

Thanks for any help

Taras

discoferret:
Hi, I have just started using vLSO and have a problem with a "wave off" after I've caught the wire, which obviously give me a cut pass. It happens a lot, has anyone else having the same problem?

GOONIE:
discoferret,

Can you post a screen shot of the vLSO debrief when this happens? Is it an On/On pass, with a random WO in the wires? Or is it a dive "spotting the wires" pass, which deserves a late WO? Could also be a delay in the program due to many calls being triggered, are you getting a lot of calls prior to the WO call?

GOONIE:
Paddles,

Looking forward to the $HB feature in vLSO, I've been practicing

 8)

Navigation

[0] Message Index

[#] Next page

[*] Previous page