Jump to content
The simFlight Network Forums

Controller mapping


vgbaron
 Share

Recommended Posts

Am I correct in assuming that the mapping of flight controls for individual a/c is still waiting for Asobo to enable various inputs? With the Simconnect fix coming today, I thought I'd revisit controlling my hardware via FSUIPC but if various axes are still inop, it might be a waste of time for now.

I hope you guys get a proper SDK to work with soon, from what I hear, the current one is a mess.

Thanx,

Vic

 

 

Link to comment
Share on other sites

As it looks like I'm going to have a four day weekend  and I have the update, I'm going to dig into mapping my controllers as close as i can gto my p3d setups.

With P3D/FSX using FSUIPC to control all inputs required disabling the joysticks.  How do we get around this in MSFS2020? I haven't found any specific "disable joystick" command.

I am assuming that I can go through each controller in MSFS and set up a null profile and assign that. 

Would this be the correct way to approach using FSUIPC for this? Again I assume that if I leave my current profiles alone and create nulls and assign the as active in sim, there should be no conflicts with anything in FSUIPC and should I want to revert to in sim control, just not run FSUIPC and assign an active (not null) profile.

As usual I am probably overthinking this - I appreciate any suggestions you have.

Thanx,

Vic

Link to comment
Share on other sites

14 hours ago, vgbaron said:

but if various axes are still inop, it might be a waste of time for now.

I think most axes are working, apart from the view (PAN VIEW) and slewing axes. If not, please let me know.

4 hours ago, vgbaron said:

I am assuming that I can go through each controller in MSFS and set up a null profile and assign that. 

You can try that. My devices don't have any default assignments so I haven't investigated this yet. Otherwise, just remove any default assignments that you don't need. You may want to keep some assignments anyway, e.g. for controlling the views.

You should initially try with you existing FSUIPC4/5/6 ini if you have one. Just copy it to your FSUIPC7 installation directory and rename it to FSUIPC7.ini, and copy across any auxiliary files that you may use (.lua, .mcro). Anything using lvars or mouse macros will not work, or anything using P3D specific controls, but you can remap these afterwards. Anyway, worth a try rather than starting directly from scratch.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.