General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
SpazSinbad:
8.3 NIGHT OPERATIONS F/A-18A/B/C/D NATOPS http://info.publicintelligence.net/F18-ABCD-000.pdf
"8.3.1 General. Night carrier operations have a much slower tempo than daylight operations and it is
the pilot’s responsibility to maintain this tempo. Standard daytime hand signals from deck crew to
pilot are executed with light wands. The procedures outlined here are different from, or in addition to,
normal day carrier operations.
8.3.2 Preflight. Conduct the exterior preflight using a white lensed flashlight. Ensure that the
exterior lights are properly positioned for launch and the external lights master switch OFF before
engine start. Ensure that instrument and console light rheostats are on. This reduces brilliance of the
warning and advisory lights when the generators come on.
8.3.3 Before Taxi. Adjust cockpit lighting as desired and perform before taxi checks.
8.3.4 Taxi. Slow and careful handling by aircraft directors and pilots is mandatory. If any doubt
exists as to the plane director’s signals, stop the aircraft. At night it is very difficult to determine speed
or motion over the deck; rely on the plane director’s signals and follow them closely.
8.3.5 Catapult Hook-Up. Maneuvering the aircraft for catapult hook-up at night is identical to that
used in day operations; however, it is difficult to determine speed or degree of motion over the deck.
8.3.6 Catapult Launch. On turn-up signal from the catapult officer, ensure throttles are in MIL or
MAX and check all instruments. Ensure that launch bar switch is in the retract position. When ready
for launch, place external lights master switch ON.
All lights should be on bright with the strobes on. If expecting to encounter instrument meteorological
conditions shortly after launch, the strobes may be left off at the discretion of the pilot.
After launch, monitor rotation of the aircraft to 12° nose up crosschecking all instruments to ensure
a positive rate of climb. When comfortably climbing, retract the landing gear and flaps and proceed on
the departure in accordance with ship’s procedures. The standby attitude reference indicator should be
used in the event of a HUD failure.
8.3.7 Aircraft or Catapult Malfunction. If a no-go situation arises, do not turn on the exterior lights
and transmit SUSPEND, SUSPEND. Maintain MIL/MAX power until the catapult officer walks in
front of the wing and gives the throttle-back signal. If the external lights master switch has been placed
on prior to ascertaining that the aircraft is down, transmit SUSPEND, SUSPEND and turn off the
exterior lights and leave the throttles at MIL until signaled to reduce power.
8.3.8 Landing Pattern. Night and instrument recoveries normally are made using case III procedures
in accordance with the CV NATOPS Manual.
8.3.9 Arrestment and Exit From the Landing Area. During the approach all exterior lights should
be on with the exception of taxi/landing light. Following arrestment, immediately turn the external
lights master switch off. Taxi clear of the landing area following the plane director’s signals."
thetford569:
--- Quote from: rsgunner on September 01, 2014, 06:24:22 pm ---I had a 3wirex entry that I had disabled.
I had not used that program in awhile so I just backed up the old EXE.XML and made the simplified one and it just worked.
Russ
--- End quote ---
Russ what exactly did you change in your exe.xml file? I am using Prepar3D 2.3 and am having the same problem with vLSO only working at one airfield but not the others. I only have 2 entries in my exe.xml and these 2 entries have been there for a long time. I have never seen anything related to vLSO in the exe.xml file that I can remember and I certainly don't have any entries in there now. My exe.xml looks like this:
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
<CommandLine>--mode=prepar3dv2</CommandLine>
<Launch.Addon></Launch.Addon>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name>
<Path>F:\Flight Simulator Programs\AICarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
</SimBase.Document>
vLSO has previously worked in Prepar3D with all of the FCLP airfields but for some reason right now it's only working at NJW. I tried to look at your solution hoping I had the same issue but all I have is aicarriers and coutl (which is for FSDreamTeam Airports).
Brandon
rsgunner:
Brandon
This is what my EXE.XML looks like.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>TrackIR5</Name>
<Path>C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name>
<Path>E:\AIcarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
<Launch.Addon>
<Name>vLSO</Name>
<Disabled>False</Disabled>
<Path>E:\vLSO\vLSO.exe</Path>
<CommandLine>auto</CommandLine>
</Launch.Addon>
</SimBase.Document>
Russ
thetford569:
--- Quote from: rsgunner on September 16, 2014, 02:01:15 pm ---Brandon
This is what my EXE.XML looks like.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>TrackIR5</Name>
<Path>C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name>
<Path>E:\AIcarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
<Launch.Addon>
<Name>vLSO</Name>
<Disabled>False</Disabled>
<Path>E:\vLSO\vLSO.exe</Path>
<CommandLine>auto</CommandLine>
</Launch.Addon>
</SimBase.Document>
Russ
--- End quote ---
Thanks Russ....I was hoping this would be the answer to my problem and while I do see the menu options now in P3D I still don't have vLSO working at NALF Choctaw. It still works at NOLF Joe Williams. It is really strange how at one point it was all working but now KNJW is the only field I can get to work. I will still keep digging into this problem as time permits.
Brandon
rsgunner:
Brandon
Bring all the FCLP scenery to the top of the scenery library, see if that helps.
My only issue is KNMM has trenches and display issues.
Russ
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version