gnukix Posted February 8, 2022 Report Posted February 8, 2022 Did a last state restore during climbout after having to leave and close X-Plane unexpectedly, and upon restore A/P disco (fine, kind of expect that), but the pressurization system was completely unstable until I cycled the packs off, let the rates calm down a bit, then back on. Kept cycling, rapidly, from a 2000+ cabin climb to a 2000- cabin descent. Might be a state restore problem, unfortunately, it was a "last state" restore so got overwritten almost immediately. I'll try to reproduce later and make better notes of what is happening, and after I complete this flight I'll attach the FDR csv.gz's from the Output/CL650 folder. Quote
gnukix Posted February 8, 2022 Author Report Posted February 8, 2022 Basically kind of looked like a PID windup from one of the controllers for the pressurization/env system, and it wasn't settling down on it's own. Might be b/c of XP loading it paused before I loaded the state from the airframe manager? I'd think those PIDs would all be paused/stopped though while the sim was going through that state? Quote
gnukix Posted February 8, 2022 Author Report Posted February 8, 2022 FDR-2.csv.gz is the initial sim session, FDR-1.csv.gz is the restored session which will have the bonkers pressurization behavior at the start until I cycled the packs off to on. FDR-1.csv.gz FDR-2.csv.gz Quote
Graeme_77 Posted February 9, 2022 Report Posted February 9, 2022 Can you please confirm this happened with the very latest v1.3.1 version? Issue 2589 should improve this behaviour. Also please attached the log.txt from the X-Plane folder after any event like this. Thanks. Quote
gnukix Posted February 12, 2022 Author Report Posted February 12, 2022 On 2/9/2022 at 10:31 AM, Graeme_77 said: Can you please confirm this happened with the very latest v1.3.1 version? Issue 2589 should improve this behaviour. Also please attached the log.txt from the X-Plane folder after any event like this. Thanks. Yes that was with 1.3.1. I’ll have a chance Sunday to try for repro and gather the rest of the XP11 logs. If I get a repro I’ll snapshot my install and try with 1.4.1 as I see 2674 modified the CPC PID. I’ll take a look in a few here and see if the xp11 logs from the incident flight are still present and attach. Quote
gnukix Posted February 12, 2022 Author Report Posted February 12, 2022 Also apologies for the delay in reply, I didn’t see any notification in my email (might be a spam filter issue, I’ll try to resolve that) Quote
gnukix Posted February 12, 2022 Author Report Posted February 12, 2022 Tried a few different things, could not get a repro on this today (still 1.3.1) so going to say it was a one time fluke....If I catch it again I'll be sure to preserve everything. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.