Ixoye

I have no idea, just that AMD themselves and all the videos I've seen recommend it, this instruction is for Ryzen 9 but applies to all X3D as far as I understand. https://community.amd.com/t5/gaming/how-to-set-up-your-system-with-a-new-amd-ryzen-9-7950x3d-or/ba-p/589464

If you use FG you need HAGS on, and if you use AMD X3D cpu's you need Game Mode on, the rest? personal options.

Honestly, I don't really see anything unusual, maybe there is some minor that hasn't caught my attention, I use TAA with FG + AMD FidelityFX at 50, G-Sync + V-Sync on in NVCP.

EXPO are AMD's version of memory overclocking, the same as Intel's XMP.

I have never had any of these problems, neither any else actually, AM5 have worked flawlessly for me.

AGESA is the AMD Bios, maybe MSI have another name for it, but if you have the latest it should be fine.

It is a bug that have been fixed in SU15 beta, so it will be corrected with next update.

Have you updated the Bios to the latest AGESA version? the longer boot times are due to AM5 motherboards doing memory training if you change som major settings in Bios, but they goes way faster with the latest version, but my motherboard also does memory training from time to time without me changing anything.

I agree, FS Traffic have way better performance for me as well.

I have it on, performance is the same on or off for me.

I'm surprised no load screen replacement mod (DUN) has come out as they are horrible.

This is how I set it up. 1. Go into Options > General > Camera (NOT the in-flight Camera Menu) and make absolutely sure that Height, Horizontal Position, and Zoom are set to 50! These are the global values and if they're not set to default (50), all of your future custom views will not save correctly. This is probably a bug because it's counter intuitive to apply global changes all over again when trying to save a view; but it is what it is. 2. In Options > Controls, search for the command "VFR Pilot View Save" and assign a key binding. By default, this command is unassigned... I assigned it to Ctrl + Alt + V. 3. Make a note of your controller assignments for "Reset Cockpit View". Default is Left Ctrl + Spacebar and/or "F" (I also have it assigned to the trigger on my joystick). 4. Load the aircraft of your choice and use the translation, look, and zoom controls to position the camera exactly where you want it. When you have what you want for a default view, press the "VFR Pilot View Save" binding assigned in step 2 (Ctrl + Alt + V in my case). Now, every time you press the "Reset Cockpit View" button(s), it will go back to this view and will NOT alternate to other intermediate views with subsequent presses... yay! 5. Now that you have a default view defined, custom cameras may also be saved the same way using the associated key bindings... default is Left Ctrl + Left Alt + Numpad 0 to 9. These views are recalled using the corresponding "Load Custom Camera #" commands... default is Left Alt + Numpad 0 to 9 6. Repeat steps 4 and 5 to set individualized default and custom views for each aircraft you own.

Check your VRAM usage, I assume your 8GB is full loaded, 8GB is not enough to use with FG.

Yes it is, this is how the game should work for everyone, hope it will be like this with less expensive hardware in MSFS 2024.

I use PBO -30, you can try that first and run a 10 min Cinebench and see if it is stable, if not try -20 and so on, you can also try -40 if it is stable at -30, some chips can run that low as well, but it's unusual, mine crash at -40.