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

Monday, January 16, 2017

Update to 0.9.8.7

Guys,

Here's a new build of vLSO.

Two RFN aircraft added as supported by default.

Some bugs fixed (incorrect add/remove of logbook records). Thanks to Michel and other guys from RFN for reporting this bug!

And, as always, read the manual 😉

Friday, January 13, 2017

Update to 0.9.8.6

Friday 13...

Time for a new build - 0.9.8.6

Two bugfixes:

  • Correct detection of changed CASE conditions during a flying session
  • Correct altitude detection when flying above water bodies (seas, lakes, ponds etc.)
Thanks to Scott Gray and Matt Thiffault for reporting these bugs!

Thursday, January 12, 2017

Update to 0.9.8.5

Guys,

From now on each new vLSO build/release will be distributed as an installer, not as a ZIP file.

No more unzipping, copy and paste... Just run the installer, point it to a folder of your choice and in a few moments a new version will be ready to use. All the necessary files will be right there. You can even install it into an existing folder - all your settings and logbook files will remain intact. Cool, eh?.. 😎

This setup makes no changes to the registry, so to uninstall vLSO just delete its entire folder!

Apart from that, in this version CASE III redundant 'Paddles contact' bug has been fixed.

And don't forget to read the manual...

Happy flying!

Wednesday, January 11, 2017

Update to 0.9.8.4

Guys,

At last I managed to nail a nasty 'Access violation' bug, reported by many Windows 10 users. I initially thought that somethig very Windows 10 specific caused that bug... Well, long story short, it was FSX Steam Edition. 😕

If installed on a computer along with FSX and/or Prepar3D, this version works just fine. But when deployed on a clean machine (no flightsims ever installed), FSX:SE uses registry keys and certain folders and files, specific to FSX. My program mistakenly tried to open FSX:SE config files at non-existent locations, which caused that 'Access violation' error. I don't have the slightest idea why Dovetail guys decided to do that, but their decision definitely added some grey to my hair (and to many other simmers', according to numerous topics on devs forums).

I am grateful to Michel Raemy and Matt Thiffault for their assistance and help in searching and debugging this error.

Also, in this version the 'Use real WOD calls' switch is now functional.

The next version will feature its own installer. No more manual unzipping and copy/pasting! 😎

Tuesday, January 10, 2017

Update to 0.9.8.3

Guys,

Finally I got rid of the CHM help format which brought more pain than gain. Back to good old PDF! :-)
Please bear in mind that the manual is still WIP so feel free to suggest and critisize.

Also, as a minor tweak, an average flight deck outline has been added to the debriefing chart. Average means average, because flight deck heights vary from carrier to carrier.

Saturday, January 7, 2017

Update to 0.9.8.2

Guys,

Just one major bugfix - the callsign didn't save upon changing it. Thanks to Robert "Axe" Timberlake!

And a few minor changes here and there...

Friday, January 6, 2017

Update to 0.9.8.1 [Edit]

Just one major bugfix concerning data sampling routines, thus a new release number 8.

And I'm still not happy with the wind settings... I guess most of pilots would prefer the FSX standard Wind speed slider. Any suggestions?

I found that most suitable WOD values for the Wind speed slider values would be:

  8: 20..22
16: 24..32
24: 34..40

These values are implemented in the 0.9.8.1 version 

The program will prompt you the Wind speed value if it doesn't match the required WOD conditions.

Thursday, January 5, 2017

Update to 0.9.7.2

Guys,

Michel reported a bug found during his tests of the practice carrier option - if the WOD value was less than the natural wind speed, it caused 'Range check error'.

Apart from the natural wind limits of 8..24 knots, mentioned in the manual, you should take into account this simple formula:

(WOD / 2) < Natural wind < (WOD / 1.5)

For example, for the desired WOD of 22 knots natural wind must be set from 11 to 15 knots. The program now checks these limits and will infrom you if natural wind doesn't meet these requirements.

You might have noticed that the Wind speed slider allows only 4 settings for the speed - 8, 16, 24 and 32 knots. So, using this slider it is impossible to set required natural wind.

It's ok! Open the Advanced weather settings, then on the Wind tab set the exact wind speed, i.e. from 11 to 15 knots in our example.