Version 4.2.00 Issues

[tgibson]

• Taxiway edge lights now appear (I had inadvertently declared then to be surface mounts, which suppresses display of the 3D model)
• The exception when adding a new line caused by placing the cursor over the just-placed is fixed. Doing so now just takes you out of the hot-cursor mode.

Both of these indeed appear to be fixed, thanks.

 

[tgibson]

Hi again,

I've done a little work on aligning your VASI lights with the default lights as defined in ADE.

When I define a VASI this way in ADE:

I need to set the following values in AFLT for the lights to be quite close to each other:

So it would appear that if you adjust your light placement by moving them 6 ft further out and 10 ft closer to the threshold then by setting these values the same in the ADE file and thus in AFLT upon import the lights will be at the same place. As I said before the default light moves around when you look at it from different angles so these values are only approximate, but they look pretty good when making a landing, which is the important view. They could be fine tuned later with more experience. Hopefully these adjustment values will be much the same in all situations and do not change when other values are entered.

 

[gadgets]

Thx Tom.

I've eliminated ALL the duplicates, but I still have on minor issue to sort out. Another release tomorrow.

Don

 

[tgibson]

Hi,

Now using 4.2.08.

I first created a new project, using the SAN ADE file I posted above. I then edited one of the VASIs:

1. Right Click, Edit VASI/PAPI
2. Edit the values
3. Click Place Lights.
4. The location of the VASI lights does not change, and now when I right click on the VASI, I get the menu choice of Edit C/L Lights instead of Edit VASI/PAPI. If I choose it, nothing happens.

AFAIK, there is now no way to re-edit the VASI/PAPI lights.

 

[tgibson]

After Creating the Project using the SAN ADE file above, when I try to move any light (Runway, Taxiway, Apron) they will select, but not move by dragging with the mouse. Stock Data is not checked in the View menu.

 

[tgibson]

When trying to create a new light of lights (Right Click on blank space, Add Line of Lights, Model Name: Edge, Color: Blue, Nominsal Spacing: 100 ft), when I click on Place Lights, I get this error:

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.AirportSurfaces.SurfaceFromStrip(Int32 iStrip)
at AFLT4.MainPanel.cmnuPlaceEdit_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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)

Hope this helps,

 

[gadgets]

Welcome back, Tom. I'll address these ASAP.

Don

EDIT: I can reproduce all but the following:

, and now when I right click on the VASI, I get the menu choice of Edit C/L Lights instead of Edit VASI/PAPI. If I choose it, nothing happens.

AFAIK, there is now no way to re-edit the VASI/PAPI lights.

After editing the vasi from right-clicking on the runway, while the edit was not effective, I still get the expected PAPI/VASI menu item if I right-click the runway again.

Don

 

[tgibson]

I did not click on the runway, I clicked on the VASI line, then right clicked.

 

[gadgets]

4.2.09 posted at http://stuff4fs.com fixes all issues. The underlying problem was a typo I made during the "cleanup" a week or so ago.

Don

 

[tgibson]

Hi,

Looks like all issues above have indeed been fixed, thanks.

When I select a line of apron lights (newly created or loaded from the BGL file) and choose Delete Line (or press the delete key), I get this error:

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.cmnuDeleteLine_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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)

 

[gadgets]

Tom, I'm unable to duplicate. This appears to be the same as one of the errors I fixed this morning. Please check again with 4.2.09 and give me a specific set of lights to test.

 

[tgibson]

Hi,

I confirm I'm using 4.2.09.

It's still happening.

1. Opened AFLT.
2. Created new Project called Test
3. Loaded KSAN_ADE9_CA62.BGL file.
4. Clicked on the line of lights at the bottom of the diagram - the line turned red.
5. Pressed the Delete key.
6. Got the error above.

 

[gadgets]

Thanks. The bottom line of lights is a strip of apron edge lights, Now I get the exception.

New release tomorrow AM

 

[gadgets]

4.2.10 posted at http://stuff.com.

 

[tgibson]

Hi,

That fixed it, thanks.

It appears that now when the lights are loaded from the original BGL file, you can no longer edit lights by selecting a taxiway link and using the Properties box?

I thought I would remove some taxiway lights from one side of a taxiway and instead of just deleting the line I selected the taxiway link, right clicked and chose Edit Link Lighting and unchecked the Left box. Clicked Place Lights but the left string was not removed. The property box when brought up again still has the Left box unchecked. The lines of lights spanned two links, but both are selected below.

I also clicked on a link that had no lights and added them via the properties box - no lights appeared. However, it did delete a light already present a few links away.

Using SAN as an example,

1. Create new project, load the SAN 62 BGL file.
2. Select the link shown below.

3. Right click, Edit Link Lighting. Add left and right lights, click Place Lights.
4. Result below - no lights on link, but a light above it deleted.

If this is the intended behavior then it is a bit confusing to have the Edit Link Lighting choice present.

I also tried selecting a bunch of links with no lighting and adding Left/Center/Right lights through the Properties box, no luck.

Hope this helps,

 

[tgibson]

However, the converse works fine. If I delete a line of lights directly, the Properties box for an affected link now displays the Left/Center/Right box unchecked. So that works OK.

But checking the box(es) again does not bring back the lights.

 

[gadgets]

I've found and fixed the cause of the Properties box having no effect. I had only updated one of the required two sets of flags.

In your points 3 and 4, the cause of the light above being deleted is an error in the handling of taxiways with discontinuous lighting. I'm working on an improved algorithm for placement of taxiway lights that handles full lines of lights rather than on a link by link basis and should allow better matching of left and right strings on straightaways. So, it may be a few days before this is fixed.

Keep up the good work.

DOn

 

[tgibson]

A minor thing, but AFLT doesn't show up on the list of recently run applications in the Start menu of my Windows. Makes it harder to run since I have to use the Shortcut on my Desktop instead. AIFP3 does show up there, so I know it's possible.

 

[gadgets]

Tom, I have no idea what is the criteria for a non-registered application to show up in Windows MRU list. All my applications are compiled and zipped in a similar fashion. If you or someone else can tell me how to make it happen, I'll be happy to try.

Don

 

[tgibson]

I figured it out. I misspoke when I said I ran it from a desktop shortcut - I ran it by double clicking the EXE file in Windows Explorer. This does not generate an entry in the list displayed by pressing the Start button in Windows 7. When I created a shortcut and used that, now the program appears on the Start button listing the next time I want to use it. Lesson learned.

Sorry,