QuaxTheSnoopie

As no one explained 😜:

Maybe here: https://library.avsim.net/search/basic/root/Steve Parsons ?

What about sleeping masks ? For long flights in a widebody aircraft - change the pilot's seat with a passenger 🤣

Fortunately you were not flying a real aircraft, so no new episode of Mayday 🙃 At Oct 25 Developer Livestream they admited a decrease in MSFS 2020 graphic quality. It seems related to SU16. But listen to the answer, there's hope 😊 - sorry for off topic.

After update to P2A V3 0.2.4 : I found P2ALanguageTrainer.exe Speech training is available again. Maybe former interference with security software blocking

Had the same issue with wrong altimeter values, since update to 0.2.3... works correct for me. Imho updating your 0.2.2 version may solve your problem too...

No issues but I render TAA. So maybe coherent relation to DLSS downsampling ? Lower texture size should be neutralized by lowering DLSS downsampling (higher target resolution) ? May not resolve ZL but reduced tile resolution ?!? So I should have saved my money for better glasses instead recently buying a 5070 TI ? And I understand why the noise of nine fans in my case doesn't bother me.

Hi Dave, today I updated P2A V3 to 0.2.3B then tried speech training: P2A V3 0.2.3B -> Settings -> Utilities -> Speech training -> Train After pressing the "Train" button, P3D immediatly crashed. I don't think its a problem of Windows as I did a successful speech training in P2A V2 yesterday (as I had some troubles with voice recognition, maybe my "automn voice" 🙃, that was the reason to try it in V3 too). Did a test flight in P2A V3 0.2.3B, voice recognition by ATC works. As I think, voice training in V2 and V3 lead to the same Windows engine (?) and my voice shouldn't change each day ☺️, for me it's not a problem, just to report... Windows Event entry: P2A trace:

https://www.flightsim.com/files/file/197119-fs2004fsxaccelp3d-v3-pilotable-eagle/

I don't use it with GPS, just for short "manual flights" after work 🙃 BTW - if you're a rebel: https://flyawaysimulation.com/downloads/files/2974/fsx-star-wars-millenium-falcon/ (restricted to 32bit sim 😞). And what about thi 🤣s:

Stumbled across this post by configuring Plan-G for MSFS 2020 (it works with P3D V4.5 since years). As I cannot see any news on their website - most of the links incomplete and lead back to the website itself, in facebook no reply newer than 24 weeks, I don't think, my MSFS 2020 database load problem will be solved. Talking about Plan-G 4.2.6.297 and in my case MSFS 2020 Steam installation, I found the "MSFS Content Folder" via AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt -> last line in this file states the Plan-G mentioned "content folder": MSFS Content Path: C:\Games\MSFS2020\Packages But entering this path in Plan-G, it crashes while searching the airports, logfile Documents\Plan-Gv4 Files\Plan-Gv4_Log.txt tells me 12:51:55.2 C:\Games\MSFS2020\Packages\Official\Steam\fs-base-genericairports\scenery\0601\APX50130.bgl: Apts: 187 12:51:56.0 Error reading file: Exception of type 'System.OutOfMemoryException' was thrown. 12:51:56.0 Apt: EDKQ TT:AIRPORTEK.EDKQ.name Id: 0xd0 prev: 0xd0 Restricting the "Content Folder" to subdirectory C:\Games\MSFS2020\Packages\Community , I get only a subset of the airports. @Alex voor Plan-G : I don't think it's related to the airport locpak - as I have to select a specific .locpak file, not a folder. @doudou : in Little Navmap, it's possible to change the map to "OpenStreetMap" or "OpenTopoMap", but it's hidden in View -> Theme (I use OpenTopoMap in Plan-G too because of it's contour lines).

In the FSX days, there was an eagle as steerable aircraft. Piloting this bird (with feathers and moving wings - depending on throttle), one looked through his eyes (and it screamed from time to time like eagles do). I think, it would have been funny to fly such an animal from the mountains top down to the valleys...😜

We're living in the Matrix 🙃

