I have not had this issue on my PC. AMD FSR3 was enabled prior to SU5, and I have loaded into the sim multiple times since the upgrade without any issues.
I believe the conflict here is having dev mode enabled with Smart Docking. If you delete UserCfg, boot the sim, enable dev mode, disable smart docking, and then enable frame generation, you should be fine if my theory holds.
Deleting UserCfg restores settings to default which should disable FG and allow you to boot the sim and follow the above steps. Good luck and let us know if that works!
You don’t need to delete the usercfg.opt file - just edit FrameGeneration line so that it has NONE (which simply means frame generation is disabled) instead of FSRFG or DLSSG.
Regarding Smart Docking, in one thread I recommended turning it off because it can affect performance when Frame Generation is enabled, so it might also be a potential cause of CTDs.
Yeah, fair point - I spend most of my beta testing with default settings so this is the easiest solution for me, but totally reasonable to just change the single line within. Thanks!
Then launch MSFS again and open Developer Mode. If there’s no CTD, while in Developer Mode, go to the Options tab and turn off the Smart Docking System.
This CTD is very easy to reproduce. You just need to enable Developer Mode and make sure the Smart Docking System is checked. Then turn on Frame Generation and select AMD FSR3 - the CTD happens instantly.
If I was able to force the crash that easily, the team responsible for testing and verifying bugs should have no trouble reproducing it as well, and the thread will likely end up with a bug-logged tag.
To be fair, AMD FSR 3 is available to all users irrespective of hardware. That said, public beta testing is specifically because the official testers will never get to every combination of settings, either.