• 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.

FS2004 Can't Get Started

tgibson

tgibson

Resource contributor
Messages
11,780
Country
us-california
Hi Don,

OK, I've decided to improve an airport using AFLT, or at least explore the program.

I downloaded AFLT 4.1.07, which says it's up to date. I then:

1. File/Create Project, gave it the name KSAN.
2. Browsed to my FS2004 folder and chose the file KSAN_ADE9_CA62.bgl. I get the error at the bottom of my post. I opened the BGL file in ADE 1.65 and 1.75 and it loads and displays fine.
3. OK, I tried a different ADE BGL file (KFAT_ADE9_CA59.bgl). AFLT instead says "File Appears to Contain No Useable Data".
4. I also tried some AFCAD BGL files - I get the same message as in #3.
5. I then tried using ADE to compile the KSAN AD4 file to get an XML file. It created a 243 KB XML file. I loaded that into AFLT and get a blank screen.

None of these files or AFLT are in any Program Files folders, and AFLT loads as adminstrator with the warning box on startup. I am using System 7.

I have attached 3 of the files mentioned above.

Thanks,

Error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: startIndex
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.BitConverter.ToInt16(Byte[] value, Int32 startIndex)
at AFLT4.AirportSurfaces.ExtractAirport_bgl(Byte[]& data, Int32 iRec, Int32 iNameData, Object& param1, Object& param2, Object& param3)
at AFLT4.Files_Binary.GetAirportData(String sPath, String sICAO, Process_GetAirportData pProcessAirportData, Object& param1, Object& param2, Object& param3)
at AFLT4.AirportSurfaces.GetAirportOutlines(String sPath_File, String sICAO)
at AFLT4.MainPanel.mnuProject_GetAirportData_Click(Object sender, EventArgs e)
at AFLT4.MainPanel.mnuProject_Create_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AFLT
Assembly Version: 4.1.7.0
Win32 Version: 4.1.07
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/AFLT.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.3062.0 built by: NET472REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
FSUIPCClient
Assembly Version: 2.4.4910.2
Win32 Version: 2.4.4910.2
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/FSUIPCClient.DLL
----------------------------------------
LockheedMartin.Prepar3D.SimConnect
Assembly Version: 3.3.0.0
Win32 Version:
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/LockheedMartin.Prepar3D.SimConnect.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 

Attachments

PS. As you can perhaps see from the error report, I have NET 4.72 loaded. MS says it's an in-place update for 4.5, so that should be OK, right?
 
PPS. I did get one XML file to load, which was not created by myself. But I don't see anything different in the first few sections of XML between that file and mine.
 
Last edited:
Hi again,