Now my first short VFR flight after the update and what I observed: Got a loop between ATC and copilot: ATC (white) > Skyhawk Zero Charlie Papa Visual Straight In approved. Call 5 mile final for Runway 35R (yellow) > Cleared for Visual Straight in Runway 35R Skyhawk Zero Charlie Papa Copilot (green) > Cleared for Visual Straight In runway Tree Five Right Skyhawk Zero Charlie Papa ATC (white) > Skyhawk Zero Charlie Papa Visual Straight In approved. Call 5 mile final for Runway 35R (yellow) > Cleared for Visual Straight in Runway 35R Skyhawk Zero Charlie Papa Copilot (green) > Cleared for Visual Straight In runway Tree Five Right Skyhawk Zero Charlie Papa until I asked "Skyhawk Zero Charlie Papa Say QNH", then another "5 mile final", then "Altimeter i 29.94 Skyhawk Zero Charlie Papa". Another observation was the answer of ATC / Gnd to the copilot: "You were garbled. Please say again". I don't think the (P2A-) copilot was garbled as I understood her very good. Can a computer copilot speak garbled at all 😉 ?

Sorry to say but it seems, update 0.2.1 didn't fix my problem, same crash as before. Correction: as I would have shown you more of problem data here, I typed in this answer... ...then decided to investigate a little deeper and eventually resolved the crash. At first, I thought about a parameter error, so I renamed AppData\Roaming\P2A_300\Settings\AppSettings.xml and as I suspected, P3D V3 created this file from scratch. Then I prepared copies of old and new AppSettings by deleting unnecessary lines (Notepad++) to review them. After I extracted the most part of different lines for later analysis, luckily the different size/position parameters of "MainWindow..." and "FreqWindow..:" caught my eyes I tried it: renamed the old file back to AppSettings.xml and removed these window size/position parameters and voilà: Pilot2Atc V3 0.2.1 started without crash. Problem solved.

Now some months later, all links on the bottom of the page lead to the page itself, no forum, the mentioned link to https://tasoftware.co.uk/index.html leads to "Men Outdoor Sneakers" (possibly used in aircraft too but not what I've expected 😁). Plan-G 4.2.6.297 "Check for Updates" shows it was unable to check the current version: "please check again in the near future". Strange and mysterious...

I didn't run P2A V3 some time, now today, I got an appcrash each time I start it, a reboot didn't resolve the issue. It may be related to Windows 10 22H2 or DOTNET updates in the last weeks. Windows event viewer shows me two consecutive error msgs: 1. 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() 2. In the same second: Faulting application name: Pilot2ATC_3.exe, version: 3.0.0.0, time stamp: 0xc3dd21ff Faulting module name: KERNELBASE.dll, version: 10.0.19041.5678, time stamp: 0x024a42e4 Exception code: 0xe0434352 Fault offset: 0x000000000003b699 Faulting process id: 0x3988 Faulting application start time: 0x01dbce41fde928eb Faulting application path: C:\Games\Pilot2ATC_3_x64\Pilot2ATC_3.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 81eefbbe-6cb8-41a9-8de7-fd04d8406c4a Faulting package full name: Faulting package-relative application ID: I found Pilot2ATC_3.exe.xxxxx.dmp files for each incident, if you need them, I will upload. I can provide a list of Windows/Dotnet Updates (KB...) in this system of the last weeks too on request. Meanwhile I work with P2A V2, no problem. Update 1: I remember I did an update of VS C/C++ runtime 64bit for another app some time ago. Update 2:Sorry, forgot the update Office 2016 (32bit) -> Office 2024 (64bit) last week.

Maybe dependent on minimize/maximize P2A with button or key ? A minute ago after closing P3D with P2A window hidden (forgot it after aircraft shutdown), I couldn't reopen it by clicking on it. After right click on the task bar icon of the initial P2A instance, strangely a second instance starts up, I closed it. Then I pressed my HOTAS button and the initial P2A instance came up, so I could close it. Btw: in the initial instance, the MAP and COMM window were disabled, don't know if this matters.

