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!

Monday, October 6, 2014

Prepar3D and FSX registry issues

Guys,
These days I've been working on a very strange problem (please first read its not lenghty discussion on FSDT forum to get into details). To help solve this problem I'd like to get more information from a wider simmers community, especially from those of you who have both sims installed.

Please download the FSchecker 3 program from the sidebar, run and see what it finds. If its output matches to what you have then it's ok. If not, please report what it finds and what you have in fact (screenshots of the relevant registry keys would be just fine).

Thanks in advance!

Wednesday, September 17, 2014

Couple of words about FCLP packs

As an example, I'll list my KNMM_Mk14 pack files and explain how it all works. There are seven files and one folder in the KNMM_Mk14.zip:
KNMM_Mk14\IFLOLS_Mk14.dds
KNMM_Mk14\KNMM_FCLP.tag
KNMM_Mk14\KNMM_Mk14_01L.bgl
KNMM_Mk14\KNMM_Mk14_19L.bgl
KNMM_Mk14\KNMM_Mk14_28.bgl

KNMM_Mk14_Add.cmd
KNMM_Mk14_Remove.cmd


Unzip the pack to your KNMM folder. You should now have there the KNMM_Mk14 folder with five files inside it and two .cmd files. These command files are there to help you manage vLSO compatible stuff.

The KNMM_Mk14_Add.cmd copies files from the KNMM_Mk14 folder to their destinations as follows:
to the KNMM scenery folder
KNMM_FCLP.tag
KNMM_Mk14_01L.bgl
KNMM_Mk14_19L.bgl
KNMM_Mk14_28.bgl


to the KNMM texture folder
IFLOLS_Mk14.dds

From now on your KNMM scenery becomes vLSO compatible - there are three Mk14 IFLOLS at runways 01L, 19L and 28, and you can choose either of them via vLSO add-on menu (provided you are within a 6 nm range from NAS Meridian).

The KNMM_Mk14_Remove.cmd reverts i.e. removes the above mentioned files.

The key part of any of my FCLP packs are .tag files. vLSO reads a .tag file to find all the necessary info on a given FCLP site (the number of Mk14s, their locations, their glideslope settings etc.)

It should be noted that during its startup the program browses scenery folders of all active sceneries and tries to read any .tag file found there. This means that if a .tag file has the wrong format (it was created by another application, for example, or somehow corrupted) then most likely there will be errors when loading that file. My sceneries' .tag files follow this simple naming format: [ICAO]_FCLP.tag, where ICAO is the ICAO code for a given airfield. For example, KNMM_FCLP.tag for NAS Meridian, KNFJ_FCLP.tag for NOLF Choctaw, KNFE_FCLP.tag for NALF Fentress etc.
Please make sure all .tag files in all your active sceneries meet this format at least.

Wednesday, September 10, 2014

FSX Meridian FCLP add-on now vLSO compatible

Ok, guys
At last uchi's FCLP add-on to FSX NAS Meridian now gets its Mk14 IFLOLS and becomes vLSO compatible.

First, visit uchi's page and follow his instructions on downloading and installing the mod.
Then download my small pack from the sidebar and unzip it to the scenery folder. For your convenience I've created two command files to add and remove the IFLOLS. Just double-click the KNMM_Mk14_Add.cmd and go bouncing!
When you decide to get rid of the Mk14 IFLOLS, double-click the KNMM_Mk14_Remove.cmd...

Monday, September 1, 2014

vLSO 0.8.1.2 is ready

Ok guys,
This time nothing special, just some small cosmetic changes and a 'Range check error' correction. People would experience this error only when approaching a FCLP area with a carrier (or two) present within a 50nm range.

Happy bouncing!

Tuesday, August 26, 2014

vLSO 0.8.1.1 is ready

Ok guys,
This time just a few new features:

  • The S-3B by Dino Cattaneo is now supported by default
  • LSO radio channel
  • Even more randomized LSO calls
  • An add-on menu option to repeat last LSO text message