Thursday, January 19, 2017

Update to 0.9.8.8

Ok guys,

Another update is ready:

  • Added support for SimObjects folders, placed outside of the main FSX folder (not tested in Prepar3d, though)
  • Corrected conditions for CASE III miles callouts
  • Corrected conditions for CASE I LSO calls

34 comments:

  1. Hi, I installed the new version, and it doesn't work with the aerosoft F-14 and the Kitty Hawk in P3D. It says VLSO disabled, your aircraft doesn't have FLOLS installed.

    ReplyDelete
  2. It only seems to work when I load vlso after loading the flight in P3D.

    ReplyDelete
  3. Also, I cannot get OK-s because all my traps are "NESA". otherwise perfect. I fly more than 1 mile ahead of the carrier before the break, am 1.2 NM abeam, and start my final turn way after real pilots do, sometimes 1.2-1.3 NM abeam. What else can I do?

    ReplyDelete
  4. All this happens with the Kitty Hawk? In this new 0.9 version the work with it's custom FLOLS still needs to be revised.

    ReplyDelete
    Replies
    1. Yes, Aerosoft F-14X + Kitty Hawk in P3D

      Delete
  5. I am getting a "Range Check error" on startup. Then when trying to shut it down to try again, I receive "Address access violation error in module vLSO.exe"...

    ReplyDelete
  6. Jason,
    Please try removing the vLSO_log.txt file, located in the vLSO folder.

    ReplyDelete
  7. Once I remove it, I restart getting the same error. It creates another log.txt file, but it is blank.

    ReplyDelete
  8. Not sure, but I recall a similar error when there was a blank or missing logbook.

    ReplyDelete
  9. I have replaced all of the logbook files with "spares" from another vUSN aviator, and still get the same errors. The question has been raised as to whether it has anything to do with my "older" version of TP and the Bug... any ideas there?

    ReplyDelete
  10. Jason,
    To make sure there's something 'wrong' with your PC you could send your logbook to your friend(s) and see if it opens Ok.

    By the way, does your logbook open with previous 0.8.* vLSO versions?

    ReplyDelete
  11. PROBLEM SOLVED (for now...) It looks like it may have been the order in which I was booting up the system. I was attempting to get vLSO started first and kept getting the errors. It never dawned on me until this morning to start the sim first, spawn a carrier, and then boot vLSO. No issues hopefully going forward...

    ReplyDelete
  12. Replies
    1. I'm currently having the same issue as Jason running FSX, on windows 10 if that's any help.

      Delete
  13. just downloaded I have the missing flols gauge error on the aerosoft cat as well. and if Ignore it and try flying the circuit anyway I only ever get wave off. not sure if thats because I skipped quals or not? also the kittyhawk does not appear in the carrier list on the program. do I have to have aicarriers installed for it to show up? didnt really see anything in manual but location dot is grey. (P3D)

    ReplyDelete
  14. Robert,
    Thank you for reporting this CV63 waveoff glitch - in case of missing gauge the program shouldn't react at all. And it has nothing to do with quals whatsoever.
    Also, the Kitty Hawk is not in the practice carriers list yet (do you mean that list, right?)

    ReplyDelete
    Replies
    1. yeah that list. good to know thanks. when I saw it was compatible I thought it was supposed to show up so my bad. for reference the error saying I dont have the gauge seems to show up by random chance. restarting P3d got rid of it. but still comes up sometimes.

      when it is working after a few passes the board seems to stop logging? like it pops up in the bar at top of the sim but log doesnt get updated

      new issue though... downloaded the Choctaw scenery but iflols doesnt appear to work for me. I can see the rig and theres the other light for the wire that seems to work some of the time. but no meatball.

      Delete
  15. Hi. Is there any chance for new updates to lock the carrier track when the aircraft is near to the carrier? (customizable distance, i.e. 5Nm, 10 NM, etc) It is very difficult to start approaches when the carrier is performing a turn. It would be a very interesting idea. Thank you.

    ReplyDelete
  16. I have P3D HF3, Aicarriers, F14X and using Javiers Nimitz. When I first start up everything is fine. I got Lso call outs and my traps recorded. but when ,lets say I goto in P3D settings. vLso still runs but no callouts and doesnt record my traps. is this a bug?

    ReplyDelete
  17. Same as Mike, anonymous and Brennan.
    When this occurs, I stop and relaunch vLSO. Then the landing officer is operational and vLSO record the flight.

    ReplyDelete
  18. Hey Paddles, Saw this on FB....You gearing up for this?

    http://www.fresnobee.com/news/local/news-columns-blogs/lewis-griswold/article143473959.html

    RADM R. Axe Timberlake
    DCNO, vUSN
    www.vusn.org

    ReplyDelete
  19. The Magic Carpet would be a nice addition. But if it's there, LSOs can retire... )))

    ReplyDelete
    Replies
    1. I hear you. Still like the human element on the other end of the procedure. So if this gets modeled in the VRS superbug and tacpack, would you modify the vLSO to still grade the landings?

      Delete
    2. I hope I would be able to do this, but that really depends on the actual Magic Carpet implementation

      Delete
    3. Hey Paddles, Thanks for the discussion on magic carpet. I have another issue. I am using uchi's kntu scenery in P3d v3 and I put the Mk14 file of yours in as directed on the install txt. It works perfect in FSX however, everyplace I have FCLP (ie Fentress, Choctaw, Meridian, Lemoore...etc) I can not see the IFOLS lights. When the sim first loads up it shows them. flashing...then I take off and the lights go dark and don't light up. I realize that most of the ifols were designed for FSX, however, is there a fix for P3d v3. Which also baits the question, are you going to update everything to v4?

      Delete
  20. Been using vLSO for over a year and recently upgraded to 0988 and I must have done something wrong on the install as vLSO remains open even after I exit FSX. Here is how my exe.xml file on FSX looks like:


    Launch
    exe.xml
    False
    False

    Saitek Panel(s) Plugin for FSX
    False
    C:\Program Files (x86)\Saitek\ProFlight FSX Plugin\SaiFlightSimX.exe
    -run


    False
    False
    AICarriers
    C:\Program Files (x86)\AICarriers\aicarriers.exe
    -nogui


    vLSO
    False
    C:\vLSO\vLSO.exe




    Any thoughts?

    fuzevt@gmail.com
    "weasel"

    ReplyDelete
  21. Please make sure the 'Auto close' slider is On (the Controls panel on the main window).

    ReplyDelete
    Replies
    1. Simple enough, appreciate that quick reply....on another note I'm a long time user of the previous version and for some reason this beta 9.8.8 is hit or miss whe reporting landing results. Sometimes it does and some it does not ....

      Delete
  22. Just downloaded this, and I'm finding that no matter how I load it (before or after sim with carrier placed) I'm getting the "Range" error, same as Jason from above. Running FSX Steam, windows 8.1, F-18E from VRS. Tried deleting the log file, have tried everything short of deleting it. Any ideas? Thanks in advance.

    ReplyDelete
  23. Hello,
    I recieved an error 14001 when installing vlso and now get the "failed to start because of side-by-side config is incorrect..." When trying to open vlso.exe. this in in P3D v3.4. Any thoughts???

    ReplyDelete
  24. This is an excerpt from an old user manual (CHM format):

    When trying to connect to Prepar3D, the program might not find SimConnect of the same version as vLSO uses. To install it, go to the [P3D Install Location]\redist\Interface\FSX-SP1\retail\lib\ folder and run the SimConnect.msi installer found there.
    If it doesn't help, try to run the SimConnect.msi installer from the [P3D Install Location]\redist\Interface\FSX-SP2-XPACK\retail\lib\ folder.

    Hope this helps

    ReplyDelete
  25. Thank you for the quick reply and suggestion. Running simconnect.msi totally fixed the problem! I've been using vLso for a long time and really love the program so thank you very much for creating it and providing kick ass support!

    ReplyDelete