Sid Starz

Latest v3.0.0.0 installed. Currently flying the FSLabs A320x. Altimeter setting was for 6000 ft. Warning started at 2000 ft. Disabled both altimeter settings to stop the warnings. Not the first time this has happened in taking off or in landing and this is not the only a/c it happens in. Anyone else experiencing this issue?

Keven, Posted this here where you requested me too. CTD after 5+ hours flying the QW 788 1. Windows 10 Pro 2. Version 1809. OS 17763.rs5_release 180914-1434 3. Norton Security 4. Samsung SSD 860 Pro 1TB with 600gb remaining 5. Active Sky for P3Dv4 This is what was in the Application event log: Faulting application name: PREPAR3D.EXE, version: 4.4.16.27077, time stamp: 0x5bfdbb35 Faulting module name: ntdll.dll, version: 10.0.17763.292, time stamp: 0x7ded7809 Exception code: 0xc0000374 Fault offset: 0x00000000000faf49 Faulting process id: 0x838 Faulting application start time: 0x01d4c52d6769d796 Faulting application path: D:\Lockheed Martin\Prepar3D v4\PREPAR3D.EXE Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 14aae333-cb87-4a9a-a759-7df1e7966ddb Faulting package full name: Faulting package-relative application ID: Application: Immersion Manager.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at .SimConnect_WeatherRequestInterpolatedObservation(Void*, UInt32, Single, Single, Single) at LockheedMartin.Prepar3D.SimConnect.SimConnect.WeatherRequestInterpolatedObservation(System.Enum, Single, Single, Single) at A.m.C(Int32) at A.V.A(System.Object, System.Timers.ElapsedEventArgs) at System.Timers.Timer.MyTimerCallback(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.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers() Faulting application name: Immersion Manager.exe, version: 1.0.20.0, time stamp: 0x5c3aff56 Faulting module name: ntdll.dll, version: 10.0.17763.292, time stamp: 0x7ded7809 Exception code: 0xc0000005 Fault offset: 0x000000000004df23 Faulting process id: 0x3448 Faulting application start time: 0x01d4c52d864ee562 Faulting application path: D:\OldProp Solutions Inc\Immersion Manager\Immersion Manager.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 834db99f-a16c-4eb8-8dab-b59329e29ea9 Faulting package full name: Faulting package-relative application ID:

Updated and Rainmaker is working for me too in the -400. A big thank you to the whole team.

OlpProp has updated the 717 Immersion package which has fixed the contrails issues I had.

Just added the 717 Immersion Package yesterday. No contrails with only this particular a/c (Own all the rest of the packages and no issues have been noted). Anyone else had this issue and can offer a workable solution? Ticket also submitted to OldProp for support.

Had the same issue again tonight when I loaded up a 748. Since all the a/c in my inventory was working except for the 748, I selected (under Preferences - General) "Recheck Configuration Files". I then generated a report file for me to review. Restarted P3D and CP and loaded a 748 again and it's working now. I guess my config file for the 748 was corrupted.

I use AS4 and REX SkyForce 3D. I had 2 files named wxstationlist.bin located in the following directories: C:\Users\xxxxxxxx\AppData\Roaming\Lockheed Martin\Prepar3D v4 and D:\REX Sky Force 3D\files\wxstationlist\P3D I suspect having 2 files with the same name caused my problems with CP. I fixed the issues by deleting both files and restarting the apps and then the sim. Works great now.

For me, it was a corrupted wxstationlist.bin file. CP working for me now.

https://fsfxpackages.com/en/support/products/ChasePlane/ 3 What is the issues? "ChasePlane and other SimConnect applications no longer interact with the sim" Reset the wxstationlist.bin file We have not found the root cause of this issue but with some add-on combinations, the wxstationlist.bin file causes SimConnect applications to stop working properly. Removing this file and letting it regenerate should fix the issue. This issue is not caused by ChasePlane as the file is not modified by ChasePlane. Shutdown the simulator Navigate to the following folder corresponding to your simulator version %APPDATA%\Lockheed Martin\Prepar3D v4 %APPDATA%\Lockheed Martin\Prepar3D v3 %APPDATA%\Lockheed Martin\Prepar3D v2 %APPDATA%\Microsoft\FSX-SE %APPDATA%\Microsoft\FSX Remove the wxstationlist.bin file Launch the simulator

I'm very surprised that other folks are not complaining if it is an outage of some sorts.

CP is locked and has been for over 5 hours now. I'm using P3D v4.3 and flying the PMDG 748i. Cannot change views. Have restarted P3D and CP several times

Never had issues before the update. Bad luck for me. CTD each time I try to start P3D. Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ntdll.dll, version: 10.0.17763.1, time stamp: 0xa369e897 Exception code: 0xc0000374 Fault offset: 0x00000000000fb349 Faulting process id: 0x3c1c Faulting application start time: 0x01d45bfe9d76d1be Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 1494fcdb-581d-42c9-8985-0bb6866a1b0d Faulting package full name: Faulting package-relative application ID: ______________________________________________________________________________________________________ I checked under windows\system32 and ntdll.dll has changed to v10.0.17763.1 where the old version was 10.0.17134.254. For me, I have other programs that are giveng me fits where the apps just get hung up and won't start. Event Viewer shows the culprit lies with the new version of ntdll.dll. Updated: Used Recovery and went back to earlier build. Seems to work but having troubles with CP now.

Same thing happening to me. All engine indications in the cockpit are normal. Presently flying from KIAH-PANC at FL380 with winds 234@78. Doesn't do it all the time but it has happened during the flight periodically with all 4 engines shaking. https://youtu.be/v15Ek_rSK4c

Just read this topic after downloading the latest version and installing it earlier. This was my first install of the A320X since the last fiasco became public. Some pics of what was changed and added during the installation and file locations. https://ibb.co/nQTYay https://ibb.co/dtxgTJ

Hot Corner it was. Thanks for the help Keven.