Sad to see no profiles for VKBSim Controllers :(

Agree, but until about 6 weeks ago the sim wouldn’t remember the settings/profile and every time a new Alpha was released I had to start from scratch. So, at least you should no longer have that frustration.

$200 AUD, Im not really inclined to be patient for a fix on things that are basic requirements to sim properly. The Winwing F-18 throttle is a paperweight with this sim as it does not recognise all of the various axis’ on the throttle, the axis they didn’t pick up is the bloody throttle control. Extremely poor release imo. With a product like this the least you would have though they could do is simply grab any and all axis’ that the USB controller detects…

Did you purchase the sim via Steam?

StangDriver sorted out my throttle issue, not too proud to say that in this case it was my fault not seeing the additional axis’ on the controls page.
I would love to see proper pre populated profiles but at least I can fly now.

What is exactly “StangDriver”? Because i’m not able to see an axis in the config page (GF MkII / SCG).

I’ll be the first to admit that setting up bindings from scratch isn’t the easiest thing in the world the first time. I remember how I felt when I first loaded the sim and my CH Yoke was “blank” :frowning: At least there are now some decent tutorials and guides.

In addition these are my general tips to help with setting up and modifying Controllers:

  • The Control Filter at the bottom of the left part of the screen defaults to “Assigned” which only shows the commands that are currently bound to the selected controller. If the controller doesn’t have default bindings, you won’t see anything! To see all the commands, change the filter to “All”. To see a recommended set of starting commands select “Essentials”. The “Search By Name” will let you narrow down the (very long!) list of commands. Helpful Name searches are “Axis” (see below) and the various views “Cockpit”, “Instrument”, “Drone”, “External”.
  • To bind an input (button, switch, slider, axis) you don’t need to know the actual input number for your controller. MSFS can recognize the input just by activating it during binding. When you click on a command, it will bring up the “binding window”. Click on the space that says “Search By Input” and it will light up. Now physically activate the input on your controller. The space should fill in with the input number. Click “Validate” to complete the binding.
  • All “linear” controls need to use the “AXIS” commands, not the basic commands. That is the issue you are having with your control inputs. This includes control surfaces, engine controls (throttle, etc), brakes, etc. Basically anything that needs proportional input will use the “Axis” version of the command.
  • Unless you have a complex throttle quadrant with multiple throttles, make sure you bind your Throttle to the “Throttle Axis” command and not any of the numbered Throttles. This will control all throttles on multi-engine aircraft simultaneously.
  • A lot of the MSFS default controller profiles use the “Cockpit Quickview” commands which snap back to center. The secret to smooth panning around the Cockpit is to use the “Cockpit Look” commands. Make sure you delete any currently assigned Cockpit View commands for the Hat and then create new bindings using “Cockpit Look”. Depending on your hat, you can map 4 or 8 directions.
  • You can actually access and change Control bindings while inside the live sim (use Esc to get to the main menus). This is helpful if you are trying to fine tune or debug things.
  • You can create multiple binding Profiles for each of your Controllers. This is helpful if you want to map your controls differently for different aircraft. It is also useful if you need to adjust the Sensitivity settings differently for different aircraft. Just make sure you select the correct Profile for each session.
  • I have not used any external controller management or calibration applications or drivers. If you do, your mileage may vary! For sure any control input assignments you make outside MSFS will not carry through inside the sim. The CH Manager application has caused problems for some users of CH products.
  • Adding an Xbox Game Controller (wired or wireless) makes controlling the Drone Cam and Slew really easy and intuitive! MSFS immediately recognizes it and sets up all the bindings by Default.

If you need more help or have other specific questions, let us know! Rick

1 Like

Negative, windows store

So today, out of the blue it suddenly recognized my VKB black box with the pedals, but my saitek throttle quadrant is no longer seen. Does MSFS have a limit as to how many game controllers it can see?

Do not think so. It can see my XBox controller, steering wheel, VKBsim joystick and Logitech throttle quadrant all at the same time.

I don’t like to plug and unplug a lot of my equipment. I fried a Warthog throttle and it makes me a little gun shy, so I have my full DCS set up plugged in including a Virpil and Thrustmaster stick, a Warthog throttle ,2 MFD panels, VKB rudder pedals, 2 button boxes, an A-10 UFC, and then my Logitech GA sims stuff, 2 throttle quads, 1 switch panel and a yoke. I’m just wondering if it’s all too much for FS to detect and it just takes the first 10 it finds or something.

It may have changed in the release build, but there used to be a limit of 5 peripherals.

https://forums.flightsimulator.com/t/five-peripheral-limit/29203?u=amiablegalaxy9

Link must be alpha a can’t read it, but that might be zeroing in on what the issue is

Apologies. I hadn’t accounted for the restriction. Glad I was of modest assistance.

Well I removed all controllers except those I use for the sim and they were all recognized and functioning. If there’s going to be a limit, I would like to choose which 5 should be used by the sim, instead of having to unplug other devices

No limit…I have seven devices recorgnised - Stick, Throttle, Switch Panel, Rudder Pedals, 2 x Cougar MFD’s and one DS Spears button box. This is on top of the keyboard and mouse.

Just remember that peripherals can have issues with USB ports. Esp ports on usb pcie addon cards. I always use the rear USB ports that directly connect to the mainboard and quality powered USB hubs.

They work fine in other simulators with them all plugged in, it’s just MSFS2020.

There is no limit…I just plugged in 3 x box controllers (that’s 10 devices), ran up MSFS and all 10 peripherals are there and can be bound!

Sounds like a USB issue to me

Putting a pin here to see if/when VKB support might appear.

I have a VKB Gunfighter Mk.III ‘Modern Combat Edition’ stick and a TWCS throttle (waiting forever for a VKB throttle). I have attempted to divide all attitude controls to the stick and all engine mgmt controls and some important misc. controls (brakes, pov hat, dive brakes, wheels up/down, etc.) to the throttle. This is because all of these controls are done by “feel” while in flight, and the logic helps a lot. I have looked around for bindings that address the large number of misc. controls (switches, navaids, etc) but every time I find somebody’s bindings, the vast majority of the stick buttons are devoted to camera choices. So, I am reduced (probably by lack of imagination) to using the mouse for Garmin selections, magnetos, fuel tank selections, etc.) while still having many unused VKB stick controls - really just because they have have no relation to attitude. This sort of defeats the flexibility of the VKB stick. Has nobody got better ideas for the stick controls than I have seen and have while still maintaining some logical division?