I've noticed that whenever anyone asks for advice about setting up controls or assigning controller buttons, the majority of replies seem to advocate using FSUIPC from the outset to configure control hardware. Why not start by troubleshooting what they've done within FSX? Although I have FSUIPC (needed for other reasons), the full version is an expensive option when compared to just using FSX (free). I've got a Microsoft Force Feedback 2 joystick (definitely the best joystick for FSX), a Saitek throttle quadrant and CH Pro Pedals and they were all set up successfully using just the internal FSX system. None of the controllers took more than a few minutes to set up. I've used a number of different joysticks and all of them were set up easily without using FSUIPC - was I just lucky?

What you say is true. However if one flies a number of different aircraft, using FSUIPC allows the user to have a different button function or axis control or calibration for each different aircraft in their hanger.

 

I use CH throttle quadrant and in a 747 the four throttle levers act as throttle levers, but in a twin engine the outer throttle levers can now be used for condition levers or fuel cut-off etc. The toggle buttons on the quad control autopilot MCP function such as changing altitude window or selecting ALT HOLD or VNAV. I can set these up differently for any aircraft I fly. No need to adjust any controls in the sim as FSUIPC knows the assignments whenever a specific aircraft is loaded.

 

No two aircraft respond the same to hardware axis inputs so using FSUIPC means every aircraft has its axes calibrated to suit.

 

Mouse macro function enables some controls to be assigned that cannot be done through the sim's assignments. Having an assignment for when a button is released as well as pressed is also a great advantage. So when i press a button to switch off the autopilot, the release of that button also cancels the aural warning.

 

I could go on, but the point I am trying to make is that FSUIPC offers far greater flexibility and control than using the "one size fits all" that FS9 or FSX native controls give you.

I can see your point about different assignments for different aircraft. That didn't really occur to me as I leave all of the assignments the same to make them easier to remember. However, would it not be more straightforward for someone new to the hobby to be guided through sorting it out from within FSX? I'm still puzzled as to why some people seem to struggle to set up their controllers at all while others with the same hardware (me included) seem to be able to just plug-and-play.

 It has to be best to have a good understanding of how FS controls work, yes.

 It has to be best to have a good understanding of how FS controls work, yes.

Peter, I have an issue maybe you know about how to solve if it's possible.

 

I have the right-most lever in the Saitek throttle quadrant assigned to Mixture for the RA Duke.  It appears one can change the range of travel in the axis so that the lowest value is above the cutoff value at the bottom, but for the life of me I can't figure out how to do it.   Have you tried and succeeded in setting this up, limited the range on the low end of an axis assigned in FSUIPC?  I can tell it appears to be an option but it's just not working.

 

 

However, would it not be more straightforward for someone new to the hobby to be guided through sorting it out from within FSX?

 

But Normal FSX controls cannot be set up to recognise different aircraft.

Say you set up your throttles for a piston twin with throttle, prop and Mixture then  switch to a turbine twin you will want them set up differently.

This is where Fsuipc profiles comes in handy, it automatically recognises the aircraft loaded and configures your hardware automatically.

So unless you just love setting up your controls every time you load a different aircraft type you really do need Fsuipc

You've convinced me to give it a try.

I've noticed that whenever anyone asks for advice about setting up controls or assigning controller buttons, the majority of replies seem to advocate using FSUIPC from the outset to configure control hardware. Why not start by troubleshooting what they've done within FSX? Although I have FSUIPC (needed for other reasons), the full version is an expensive option when compared to just using FSX (free). I've got a Microsoft Force Feedback 2 joystick (definitely the best joystick for FSX), a Saitek throttle quadrant and CH Pro Pedals and they were all set up successfully using just the internal FSX system. None of the controllers took more than a few minutes to set up. I've used a number of different joysticks and all of them were set up easily without using FSUIPC - was I just lucky?

 

I agree with you.  I use to setup my controllers within FSX, but that's when I had Windows XP, VISTA, and/or WIN 7.  Worked just fine for my needs.  When I purchased my WIN 8 system, I continued to get controller disconnects.  I tried everything I could think of, along with the help of a plethora of others on the forum, to solve the problems.  No luck.  So, I decided to configure my controls with FSUIPC.  I've not had one disconnect since doing that.  Next step is to learn to use FSUIPC in configuring the controls for different a/c. 

 

