Area

Hello, I have Navigraph 2605 AIRACs. They are active on all MSFS 2024 aircraft (tested with an A320neo). However, with the ATR 72-600 2024, the MCDU displays an older AIRAC 2024 version. Do you have any thoughts or, better yet, a solution so that the ATR has the Airacs 2506 ? Thanks in advance.

As long as I had a 3090, I used driver 566.36. It's the "reference" and, most importantly, it allows the use of game filters with NVIDIA_app_v11.0.1.184. But for those using 40xx or 50xx cards, driver 566.36 is unfortunately definitively obsolete.

Great!!! It works, thank you so much.

Hello, I play MSFS 2024 via Steam and I would like to purchase the Phenom 300 on the Marketplace. When I try to purchase MSFS 2024, it asks me to "enable the Steam overlay" in Steam. [ I go to Steam and I see that the option is activated, So I can't buy the Phenom 300 because it's blocked. Could you please help me?

In your screenshot, it looks like you're on the desktop. For me, MSI Afterburner + RSS only shows the checked options and "in ods" when I launch MSFS 2024.

Hello, I'm posting here because I never received a response on Discord. When BeyondATC gives you a vector, it's sometimes incorrect and even unrealistic (opposite direction). In this situation, if I ask BeyondATC for a "direct" flight to a waypoint on the flight plan (often IAF or FAF), which is the waypoint located after the vector, BeyondATC systematically refuses the "direct" request. However, it would be useful, when BeyondATC "gets confused with the vectoring," to create a backup option such as "Backup Direct to Resuming Flight Plan." What do you think?

Why did I disable R-Size BAR support in the BIOS? With my new configuration (AMD Ryzen 7 9800X3D - MSI PRO B850-S WIFI6E - 64GB RAM - MSI GeForce RTX 5080 16GB) and MSFS 2024 SU4, the message “VRAM overflow” appeared (a problem I never encountered with MSFS 2020 + Intel 12700 + 64GB RAM + RTX 3090 24GB). On the verge of crashing at any moment, I checked the Task Manager and found the following: With MSFS 2024 + an MSFS 2024 aircraft + an MSFS 2024 airport + an empty Community folder, the amount of VRAM used was between 10 and 11 GB. With MSFS 2024 + A320 Fenix + FSTL + GSX + graphically demanding airports (EDDF Aerosoft, EGLL Inibuilds, etc), the amount of VRAM used was between 15.3 and 15.6 GB (Dangerous state => crash imminent). And in the second case, of course, the “VRAM overflow” message appeared (NB: always on the ground, never in flight). So, after investigating the problem from every angle, the only solution I found (inspired in part by the MSFS forum) was to disable R-Size BAR Support in the BIOS. By doing this, I solved the problem; I never again received the “VRAM overflow” message, as the VRAM usage dropped below approximately 13 GB in all cases. It’s a fact. I didn’t investigate any potential side effects because, with my hardware configuration and settings (40 FPS max + everything on ULTRA except “Texture Resolution,” which is on High) and MSFS_AutoFps, MSFS 2024 runs perfectly. But what applies to my configuration doesn't constitute a universal law.

With the configuration (post above), MSFS_AutoFPS proves very useful for preventing VRAM overflow. Indeed, although it's not its primary purpose, I've noticed that with: A320Fenix, GSX, FSTL, BATC EDDF (Aerosoft) TLOD 250 - OLOD 200 without MSFS_AutoFPS, MSFS 2024 uses 13 GB out of 16 GB. with: A320Fenix, GSX, FSTL, BATC EDDF (Aerosoft) TLOD 250 - OLOD 200 With MSFS_AutoFPS (TLOD 100 up to 500 ft, then 300 upon reaching 1500 ft), MSFS 2024 uses 12 GB out of 16 GB.

I would have preferred that before Area 51, FlyTampa simply release a version of EHAM without caltrop for 2024. Simply. see video 1:25:00

Thank you for your feedback. If it doesn't provide a solution, it confirms that it's a BATC malfunction. I hope the developers will look into this issue.

Hello, I'm trying to assign a key on the keyboard or joystick (VKB) to "Push to Talk," but the window appears and disappears immediately. Video: Thanks in advance for your help. Note: I've read the manual, and I've posted several messages on the BATC Discord server, but haven't received any response.

Weird! I installed ChasePlane, keeping my cameras and views accessible via the numeric keypad. When I select a camera view using the memorized numeric keypad, it displays a view that doesn't match.

Hello, As requested, here is my humble feedback. Last year I upgraded to MSFS 2024 SU4. My profile: Fly: gate-to-gate or parking-to-parking. Aircrafts: general aviation (Baron 58 Pro and Caravan Black Square, etc.) and airliners (A320 Fenix, 738 PMDG, etc.) FPS: 40 FPS via the Nvidia control panel (the goal is twofold: silence and moderate temperature in the office). MSFS settings: TLOD = 200, OLOD = 150 With my configuration (see signature) and only with airliners, I experienced stuttering on final approach (from around 400 ft AGL) and while taxiing at major airports like EGLL (IniScene) or EDFF (Aerosoft), which made the immersion disappointing, especially since it occurred after 1.5 hours of flight, precisely when I was trying my hardest to finish in style. I tested AutoFPS, and with the settings infra, I no longer encountered stuttering. For me, it's a real plus. Many thanks for your work.

Having difficulty understanding, and with the video having no sound, I'd like to rephrase. To eliminate the stutters specifics to the 777 (and perhaps the 737), is it necessary to display the "W&B page" on both EFB for the entire duration of the flight? Thank you in advance.

Thank you all for your feedback. During my next EGLL approach, I will definitely apply: "Speed brakes are your best line of defence"

From what I understand, this isn't a way to replay the entire flight or a portion of it, like Flight Control Replay. It's a function to record a specific situation (aircraft status, altitude, speed, and other components) at a precise moment during the entire flight (NB: This goes beyond simply recording the aircraft's status on the ground, as offered by PMDG). This allows you to replay the flight if you recorded the situation at takeoff, to replay a specific approach if you recorded the situation at the IAF waypoint, or to replay a failure management scenario if you recorded the situation before the failure.

Thank you for your concise explanation. I think that for those who want to do "Study Level" (myself included), this is an essential feature for making progress and more easily understanding mistakes. This is a great step forward for MSFS 2024, and I hope others will follow.

Before upgrading to MSFS 2020 and then 2024, I used X-Plane with, among other things, the ToLiss A320, which had a save/load option for flight scenarios; examples: Aircraft configured and ready for takeoff, Aircraft configured and 10 NM from the TOD, Aircraft configured and on a vector, Etc... Is this the same feature you're referring to, the one implemented on the A400-600? If so, I haven't found any tutorials that mention it, and I know pilots on forums who never switched to MSFS because this unique ToLiss feature, which allows you to replay the same scenario indefinitely, wasn't available. Thank you in advance for your clarification.

Hello, I'm writing to the "Professionals" of airliners like the A320 or 737-800. When I approach EGLL via STAR ALES1H through BIG to land either East or West, I adhere to the speed and altitude restrictions (see chart). So, from ETVAX (FL180), I need to arrive at BIG at FL070 and a speed of 220 KIAS. However, I always arrive too fast and too high at BIG unless I manage the rate of descent with a severe V/S and "stay on the speedbrakes." Do you have any advice, or better yet, a solution? Thank you in advance.

Absolutely agree. What made me abandon BATC was the constant inability to request a shortcut and the capricious vectoring. To clarify: I mainly fly in Europe where, at major airports, transitions and approaches are generally S-shaped and extremely long. In real-world conditions, this allows controllers to sequence the approach, but for simulator flights, it's often interminable.

Yes. Settings: Language options > Unit of measurement => American. On the ground, in the weather window, I set the wind speed to "5", I close the window and then reopen it; the wind speed remains at "5". I repeated this several times; the speed remains at 5. I haven't tried testing this: on the ground, set the wind speed to "5", take off, gain altitude, and check.

Everything is here :

Since I didn't get a concise answer (this isn't a criticism of the participants in this discussion), I turned to the flightsimulator.com forum. The problem stems from this setting: Topic : https://forums.flightsimulator.com/t/custom-weather-2024-su4-wind-speed-increases/758871

Your comment is interesting, but it takes us away from the main topic : To understand the problem, watch the video : 1/ I set the wind speed to 7 knots and close the window, 2/ I open the window, the speed has increased to 13.61 knots, 3/ I open the window, the speed has increased to 26.45 knots, 4/ I open the window, the speed has increased to 51.45 knots, 5/ I open the window, the speed has increased to 77.17 knots. Video: https://drive.google.com/file/d/1t9WOcr5eRHF8Wl2RYYGbBPQb5FZqPNPp/view?usp=sharing

Thanks for the video, in it we can clearly see that when you pass 1,000 FT you are at 30 knots of wind but past 1,000 FT the wind continues to increase, increase, increase.