I assigned buttons via FSUIPC just like I had/have them through FSX itself. When I tried them out, it 'seemed' that I was getting the result as if I had pressed the button twice.

Sooooo.... do I have to remove the button assignments from FSX? What about control axis assignments and calibrations?

Should I delete the yoke, throttle, and pedals (I use CH pedals) from FSX then go into FSUIPC to calibrate and assign the axis to functions? What about the toe brakes? I couldn't find an axis in FSUIPC for those at all.

 

Just a little noob confusion going on here is all.

 

Thanks folks!

I usually delete the default FSX assignments if I suspect that they are interfering with my

FSUIPC4 assignments. I don't believe it is usually necessary however.

 

I always use the "aircraft specfic" setting in FSUIPC4 so that all my

programming is grouped by the aircraft "short aircraft name" in my case.

 

I would examine the assignments you have made to see if you can

find a cause for the 2-press symptom you see.

 

For axis, I just make sure that I delete those assignments from the

list for any controller that I am NOT using to control a given axis.

For instance, I have both an X-45 stick and a Saitek Pro Yoke attached.

I only use the X-45 for elevator and airleron control so I remove

those from the Yoke list. Same with rudder...only enabled via my

CH Pro pedals list.

 

In theory, you can have multiple controllers assigned for a given

axis and FSUIPC4 will react to the one that changes. The last one

to move 'wins'. I'd rather not chance an accidental 'bump' of a controller

axis that I wasn't using. I disable my X-45 throtlle axis and instead

use my Pro yoke dual quadrants. Since I rest my hand on the X-45

throttle to use it's buttons/switches the chance of moving it and overiding

my quad throttles is the type of condition I wish to avoid.

 

 

 Paul

As it turns out, FSX button assignment in addition to FSUIPC assignments DID cause double button presses! Using one or the other works fine but if both have button assignments, both will send button presses to FSX... so, a button to toggle the landing gear, for example, assigned in both FSUIPC and FSX will not raise the landing gear because the program receives two button presses.

It doesn't matter, as far as I can tell, which one you use to assign buttons as long as it is only one of them.

Now, I gotta figure out the axis calibration thing! It's all working but I kinda want to refine how the yoke axis respond a bit. Not sure how to get FSUIPC to override the FSX (windows) calibration...I'm sure it's in the manual...I just ain't deciphered it yet.

i use FSUIPC for all of my controller functions so i have the joystick disabled in FSX.

Toe brakes are called Right and Left brake in FSUIPC axis. They are there all right !

Got em..finally. I actually did disable the joysticks in FSX and assigned everything through FSUIPC. Still have to tweak the null areas a bit I think and maybe the slopes. I'm not a fan of how the hat switch now works... too much delay before it starts to repeat and move the view...

 

 

I'm not a fan of how the hat switch now works... too much delay before it starts to repeat and move the view...

 

The hat switch is the only thing on any of my controllers that I assign through FSX.  FSUIPC just isn't as smooth.  Absolutely everything else, however, is assigned though FSUIPC.  I couldn't handle the variety of controller I use and switch between without it.

I leave the following "legacy" keystrokes set in FSX controls gui:

 

2-D Cockpit View

Aircraft Labels

Altimeter reset

Attach/Detach Jetway

Brakes (set parking)

Coordinates

Doors - select (open/close)

End flight

Engine (auto shutdown)

Engine (autostart)

Eyepoint reset

Flight controls (center all)

Fuel dump

Joystick (on/off)

Keyboard (display/hide)

Locked Spot View

Mouse - view direction (on)

Mouse - view direction (on)

Mouse - view direction (on)

Panel window 1

Panel window 2

Panel window 3

Panel window 4

Panel window 5

Panel window 6

Panel window 7

Panel window 8

Panel window 9

Pause

Pushback

Reset flight

Select item 1

Select item 2

Select item 3

Select item 4

Simulation rate (select)

Slew mode (on/off)

Sound on/off

Spoilers (arm)

Spoilers (extend/retract)

Vew (next category)

Vew (next in current category)

View (close selected window)

View (previous category)

View (previous in current category)

View (set to default - 1x)

Virtual Cockpit (shortcut)

 

The rest of the keystrokes, along with all the axes, are assigned in FSUIPC.

 

Cheers,

Dirk.

To be clear, there's nothing wrong with leaving assigned keystrokes in FSX.  It makes life a lot easier if you're always able to fall back to the keyboard if some button you've assigned on your yoke isn't doing what it should.  It's purely the joystick buttons and various axis that can (and should) be completely reassigned though FSUIPC.

I make my xls tables to make sure the keystrokes/buttons are not double-assigned in FSUIPC and FSX as it can create even all kind of problems.  

 

Dirk.

Now, once you've done that, plug in a 2nd keyboard, assign keys & group functions & stick on coloured labels according to functions.Remember

 that this duplicates the 1st keyboard. (my laptops, in my case)