AFLT Version 1.1.03 Released

Status
Not open for further replies.

gadgets

Resource contributor
#1
I have just posted Version 1.0.02 to my website http://stuff4fs.com. The update should be automatically detected the next time you start AFLT. If not, download directly.

Several weeks ago, I reported that AFLT generated inconsistent results at headings very close to cardinal directions. At the time, I assumed it was an internal Flightsim issue. I ran into that problem again today while working on one of my own airports which had a runway at 090.17 degrees. Turned out to be an issue with how I was calculating SEPARATION_PLANE parameters. Version 1.0.02 fixes it.

As well, version 1.0.02 increases the number of strobes to 32 (strobes must belong to a set 8, 16 or 32).

Enjoy,
Don
 

gadgets

Resource contributor
#2
I have just posted Version 1.0.03 to my website http://stuff4fs.com. The update should be automatically detected the next time you start AFLT. If not, download directly.

It adds the ability to name your library files as you wish and fixes an unhandled exception that occurred should you attempt to generate a library before selecting the destination scenery folder.

EDIT Please note, I will be away from my development system until May 1. However, I will be monitoring the forums periodically and will endeavor to respond to queries.

Don
 
Last edited:

gadgets

Resource contributor
#3
I have just posted Version 1.0.04 to my website http://stuff4fs.com. The update should be automatically detected the next time you start AFLT. If not, download directly.

I recently discovered that beacons were "broken" in Version 1.0.03. This release fixes that. As well, guid-used lists are now generated when a site-library is shut-down to ensure the lists reflect the actual guids used in the individual libraries.

Enjoy,
Don
 

gadgets

Resource contributor
#4
I have just uploaded AFLT version 1.1.00 to my website http://stuff4fs.com. The update should be automatically detected the next time you start AFLT. If not, download directly.

This update contains several significant changes/improvements:
  1. Lockheed Martin recently announced it will not support legacy technologies in it's next release of P3D. The current release (P3Dv2) does not support BGL_LIGHTs either, so AFLT custom lights cannot be used with P3Dv2. Consequently, I have removed all the P3Dv2 specific code from AFLT and the related controls from the dialogs. At such time as LM announces how it will replace this legacy technology, I'll take another look at making AFLT compatible.
  2. While "chasing" what turned out to be a non-problem, I discovered that the current version of AFLT would only generate "all-in-one" configurations for simple, omni-directional lights. Then, having "removed P3Dv2 from the equation", I realized that the two-file approach (i.e., a base in one file to which was attached a light in another) was no longer necessary expect where FSX base models were used - which should be an infrequent necessity. So, I added an "All-in-One Override" checkbox to the Make Library dialog. When this box is checked, AFLT will generate "all-in-one" configuration for all FS9-based lights - which are much more FPS-efficient. No other changes by you are necessary; just recompile your libraries with this control checked.
  3. And finally, viewing AFLT-generated wig-wags at my own airports, I was very disappointed in the visibility of their flashing lights. So, I've added code to AFLT to make the light lenses on wigwags alternately brighten and dim - a substantial improvement - a capability much simpler in concept than the code required to accomplish it.
Enjoy,
Don
 

gadgets

Resource contributor
#5
When I introduced the "all-in-one" override feature in the latest general release, I neglected to delete the old, unused "bases" files (if they exist) from the \scenery folder into which the new files are saved. Development release 1.1.00(a) , available from http://stuff4fs.com, fixes this.

The is no need to download this development release unless you are using the "all-in-one" override feature.

Don
 

gadgets

Resource contributor
#6
I have just posted Development Release 1.1.00(b) to http://stuff4fs.com. It adds support for Windows versions that use comma (,) as decimal separator. (Prior to a problem report earlier this week, I hadn't realized that any special support was needed).

Once this new development version has "soaked" for a week or so without difficulty, I'll release it generally.

Don
 

gadgets

Resource contributor
#7
I have just posted new Release 1.1.01 to http://stuff4fs.com. It allows you to choose whether the light sources are BGL_LIGHTs or effects - or a mix of both. It also fixes several issues with its predecessor - in particular issues arising from use with non-English versions of Windows. Please refer to the included Version History for details.

The update should be automatically detected the next time you start AFLT. If not, download directly.
Don
 

gadgets

Resource contributor
#8
I have just posted new Release 1.1.02 to http://stuff4fs.com. It fixes several issues with its predecessor (please refer to the included Version History for details) and adds a PAPI 2 configuration.

The update should be automatically detected the next time you start AFLT. If not, download directly.
Don
 

gadgets

Resource contributor
#9
I have just posted AFLT Version 1.1.03 to http://stuff4fs.com. It should be automatically detected the next time you run AFLT. It fixes a 32-sequence strobe issue and includes new base models for Approach-3x5F and Approach-4x5F, the previous versions of which were faulty.

There is, however, still an issue with FS9 only when BGL_LIGHTs are replaced with effects. If you start at an airport with AFLT effects, go far away and then attempt to return, FS9 CTDs as you approach that airport. At this point, I have no idea what's causing it. Any insight from those of you familiar with effects would be appreciate.

EDIT: The FS9 CTD has been fixed. If you have previously downloaded the new 1.1.03, please do so again and copy the effects in the AFLT effects folder into your FS Effects folder. (The effects simply needed to be changed from Type 19 to Type 25)

Merry Christmas!

Don
 
Last edited:
Status
Not open for further replies.
Top