constant crashes of AFLT

[windshear]

I am using AFLT for P3DV4,5 and its not running when I use your app.

I have constant crashes with the following errors:

"Application: AFLT.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.ExternalException
at System.Drawing.Graphics.MeasureString(System.String, System.Drawing.Font, System.Drawing.SizeF, System.Drawing.StringFormat)
at System.Drawing.Graphics.MeasureString(System.String, System.Drawing.Font, Int32)
at System.Windows.Forms.ThreadExceptionDialog..ctor(System.Exception)
at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)
at System.Windows.Forms.Control.WndProcException(System.Exception)
at System.Windows.Forms.Control+ControlNativeWindow.OnThreadException(System.Exception)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)"

"Faulting application name: AFLT.exe, version: 4.4.0.0, time stamp: 0x5ec544d2
Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0x67005c2a
Exception code: 0xe0434352
Fault offset: 0x00114402
Faulting process id: 0x60fc
Faulting application start time: 0x01d633eaebee0c50
Faulting application path: H:\AFLT4400\AFLT.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: b27f294e-d700-4801-bb3c-2f599a9799c5
Faulting package full name:
Faulting package-relative application ID: "

"Faulting application name: AFLT.exe, version: 4.4.0.0, time stamp: 0x5ec544d2
Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0x67005c2a
Exception code: 0xc000041d
Fault offset: 0x00114402
Faulting process id: 0x60fc
Faulting application start time: 0x01d633eaebee0c50
Faulting application path: H:\AFLT4400\AFLT.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2d28d263-f066-4a2b-874d-1ffcf9bda621
Faulting package full name:
Faulting package-relative application ID:"

 

[windshear]

"
Fault bucket 1816035666778077027, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: AFLT.exe
P2: 4.4.0.0
P3: 5ec544d2
P4: KERNELBASE.dll
P5: 10.0.18362.815
P6: 67005c2a
P7: c000041d
P8: 00114402
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4D2.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE57E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE58F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5A5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5C5.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AFLT.exe_fad198c2e1c41c2265c0ce3537b2867b6d29cab3_bb26622e_0ef5f344-4293-4b5b-883d-f46b1974322b

Analysis symbol:
Rechecking for solution: 0
Report Id: 2d28d263-f066-4a2b-874d-1ffcf9bda621
Report Status: 268435456
Hashed bucket: f27c76f9702c0cdde933dad131bf3763
Cab Guid: 0"

 

[gadgets]

I have no such difficulty. Perhaps there is something in your airport configuration AFLT doesn't "know" how to handle. But, without your project folder and airport reference file (.bgl or .xml), I can't comment further. Please also include the AFLT for P3D folder from Documents\Prepar3d v5 Addons

But, before sending me anything, please install AFLT 4.4.20, released only a couple days ago and give it another try.

 

[windshear]

Here you go

 

[gadgets]

The reason for the crash is (presumably) because there's nothing in AFLT for P3D for PV5 to process. I didn't realize this would cause a crash and it will be fixed.