I added edge lights to the one XML airport that would load, then tried to compile as an FS2004 BGL file. It warns me that no files will be copied to a Scenery folder, and then I got an unhandled exception with this error message. The first time I got this message the error pointed to a P3Dv4 folder, (I think it was to the Addons folder, but I'm not sure) but all subsequent attempts result in this null path result.

In my KBFI project folder I have a Lights folder with FS9/MDLs./MDL files in it, and Library.ini, Placements.xml, and StockData.xml files.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: path
at System.IO.Path.GetFullPathInternal(String path)
at Microsoft.VisualBasic.FileIO.FileSystem.NormalizePath(String Path)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards, Collection`1 Results)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards)
at AFLT4.MakeLibrary.SaveLibrary()
at AFLT4.MakeLibrary._Lambda$__R19-1(Object a0, EventArgs a1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AFLT
Assembly Version: 4.1.7.0
Win32 Version: 4.1.07
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/AFLT.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.3062.0 built by: NET472REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3416.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3429.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
FSUIPCClient
Assembly Version: 2.4.4910.2
Win32 Version: 2.4.4910.2
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/FSUIPCClient.DLL
----------------------------------------
LockheedMartin.Prepar3D.SimConnect
Assembly Version: 3.3.0.0
Win32 Version:
CodeBase: file:///C:/FS/Airfield%20Lights%20Toolbox/LockheedMartin.Prepar3D.SimConnect.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Last edited:
I was wondering if the "no scenery path" was a problem, so I had it compile the files to the Addon Scenery/scenery folder, and that worked. I did get two BGL files, and they display lights at that airport. So I can get the program working, but only at that one airport.
 
Hi, Tom. It would seem AFLT4 did not get fully exercised with FS9 during beta. I must admit, it's been a while since I have attempted anything with FS9.

Thanks for the detailed reports and the files. With a little luck, I'll have it all working by end-of-day and a new release out.

Don
 
Hi again,

Yeah, I always seem to be the FS2004 guinea pig - the same was true for ADE. I do appreciate you supporting the sim, though. :)

A minor UI snafu.

1. I have only one Project in my Projects folder, KBFI.
2. When I start AFLT it loads, and the Select Project menu choice is grayed out.
3. I use Create New Project and create KBFI_2.
4. I decide I do not need my new project and use Delete Project.

I'm left with a blank screen and the Select Project menu still grayed out. The only way I can find to recover is to quit and restart the program.

Hope this helps,
 
When I import (and use) the stock lights, the VASIs don't seem to get included. Is this supposed to be true?
 
I've found and fixed all the issues you encountered up until 3 posts above. But, I see you've been busy while I've been fixing.

Re the inability to re-select the single project, I can duplicate. It will be an easy fix.

Re the missing VASIs, No, it is not intentional. I don't have any airports with VASIs. Please send me that one and I'll take a look. You can e-mail if you wish to don at stuff4fs dot com.

Don
 
No need to send me anything, Tom. I just found that there are VASIs in the .bgls you sent earlier.

BTW, the final project is now reselected automatically.

Don
 
I have updated to 4.1.08, and all airports so far are being loaded. Yay!

You are faster than I am - I was going to say the airports from the previous post had VASIs. :)

While I can left click and select objects, I don't seem to be able to right click and get the context menu?
 
Another question. Am I supposed to be able to change the radius of the lights in the display (i.e. did I do something wrong)?

When I load some projects from the Select Project menu, I get "normal" sized lights:

aflt_small_lights.jpg


but when I open others I get very large lights:

aflt_large_lights.jpg


Is there a way to switch these to small lights?

Thanks,
 
I think that I get normal sized lights if I use Create New Project and load the airport BGL file using that dialog, while I get the big lights if I then use Load Airport Image to change the airport version displayed?

I also have to use Load Airport Image twice to get the popup path box to disappear.
 
Last edited:
Also, if you look at the top image I posted, you can see that the width of the taxiways is not being displayed properly - all of the parallel taxiway segments at the left edge of the image are the same width. The wide segments are selectable, but the narrow ones are not.
 
Last edited:
I've now found the cause of the missing VASIs, but not yet fixed.

Lights size is a function of zoom level. When zoom level 1 is when all airport components (displayed or not) can just be contained in the window. The light size is not (at the moment) otherwise user adjustable.

the width of the taxiways is not being displayed properly
Click to expand...
So it would seem. The narrow segments are undesignated and are not normally displayed. But, I agree, when they are displayed, they should be shown at the proper width. You are the first person to pick up on that.

Don
 
Either you've taken a rest or things are working well for you. Anyway, 4.1.09 was just posted at http://stuff4fs.com. It now imports VASIs and draws undesignated taxiways at their proper width. As well, I've given you a "quick and dirty" way to adjust light size under the View menu.

That's "it" for today. Enjoy,
Don
 
Hi,

We're making progress!

I can't do much testing when I can't right click the airport. :) I right click on the airport map and nothing happens. I did mention it above (post #11). BTW, it still doesn't work in 4.1.09.

The taxiways are now the correct width, but only the ones that were correct before are selectable. The skinny ones before this are now the right width, but they are still not selectable.

The VASIs now appear, but are not placed in the correct position. Here is the map of the KSAN file I uploaded and its VASIs:

aflt_VASIs.jpg


I can't test much more until I can right click the airport.

Hope this helps,
 
Tom. do you still have View/Stock Data checked. If so, that's the problem. The View/Stock Data item does just that. It lets you view the stock data. If you want to use some or all of it, uncheck that item (which puts you back to the bare airport and any other lights, including stock lights, you may have entered) and right click there.

I'll see if I can intercept the right-click when viewing stock data and issue a message to this effect.

Re the VASIs, that looks like a feet/meters issue. I'll make another release shortly.

Don
 
Hi,

Yes, that was the issue with the right clicking. I didn't realize that prevented it.

Now when I load the KSAN test BGL file everything seems to work (so far) except the VASI location and some of the taxiways are not selectable (the ones with no designator).

Thanks,
 
VASI location is fixed. (I didn't realize the data in the .bgl was offset from the center of the runway and not the end.)

I'll check on the selection of undesignated runways.

Keep up the good work, Tom. Sure wish you'd tried AFLT4 earlier.

Don
 
You must log in or register to reply here.
Back
Top