General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
Wingmate:
Just loaded up flightsim for a flight and vLSO loaded up correctly, no idea why I hadn't changed anything yet but now it is working.
Thanks for all the help
Edit:
It is not quite entirely fixed, it still throws the odd error occasionally and will some times revert to throwing them non stop on start up, but it is working to the point that I can use it now.
texxasal:
Sir,
Thanks very much for 0.8.1.2 Beta. It significantly enhances our enjoyment of the simulation.
The only "anomalies" I have noticed relate to the "Marshal" calls (those prefixed with the 99 identifier), and the "Taxi Lights On" and "Lights on Deck" advisories.
For some reason, the "99" calls don't go to the selected COM1 or COM2 frequency. They route appropriately to the vLSO Audio Device specified in the settings, but don't "track" to a discrete COM channel.
I have also noted that the Taxi Lights on & Lights on Deck seem to persist for a rather long time after corrective action has been applied by the pilot. How long should these message persist and, what criteria are you looking for to trigger/reset the "Lights on Deck" advisory? I fly the VRS Superbug with TacPack, and we have the ability to control exterior lights individual, as well as by the "External Lights Master" switch, per NATOPS for the airframe.
Again, thanks very much for a wonderful product. It completes the environment for carrier operations quite well.
regards
Al
Paddles:
--- Quote from: texxasal on September 14, 2014, 04:55:02 pm ---The only "anomalies" I have noticed relate to the "Marshal" calls (those prefixed with the 99 identifier), and the "Taxi Lights On" and "Lights on Deck" advisories.
For some reason, the "99" calls don't go to the selected COM1 or COM2 frequency. They route appropriately to the vLSO Audio Device specified in the settings, but don't "track" to a discrete COM channel.
--- End quote ---
Currently all Marshal calls go through the selected audiuo device, no matter what COM frequency is selected. Definitely this needs to be fixed.
--- Quote from: texxasal on September 14, 2014, 04:55:02 pm ---I have also noted that the Taxi Lights on & Lights on Deck seem to persist for a rather long time after corrective action has been applied by the pilot. How long should these message persist and, what criteria are you looking for to trigger/reset the "Lights on Deck" advisory? I fly the VRS Superbug with TacPack, and we have the ability to control exterior lights individual, as well as by the "External Lights Master" switch, per NATOPS for the airframe.
--- End quote ---
Once on deck, the program checks the lights state every 10 seconds. If any of the following lights are on, you'll hear 'lights on deck':
Strobe
Nav
Beacon
Taxi
Logo
Wing
Recognition
Landing
The 'taxi lights on' is triggered just twice - 30 sec and 1.5 min after the minimum visibility (1km) has been detected.
texxasal:
Thanks very much for the prompt reply.
For the Superbug guys, then "External Lights Master" is the way to go.
With the 10-second trigger, T/O procedures need to be modified.
1. Pre-takeoff checks prior to moving into t/o position on the CAT.
2. After "Bar Down" & "JBD UP", then t/o trim reset.
3. Power to T/O thrust.
4. Controls exercised & free.
5. External Lights Master "ON"
6. Launch trigger.
Slightly different from observed videos, which go lights on before Controls exercised & Power to T/O thrust.
Anyway, Thanks again.
Al
GOONIE:
Al,
The lights come on last to signal you are ready for takeoff on the carrier at night, just like the salute during the day, so it is the last thing you do to signal you are ready. Can you share the videos of the lights coming on then the control wipe out?
So the takeoff steps you show look in a good order, and should work with vLSO.
GOONIE
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version