Tuesday, January 9, 2018

vLSO 1.0.1

Guys,

This is a new version of this program with numerous changes and bugfixes:
  • CV63 not detected. Fixed
  • Abeam calls absent. Fixed
  • Wrong waveoffs, bolters etc. Fixed
  • Wrong WOD calculation for practice carriers. Fixed
  • Added support for SimObjects installed outside the Prepar3D root folder
  • Added RFN and SWS practice carriers
  • The SDB CVN-65 is now supported both in FSX and RFN modes
  • some cosmetic changes...
My special thanks to Michel Panattoni for his assistance and suggestions.

31 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. Hi Paddles,
    I have downloaded and installed this version and I got a cascade of ''Access violation'' errors as soon as I launched the application with the sim (P3D v2.5). I can close all the error tabs and run vLSO flawlessly but it is a bit annoying. I hope you can fix it as already done before. Great job anyway!

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete
  4. garep17,
    These errors usually occur because of wrong logbook file format (older version). Try running the program from scratch, i.e. rename/remove the existing logbook.

    ReplyDelete
    Replies
    1. I tried to delete logbook.ldf and rerun vLSO but still no joy.

      Delete
    2. That's interesting... Could you first enable 'Log events' on the Controls tab and then restart the program with a command line switch 'verbose'? Like this :

      vLSO verbose

      This will produce the vLSO_log.txt file with lots of technical info. Please email me this file to fsxnavypilot at gmail dot com

      Delete
    3. I found out that the 'Access violation' errors pop up only if vLSO is launched through the exe.xml file. If I run it manually or via command prompt, as you asked me, everything is fine and the generated log is very short and does not report anything strange, I think there's no point in sending it to you. Let me know if you need more info.

      Delete
    4. What windows and sim version do you have? On what drive and in what folder is the sim installed?

      Delete
    5. I had this error and discovered that it was a problem of simconnect.
      The access violation has been corrected by going to "Prepar3D v4 \ redist \ Interface \ FSX-SP-XPACK \ retail \ lib" and launching SimConnect.msi.

      Delete
    6. - Windows 10 Home 64-bit, version 1709
      - Prepar3d Academic v2.5.12946.0
      - C:\Program Files (x86)\Lockheed Martin\Prepar3D v2

      Delete
    7. By the way, the proposed solution of launching SimConnect.msi do not fix the issue.

      Delete
    8. I thought that it was a W10-related problem. I'm curious, what if you turn UAC to none and try running vLSO via the EXE.XML? And in what folder did you place your copy of vLSO, by the way?

      Delete
    9. C:\vLSO\vLSO.exe
      After disabling UAC problem persists.

      Delete
  5. Hi Paddles,
    The RFN carriers CDG, Foch and Clemenceau are not presents in the "practice carrier" of the P3D v4 simu. Normal ?

    ReplyDelete
    Replies
    1. The 'practice carriers ' contains only carriers that a) suitable for practice and b) currently present in a simulator. Do you have the RFN carriers in your P3Dv4?..

      Delete
  6. Yes, I have de "VEH_Charles de Gaulle" and "VEH_Foch-Clemenceau" in the P3D v4.1 SimObjects\Boats library

    ReplyDelete
    Replies
    1. The problem is that there is no RFN gauge (which is 32 bit) for P3D v4 (which is 64 bit). The three carriers are RFN and they FLOLS won't work without the RFN gauge, that's why vLSO couldn't put them on the practice list. We all are waiting the 64 bit RFN gauge...

      Delete
  7. Thank you Paddles. I know for the rfn gauge in 32 bits. I thought it was not related to that.

    ReplyDelete
  8. Hi Paddles, thank you for your awesome work.
    I have this error messenge ever time I try using the new version [Access violation at address 006F2AF in module 'vLSO.exe'. Read of addresse 00000070]
    I am using FSX: acceleration on windows 8.1 64bits

    ReplyDelete
  9. Does this error occur only if vLSO is launched prior to flightsim?

    ReplyDelete
    Replies
    1. Yes, prior and during FSX launching. But when launched afterward, vLSO seems not to work.
      In vLSO ; Simconnect is green, Flightsim is green, Aircraft show the selected aircraft, Location is grey (even when on a carrier or FCLP area)
      In FSX ; vLSO is displayed in the “Add-on” bar with none of the different options working (except for “repeat LSO message, which is always empty)

      Delete
    2. It doesn’t detect any supported aircrafts nor Carriers/FCLP areas

      Delete
    3. There is a bug in my code, causing that AV error when launched prior flightsim. Will be fixed in the next build.

      As for 'not detecting' caariers - most likely you have not tuned NAV1 to a proper frequency, as described in the manual.

      Delete
  10. Does Vlso work across JoinFS.....ie. We get a green light for the CV/ position but the TACAN and or the ILS will not pick up. This results in not getting the calls from the Air Boss. Your thoughts on a solation.

    BT
    Thanks for the Awesome job with Vlso.
    /r
    WN

    ReplyDelete
  11. Thank You Paddles for all the hard work you put into vLSO. You really make carrier aviation enjoyable. I'm hooked! Hard to land without your program now. Are you activating PayPal for donations again?

    ReplyDelete
  12. Paddles I tried twice to donate using the PayPal button. I don’t think but not sure it worked. You might want to check the link.
    Terry

    ReplyDelete
  13. Aerosoft released their updated F-14 with support for P3D4. With P3D4 running, my vLSO is not seeing the CV-63 Kittyhawk (in the settings page under practice carriers and in the nav settings). I do have the drop down box set to Lockheed Martin Prepar3D v.4. It is seeing the F-14, though the airplane has a red dot next to it in the status on the bottom.

    Thank you for all of your work on this, I have been enjoying it immensely for years!

    ReplyDelete
    Replies
    1. I used the Aerosoft default installation path to point to \Users\name\Documents\Prepar3D v4 Add-ons. I hope that helps!

      Delete
  14. Scitaborea,
    The red indicator is for the RFN gauge, not for the aircraft (which could be grey or green only).
    When spawning the CV63, is there a text message, saying that FLOLS gauge not installed?
    Also, could you send me your Simobjects.cfg file, found at C:\ProgramData\Lockheed Martin\Prepar3D v4?

    Thanks for the info!

    ReplyDelete
    Replies
    1. Thanks! I emailed you the file and some pictures showing what I'm seeing.

      Delete
    2. Hi Paddles, thank you for the wonderful piece of add-on. Really increased immersion for carrier operations. I'm seeing the same situation with Nimitz. Any suggestion? It also displays something like "This aircraft is not supported by vLSO." in P3D4. Thanks.

      Delete