Tuesday, December 23, 2014

vLSO 0.8.2.0 is ready

Ok, guys,
Here's a Christmas gift for you - the 0.8.2.0 beta. Hope you will thoroughly enjoy it.
What's new?
  • Prepar3D support (v1 and v2)
  • CV63 Kitty Hawk (Aerosoft) support
  • A history window of LSO text messages
  • New aicraft types supported by default
  • The AUTO and LOG options moved from the .ini file  to the settings window
  • CASE3 'BRC' calls replaced with 'Expected final bearing' calls
  • A window for manual ball calls is extended up to 0.5 NM
  • Eased IW waveoff restrictions
  • A number of other minor tweaks and fixes
This version is backward compatible with previous 0.8 and 0.7 versions and vLSO 0.8.2 can read logbooks written with previous versions, but not the opposite.

Also, please first read the manual (p.6) on possible SimConnect issues with Prepar3D installs.

Merry Christmas and Happy New Year to all of you and your families!

WARNING! 
There was a bug crawled into the final release, which garbled LSO comments to something unreadable and caused range errors when trying to debrief them.
Please re-download the 0.8.2 beta now free of this bug.
You can e-mail me your garbled logbook and I will convert it back to a readable form. My apologies for this inconvenience...

Monday, December 22, 2014

vLSO integration pack for FSX NAS Lemoore

I'm happy to share my vLSO integration pack for uchi's NAS Lemoore scenery.

Please download the pack from the sidebar and read the included readme file prior to unzipping.
Be advised that the KNLC_SceneryConfigurator.exe utility, bundled with the Lemoore scenery, does not add or remove Mk14 trailers. This is done by the two .cmd files included in my pack.

Happy bouncing!

Friday, December 19, 2014

Some thoughts...

Guys,
As you know, in FSX we have a number of similar aircraft created by different authors. Example: the Acceleration F/A-18A and the FSXBA F/A-18C. Another example: the Aerosoft F14A/B and Dino's F14D... Despite these are different aircraft they all have the same FSX designation (namely the atc_model parameter). By the way, vLSO relies on that atc_model parameter, so in logbooks you can see both Hornets as F18, and all three Tomcats as F14. The only good exception to this 'rule' is the VRS F/A-18E Super Hornet, whose atc_model is F18E.

What to do? How to tell one model from another? Well, my suggestion is to manually modify the atc_model parameter as follows:

F18C = FSXBA F/A-18C
F14A = Aerosoft F14A
F14B = Aerosoft F14B
F14D = Dino's F14D

I'm going to integrate these models into the upcoming 0.8.2 beta and all you'll have to do is to edit the above mentioned parameters. It's easy - open the relevant aircraft.cfg file in an editor (e.g.Notepad), find the [General] section, edit the atc_model parameter and save the file.

Of course, the old F18 and F14 parameters will remain as default, too.

Wednesday, December 3, 2014

FSX Oceana FCLP add-on now vLSO compatible

I'm happy to share my vLSO integration pack for uchi's NAS Oceana scenery.

Please download the pack from the sidebar and read the included readme file prior to unzipping.

Happy bouncing!