TBM loses bindings every load
-
With the excellent Echo19 sound pack for the TBM I dusted off my TBM for a series of flights. It was a real joy, except I experience the same issue. First thought: it must be the sound pack or the liveries that came with it! But no, with or without, I loose my TBM 850 MSFS2024 binding profiles (which are all (almost) empty as I use SPAD.neXt). I just tried the Rockwell Commander 114 and found no issue, all binding profiles were there.
-
Have you tried loading the plane without starting Spad, to see if your sim bindings are there? I ask because I use a combination of Axis and Ohs and sim bindings (my elevator & aileron axes as well as any electrical trim switches are bound in the sim), and I don't have this problem with the TBM -- everything is remembered.
-
It won't save the profile you have selected - at least for me. No matter what I do it goes back to the original setting. So each time I have to go in and select the profile for my various peripherals - it's a pain. I'm considering taking everything out of msfs and putting it all into spad.next.
-
It won't save the profile you have selected - at least for me. No matter what I do it goes back to the original setting. So each time I have to go in and select the profile for my various peripherals - it's a pain. I'm considering taking everything out of msfs and putting it all into spad.next.
@MiRexer That is exactly what I did for the Honeycomb Bravo and my Virpil rudder pedals. And it doesn't make any difference, MSFS2024 just chooses it's own profiles, mostly the standards but also some profiles for different aircraft and does so consistently.
With or without SPAD.neXt makes no difference.
I deleted all TBM 850 profiles, removed the add-on entirely, restarted PC, reinstalled the aircraft, started the sim, made new profiles for my peripherals, did a short flight, ended the Sim the proper way and was hoping for the best. But ... nothing changed, the same (wrong) profiles were activated #@@!!!%#
I'll try to think of something else. If that doesn't come up, I will contact Support.It looks like MSFS2024 does not recognize the airplane, and falls back to some other profile.
-
Have you tried loading the plane without starting Spad, to see if your sim bindings are there? I ask because I use a combination of Axis and Ohs and sim bindings (my elevator & aileron axes as well as any electrical trim switches are bound in the sim), and I don't have this problem with the TBM -- everything is remembered.
@RPGamerous Yes, SPAD.neXt works as it should, all controls are bound correctly.
-
I was going to try to edit whatever profile it's coming up on and remove all bindings from that profile. Same thing happens to me on some of the Baron liveries - not all but some. I've tried everything I (and AI lol) can think of. I've just tried to make it a habit to check all the profiles in msfs whenever I load a new plane.
-
I'm afraid that's not going to fix the problem for me, because the Sim falls back to a standard profile for keyboard, Alpha and Bravo causing binding conflicts.
Your idea of removing all (unwanted) bindings from whatever profile comes up sounds interesting. Also, I'll try a different livery, I never suspected different liveries would been seen as different airplanes. -
Have either of you tried resetting your cloud save? I wonder if a corrupted cloud save could be the culprit.
-
No, I haven't. I'll try. You never know....