• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Version 4.2.00 Issues

But there still seems to be an issue with apron lights
Click to expand...
. Yes, I see what you mean.
There are now only a few extra lights generated
Click to expand...
Those're what I was referring in my post covering the release of 4.2.00. They're next on my list.
AFLT asks if you want to save the changes, which have been deleted.
Click to expand...
I guess I didn't clear the changes flag
4. This does not trigger a change message when closing AFLT.
Click to expand...
Opposite problem. The changes flag appears not to be set after a move.

All eminently fixable. But I'm rather busy with personal; matters, so it may be tomorrow before I post a new release.
 
4.2.03 posted to http://stuff4fs.com as the current Development Release.

Duplicate lights are gone and the runway/taxiway junctions are now lighted (when the link flags say to do).

We're getting close!

Don
 
Hi,

Nice - getting to only some rather minor nits now.

1. When a line of apron lights is created from scratch (right click, choose Add Line of Lights, create them by clicking, double click to end), only the corner/end lights can be moved, as is correct. BUT they can only be moved in the direction of the line, not in any direction as the manual states:

"in a line created as a line of lights, the end lights and those at “corners” may be –
“dragged” in any direction; upon completion of the “drag” operation, intermediate
lights (between ends and/or “corners”) are automatically moved to form a series
of straight lines; only ends and corners may be selected;"

2. There are 3 T intersections at KSAN, 1 is OK but the other two still have duplicate lights. I can't find any others though, so we're getting closer.

3. Still here:

1. Create a project, load a BGL file.
2. Create a new string of apron lights.
3. Delete Project, say yes to confirmation.
4. Create new Project

AFLT asks if you want to save the changes, which have been deleted.

The next 2 are requested improvements, not bugs.

4. When you strip an airport, this box pops up:

aflt_strip_box.jpg


Wouldn't it be easier just to have 4 radio buttons and you can click the one(s) you need? I'm also not clear if you can only enter one number or several? I'm confused what the multiple versions are and how you create them? I did read the manual but that didn't make it clear to me.

5. When stripping the original BGL file, I would love to be able to keep the VASI/PAPI lights in the ADE/AFCAD file, since they are visible farther away than any of the AFLT effects (and need to be). Could this be made an option?

Thanks,
 
1. In my testing, the corners are restricted, but the ends are not. Will be fixed.

2. Yes, I can see the algorithm is not working fully as expected. I was wondering what I was going to do today.

3. I thought I had fixed that. Turns out I needed two changes. The second has now been done.

4. Easier for you, but not for me. That little dialog is a simple Windows function (Inputbox). What you suggest would mean creating another custom dialog. But, having examined the code, all that selection does is label the output file. AFLT4 strips the reference airport file, regardless of the version of FlightSim to which it applies. For example, if the reference airport file is an FS9 file, that's what the stripped file would be. If you wanted to create a PV4 version, the airport reference file would have to be a PV4 file or that of another Flightsim version compatible with PV4. The input box selection is simply to be able to keep multiple stripped files in the same project folder. I'll take another look at the mechanism since, I agree, the current mechanism/documentation is not clear. In the meantime, you can only enter one number at a time - but you don't need to enter any number if you're only going to create one stripped-file version.

5. In version 4.1.n, the only "stuff" that got stripped was "stuff" you had created. But, in 4.2.n, all the "stuff" in the stock airport is created for you, so it all gets stripped. I hadn't considered that in the rework (but will do so now). One way that would accomplish what you want is to delete the PAPI/VASIs before stripping the airport. But have you tried using inverse-mapped effects? They should give you effectively unlimited range.

Don
 
Hi Don,

Oh,, if I can just leave that box blank then that's no big deal (for me, anyway).

I had tried the inverse-mapped effects and as I remember they were not bright enough just when I needed them. Part of the problem is that I am using VASI 21 at my classic airports, which is the worst case (just one light each). Modern users with more lights probably won't have a big problem with this. Once I get to FS testing I will look at that again and let you know what I find (with 4.2 I have only tested AFLT itself so far - one step at a time).

Deleting the VASI/PAPI won't work either since I want the neat little 3D stands that AFLT places. :) It would be great though if there was that option to keep the VASI/PAPIs, either in the stripping dialog box or just in Options.

Thanks,
 
Hi again,

I tried out the inverse mipped lights in the previous thread beginning here:

https://www.fsdeveloper.com/forum/threads/cant-get-started.445807/post-827296

