Area

I don't usually post emotional, unfactual opinions on forums or about the people who write there; after all, everyone forms their own view based on their personality, life experience, and knowledge of the subject. But I share the opinion of @LRBS 's comments, having experienced the frustration of reporting a bug and receiving only responses from PMDG "experts" trying to prove me wrong. It took submitting a support ticket for the PMDG developers (not the forum developers) to acknowledge the bug and fix it. And in the end, the forum "experts" who had been criticizing my factual arguments became completely silent. NB: the post https://forum.pmdg.com/forum/main-forum/pmdg-737-for-msfs/general-discussion-no-support/401675-unable-to-delete-aircraft-state-file

Hello, I have just installed version V 4.00.059 by OC3. This fixes the issue mentioned above. Have a good day

I think saving certain aircraft states is causing the PMDG 737-800 to crash (WASM) with MSFS 2024 SU5. To install update 4.00.057, I performed the following steps: Uninstallation via OC3. WASM folder : Deletion of the pmdg-aircraft-738 folder in C:\Users\UserName\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\. Reinstallation. Since then, I've noticed: If I create an aircraft state with only hardware configuration (flaps, altitude, flight deck), it creates two files: the first is .fmc, the second is .sav. This state works perfectly. If I create an aircraft state with a hardware configuration (flaps, altitude, FD) and a flight plan, it creates three files: the first is .fmc, the second is .sav, and the third is .0.rte. This state causes the aircraft to crash (WASM).

MSFS 2024 Steam path : C:\Users\UserName\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-738\work\PanelState

OpenStreetMap blocked: disaster!!! So I came to the forum and read this thread. I’ve just installed "OpenStreetMap French" locally, as recommended above. Great!!! 😃 Many thanks. 🤩

I think I’ve found a solution: Position the tablet as indicated @ozzieblr , enable "Auto position EFB camera" in the settings, stow it in the pouch, and then exit MSFS 2024 properly. When you relaunch MSFS and the Phenom, the EFB is in the pouch; when you bring it up, it positions itself according to the previous setting.

Thank you so much @Funky D But I have the same question as @ozzieblr

Hello, I am unable to set the EFB to horizontal mode (see video: https://drive.google.com/file/d/1YddaRZRrZXqyb7YsFE9QYHk1_89tGmub/view?usp=sharing). Could you please help me? Note: It was positioned correctly before, and I have already uninstalled and reinstalled it.

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.