November 25, 20241 yr Hey all, I had a quick flight in the updated A319 from Luton to Brussels. All was going perfectly normally until the last phase of the flight. Just after sunset getting vectored into 25R by BATC I suddenly noticed that both left and right PFDs were showing the aircraft in a descending turn at 2800 feet or so. This was after a second or two earlier when I was just passing through 4000 descending to 3000. On popping outside briefly I saw that the aircraft was not in a descending turn at all. I disengaged the AP but it was no good engines didn’t spool up and I eventually just fell out of the sky. That’s never happened before! No obvious faults, no signs of icing. Actually the first thing I noticed that was wrong was when the MCDU didn’t respond to any inputs. My last input was a runway change from 19 to 25. That’s when it all started to go a bit wrong! Sadly it was all over pretty quickly so didn’t have enough time to do anything other than try opening the app to make sure it was still on (it was) And then checking the lights to see if they responded which they did. Has anyone experienced anything like this? I’ve spent many hours with it since it’s initial release and never had anything like that before? Could it maybe be something introduced in the latest patch? Many thanks! Anthony Milner
November 25, 20241 yr 6 minutes ago, antic81 said: Could it maybe be something introduced in the latest pat I have never experienced such behavior but clearly you did. Did you report to Fenix? -B
November 25, 20241 yr Author Not yet no! I just wanted to see if someone else has had anything similar happen. For some annoying reason I’ve never managed to properly tie my account on discord, I’ve raised it with them a few times and they say on their end I’m all good, sadly on my end I only see their announcements channels but not the lounge! I can always raise a ticket I guess, just wanted to make sure it wasn’t a known issue that I’ve missed. Edited November 25, 20241 yr by antic81 Anthony Milner
November 25, 20241 yr Not sure if it’s the same issue you had, but all displays freezing is apparently a known issue, but if you’re like me and had been on an older Nvidia driver you wouldn’t have seen it. I updated my nvidia driver to the latest for MSFS2024 and ended up having this issue in 2020 last night. More info: https://forums.flightsimulator.com/t/fenix-a320-freezes-with-instrument-pop-outs-nvidia-driver-related/651541 Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
November 25, 20241 yr Author 39 minutes ago, regis9 said: Not sure if it’s the same issue you had, but all displays freezing is apparently a known issue, but if you’re like me and had been on an older Nvidia driver you wouldn’t have seen it. I updated my nvidia driver to the latest for MSFS2024 and ended up having this issue in 2020 last night. More info: https://forums.flightsimulator.com/t/fenix-a320-freezes-with-instrument-pop-outs-nvidia-driver-related/651541 Ah interesting! I did the same with my driver so it could be. The only thing I will say is that they weren’t actually frozen, they were erroneously showing a descent that wasn’t happening even after they went to negative altitude it just kept going until I went splat. Anthony Milner
November 25, 20241 yr I remember seeing this happen, in the earlier Block 2 versions, when the GPU load was maxing out. However, Fenix improved later their code. How was your GPU load during this incident? Best regards,Luis Hernández Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.
November 28, 20241 yr I actually encountered the exact same issue after the recent update, I believe it's v2.3.0.524. Not only the A319 but the A320 base pack as well. I contacted Fenix and they responded that this is a known bug in this new update and they are already aware of that. Looks like nothing we can do here but just waiting for the next version.
Create an account or sign in to comment