General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
Paddles:
--- Quote from: capthaltli on December 06, 2011, 03:18:06 pm ---One thing I noticed which might need to be tweaked is the OK3 scoring criteria. I noticed you implemented the _OK3_ since I got two of them last night; however, on both of the approaches I had minor errors on speed and g/s which were in the LSO logbook. I think this score should be reserved for only those approaches where no parameters are flagged in the LSO logbook entry, besides just an OK three wire, what do you think?
--- End quote ---
Yes, the scoring system currently is just basic and primitive and really needs to be tweaked. I will concentrate on this in the next betas.
--- Quote from: capthaltli ---I like when you catch a three wire (and get the OK3) the LSO in FSX says something like "very nice" or "great job" it is hard to hear, but I did notice it. 8)
--- End quote ---
The vLSO says something like that, too. Didn't you hear it? ;)
--- Quote from: capthaltli ---Also, is there a way to make the OK3 score in the vLSO completely underlined like OK3, not just underlines to the left and right of the _OK3_ ?
--- End quote ---
Yes, it's easy. Fixed in beta 0.4
--- Quote from: candy ---After launching vLSO the abeam call only sound off once and never again till you re-launch the program
--- End quote ---
Oops... That's my fault. Fixed in beta 0.4 :)
GOONIE:
--- Quote from: fsxnavypilot on December 07, 2011, 04:31:47 am ---The vLSO says something like that, too. Didn't you hear it? ;)
--- End quote ---
Just got it, "beauty" for an OK3
-CAPT
Sludge:
CAPT...
Got that "beauty" for an OK, 3 pass last night. I usually fly at Fleet level but havent tried CAG level yet. Thatll wait for a few nights this weekend.
Serge...
I'm having problems with the Abeam distance call, still get "TOO CLOSE ABEAM" at 1.3 NM on the HUD. I'll try to get more passes, and give you a more comprehensive data set to work with. Obviously flying the Sludge, and doing the standard pattern. Not sure why I'm getting that but I do have a request for the next release. Can you make all the aircraft parameters (name/type/call abeam and [locus] info) selectable like you do with the "custom aircraft"? That way we can customize it.
Later
Sludge
Paddles:
--- Quote from: Sludge on December 08, 2011, 08:40:59 pm ---I'm having problems with the Abeam distance call, still get "TOO CLOSE ABEAM" at 1.3 NM on the HUD.
--- End quote ---
Sludge,
Remember this discussion http://www.fsdreamteam.com/forum/index.php?topic=3093.msg30177#msg30177? Look how this work with the vLSO...
The HUD shows the slant distance from your aircraft to the TACAN antenna, located at 205' AMSL. The vLSO computes the horizontal distance from the glideslope origin. Because of that this origin is some 280' afore, the slant distance between these reference points is about 350' (that's just for your information).
So, if you are at 1.24 nm abeam the GS origin (i.e. TCA for the Hornet), it will give us 7534' of horiz distance. However if your altitude at this position is 600', this equals to 7717' of slant distance, which is 1.27 nm, or 1.3 TCN on the HUD. And the higher altitude, the longer the slant distance...
Finally, the slant distance for 1.25 nm abeam at 600' AMSL should be 7777', or 1.28 nm, which is the same 1.3 TCN on the HUD. Bummer!... ;D
That's why you shouldn't rely solely on TCN readings when flying abeam.
FYI. The HUD rounds TCN distances this way: 1.20 is 1.2, but 1.21 is 1.3 and 1.29 is 1.3 too....
Hope this helps... :)
Sludge:
Serge...
--- Quote ---Remember this discussion http://www.fsdreamteam.com/forum/index.php?topic=3093.msg30177#msg30177? Look how this work with the vLSO...
--- End quote ---
O yeah, I remember that discussion and I see what you're saying.
--- Quote ---Finally, the slant distance for 1.25 nm abeam at 600' AMSL should be 7777', or 1.28 nm, which is the same 1.3 TCN on the HUD.
Bummer!... That's why you shouldn't rely solely on TCN readings when flying abeam.
--- End quote ---
So I think we can just use 1.4 NM? The reason I'm asking is that what else do we use? We dont have an HSI readout (HSI w/TCN filter set @ 10 NM range setting;left wing of AC symbol on the carrier TCN) to help us get the correct starting abeam. I'm guessing 1.4 HUD TCN will be a good starting point and then go from there.
As JJ says: these are "training wheel" numbers. For me, these will help us non-real world naval aviator wannabe's get a good starting abeam position, so we can see the correct outside visuals (at the 90, crossing wake at 45; in FSX) that will let us fly good patterns once we get the feel of it.
Later
Sludge
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version