Monday, March 5, 2018

vLSO 1.0.4.1 update

Guys,
This update fixes some bugs, found recently:

wrong groove time calculation,
unrealistic carrier detection range (FSX mode)
and a few other improvements and corrections.

Previous release 1.0.4.0 has been withdrawn from downloads

37 comments:

  1. Hi,I´m new with this program,I READ the entire manual but I didn´t find what to do with the vLSO.xml file in my Desktop after my setup (Advanced settings)(I use P3Dv3 and v4.2) Thanks.

    ReplyDelete
  2. vLSO.xml is the program's config file. Users usually have nothing to do with it.
    Why did you install vLSO on desktop? It's better (and more practical) to install it in a separate folder like C:/vLSO

    ReplyDelete
    Replies
    1. Interesting,because I installed in the default c:/vLSO directory and I have the .xml file n the vLSO directory and in desktop, but never mind,I deleted the desktop file and the program is running OK. Thanks for your answer and it's a fantastic program and it deserves a donation.

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

    ReplyDelete
  4. I am constantly receiving waveoff calls even though I have performed a near perfect approach (I have a debriefing photo proving it).I was flying Aerosoft F-14B Extended v3 with vLSO 1.0.4.1 (P3D v4.2). Thanks for any input.

    ReplyDelete
    Replies
    1. It sounds like you have manual ball call setup, so you must activate the ball call or you will always get a waveoff pattern.

      Delete
    2. Bingo! Thanks Scott,that´s exactly the problem.Rgds.

      Delete
  5. Hello Paddles!

    First of all: Congrats on vLSO! -Just awesome to do trap-landings like this! Great work! :)

    A possible bug I found is, when you load Patuxent (KNHK) Rwy32, open RFN-Gauge and tune in to TCN X96 (114.90), a series of small vLSO-windows pop up stating "Invalid floating point operation." -Nevertheless the catapult works normal.

    Carrier-ops seem to work great, but I've done only two traps on the latest vLSO-version (1.0.4.1) by now.

    Tested using Win7(64bit), FSX:SE, Dino Cattaneo's T-45C, RFN-Gauge 4.40 (32bit).

    All the best,
    Stinger

    ReplyDelete
    Replies
    1. Stinger,
      Thanks for the bugreport. This error caused by the RFN catapult and I reported it to Sylvain. Please avoid using Patuxent and Lakehurst sceneries until this bug is fixed.

      Delete
    2. Paddles,

      you're welcome. Thank You very much for the info, and for constantly improving vLSO. It seems to me the latest vLSO-version has become much more diverse in judging the approaches. Awesome!

      Another question: I qualified (in the new vLSO-Version) a month ago. Unfortunately I didn't enter my callsign beforehand. Is there any way to get my callsign into the database after around 50 trap-landings?

      Thank You very much!
      Stinger

      Delete
  6. Hey Paddles, thanks for all the updates!
    I don't know what's going on, but I'm sure it's something I did.
    For some reason vlso won't detect my sdb enterprise, it does detect my sws carriers but it won't give me any calls and won't let me make the ball call. I set the freqs via tacpack and tune them in my radios. I use fsx acc, fsx@war, F-14x v3 and vrs superbug. When I tune them I do get ILS needles and TCN distance.
    Thanks in advance!

    Daniel.

    ReplyDelete
    Replies
    1. Daniel,
      If you use TP to set freqs, don't forget to update frequencies in vLSO - Advanced settings, NAV settings, 'Import TP' button.
      The SWS carriers don't use frequencies whatsoever, that's why they work ok with vLSO (which is aware of that)

      Delete
    2. Paddles,
      I imported all the freqs and still no joy with the enterprise. It's not detected.
      I tested the sws carriers with older versions, 1.0.3 and 1.0.2 and they both give me abeam calls, but waveoffs right before trapping. The newest version doesn't give me any abeam calls, no callouts on approach and can't make a ball call. The carriers get detected ok, same as simconnect and my plane, but it's as if I'm not in the circuit. All calls with older versions are ok, can call the ball and all, but not with the new one.

      Also, I made carrier presets in tacpack for the enterprise and the sws carriers. I think they are quite accurate. In case anyone needs them, I'll be happy to share.

      Regards,
      Daniel.

      Delete
  7. Hello Paddles,
    Found a minor error
    When prompted exit by the program, there is an error in the text. It says "Do you really want to close vSLO”
    Pretty insignificant error I know 😊
    Thank you for everything you do

    ReplyDelete
  8. Hello
    I just begin to use vLSO with P3D V4, however I don´t find any scenery FCLP compatible with vLSO and P3D (Coupeville and others are functionals only for FSX), so I can´t do the Field Practices. Is this right?
    Thank you and best regards
    Pablo

    ReplyDelete
  9. Pablo,
    You can use RFN sceneries for FCLP. These work well with P3D

    ReplyDelete
  10. Hi Paddles,
    Thanks a lot for this idea. RFN gauge installed and now FCLP sceneries are working.
    Thank you!
    Pablo

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

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

    ReplyDelete
  13. Hey dude, thank you for exellent work, some years i use your add-on with FSX and it's still amazing to use it.

    I have a problem with the CDG, after follow the user manual (vLSO, RFN & RFN_CDG) vLSO doesn't find the CDG.

    I can see "R91 Charles de Gaulle Config 1 (and 2) (RFN)" on the "Practice carriers" part, but the indicator on the main page stay grey and don't detect my carrier (Location not selected). The RFN indicator is orange.

    Can you help me please?

    Thank you in advance.

    ReplyDelete
  14. Please make sure your NAV frequency is tuned to the CDG. It's 108.25 or 108.30 as far as I remember.

    ReplyDelete
    Replies
    1. Hey thanks for your quick reply.
      Ok, with my Nav on 108.30 you solve my second problem, it was I didn't have a mirror light on CDG now it's working.
      The RFN indicator on the vLSO main page is now green. But, the location indicator stays gray with "Location not selected" :(

      Did I miss something?

      Thank you again for your help
      (sorry for my bad english, i'm not..)

      Delete
    2. PS, i use the FA/18 E VRS...

      Delete
  15. Oh, I forgot that you use 1.0.4.1, sorry. That version has a bug, preventing proper detection of RFN carriers. I'm in a process of preparing an updated version, free of this bug (an some others). I hope it will be ready in a few days. Sorry for this inconvenience...

    ReplyDelete
    Replies
    1. Please dont be sorry you don't need to do, you make an amazing work since lot of years for free. Thank you very much for your answers, so i'll waiting the release of this uptade. I'll gonna donate on your Paypal coz you deserve.

      Thank you once again dude.

      Delete
  16. Hi all, thanks for your great job Orion! I've a little problem... FSX:SE, AICarriers.NET and USNimitz V2 pack of Javier Fernandez (i mean) correctly installed, but in VLSO, under section Flight Simulator X:Steam Edition, no one carrier to practice... all the carriers are under Flight Simulator X section. I need a help with... Thanks!

    ReplyDelete
    Replies
    1. More: in the Addons bar in fsxse i can correctly see the VLSO and the AIShips options

      Delete
  17. Marco,
    Please run the FSchecker6 program, found on the right panel of this blog, and see what it discovers. I suppose your FSX:SE install somehow mixed with FSX

    ReplyDelete
  18. I tried to uninstall FSX:SE, clean the registry of all the reference to my previous FSX Acceleration version (uninstalled) and FSX:SE and reinstall all again... the result of FSchecker6 is:
    App data path: C:\Users\Marco2\AppData\Roaming

    Local roaming path: C:\Users\Marco2\AppData\Local

    Roaming path: C:\ProgramData

    === Scanning HKCU root... ============================


    Checking FSX...
    ------------------------------------------------------

    Registry key SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 - OK
    AppPath value - C:\Program Files (x86)\Steam\steamapps\common\FSX\
    fsx.exe - OK
    Now trying to read FSX scenery config file C:\ProgramData\Microsoft\FSX\Scenery.cfg...

    OK, 127 scenery definitions read



    Checking FSX:SE...
    ------------------------------------------------------

    Registry key SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 - NOT FOUND



    Checking Prepar3D v.2...
    ------------------------------------------------------

    Registry key SOFTWARE\Lockheed Martin\Prepar3D v2 - OK
    AppPath value - NONE
    Prepar3D.exe - NOT FOUND


    Checking Prepar3D v.3...
    ------------------------------------------------------

    Registry key SOFTWARE\Lockheed Martin\Prepar3D v3 - OK
    AppPath value - NONE
    Prepar3D.exe - NOT FOUND


    Checking Prepar3D v.4...
    ------------------------------------------------------

    Registry key SOFTWARE\Lockheed Martin\Prepar3D v4 - OK
    AppPath value - C:\Program Files\Lockheed Martin\Prepar3D v4\
    Prepar3D.exe - NOT FOUND
    Now trying to read Prepar3D v.4 scenery config file C:\ProgramData\Lockheed Martin\Prepar3D v4\Scenery.cfg...

    OK, 127 scenery definitions read

    Now VLSO recognizes only FSX and Prepar3D (uninstalled), not FSX:SE

    ReplyDelete
  19. Hello i have a new question please,

    Before i used a old (very old) version of vLSO. Now i have intelled a new config (Motherboard, cpu etc.) and i have reinstalled the last version of vLSO. In the old vLSO manual.pdf you describe how to launch with FSX and automaticaly vLSO without make it manualy. But i don't find this in your "new" manual.

    I don't find it on the web too.

    Can you give me the process please?

    Thank you in advance.

    ReplyDelete
  20. The same procedure, no difference.
    I'll add it to the new manual, thanks for the headsup

    ReplyDelete
    Replies
    1. ho thanks! but my problem is, with my new PC i have delete my old vLSO version and i have just the new release. So i have lost the script... Can you copy/past for me please? sorry for disturbing you bro

      Thank you in advance

      Delete
  21. To start vLSO automatically (i.e. synchronously with a flight simulator), first locate relevant EXE.xml file in corresponding folders:

    FSX %APPDATA%\Microsoft\FSX
    Prepar3D %PROGRAMDATA%\Lockheed Martin\Prepar3D vX
    or
    %APPDATA%\Lockheed Martin\Prepar3D vX

    where X is the number of Prepar3D version.

    Edit the EXE.xml with Notepad and make sure it contains these lines:

    < ?xml version="1.0" encoding="Windows-1252"? >
    < SimBase.Document Type="Launch" version="1,0" >
    < Descr>Noname< /Descr>
    < Filename>exe.xml< /Filename>
    < Disabled>False< /Disabled>
    < Launch.Addon>
    < Name>vLSO< /Name>
    < Disabled>False< /Disabled>
    < Path>D:\vLSO\vLSO.exe< /Path>
    < CommandLine>< /CommandLine>
    < /Launch.Addon >
    < /SimBase.Document >

    Remember - in this example the program is located in the D:\vLSO\ folder. Change this path according to your setup!

    ReplyDelete
  22. You are awesome dude! thank you very much!! "Tu déchires" like we say in France ;)

    ReplyDelete
  23. Loaded v1.0.5.5 and I am not getting any LSO callouts or CASE condition announcement after choosing the carrier. This is after I upgraded from v0.9.8.8. Also I noticed there is no .ini created and the .ldf file on 1.0.5.5 had only this line "vLSOé WEASEL _ _ "
    HELP!!!

    ReplyDelete
  24. Wilfred,
    I my December 26 post I wrote:

    'The data structure was changed and new version is not compatible with any of the previous beta versions. This means that you will have to qualify again...

    Also, the vLSO config file format changed from INI to XML, which means that you will have to manually transfer your custom aircraft settings to the new program.'

    That's why there's no INI file and your LDF file is so short (it's actually empty).

    The reason you have no callouts is most likely you didn't assign proper NAV1 frequency. Please read the 'NAV settings' chapter of the manual.

    ReplyDelete