The last hours, updated P2A V3 to 0.1.2 and did a VFR flight. My observations: Voices -> Radio Sound Effects -> Enable Background Noise: voices send correctly to my USB headset, but the noise is send to the speakers (maybe not always as after one of the many restarts I think, I heared them in the headset). Clearance delivery didn't like "Radio Check" (spoken by me but even by "Speak" button): "... appears you're on the wrong frequency" Validated and filed VFR flight plan between small "INFO" airports. Now "RADIO acts as ATC" delivers more functions (not as much as P2A V2), but doesn't handle all of them. "Ready to copy VFR clearance" lead me to Center and the same to Center lead me back to INFO. The same happened on a bigger airport against tower and clearance. Button assignments show button numbers + 1 compared to P3D (V4.5 HF3) and P2A V2, say: HOTAS button 7 in P3D and P2A V2 is shown as button 8 in P2A V3. So I will continue to use P2A V2 at first, but from time to time run V3 and report my findings.

Me too, any news ?

Just to add: the payed version of FSUIPC is able to run "LUA scripts". That needs some fiddling but supports enhanced steering aircraft by USB controllers (switches, buttons a.s.o.).

Just a thought: as your graphics card is not a monster (don't know your resolution) and modern webbrowsers use it for rendering, maybe an open webbrowser in the background rendering advertisements ? Or a scanning of a security suite from time to time ? I would recommend process explorer or MSI Afterburner to get deeper in detail.

According to this reddit thread , But as @blaunarwal already stated, I never removed the NVIDIA shader cache, just the P3D shaders directory. I think, the NVIDIA location is used if an application doesn't set it by itself.

What's sufficient for me and ended decades of fiddling/tuning - just let me fly: 1. P3D 4.5 HF3 (on 7800X3D + 4070 SUPER + G-Sync compatible 1440p monitor = after decades of optimization now stable 30 fps without stutter out of the box) 2. Although I've licensed Aerosoft Airbus, I use only GA (A2A, Realair, Flysimware). 3. Active Sky (historical weather, I select the days in timeanddate.com and wunderground.com , the second accepts ICAO) 4. REX Texture Direct + Soft Clouds 5. Most of ORBX, especially ORBX Germany North+South and ORBX LOWI (special eastern approach RW08) Other addon airports/airfields "as needed". 6. FSUIPC licensed to create LUA scripts for non-standard aircraft controls (HOTAS, throttle quadrants, switch panel) I want to control as most as possible aircraft instruments by real switches and sliders and minimize mouse/keyboard action. 7. I don't need additional AI besides the P3D internal and some ORBX AI traffic freeware. 8. Pilot2ATC because of voice recognition and "virtual copilot", talking to ground/ATC/center instead of clicking buttons or pressing keys. 9. NVIDIA Inspector setting SGSSAA for sharp instruments and no shimmering livery parts (only P3D <= V4) That may not fit for others but it's allright for me.

Sorry, my fault, as a former mainframe/unix gui, I'm not deep in Windows security mechanism - and it's no security problem. Now, what happens ? It made me wonder, why I had setup a folder structure in P2A V2 ...\Sounds\ATC_Chatter\Regions with empty folders below: Africa, Asia, Canada, Custom, Europe, ... although in P2A V2 config, the "Root Folder" entry points to ...\FS_ATC-Chatter (with the real sound files below Regions\Africa Regions\Asia ...). It seems, P2A V2 uses the "Root Folder" entry (...\FS_ATC-Chatter\Regions\...) to get the sound files for each region but uses its own folder ...\Sounds\ATC_Chatter\Regions to get the default region. And it seems, P2A V3 has taken over this mechanism in Settings -> Chttr: In block "ATC Chatter", the "Default Chatter Region" is only selectable if there are these (empty) region folders below ...\Sounds\ATC_Chatter\Regions in the P2A installation directory But it plays the chatter (correctly) from the entry in block "ATC Chatter Folder". That's the reason why it only works for this guy as he copied the FS_ATC-Chatter folder "Regions" into the P2A installation directory. He hadn't to copy the files, the empty region folders are sufficient (as in my case). Or route the P2A ...\Sounds\ATC_Chatter\Regions with a symlink to the FS_ATC-Chatter "Regions" folder as I did before and now, after my tests, again until this behaviour would be changed. So in my opinion - and maybe I'm wrong, but did some intensive testing the last hour, this P2A behaviour should be corrected so that the P2A settings -> Chttr : "Default Chatter Region" field checks against the subdirectory "Regions" in the folder specified in block "ATC Chatter Folder" below, but not - as it seems for me - hard coded against the P2A installation folder ...\Sounds\ATC_Chatter\Regions.