The problem for me is while they look good from quite far away (7-8 NM), they lose their brightness by 6 NM (where I need the VASI lights to be bright) and they are tiny pinpoints close to the airport while making your final approach (just like regular effects - tiny pinpoints). At least in FS2004 there needs to be the "regular" LOD for very close up, but further than a thousand (?) feet away they need to be brighter (for the landing final approach) and brighter still 4-6 NM away. The distant LOD can stay the same or also be used for the 4-6 NM distance.

The other problem with the inverse mipped effects is you get a flashing glow just before touchdown, I assume due to passing over all the approach lighting. No such effect with BGL lights.
 
There are a number of things you could try to address the VASI brightness issue
  • Increase the X Scale and Y Scale values in the PAPI/VASI effects; if this works you'd have to save them as custom effects
  • Increase the Intensitry Adjust value in Colors.txt;
  • Increase the Light Size-Mipped value in Lights.txt: you'll probably also have to reduce the Range.
Not stripping the VASIs is, of course, possible but seems to have very limited applicability.

Don
 
I've now tried all those things, and nothing is as useful as the default VASI lights. Either they fade away too fast, they are way too big when on the runway (even the current 2.0 is too big), or they cause a funny glow when on short final. The combination of BGL lights and an added default VASI is the only thing that works for me in FS2004. If you don't want to make retaining default VASI lights an option then I'll have to stick with the default lighting.

BTW, when I compiled my KSAN project using the latest AIFP all the 3D taxiway lights are missing. The runway and approach structures are there though. The lights are there at night, but the little 3D objects are missing, day and night.
 
There are also some duplicate lights at both ends of the main runway at KSAN. I've moved them away from their duplicates here:

aflt_dupe_lights_2.jpg
 
If you don't want to make retaining default VASI lights an option then I'll have to stick with the default lighting.​
Click to expand...
Let's put this on the "back-burner" until we get the more critical issues sorted out. I'm sure we can find a solution.

I'm working on the remaining duplicates at the moment.

The 3D lights will appear in the next release.

Don
 
OK, I'll string along a little longer, we're almost done anyway. :)

I find there are some extra lights at the end of runway 27 at KSAN; there are none there in the ADE file. The little taxiway segment leading to the black runway line does have lights assigned to one side by mistake, but that little segment is parallel to the runway, not perpendicular:

aflt_runwy_27_lights.jpg
 
1. My MALSR approach at KSAN does not specify green end lights in the ADE file, but it's added to the approach when I use that BGL to create a project.

2. Also, in the default lighting there are some green/red lights along the edges of the runway at each end. I'm not sure why they are there, and it appears from looking at ADE they appear when you turn on runway edge lights. You can see them here in this shot, 4 green lights on each side:

aflt_ksan_default-jpg.50974


Now I'm NOT saying you should add them because I DON'T want them in my lighting, but I thought I would mention that they are missing. :)
 
Last edited:
1. I decided to widen the spacing of my green end lights on my KSAN MALSR approach based on an old photo, so I right clicked the runway and chose Edit Approach Lights. In the box that came up, the Strobes box was checked, even though this approach has no strobes. Thus after changing my spacing and clicking Place Lights, I now had 5 strobes added to the approach as well.

2. I was creating a Line of Lights (right click on a blank area and choose Add Line of Lights), created multiple segments, and then inadvertently clicked on the existing last light of the string I was creating. I get this exception:

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at AFLT4.MainPanel.JoinLine()
at AFLT4.MainPanel.pbData_MouseDown(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
Those green lights (they're red on the other side) are runway end lights. They will be at every airport unless they are replaced by the theshhold lighting associated with the approach system.

Re the VASI, what I'm thinking of is having the user decide whether or not he wants the stock lights left and, if so, adjust the stock lights so that it will coincide with the 3D models. It will be a couple days before I can explore further.

Re the exception. it would seem you're not supposed to do that . System probably thought you were attempting to select that light. I'll investigate.
Don
 
That VASI solution would be perfect.

Yes, they are at every airport with edge lighting, which is bad. So I'm glad you don't include them.

1. When FS is running and I use Add Line of Lights, I can only add Strobe-T and WigWag lights. But when FS is not running, I can add all types of lights. Thus I cannot add a string of taxiway lights while FS running. EDIT: I see what this is - if FS is running and I don't minimize it, AFLT will not display the entire menu. All I need to do is minimize FS and all is well.
 
Please read the EDIT in the post above yours, the problem is solved.

When I edit a line of lights i created from scratch, I still cannot move the interior corner lights in any direction; they are limited to the line directions. The end lights move in all directions.
 
PS. Is there currently any way for the AFLT map display to follow the aircraft in FS? Editing light placement using the aircraft as a guide would be faster if that were an option.
 
Most dialogs that accept mouse position will also accept a/c position, Just run Flightsim..
Don
 
You must log in or register to reply here.
Back
Top