Author Topic: vLSO Beta release  (Read 814509 times)

SpazSinbad

  • Hero Member
  • *****
  • Posts: 1198
  • RAN FAA: https://www.faaaa.asn.au/spazsinbad-a4g/
    • A4G Skyhawk & Fixed Wing history scrapbook PDFs & videos RAN FAA + How to Deck Land Various Aircraft
Re: vLSO Beta release
« Reply #1035 on: September 15, 2014, 04:44:36 am »
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."
https://www.faaaa.asn.au/spazsinbad-a4g/
RAN FAA A4G NAS Nowra ɐıןɐɹʇsn∀ :-)

thetford569

  • Newbie
  • *
  • Posts: 24
Re: vLSO Beta release
« Reply #1036 on: September 16, 2014, 04:52:10 am »
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

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

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1037 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
Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

thetford569

  • Newbie
  • *
  • Posts: 24
Re: vLSO Beta release
« Reply #1038 on: September 18, 2014, 04:20:02 am »
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

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

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1039 on: September 20, 2014, 10:33:23 pm »
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
Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

thetford569

  • Newbie
  • *
  • Posts: 24
Re: vLSO Beta release
« Reply #1040 on: September 22, 2014, 04:09:09 am »
Tried putting the scenery entries at the top of the library and also tried flipping the order of them at the top and no joy.  I finally decided to delete both KNJW and KNFJ from the library and download the files again for KNFJ to try it by itself.  I tried and it still didn't work.  I put KNJW in there and when I moved to KNJW then vLSO connects and works.  Moving back to KNFJ or trying to start from there and it still doesn't work.  I hate how finicky FS (P3D in my case) can still be.  I have no idea what could be causing this issue.  I know its certainly not a vLSO problem or a scenery problem from the download.  Sucks that I built this scenery of Choctaw and it was improved and made compatible for vLSO and now I can't use it!  I imagine the only cure for this is a re-install of everything and I'm not ready to do that so I guess I will just deal with KNJW being the only place I can practice FCLP.  I tried Coupeville as well and it wasn't working there either.  I haven't tried the new KNMM pack yet but I'm expecting more of the same.

Brandon

Paddles

  • Hero Member
  • *****
  • Posts: 721
  • Lurking around
    • vLSO blog
Re: vLSO Beta release
« Reply #1041 on: September 22, 2014, 07:20:52 am »
Brandon and other fellows running P3D,

I've been reading manuals and it is clear now that P3D uses its own set of registry keys. That's why vLSO couldn't reliably locate FCLP areas on P3D setups. That's why I have written a test program to make sure I correctly understand LM written words  ;D

Please run this small proggy on your systems and show me its output (a screenshot). Hopefully it will find all your active FCLP areas...
Want it done right? Do it yourself!


rsgunner

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1042 on: September 22, 2014, 01:52:38 pm »
Here is what mine looks like. I use P3D.

Roaming path: C:\ProgramData

FSX installed in E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\
FSX actual scenery config file found in C:\ProgramData\Microsoft\FSX\

274 scenery definitions read

An active FCLP area FSX_Meridian found. Local path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Addon Scenery\FSX_KNMM\FSX_Meridian

An active FCLP area KNFJ_FCLP found. Local path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Addon Scenery\KNFJ_FCLP

An active FCLP area KNRA_NOLF found. Local path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Addon Scenery\KNRA_NOLF

An active FCLP area KNFE_FCLP found. Local path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Addon Scenery\KNFE_FCLP

An active FCLP area KNJW_FCLP found. Local path: E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Addon Scenery\KNJW_FCLP


Russ
Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

Paddles

  • Hero Member
  • *****
  • Posts: 721
  • Lurking around
    • vLSO blog
Re: vLSO Beta release
« Reply #1043 on: September 22, 2014, 06:59:34 pm »
Thanks Russ!
A couple of questions:

Do you have FSX installed on the same computer? My program reported FSX found in LM folder, very interesting.

274 sceneries... Very strange (usually in FSX we have up to 130..140 items). Looks like this number is somehow doubled (by my program, indeed).

What does vLSO show when started on your system? Green or red SimConnect and FSX indicators?
« Last Edit: September 22, 2014, 07:01:40 pm by Paddles »
Want it done right? Do it yourself!


rsgunner

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1044 on: September 22, 2014, 07:30:23 pm »
The fsx executable is in the P3D main directory. Some programs want to see it.

I do have FSX installed on the same HD. I don't use it anymore for simming.

Green on the SimConnect and FSX indicator.

It would be fantastic if there was a P3D version.
I was thrilled that it runs in P3D with just a minimal number of issues.

I will look at the FSX scenery.cfg and see what is there.

Russ

Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

Paddles

  • Hero Member
  • *****
  • Posts: 721
  • Lurking around
    • vLSO blog
Re: vLSO Beta release
« Reply #1045 on: September 22, 2014, 08:22:12 pm »
Ok, is that 'FSX in the P3D folder' trick documented/recommended somewhere?
Want it done right? Do it yourself!


rsgunner

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1046 on: September 22, 2014, 08:25:49 pm »
Paddles

The FSX scenery.cfg file list ORBIX and Megascenery plus a bunch of other addon scenery, that is why it list so many.

I discovered something just now. I had put all of the FCLP scenery into FSX just to see if I could get them to work in FSX in the beginning of September, and they did.
It was at that point they begin to work in P3D, I just fired up FSX and and deactivated Choctaw in the scenery library. It would not work in P3D. Only when I activated Choctaw again in FSX would it work in P3D.

It appears the EXE.XML had nothing to do with it.

Seems vLSO is looking for some very specific locations and files.

Thanks for your information.

Russ

Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

rsgunner

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1047 on: September 22, 2014, 08:30:06 pm »
Ok, is that 'FSX in the P3D folder' trick documented/recommended somewhere?

It has been brought up numerous times especially during some addon installations that don't have a P3D version and hunt for the FSX directory. I just change the registry to point it to the P3D directory that has the FSX. exe in it.

Russ
Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.

Paddles

  • Hero Member
  • *****
  • Posts: 721
  • Lurking around
    • vLSO blog
Re: vLSO Beta release
« Reply #1048 on: September 22, 2014, 08:47:37 pm »
It appears the EXE.XML had nothing to do with it.

Seems vLSO is looking for some very specific locations and files.

Sure, the EXE.XML has nothing to do with sceneries and vLSO looks for the SCENERY.CFG file, then reads it and gets all the necessary information on FCLP locations, if any.
Want it done right? Do it yourself!


rsgunner

  • Newbie
  • *
  • Posts: 48
Re: vLSO Beta release
« Reply #1049 on: September 22, 2014, 09:16:25 pm »
Paddles

If I do a SCENERY.CFG in FSX that is P3D specific it should work?

Making sure it points to the proper directories.

Russ
Many may fly and some are rewarded
handsomely, but the wings of gold of a
United States Naval Aviator mean more
than flying. It is dearly bought, requires
sacrifice to keep and represents a way of life.