Safe Flyin'

Rod

A few other concrete examples...

 

I have dual Saitek quadrants configured as TT PP MM.  When I bought the A2A 172, I discovered that it was the only single I own that wouldn't recognize Mixture1 as being the single mixture control - it required Mixture.  Enter an FSUIPC profile for the A2A 172 and the mapping is automatically changed when I load the A2A plane.

 

I have the Carenado 210, which can be a very nice plane after a few mods.  One of the issues is that the elevator control is a bit abrupt.  Many users back off elevator effectiveness in the .cfg file to compensate, but this can make for reduced authority in landing.  Instead, I put in a slope in FSUIPC which makes my Saitek yoke less sensitive in the center of its range, but more at the edges.  Again, a profile makes this automatic when I load the 210.

 

And finally, I had a specific problem with my Saitek yoke which required an unplug and recalibration in the Windows calibration panel following every reboot.  This got really old.  By controlling through FSUIPC, this problem was eliminated.  I still occasionally have to unplug and replug following a reboot, but the calibration stays.

 

You're quite right that FSUIPC is often offered as a fix when it doesn't need to be.  But that doesn't mean it doesn't offer some very real advantages for even basic control mapping and calibration.

 

Scott

I use FSUIPC for a number of functions, although nothing too sophisticated. But here's an example of how I use the power of FSUIPC. I use a CH Pro Throttle, a CH Yoke and CH pedals. The default throttle axis on the Yoke is therefore not required and in fact should be disabled so as not to conflict with the Ch Pro Throttle. So I use it to toggle the landing gears UP and DOWN using FSUIPC's Axis Assignment using three ranges: Range 1 - Gear Down, Range 2 - No action, Range 3- Gear Up. For me, this provides for a more realistic cockpit operation. See page 41 of FSUIPC's User Manual.

 

Regards,

 

JJ

Peter, I have an issue maybe you know about how to solve if it's possible.

 

I have the right-most lever in the Saitek throttle quadrant assigned to Mixture for the RA Duke.  It appears one can change the range of travel in the axis so that the lowest value is above the cutoff value at the bottom, but for the life of me I can't figure out how to do it.   Have you tried and succeeded in setting this up, limited the range on the low end of an axis assigned in FSUIPC?  I can tell it appears to be an option but it's just not working.

 

Noel, I am not sure i understand exactly what you are trying to achieve. Can you elaborate ?

Let's say the full range of values an axis assigned to Mixture is -10200 to +10200.   If I bring the lever all the way down to -10200 the engines shut down.  This happens at about -9500.   I was hoping to define the bottom of the physical range (i.e. , how far the lever moves fully pushed forward to fully pulled backwards) such that the lowest value is now -9000, instead if -10200.  Of course, I can manually NOT pull the lever all the way backwards past -9500 value to the hard stop of -10,200.  I was just hoping to put an artificial stop so that it thinks it's fully pulled back but only gets to -9000 value, i.e. just above engine shutdown.  That's about as elaborate as I can make it!!

That's easily done in the Joystick calibration page using the Min And Max buttons

The range normally should run from 16384 (max) to -16384 (min), just pull your lever back to a value short of the minimum and press the corrosponding button in Fsuipc.

Alternativly just edit the values in your Fsuipc.ini by hand

That's easily done in the Joystick calibration page using the Min And Max buttons

The range normally should run from 16384 (max) to -16384 (min), just pull your lever back to a value short of the minimum and press the corrosponding button in Fsuipc.

Alternativly just edit the values in your Fsuipc.ini by hand

Well, I'll try it again but I don't think it will work.  What I see happening is:  you set it at -9500, but when you move the physical lever, it simply just keeps going to -10200.  Maybe I'm not saving it somehow first?  Or sending the values to P3D V2.1?

 

Also, if I hit RESCAN and move this lever, FSUIPC clearly senses it and reports the full range of -/+ values.  But, despite the fact I have this axis deselected in P3D V2.1, when I physically move the lever the virtual lever in the VC doesn't budge--it's just not connected.  And that seems odd since when I run the AXIS ASSIGNMENT in FSUPIC it is clearly sensing the physical motion predictably.   

Noel

 

I understand now. You want the OUTput from FSUIPC to send a value no lower than -9500.  I am not sure if that can be done. I suggest you post on Pete Dowsons support forum http://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/