"apply to all aircraft" controls setup option not working

The same thing just now happened to me (12/28/2024). I tried applying the “None” Keyboard profile to the stock C-172. However, I accidentally clicked ‘Apply to All Aircraft’, at which it hung for about 20 seconds, then CTD.

2 Likes

Have the same issue mid Jan 2025, v1.2.11.0, sim always CTD’s if I click the controllers ‘Apply to all aircraft’ button.

I’m not sure if this is on the Asobo list of bugs so they will eventually patch it, in which case I’ll wait for that, or there’s an assumption everyone will go through the delete-cloud-saves stuff and it’ll never get fixed.

1 Like

ISSUE DESCRIPTION

Description of the issue:
When settings the controls, selecting “Apply to all aircraft” in the profile selection causes CTD.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes, I did.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:
1. Start MSFS24
2. Enter Settings/Controls
3. Create a new control profile in the aircraft category section.
4. Select “Apply to all aircraft”.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
Genius K640 PS/2 keyboard
Microsoft Mobile Mouse 1850
Saitek ST290 joystick
Logitech Throttle Quadrant
Logitech G Pro Flight Rudder Pedals

[PC Only] Are you using Developer Mode or have you made any changes to it?
No, I’m not/I haven’t.

[PC, MSFS 2020 Only] Are you using DX11 or DX12?
N/A

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
NVIDIA, 566.36

[PC Only] What other relevant PC specs can you share?
AMD Ryzen 7 9800X3D / 4070Ti SUPER / 48 GB RAM

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes

Provide extra information to complete the original description of the issue:
N/A

If relevant, provide additional screenshots/video:
N/A

Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes

Provide extra information to complete the original description of the issue:
N/A

If relevant, provide additional screenshots/video:
N/A

I went through the delete-cloud-saves route a week ago. Pretty much everything you’ve personalised in MSFS2024 gets erased, not just the control settings, it even asks you for your xbox user name again, so it’s an initial reset but probably not a fix (see below).

I went back through setting up stick controls for one aviation category (Gliders), which, for example, includes setting up the joystick axes for ailerons, rudder, elevators. That went ok and it was still ok when I clicked “Apply to all Aircraft” (still don’t know what that actually does).

But yesterday I selected the Cessna 152 (keep it simple). No sign of the stick settings I’d set up for the gliders. So OK, maybe that “Apply to all Aircraft” means something other than apply to all aircraft.

With the Cessna selected but in the ‘Aircraft’ category I go again through the stick controls setup. Just those axes, keep it simple, guessing ‘Airplane’ is just some category of aircraft that includes the Cessna but not the gliders.

Clicked “Apply to all aircraft” and BLAM, the sim CTD’s.

This is within a week of the wipe, still not having set up the controls for anything other than gliders. Understandably I’m reluctant to repeat the cloud wipe.

I’m still interested to know what that “Apply to all aircraft” button is actually supposed to do? For me it honestly seems a ‘do nothing’ | CTD toggle.

2 Likes

It is disturbing that this is listed only as workaround and not listed as feedback-logged or bug-logged . That would indicate there is no intention here of investigating this and/or fixing it.

I have already once had to delete my cloud save to fix this issue and, thus, lost all my control mappings and logbook progress.

Now this issue has returned.

This is unacceptable. This is a CTD bug, and like other CTD bugs, it needs to be logged and fixed with priority. The workaround shouldn’t be the solution.

Wiping user data shouldn’t be considered a viable fix for a crash bug.

ISSUE DESCRIPTION

Description of the issue:

  • Trying to set another plane profile (“None” or a new customized profile) with the button “Assign to all Aircraft” → immediate CTD

Did you experience this issue before you joined the Beta?

  • No

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

  • community empty

FREQUENCY OF ISSUE

  • every attempt

REPRODUCTION STEPS

  1. Plug in a peripheral (my case: VirtualFly TQ3+)
  2. Go to Controls, click on V.TQ3+
  3. Set profile to None
  4. click the gear icon for the menu, Apply to All Aircraft
  5. Boom.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

  • VirtualFly TQ3+

[PC Only] Are you using Developer Mode or have you made any changes to it?

  • No

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:

  • Nvidia 572.65, RTX 3090

[PC Only] What other relevant PC specs can you share?

  • 5900X 64Gb

MEDIA

Log Name:      Application
Source:        Windows Error Reporting
Date:          3/4/2025 6:32:55 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      5900x
Description:
Fault bucket 1594121740748881558, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.3.24.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.3.24.0
P7: 00000000
P8: c0000005
P9: 00000000031a7dab
P10: 

Attached files:
\\?\C:\Users\smitty\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4278.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44F9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4529.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4537.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4557.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_c43ecd1343197fc5b196f73256142996a847c58_4cb5a560_e123e501-d605-4e14-b4c9-f23814f4ab54

Analysis symbol: 
Rechecking for solution: 0
Report Id: 89b3f065-01a2-4d40-995c-1c5abdcc7352
Report Status: 268435456
Hashed bucket: d6430d82e211ffb5461f7546f6107e96
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-03-04T23:32:55.5785565Z" />
    <EventRecordID>160824</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>5900x</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1594121740748881558</Data>
    <Data>5</Data>
    <Data>MoAppCrash</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe</Data>
    <Data>praid:App</Data>
    <Data>1.3.24.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator2024.exe</Data>
    <Data>1.3.24.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000031a7dab</Data>
    <Data>
    </Data>
    <Data>
\\?\C:\Users\smitty\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4278.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44F9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4529.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4537.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4557.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_c43ecd1343197fc5b196f73256142996a847c58_4cb5a560_e123e501-d605-4e14-b4c9-f23814f4ab54</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>89b3f065-01a2-4d40-995c-1c5abdcc7352</Data>
    <Data>268435456</Data>
    <Data>d6430d82e211ffb5461f7546f6107e96</Data>
    <Data>0</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          3/4/2025 6:32:53 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      5900x
Description:
Faulting application name: FlightSimulator2024.exe, version: 1.3.24.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.3.24.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000031a7dab
Faulting process id: 0x83c8
Faulting application start time: 0x01db8d5d2ee74ce1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: 89b3f065-01a2-4d40-995c-1c5abdcc7352
Faulting package full name: Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-03-04T23:32:53.6929378Z" />
    <EventRecordID>160823</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>5900x</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator2024.exe</Data>
    <Data>1.3.24.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator2024.exe</Data>
    <Data>1.3.24.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000031a7dab</Data>
    <Data>83c8</Data>
    <Data>01db8d5d2ee74ce1</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe</Data>
    <Data>89b3f065-01a2-4d40-995c-1c5abdcc7352</Data>
    <Data>Microsoft.Limitless_1.3.24.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Above post moved from SU1 beta category as this is not unique to SU1 Beta.

1 Like