Thursday, December 28, 2017

vLSO v.1.0.0.1

Guys,
This version fixes some bugs reported during first flights with the new release.

  • 'Add-ons' menu inconsistencies (spawn/remove practice carrier). Fixed
  • Triggering the ball call (UAC) without a carrier caused 'Access violation' error. Fixed
  • Customized NAV1 settings not saved. Fixed 
  • Wire caught not registered for SWS carriers. Fixed  
  • The SDB CVN-65 not properly detected. Partially fixed
The SDB CVN-65 comes in two versions - with default FSX FLOLS (4.12 degrees) and custom FLOLS, controlled by the RFN gauge. The program properly detects both variations, provided NAV1 is properly assigned and tuned to (NAV2 might be used in case of custom FLOLS). The last version of the RFN gauge works seamlessly with the carrier and the only problem yet to be solved is the glideslope differences in FSX and RFN modes, which causes some inconsistencies in monitoring and grading of an approach.

This version is an executable replacement, no need to install anything. Just download it and replace the existing vLSO.exe.

Good luck!

PS. Couple of small bugs were fixed today (28 December), so in case of 'Access violation' please re-download the 1.0.0.1 version.

28 comments:

  1. Hello,
    The link to download the vLSO 1.0.0.1 bugfix refer to the 0.9.9.3 version.
    Cordially

    ReplyDelete
  2. Corrected. Thank you for the heads-up!

    ReplyDelete
  3. Thank you.
    But it does not work.
    I obtain an error :
    Access violation at address 0067C643 in module vLSO.exe
    Read of address 00000002.

    The version 1.0 was OK in the same conditions.

    ReplyDelete
  4. I use P3D v3.4 for the test.

    ReplyDelete
  5. Fixed. Please re-download the program

    ReplyDelete
  6. Thanks, Now it work fine (FCLP test)

    ReplyDelete
  7. Thank you for this great job Paddles, just one quicky: I tried it on P3D V4.1 with AI Carriers.net and Rikooo AC but I have no sound and no trap recording, not sure what os wrong with the install.

    Ben

    ReplyDelete
  8. Hey I use p3d v4 with sws midway carrier and this works great. With RFN gauge team sdb and javier I never geat a location in vlso. So this is normal because RFN is 32bit and p3d4 64bit? Thx for the help chris

    ReplyDelete
  9. Chris,
    As far as I know, the RFN gauge is 32bit, thus is not compatible with P3D v4.
    But the SDB Enterprise should work in standard configuration (w/o custom FLOLS). And Javier's Nimitz as well.

    ReplyDelete
  10. Hey Paddles, thanks for this new vLSO! I have same the problem, I never get green light on location. I use p3d v4.1, and Javier's carriers spawned either with AI Carriers or through VRS. No location is detected. It green lights the sim, and aircraft fine though. Also, I'm not exactly sure about the RFN, and SWS functions, and don't have them, as they are red lights. Do this matter?? Thanks again!

    ReplyDelete
  11. Forgot to sign my above post, I'm Jeff.
    Thanks.

    ReplyDelete
  12. Guys,
    Most likely, the reason vLSO doesn't detect your carriers is that you have not tuned NAV1 to Javier's Nimitz (which is 112.00 by default). This new version uses NAV1 to detect carriers. Open the 'Advanced settings/NAV1' and assign/change frequencies to your carriers, as required.

    ReplyDelete
  13. Ah, ok! Simple enough, will try it.
    Thanks!
    Jeff

    ReplyDelete
  14. Hi Paddles,
    Have been testing and re-qualifying cases I and III. It works great with spawning an AC from joystick, thank you. It looks though that you don't have the option anymore in the addon menu to chose between carriers when you have several around? Unless I am missing something.
    Thanks a lot,

    Johan

    ReplyDelete
  15. Yep, you have to use NAV1 to choose between carriers (and FCLP fields) instead of add-ons menu items. See my post above.

    ReplyDelete
  16. Paddles , thank you , using the updated exe, SDB carrier 80's works OK at 110.50 but I don't get the loc and the gs lines or the arrow..any clues?? This is V4.1 no RFN or SWS)
    Jorge

    ReplyDelete
  17. Thanks Paddles. I also have the Aerosoft CV63 USS Kitty Hawk (provided with the F14) but it doesn't show up in my list of "Available Carriers"...anything special about this one?
    Thank you,

    Johan

    ReplyDelete
  18. Hey Paddles and others , I just realize that the GS/Loc function comes from the HUD in the AC , so I edited the .xml gauge for the T45 to include the CVN-65 and now OK..
    Jorge

    ReplyDelete
  19. Hi Paddles,
    thanks, great update for p3dv4! had problem figuring out getting the location fixed but as mentioned above, 1) tune a/c to carrier tacan 2) vlso nav setting to same tacan freq. works like a charm.

    ReplyDelete
  20. Hi, Aerosoft USS Kitty Hawk not working. Thank you.

    ReplyDelete
  21. Does anyone know how to get the MK14 IFLOLS trailers to work in P3Dv4? The lights seem glitchy

    ReplyDelete
  22. Guys,
    The Kitty Hawk is on my 'to do' list.
    As for the Mk14 in P3Dv4, they don't work as intended, because of old FS2002 technology.

    ReplyDelete
    Replies
    1. Gotcha. Any chance they’ll be updated? Definitely useful for real T45 training!

      Delete
  23. I have looked for a place where the RFN Gauge and it's status is discussed to see if there are any plans to update it for 64 bit. Does anyone have any info on this?

    Thanks
    Terry

    ReplyDelete
  24. Is there a place to make donations for VLSO?

    ReplyDelete
  25. Hi Paddles,
    A little bit of a conflict with Jimi's FSXBA as you mentioned there:
    http://www.fsdreamteam.com/forum/index.php/topic,6944.msg77365/topicseen.html#msg77365
    The TOGGLE_WATER_RUDDER assignment automatically triggers the ejection - not good.
    And for some reason, I cannot assign any other simulator event for spawning a practice carrier in that menu.
    Works fine with other aircrafts, so no big deal.
    Johan

    ReplyDelete
  26. Did you try assigning a joystick button for this purpose, by the way?
    You have now three options - an addons menu, a sim event and a stick button.

    ReplyDelete
    Replies
    1. Assigning directly a joystick button won't work for me because my Thrustmaster WH is driven through FSUICP, not directly engaged through FSX. However, I was able to assign STROBES_TOGGLE to a joystick button and now it works, I can spawn an AC with it. I am still exploring some little inconsistencies of this release. For example (and I can't attach a picture here but will send through email), after I spawn an AC under my plane and request the bearing through vLSO controls, it tells me the AC is 6893.6 NM away...

      Johan

      Delete