December 12, 20241 yr Took off in the ASOBO C-172 from KRNM (Ramona California) and flew at 8,000' along the spine of the San Diego mountains down to the Mexican border then west to Brown Field (KSDM). I then turned North and flew the ILS 28R approach to Montgomery Field (KMYF). Great scenery with TLOD and OLOD at 250. Using Frame Gen and MSFS2024_AutoFPS I saw a very consistent 50+ FPS from takeoff to the PENYY waypoint, which is at 3,500' on the ILS 28R approach. Then, very suddenly the FPS dropped to 6 to 8 (with frame gen). The CPU time per frame did not change nor did the GPU usage, which stayed around 85%. I manually changed TLOD and OLOD to 50 but it made no change to the dismal FPS. Taxied (very wobbly at 5 fps) to the GA parking area. I experimented with all the settings (stopped AutoFPS) but could find nothing that would bring the FPS above 10 (with frame gen). CPU usage was low, network traffic was almost non-existent but could not control the aircraft at such low frame rates. How can the sim work so well for 35-minutes and then suddenly become unusable? Edited December 12, 20241 yr by TacomaSailor AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 12, 20241 yr Author Yes - my point was that I had great performance at the origin airport - frame rate was same as in the air. Taxi at origin was good and easy and scenery was very nice at 150 for both LODs. Lots of network traffic. It all fell apart when I came within 6 NM of the airport on approach. Flying around the airport at altitude did not make the FPS drop. Traffic of all kinds set to low. I do agree it is probably all a common problem. AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 12, 20241 yr This sounds like the VRAM bug. https://forums.flightsimulator.com/t/fps-performance-vram-bug/668753/899 There seems to be an issue with their DX12 implementation not unloading things from VRAM or something to that extend - I’m not very technical. On my 4080 card I’ve been able to avoid it by turning off ray traced shadows (big VRAM draw) and reducing texture quality to high. Edited December 12, 20241 yr by regis9 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
December 12, 20241 yr Hi Apparently there area bunch of airports that are causing this issue. Directly after the patch became available I loaded into NZNS and only had about 5-6 FPS. I then loaded into NZCH the same 5-6 FPS so I tried NZAA and a few other airports which all were fine. I mistakenly thought it was the NZA scenery causing the problem as I have it for NZNS and NZCH. So I reached out to NZA who confirmed there is an issue with NZNS and NZCH with or without NZA scenery installed. As a developer, NZA contacted Asobo who confirmed there are a bunch of airports that have this issue. It only when you get close to them. Asobo have fixed the problem and it will be available in the next patch. However Asobo did not say when the next patch will be available. I am happy flying around avoiding those airports. I hope this helps Best wishes. Bob
Create an account or sign in to comment