Thebuttons in VA are actually PTTs not radio select buttons according to the Vaicom manual, in reality they do both. The Vaicom PTTs execute the Plug In and the Plug In also starts/stops VA listening.
2. Define your PTT button with two different functions (one for press and one for release) to read that variable and then conditionally invoke one of the VAICOM API commands that simulate a TX press or release. See the API section of the manual for details.
For example, you could program buttons 1 and 2 to "select" radio 1 or 2 (respectively) by setting a variable equal to the string "TX1" or "TX2" (respectively), but do nothing else. Then define a button 3 press to send ptt.hotkey.TX1.press or ptt.hotkey.TX2.press to VAICOM depending on the setting of the variable. You would also define a button 3 release function to send ptt.hotkey.TX1.release or ptt.hotkey.TX2.release. Then button 1 or 2 would select TX1 or TX2 but the TX function would not be invoked until you pressed button 3.
I have just upgraded my MP and now when I set all of the channel controls for my Joystick I hit save. If I close the joystick window and then open it again all of my settings are back at the default settings.
I am using Pixhawk Rover with latest build ( v3.0.1), MP latest build (1.3.41 build 1.1.6110.31287). I can connect the MP to the Pixhawk, telemetry is accurate and functions, I can ARM and DISARM through MP, I can open the Joystick settings window and change the settings, mapping the rudder and throttle, also mapping/setting the mode change buttons. As soon as I hit enable the output bars freeze and the joystick does not engage with the boat. Once I disable the Joystick the output bars become responsive to the Joystick.
Ok, I found one of my laptops with an older build of MP (1.3.39 BUILD 1.1.6038.12291) fired it up and connected to my boat (pixhawk, rover 3.0.1, over 3DR radios), all worked fantastically, my settings were saved and everything functioned as expected. When I hit enable, joystick becomes live and the boat responds - throttle, steering, mode settings etc.
There are quite a few peripherals that do not have default control Profiles (bindings) in the current version of the sim. To help answer your question, we need to know a couple of basic things first (as noted by @SteepFarez):
There are a lot of Saitek threads already in the Peripherals section of this Forum and you may find some specific help there. In general, here are some resources and guidelines to help you work through the process of setting up controller bindings. These are the ones I recommend:
In addition here are some general hints and tips. I know the Control setup interface seems intimidating, but it actually works well once you understand the process and is really powerful in helping you set up your controls exactly the way you want!
These are two tools included in the Ubuntu repositories that I have not tested recently (I found these when looking for other options). The first of the two, jstest-gtk, is a graphical tool, and joystick is a set of commandline utilities.
There is also an application called jstest-gtk, which seems to do something like that, I post here a screenshot and the link for you: -gtk (This software may need to be compiled in order to make it work)
I'm using Ubuntu 13.04 and have Logitech Rumblepad 2. And what I did was installing these, joystick and jstest-gtk. It's already been calibrate to default and joystick device is detected right. Just plug and play.
I am currently using qjoypad for mapping keys (even the mouse) to a Logitech Gamepad F310. It's working well for games that are designed with only keyboard and mouse controls in mind. It seems to require being run from cli as qjoypad --notray. It does use a GUI.
That's the same exact model I use. From the first screen in KSP, open the 'Settings' menu, then the 'input' section. Click the button that says 'Staging UI' and the right side of the menu (under 'Axis Bindings') should now have some options. Click on the long grey bar labelled 'Pitch Axis', and then (very carefully) move your joystick forward or back. Now it should be bound to that axis. Do the same for other axis, including setting the little paddle to control the throttle (You're going to love how precise your throttle control is with that, by the way).
You may have to come back to invert an axis or adjust the sensitivity or dead band (I find my self lowering the sensitivity and raising the dead zone a little). As for other buttons, you can set them however you wish, using the same method (click a grey bar, then mash the joystick button you want to assign to it). I find value in setting joystick buttons 3 & 4 to RCS and SAS toggle, respectively, and the trigger for temporarily toggling SAS on/off. Some handy functions for buttons down on the base are map-view, stage, abort, brakes, or whatever you find yourself using most frequently.
Hey I got one too. If I remember correctly you also have to invert the throttle axis to match the markings on the controller. Also keep in mind the estimated burn times will be off of you're using the throttle slider.
On an interesting side note ambidexterity has it's plus's and minuses. Plus I can use my mouse with my left hand because minus I didn't think about the joystick being left or right handed I've ended up binding it to translation and kept WASD as rotation. This should making docking faster and easier.
I'm having exactly this issue. Clockwork_werewolf's fix didn't work, though my buttons mapped to keys work fine (which makes sense; I think it's talking joystick to USB Overdrive, and USBO is talking keyboard to KSP.)
This is an old, old Saitek 3D USB. I just went on an extensive, two-day search for it so I could fly my VTOL, and now it's all for nought. I've got another very similar one that I'll try, but I don't have much hope.
I suggest using Advanced Flyby-Wire, since the stock controller detection is broken and doesn't work. I purchased a remote control about a year ago and I tried to get the analog sticks to map, but it wouldn't detect my inputs so I gave up on it. Then I bought a new SNES PC remote and got that mod and now it works.
That being said, A3 does support control schemes for several controllers. But, I much prefer to set my own controls up, especially with Arma, because the game actually has the ability to set every button on my X52-Pro to doing something.
Anyway, if you do choose to use a scheme, go to Options > Controls > Controller tab, then select your X52 from the customizable controllers list. Once it's highlighted click customize, and then you can change the sensitivity and dead zones for your control axes. After doing that, click Unmap, (warning!) this will delete all the buttons you've set for the controller. Next click schemes and browse about for one that you want to try, then click Map.
After you've chosen a scheme, I would still highly recommend going through each of the control pages under keyboard controls (especially the ones for vehicle, helicopter, and plane) to familiarize yourself with the controls and change any that were mapped from the scheme that you don't like.
Not sure I understand: I bought an ordinary 'Thrustmaster T-FlightstickX' joystick early this year and simply plugged it into my PC and can fly planes and helis in AA3 just fine without any manual key adjustments of any kind.
Hi everyone,
I have the CH Pro Pedals & CH Products Flight Sim Yoke for X-Plane 11.41r1 (build 114100 64-bit).
Every time I do a joystick configuration/calibration, it never saves upon exit. I have tried to ensure the default X-Plane folder is set to read/write instead of read only to no avail. I've disconnected, restart and reconnected my USB ports to no avail. I've tried saving in different profiles and that doesn't work.
Each time I go back, the settings are still red instead of blue which is frustrating because I cannot fly properly.
Help please?
Hi everyone,
I have the CH Pro Pedals & CH Products Flight Sim Yoke for X-Plane 11.41r1 (build 114100 64-bit).
Every time I do a joystick configuration/calibration, it never saves upon exit. I have tried to ensure the default X-Plane folder is set to read/write instead of read only to no avail. I've disconnected, restart and reconnected my USB ports to no avail. I've tried saving in different profiles and that doesn't work.
Each time I go back, the settings are still red instead of blue which is frustrating because I cannot fly properly.
Help please?
Take a look at the before/after pictures. Immediately after exiting the calibration screen with everything in blue, it reverts to everything being in red after I go back into the calibration screen. This is also confirmed when I try to operate any aircraft.
Why are you going "Back" into the calibration screen? Once you calibrate your controls,and click "Finish" you are done. If you go back to the calibration screen and click on "Calibrate" they will be red again because it thinks you want to start over.
That sounds plausible. I used the default install? I also copied the joystick and keyboard files from xp11 into the new xp12 folder and I can select the but the settings do not change. After I do a calibration and save with a new name I can select the new name but cal is not like I saved it. Any ideas.
Anytime you copy config files from one version to another, you're inviting trouble. As you can see, it would have been easier just to re-map the axis and buttons from scratch. If that is the issue, you can fix it by erasing the content of your X-Plane Output/preferences folder. XP12 will create new default files the next time you open and close it, and you will have to recreate your joystick and keyboard profiles.
Otherwise, you can attach your XP log.txt file to your next post so that someone familiar with Windows OS can verify that you did not install it in a reserved folder path. I think that the desktop is the preferred and default install location, but every app is trying to get onto that prime real estate.
3a8082e126