But, more to the point - why is there nothing in the AFLT for P3D folder? Unfortunately, you didn't send me the airport reference file (i.e., the .bgl file that you submitted to AFLT to start its processing). Or, you can send me the .ad4 file. Either way, I need that file to see what you've done (From a quick analysis of the Placements.xml file, I can see you've done a lot of work, but AFLT won't run without the airport reference file. Please send it to me.

 

[gadgets]

While waiting for you to respond, I installed your AFLT for P3D in my Documents\Prepar3dv4 Addons folder. PV4 ran normally (as I expected it would).

The exception reports you posted above are not in a format I've ever seen before. Where did you get them?

The AFLT for P3D folder with the empty subfolders suggest your airport was not successfully compiled. Were there errors present. But if there were errors, the AFLT for P3D folder should never have been created. So, at the moment, I'm at a complete loss to explain what's going on.

In addition to sending me your airport reference file, please also provide a summary of your related actions starting at the time you attempted to compile VHHH until you executed PV4.

 

[windshear]

I am using P3Dv4 not V5

I am new to this completely so could you please explain what you need and what AFLT did not get etc? I have very little understanding of what you are mentioning? You want the AFCAD this is based on?

 

[windshear]

Here's the AFCAD I used... Now should I have pointed to the AFCAD installed in the scenery? Its the same, but under a different name

 

[windshear]

So I wrote the path to the scenery folder, but it did not make any difference, upon attempting to compile, I get an "unhandled exception" failure:

"
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: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.Collections.Generic.List`1.get_Item(Int32 index)
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.8.4180.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AFLT
Assembly Version: 4.4.2.0
Win32 Version: 4.4.2.0
CodeBase: file:///H:/AFLT4400/AFLT.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_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
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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:///H:/AFLT4400/FSUIPCClient.DLL
----------------------------------------
ASToFra.Coordinates
Assembly Version: 1.0.0.0
Win32 Version: 1.4.0.0
CodeBase: file:///H:/AFLT4400/ASToFra.Coordinates.DLL
----------------------------------------
ASToFra.ObjectModel3D
Assembly Version: 1.0.0.0
Win32 Version: 1.4.0.0
CodeBase: file:///H:/AFLT4400/ASToFra.ObjectModel3D.DLL
----------------------------------------
LockheedMartin.Prepar3D.SimConnect
Assembly Version: 3.3.0.0
Win32 Version:
CodeBase: file:///H:/AFLT4400/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.

 

[gadgets]

I am using P3Dv4 not V5

Yes, I realize this. Makes no difference to the issue since the procedures are the same. Only the destination folder is different.

Here's the AFCAD I used...

Thanks. That's the file I needed.

So, first, the bottom line. I compiled your file for PV4, fired-up PV4 and "Voila!", there was your fully lit airport. It took only three steps:

• create the project, which appears you did correctly since your Placements.xml file appeared normal
• select Compile Data from the Project menu,
• select PV4 and the light source on the Make Library dialog and click Create/Save Library.

Therefore, it would seem your procedure is suspect. You said:

So I wrote the path to the scenery folder, but it did not make any difference, upon attempting to compile, I get an "unhandled exception" failure:

which is troubling in two respects. First, AFLT should never crash or throw and exception regardless of what you do. So, I've still got some work to do). Of greater concern, though, is that if you were compiling for PV4, the Scenery Folder Path is not used and, in fact, is disabled. Therefore, I need to know into which textbox you entered the scenery path and, since it caused an exception, I'd like to know exactly what you entered.

Regarding your initial report, clearly this is an unusual situation. As I reported yesterday, the AFLT for P3D folder was "empty", i.e., the usual folders were there but they contained nothing. I have no idea how this happened so, once again, I'd like to know exactly what you did that "upset" PV4 and what non-default values you may have entered.

 

[windshear]

which is troubling in two respects. First, AFLT should never crash or throw and exception regardless of what you do. So, I've still got some work to do). Of greater concern, though, is that if you were compiling for PV4, the Scenery Folder Path is not used and, in fact, is disabled. Therefore, I need to know into which textbox you entered the scenery path and, since it caused an exception, I'd like to know exactly what you entered.

Regarding your initial report, clearly this is an unusual situation. As I reported yesterday, the AFLT for P3D folder was "empty", i.e., the usual folders were there but they contained nothing. I have no idea how this happened so, once again, I'd like to know exactly what you did that "upset" PV4 and what non-default values you may have entered.

I really don't understadn what the "AFLT for P3D folders" are, and how do I "upset" p3dV4?! I am sorry if I am sounding stupid but I cannot check or answer if I don't know what to look for...

 

[gadgets]

I was not asking you about the AFLT for P3D folder. The purpose and use of that folder is explained in the user manual. I was asking you for a detailed description of the procedure you used from the time you opened the Make Library dialog until you closed it. (Your previous report claimed you had done something that should not have been possible when compiling for P3D.) I need to know what you did in order to duplicate your situation and determine what's wrong.

 

[windshear]

I don't know if I did anything else than begin doing lights... Honestly

 

[windshear]

I did create a custom color... And the explanation as to how to do this was not really understandable, so maybe I did something wrong here?

;
; User-colors i.e., colors that may be assigned by the user.  The order must not be changed.
; Add any additional colors at the end of the first section - named "Custom1", "Custom2" or "Custom3".
;
; A named effect is supplied by the user - in _Lo, _Med and _Hi varieties as required
;                                         
;               |  RGB   |     Bahr Texture U/V      | Intensity | Effect Size |   Custom
;   Name        |        | Umin | Umax | Vmin | Vmax | Adjust(%) | Multiplier  | Effect Name   
Amber            | ffc000 | 0.50 | 0.75 | 0.75 | 1.00 |  100      |  1.0        |       
Blue            | 0000ff | 0.00 | 0.25 | 0.75 | 1.00 |  100      |  1.0        |     
Dark            | 404040                             
Green           | 20ff20 | 0.00 | 0.25 | 0.50 | 0.75 |  100      |  1.0        |   
Red             | ff2020 | 0.75 | 1.00 | 0.75 | 1.00 |  100      |  1.0        |   
White           | ffe0c0 | 0.25 | 0.50 | 0.75 | 1.00 |  100      |  1.0        | 
Custom1       | FF00FF | 0.25 | 0.50 | 0.75 | 1.00 | 100 |  1.0 | fx_Custom1|
Custom2         | 000000                             
Custom3         | 000000

 

[tgibson]

You do have a vertical line after your fx_Custom1; no other line ends with that. Perhaps that may be a problem?

 

[gadgets]

No, that's not the problem, Tom, AFLT will ignore that. (If it didn't, it would report the problem and close down.)

Windshear, I suggest you focus on getting AFLT working in a basic sense before worrying about custom colors. I have asked you several time for details as to your procedure. You responded only with:

I don't know if I did anything else than begin doing lights

. That tells me nothing.

I have previously confirmed that the .ad4 file you sent me compiles properly and the lights all display in PV4. Upon further investigation, I can tell from the Project Folder you sent that the lights compiled for you as well. I also advised you that in the copy of the AFLTforP3D folder you sent, all the subfolders were empty and I have just observed that LockheedMartin.Prepar3D.SimConnect.dll is not in that folder. So, where did all those missing files go?

There is no doubt the problem, whatever it is, is in your system and not in AFLT. My instincts tell me that you have unusual anti-virus software that is designating those files (most system generated and all new to your system) as hazardous and removing them. Strange that it wouldn't tell you it was doing so. But, whatever the cause, I'm afraid its up to you to find it. I cannot diagnose your system from afar.

If you choose to pursue this and do find the problem, I'm happy to advise you on any AFLT issues you may encounter afterwards.