Im starting to experiment with my own setup as compared to using snippets in the past. I use the honeycomb yoke and throttle, fyi. 

I have a basic question on how spad works.... it does not actually complete the bindings within MSFS, correct? meaning, when I go to the controls menu, will all of the changes be reflected there? 

If this is the case, can I just wipe all bindings that exist in the MSFS controls menu? I have had some conflict issues that was unaware of so I figured if spad doesnt mess with the in-sim control menus at all, I can just delete all of them in MSFS. 

 

thanks!

5 minutes ago, avi8tir said:

this is the case, can I just wipe all bindings that exist in the MSFS controls menu?

Yes. You will need to do this. I have blank profiles for all my controllers in MSFS to avoid conflicts. I have Spad manage all my bindings in its app.

7 minutes ago, BrammyH said:

Yes. You will need to do this. I have blank profiles for all my controllers in MSFS to avoid conflicts. I have Spad manage all my bindings in its app.

Is there an easy way to wipe everything in the sim instead of going one-by-one?

Not that I know of. 

I suggest keeping the yoke’s X and Y axis bindings as it is far easier to adjust the sensitivity curves in MSFS than trying to do this in Spad.Next. 

Edited July 9, 20241 yr by petz_e

1 hour ago, petz_e said:

I suggest keeping the yoke’s X and Y axis bindings as it is far easier to adjust the sensitivity curves in MSFS than trying to do this in Spad.Next. 

This. Much easier in MSFS, I have a few profiles for different types of aircraft with just these two axes and camera views set up. The rest in Spad.next.

I also learned to make a simple image of all controllers for each aircraft. All buttons and axes have their numbers/letters and function/command written next to their pictures. And of course, I write the name of profiles for each controller that are in use by each particular aircraft. Makes life much, much easier! 🙂