Controls mapping

[RPN]

Is it possible to map the mixture lever of the CH products Yoke to a condition lever?
Richard

[HardCorePawn]

You sure can...

are you using FS9 or FSX? and are you trying to map using the CH Manager? FSUIPC? or the built in FS control settings?

[RPN]

QUOTE (HardCorePawn @ Jul 1 2008, 09:52 PM) <{POST_SNAPBACK}>

You sure can...

are you using FS9 or FSX? and are you trying to map using the CH Manager? FSUIPC? or the built in FS control settings?

I am using FS9,
I have CH Manager but don't use it,
I have a registered copy of FSUIPC,
The FS control settings don't seem to have any provision to map the condition lever.
FSUIPC might be the best bet.
Many thanks for your quick response
Richard

[Chairman]

Which plane ? I seem to recall reading somewhere that the condition levers in the atr72-500 were only accessible by mouse ...

That said, you should be able to do pretty much anything with the switches on the yoke. With reg fsuipc you can make any switch produce any sequence of keystrokes, so anything that can be done in FS with your keyboard can be assigned to a yoke switch.

Gary

[RPN]

QUOTE (Chairman @ Jul 2 2008, 10:54 AM) <{POST_SNAPBACK}>

Which plane ? I seem to recall reading somewhere that the condition levers in the atr72-500 were only accessible by mouse ...

That said, you should be able to do pretty much anything with the switches on the yoke. With reg fsuipc you can make any switch produce any sequence of keystrokes, so anything that can be done in FS with your keyboard can be assigned to a yoke switch.

Gary

Thanks for that. I just thought that it would be ideal to use the mixture lever as the condition lever.
Richard

[RPN]

Solved this by this method
Open the Axis Assignment tab in FSUIPC.

Click the 'rescan' button and move the condition lever, that should change the value in 'joy#' and 'Axis#' to show FSUIPC has identified the control you moved.

In 'Type of action' select 'Send to FS as normal axis', tick the first box and from the list select 'Axis Mixture Set'. That should set the condition lever to act as a mixture control, all you need to do then is calibrate it in the 'Joystick Calibration' tab.

Also note that you can, if you wish, make that axis assignment specific to the current aircraft or to all aircraft.

[Chairman]

FSUIPC and aircraft specific settings are a wonderful thing.

On my TQ, lever three magically turns from a pitch level into a throttle when I'm in a 727, and something I'm particularly happy to have achieved, no matter which of my usual planes I'm in (767, 747, dc3, C172, B200, 727)
- switch 1 opens the captain's panel
- switch 2 opens the 1st officer panel
- switch 3 opens the overhead or switch panel
- switch 4 gives me the radio stack
- switch 5 gives me autopilot or the mcp/eicas as appropriate
- switch 6 gives me an FMC in a new airliner, or the flight engineers panel
- switch 6 up gives me the throttle quadrant

Took a bit of doing but it works a charm.

Gary

[HardCorePawn]

FSUIPC is great...

The only downside I have found to FSUIPC, is that (at least in FSX), each repaint is classified as a 'different' aircraft... so if you tick the 'aircraft specific' checkbox, it will only work for the current repaint for the current aircraft.

Which can be a pain if you have several repaints for a specific aircraft...

Means you either have to map the controls for each repaint () or you have to edit the FSUIPC.ini file and copy+paste the controls for each repaint...

[RPN]

QUOTE (HardCorePawn @ Jul 4 2008, 09:30 PM) <{POST_SNAPBACK}>

FSUIPC is great...

The only downside I have found to FSUIPC, is that (at least in FSX), each repaint is classified as a 'different' aircraft... so if you tick the 'aircraft specific' checkbox, it will only work for the current repaint for the current aircraft.

Which can be a pain if you have several repaints for a specific aircraft...

Means you either have to map the controls for each repaint () or you have to edit the FSUIPC.ini file and copy+paste the controls for each repaint...

Yes thanks for that I will keep it in mind.
Richard

[Chairman]

QUOTE (HardCorePawn @ Jun 30 2008, 09:30 AM) <{POST_SNAPBACK}>

FSUIPC is great...

The only downside I have found to FSUIPC, is that (at least in FSX), each repaint is classified as a 'different' aircraft... so if you tick the 'aircraft specific' checkbox, it will only work for the current repaint for the current aircraft.

Which can be a pain if you have several repaints for a specific aircraft...

Means you either have to map the controls for each repaint () or you have to edit the FSUIPC.ini file and copy+paste the controls for each repaint...

Golly, you do like to do things the hard way. Yes you need to Edit fsuipc.ini but you don't add things to cover the repaints, you delete things.

FSUIPC will apply the best match it can find in the .ini file when looking for aircraft specific settings. So, using the PMDG744 as an example, set up any paint of the plane the way you want it using the aircraft specific settings, this will create repaint specific entries in the .ini file like [Axes.PMDG - 747-400 GE CF6 Engines Air Atlanta Icelandic]. Then delete the repaint info off the end, so you're left with just [Axes.PMDG - 747-400] and you should find that, as the best match in the .ini file, those settings will get used for any paint of the Queen you fly. Make sure you do it to all the sections that deal with the 747 though, else some parts of the aircraft specific settings will only work with some repaints

Cheers
Gary

[HardCorePawn]

Thx for the headsup... that is about to make my life much easier... seriously, why is this not mentioned anywhere?!?!?

[Chairman]

Because the documentation for fsuipc was written by the same geek who programmed it. Programmers should never be allowed to write their own manuals It's awesomely powerful software but the manual is errr basic. If you want to know how to do anything advanced you have to go to the support forum, which is a problem without knowing what it's capable of !

FSBuild has the same problem.

Gary

[HardCorePawn]

QUOTE (Chairman @ Jun 30 2008, 10:39 PM) <{POST_SNAPBACK}>

FSUIPC will apply the best match it can find in the .ini file when looking for aircraft specific settings
<snip>

hmmmm this did not seem to work very well

I created a setup for the default FSX Boeing 737-800, using the 'Boeing' skin which was recognised by FSUIPC as "Boeing 737-800 Paint 1"... I then edited the FSUIPC.ini file, and changed the section names to:

[Axes.Boeing 737-800]
[JoystickCalibration.Boeing 737-800]
[Buttons.Boeing 737-800]

but if I selected another skin, like the Orbit Airlines one, it did not recognise the setup

So I went to the support forums, and found a post by the FSUIPC author, who notes that he put it in as an option in the .ini file... you need to change ShortAircraftNameOK to 'Yes'... by default this is set to 'No'...

So yay... all my 737's are working as per my control setup... yay!

Now I just have to figure out how to fly it properly!

[Chairman]

Phew, you had me worried there for a minute !

Of course the real fun will start when you want to change something in the setup ......

Gary

[HardCorePawn]

QUOTE (Chairman @ Jul 8 2008, 12:49 AM) <{POST_SNAPBACK}>

Phew, you had me worried there for a minute !

had you worried?? I was looking at having to copypasta a whole heap of settings!!

QUOTE

Of course the real fun will start when you want to change something in the setup ...... [/quote]

Not really... I noticed that when I loaded up another paint and went into FSUIPC and ticked the 'aircraft specific' box, it was still identifying as 'Boeing 737-800', regardless of which paint it was using.

So it would appear that any changes will affect all the paints