Concurrent use of SPAD.next with MSFS 2024 can sometimes lead to a CTD. This can occur in a variety of scenarios:
1 SPAD.next is loaded before MSFS 2024, with MSFS 2024 loadin before the start button appears.
2. SPAD.next is loaded after MSFS 2024 is loaded
3. A change in SPAD.next profile triggered by a change in aircraft in MSFS 2024.
Somehow this issue is back with MSFS 2024. Would appreciate if other users of SPAD.next could chip in if they are experiencing the same, with the hope that this gets investigated and resolved.
Have not had any CTDs attributable to SPAD and I use it all the time with plenty of success. I wonder if your setup is making a call that isn’t recognized or is otherwise conflicting.
I had not been aware of this, but I use Spad exclusively so it’s more than possible that this is causing my inconsistent yet regular CTDs especially when either selecting an aircraft or changing aircraft in the main menu. Voted.
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
But I don’t think it’s just SPAD that’s causing the issues…. Just tried to do a flight from CYBL to CYVR. No scenery addons and poof CTD on 2 mile final into Vancouver. GRRRRRTRTTFR