Jump to content


  • Posts

  • Joined

  • Last visited

Nyana's Achievements


Apprentice (3/12)

  • Week One Done
  • One Month Later
  • First Post
  • Conversation Starter

Recent Badges



  1. Hi Fabio and all, I did some testing with PACX and it runs stable, no app crashes so far. This is without admin rights. I guess it must have been the Citation file messing up. Thanks everyone for your support and for the great tool PACX is.
  2. As requested. I notice tons of errors around Latitude.txt, which is a template for the Cessna Citation Longitude for MSFS. The file Latitude.txt is there. Maybe because the 'My Documents' folder is a OneDrive location (>256 chars)? Edit: OneDrive uses placeholders, so the file isn't really there unless I tell OneDrive to keep files in their location (and not replace them by placeholders) I flew the 787 Dreamliner the other day without PACX crashing. log.zip
  3. It's with MSFS 2020. I searched left and right for the log, but I can't find one. Probably I have to turn on logging manually? I tried 2 flights today, both without any problem. I have a feeling it happens when the sim completly freezes for a moment, which happens often on my end, ie frame rate drops to 0, cockpit buttons don't work etc and after a second or 5 the sim catches up again and runs 20-30 FPS. I'll run logging the next few flights, see if the app closes again.
  4. Hi, New user, love the extra sense of realism this tool gives. But out 3 flights done, 2 of them ended in PACX closing itself down midflight. In the event log are two entries. Sorry my machine is Dutch, but this is what the event logs say Prior to application close: Toepassing: PACX.exe Framework-versie: v4.0.30319 Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering. Uitzonderingsinformatie: System.Runtime.InteropServices.COMException bij System.Windows.Media.Composition.DUCE+Channel.SyncFlush() bij System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<ChannelSet>) bij System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr) bij System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) bij System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bij MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bij MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bij System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bij System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bij System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bij MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) Application close error: Naam van toepassing met fout: PACX.exe, versie:, tijdstempel: 0x6047b9ec Naam van module met fout: KERNELBASE.dll, versie: 10.0.18362.1474, tijdstempel: 0xf0a6699c Uitzonderingscode: 0xe0434352 Foutmarge: 0x001146d2 Id van proces met fout: 0xeb8 Starttijd van toepassing met fout: 0x01d739bb81a4bdac Pad naar toepassing met fout: C:\Program Files (x86)\TFDi Design\PACX\PACX.exe Pad naar module met fout: C:\WINDOWS\System32\KERNELBASE.dll Rapport-id: 7a4b96bf-dda0-489e-9c97-2189fd314286 Volledige pakketnaam met fout: Relatieve toepassings-id van pakket met fout: Any cause, is this my end?
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.