So for patch #5, it appears there is a bug for some people on the loading screen if they have specific peripherals plugged in. It happens to some people but not for everyone.
The problem is, Asobo said their testing team had some 20 to 40 people in a previous Q&A session. Looks like 20 to 40 people on their testing team wasn’t enough to find this CTD bug.
MSFS is very complex and it appears the number of permutations for peripheral settings is just way too much for 20 to 40 testers.
I think Asobo said they will reinstate beta testing again so that’s a step in the right direction. With a larger pool of people testing, hopefully bugs like this peripheral CTD bug can be caught by the beta testing team before the patch is released to the public.
3 Likes
This is reasonable,
many other programs allow you to download the latest (potentially unstable) version IF you wish to have the latest mods and you agree to risk to have CTD or else, but you could decide not to do so and keep using the current version until the stability of the new release is confirmed.
This helps developers avoiding to be submerged by thousands of complaints and to have only specific reports.
1 Like
The problem, I think is that there is no way to delete old controller profiles without having the controller plugged in.
Case in point. If I have my CH Products Flight Sim Yoke plugged in, it loads, but loads the default profile which has no assignments.
If I try to modify that default as a new profle. Still ok.
But if I try to choose to delete one of my previous profiles. POOF to desktop.
With my HOTAS + it’s worse because it detects that better and simply tries to load the latest controller profile for that device and it CTD’s before the sim even loads.
This is pretty unacceptable, and as a minimum they should have a way to clear out old controller profiles without you needing to plug in the offending controller to do so.
I do hope hope they reinstate beta testing before releasing any more patches that break things that were working previously. I would prefer to wait for an update to be proven stable before spending my limited flying time to download and install an update only to encounter installation issues, unflyable aircraft, CTD, etc. They need to stop doing that!
2 Likes
How are we back to peripherals causing CTDs during the initial loading? This was a bug several patches ago.