![]() ![]() So a button or axis is either assigned via a MSFS binding, or via FSUIPC. All other yoke buttons and the aileron and elevator axes are assigned through FSUIPC. The only assignments in that profile is for the yoke hat switch - no axis assignments and no other yoke button assignments. ![]() ![]() If you have buttons on your yoke assigned in the MSFS Yoke profile, say to take advantage of the different MSFS camera options, then I would not assign those same buttons to any FSUIPC functions, at least not when using that particular MSFS yoke profile that has the button camera bindings.įor example, I have a MSFS yoke profile for my Fulcrum yoke. Thanks Ark, that was exactly what I asked.īut, should that remaining assignments at the FSUIPC profile you mentioned, eventually collide with those set at FSUIPC, thus it become necesary to clean up all assignments and make a totally empty profile ?Ī button on a controller should only be assigned in one 'place' at one time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |