Sunday, January 28, 2018

vLSO 1.0.2

Guys,

This is another version with some bugfixes, updates and improvements.

One of the funny bugs worth mentioning was the Aerosoft F-14B Extended v3, named as follows:

[General]
atc_type=Grumman
atc_model=.NoMirrorF14
performance=
category=airplane

So, in order to recognize this aircraft you have to open its Aircraft.cfg and change the atc_model to 'F14'. 😉

My big thanks go to Michel (as always), Scott Gray and Scita Borea, without whose help this version would not have been realized.

This version upgrades the logbook format, so I suggest to install this version into a new folder and copy your logbook into it, so the program will automatically update the logbook. Be warned that this 1.0.2 logbook can not be read by previous 1.0.1.* versions!

13 comments:

  1. changing the ATC model to F14 removes the aircraft from the select vehicle list.

    ReplyDelete
  2. Do you mean in the Scenario page of FSX/P3D where you change the vehicle? Did you change/replace atc_model=.NoMirrorF14 with atc_model=F14?

    It should read:
    [General]
    atc_type=Grumman
    atc_model=F14
    performance=
    category=airplane

    I have this set in mine and am able to select it in P3D v4 and vLSO recognizes it.

    ReplyDelete
  3. Ive Attempted to use this version on both P3D v4.1 and FSX:SE and both of them have an issue where it doesnt recognize any carrier. The bottom indicator always says "Location not selected", even if I spawn in the practice carrier from vLSO (Which does appears in-game when clicked).
    Ive tried rectifying this issue from multiple different troubleshoot approaches:
    - Re-installed vLSO v1.0.2.0; no resolve
    - Re-installed .NET version of AI Carriers 2 for both P3D v4.1 and FSX-SE; no reslove
    - uninstalled .NET version on FSX:SE, and installed original Java version; no resolve

    Im not quite sure whats causing this. Simconnect and Flight sim indicator both read correctly corresponding to what platform im on (FSX/P3D).
    Would anyone know why this is possibly happening? I figured that maybe I have to select the correct location because it says (location not selected), and based on my knowledge of previous versions of this addon, it would be in the in-game drop down, assuming that another carrier is conflicting with the one I spawned, if it were within 50nm. But I see no such option.. strange.
    If anyone knows what is happening, feel free to reply :)

    Thanks for this addon Paddles, Ive started loggin my passes on Google Spreadsheets https://docs.google.com/spreadsheets/d/1URV2JcpX2kYCm6TDJ_8ZFI7Af1TqkVdoMmjiNv8mqDk/edit?usp=sharing

    ReplyDelete
  4. It sounds like you haven't setup the NAV tab in vLSO to match the freq of the carrier you are placing. I would suggest you place the carrier with the Menu - VRS AI - Carrier to test it. Then you can move on to placing it using other tools. Our group has it working without issues in FSX, P3Dv3 and P3Dv4.

    ReplyDelete
  5. Hey Scott thanks for the reply. Although I do not have TacPack enabled on my computer, it did end up having to do with my Nav radio not corresponding to the NAV settings screen on vLSO. It seems like its running fine now, thanks!

    ReplyDelete
  6. Hi, after I catching wire, my measure time is still running. That´s why I have more than 25 seconds LIG and "just" (OK) grade. Time will stopped after I pull tailhook up

    ReplyDelete
  7. Hi Paddles

    I have been using vLSO for years and love it, my question is how to set up the T-28C from Ant's Airplane work properly with vLSO? I've at the NATOPS and found the abeam setting, but need the AOA settings would be helpful. And thank you for this wonderful product.

    ReplyDelete
  8. Hi Tony

    Incidentally, exactly 4 years ago I had been asking the same question to the T-28's author, Anthony Lynch ))) Here's what he answered: 'The approach light is not dependent on AOA but uses fresnel ramps to switch between green, red and yellow'. I guess you can try some averaged AoA values of, say, 6 and 9 for 'fast' and 'slow' respectively

    ReplyDelete
  9. Hi Paddles, as 425 already noticed, I believe there something wrong in groove timing logic. I can't get below 22/23 seconds, but this might be due to my flying technique (with v1.0.2 I had to modify some parameters in order to avoid early waveoff calls). However, I have three records in my log with a groove time of 49, 62 and 42 seconds which seem pretty weird, considering that those passes were flown in an F-18. Moreover the abeam call is missing now and then. I'd really appreciate if you could look at these.

    ReplyDelete
  10. garep17,
    Thanks for reporting these bugs! I'll definitely look into the problem

    ReplyDelete
  11. Hey Paddles, Got another one. vLSO starts with a splash scree, then says, "Duplicates not allowed, then proceeds to stay on splash screen until i force end it. I was editing a custom aircraft into the program, but couldnt get it to connect. I cant get you a log file as i cant open vLSO now.

    ReplyDelete
  12. Thanks for the bugreport! This error was caused by duplicated custom aircraft 'ATC model' parameters. Please download and install v.1.0.3.

    ReplyDelete