bruskey

Dave helped me locate the issue on a separate email thread. Dave suggested that my Pilot2ATC AppSettings file may have a strange value in it so I renamed it and had Pilot2ATC rebuild it. Functioning normally again. The AppSettings.xml file is located at: c:\users\<UserName>\AppData\Roaming\P2A_300\Settings\AppSettings.xml

Hello. Am receiving the follow CTD error on startup of Pilot2ATC, the main window appears for a few seconds then I receive this. I attempted a full reinstall but get the same error. Application: Pilot2ATC_3.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentException at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean) at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object) at Pilot2ATC_3.ViewModel.MainWindowVM.ShowFltPlan() at Pilot2ATC_3.MainWindow.DataLoaded(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs) at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Pilot2ATC_3.App.Main() Immediately follow the above error i receive this error as well in event logs: Faulting application name: Pilot2ATC_3.exe, version: 3.0.0.0, time stamp: 0xe7114779 Faulting module name: KERNELBASE.dll, version: 10.0.26100.6584, time stamp: 0x0a9b38fe Exception code: 0xe0434352 Fault offset: 0x00000000000c66ca Faulting process id: 0x467C Faulting application start time: 0x1DC2FD9FCDCB6BC Faulting application path: D:\Pilot2ATC_3_x64\Pilot2ATC_3.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 6b36894b-71a7-4bb4-963d-bc84891a9d81 Faulting package full name: Faulting package-relative application ID: These are the only entries from the Pilot2ATC logs. 2025-09-27 14:10:24.1035|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|AppSettings Loaded. PTT Joystick Name: PFC Cirrus Yoke 2025-09-27 14:10:24.4294|INFO|Pilot2ATC_3.Licensing.frmLicense|License Checked OK 2025-09-27 14:10:36.1234|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|Program StartedPilot 2 ATC (P2A) - version 3.0.0.0_EarlyAccess 0.2.3C 9/27/2025 2:10:36 PM 2025-09-27 14:10:36.5527|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|Pilot2ATC® starting initialization. 2025-09-27 14:10:36.5527|INFO|Pilot2ATC_3.ViewModel.MainWindowVM|NumberDecimalSeparator: Thanks, Bruce

With my 3090 running a 4K monitor 30/60 mode X2 in the mod, I'm seeing about 10 to 15 degree increase in GPU temps with this mod as well as a 20 to 30 percent increase in GPU usage, sometimes hitting close to 100% flying around JFK with mostly ultra settings. This is both in DX11 & DX12 mode with TAA and DLSS. Whereas with the FG mod my GPU is less taxed and able to maintain a constant 40 FPS. Will keep playing with it.

Hi, if you have the Descent Briefing turned on under the sound options try turning that off, I had similar random TOD crashes and this fixed it for me. Bruce

Hello, does anyone know why with HDR on under P3D the landing lights on the 737NGX look just fine from both VC and outside, however, with HDR off the landing lights look low resolution or "washed out". I prefer to fly without HDR on but the lights look so much more realistic with it on. Bruce

Just curious if any one else has tried this package with FS2004? Day and night textures look really good but my level of detail radius is much worse with this package. GePro or Fscene, yes there are blurries after a certain range, but with this package I only have a small radius around the plane that is clear, beyond that - no good. I have my cfg file set as: [TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=21TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.000000TERRAIN_EXTENDED_RADIUS=9.500000TERRAIN_EXTENDED_LEVELS=7 Just curious if anyone else tried this package and got the same results.

I always use FSbuild and KORD is the only airport thus far that gives me issues.Bruce

Everytime I attempt to fly into KORD either FSX or FS9 RC4 does not recognize KORD as my final destiantion for some reason it thinks I'm 400+ miles from KORD when in reality I'm only minutes away. KORD is the only airport that I have found so far to have this issue, has anyone else seen this? Here's an example of my FSX flight plan from KSTL to KORD...Bruce<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KSTL to KORD</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>23000</CruisingAlt> <DepartureID>KSTL</DepartureID> <DepartureLLA>N38

I have the same issue in Windows XP 32 bit with SP3 the XGUAGE never updates, so it's probably not a vista thing.Bruce

Uninstalled XGAUGE and still had the problem, will use Active Sky X for now, perhaps the next service pak release will free something up. Bruce

Unfortunately the owner of the product FSWXR2100 is no longer in business. The radar never gets past test mode to look for weather data (or maybe its trying and can't) it just sits there in test mode with all the colors on. Perhaps a conflict in guages some where? I still have Active Sky X installed with ASA installed, that combination is alright?ThanksBruce

I have the issue with the Wilco Products (737, EMB and Citation X) as well as Captain SIM 757. I decided to try Active Sky X and it appears in that version I do not have the issue. I'm running Windows XP 32 bit with SP3 and FSX with Acceleration. Let me know if you need any further info.Bruce

When I use ASA for weather I can not use the weather radar in any of my payware aircraft - for all of them they stay in test mode. When I use default FSX weather everything works fine, has anyone encountered this before with ASA and the B394 patch? Is there a setting perhaps that I'm missing somewhere in ASA that might resolve this?Thanks,Bruce