Calibrating in Windows or CH Manager

[soldano]

I am using CH Yoke, Pedals and Quadrant.- In FSX I disabled the controls and FSUIPC is in control of all axes.- I think that the joysticks must be primarily be calibrated in Windows, but I noticed that the calibrating facility is not adequate for some axis, (i.e toe brakes and the left pair or levers of the quadrant) and my question is: Is it convenient to install the CH Control Manager and use it only for the calibrating routine instead of the Windows XP facility ?.-

Thanks

[Pete Dowson]

I am using CH Yoke, Pedals and Quadrant.- In FSX I disabled the controls and FSUIPC is in control of all axes.- I think that the joysticks must be primarily be calibrated in Windows, but I noticed that the calibrating facility is not adequate for some axis, (i.e toe brakes and the left pair or levers of the quadrant)

If you assigned all the axes via FSUIPC, you must also calibrate them in FSUIPC. All you really need beforehand to do is ensure the initial windows driver calibration is adequate to allow the full range to be used and to make sure the centre (for those axes with centres) is close enough to where it should be. After that the precise calibration, and response curves, can be set in FSUIPC.

..and my question is: Is it convenient to install the CH Control Manager and use it only for the calibrating routine instead of the Windows XP facility ?.-

Ah, sorry, I don't know CH Control manager. Maybe someone else can advise there -- but did you refer to the "FSUIPC Guide for CH Users " sticky near the top of this Forum?

Regards

Pete

[soldano]

I installed the CH Control Manager, and used it only for calibrating the controls, the result was a mess in my FSUIPC settings, I had to reset all from scratch, which was very dificult and imposible in certain cases due to some strange behaviours.- I.e, I couldnt assign the Lear as aircraft specific as each time I opened the FSUIPC screen, the box appeared unchecked, other aircraft specific controls need constantly to be recalibrated, some axes couldnt be assigned, etc etc.- So I uninstalled the CM and replaced the FUIPC.ini with the previous one I had fortunately backuped, and now every thing is OK.-

It confirms what was said in other threads about some incompatibility between the CH Control Manager and FSUIPC.- It is a pity because the CM provides a better calibration facility for the CH USB controls than Windows.-

[Pete Dowson]

I installed the CH Control Manager, and used it only for calibrating the controls, the result was a mess in my FSUIPC settings

I have no idea how any separate program can make a mess of FSUIPC settings.

I had to reset all from scratch, which was very dificult and imposible in certain cases ...

It is never impossible to reset anything in FSUIPC -- if you want to reset everything to default simply delete the FSUIPC INI file. Everything you do is recorded in there. Or find the Axes or JoystickCalibration sections in that file and delete just those. It really couldn't be easier!

... due to some strange behaviours.- I.e, I couldnt assign the Lear as aircraft specific as each time I opened the FSUIPC screen, the box appeared unchecked

What box? "aircraft specific"? That has to be checked by you, not FSUIPC!

other aircraft specific controls need constantly to be recalibrated, some axes couldnt be assigned, etc etc

I really cannot imagine how you got into such a mess. There's nothing magic or clever about any of that in FSUIPC. It just does what you ask -- it sounds like you were misunderstanding some of the indicatiions.

It confirms what was said in other threads about some incompatibility between the CH Control Manager and FSUIPC

If the CH control manager is assigning FS controls, then you cannot assign them also in FSUIPC, though you should be able to calibrate any axes assigned to FS controls by any program. The axis assignments in FSUIPC are simply done by those axes which FSUIPC can see changing. The only way they cannot be assigned is if FSUIPC cannot see them changing. In FSUIPC3 that could only be because the CH Manager does not support the standard Windows "joystick" interface. In FSUIPC4 is seems more unlikely as it would mean it doesn't support the "DirectInput" interface.

Regards

Pete

[soldano]

I installed the CH Control Manager, and used it only for calibrating the controls, the result was a mess in my FSUIPC settings

I have no idea how any separate program can make a mess of FSUIPC settings.

I have no idea either, but it happened, I found all the axes changed

I had to reset all from scratch, which was very dificult and imposible in certain cases ...

It is never impossible to reset anything in FSUIPC -- if you want to reset everything to default simply delete the FSUIPC INI file. Everything you do is recorded in there. Or find the Axes or JoystickCalibration sections in that file and delete just those. It really couldn't be easier!

I know I could do it, but I preferred to delete all axis for various aircraft and configure them again

... due to some strange behaviours.- I.e, I couldnt assign the Lear as aircraft specific as each time I opened the FSUIPC screen, the box appeared unchecked

What box? "aircraft specific"? That has to be checked by you, not FSUIPC!

I refered to the "aircraft specific" box, which of course should be checked by me, it happened only with the Learjet, as everytime I opened the FSUIPC screen, found it unchecked, not with other aircraft also configured as aircraft specific.-

other aircraft specific controls need constantly to be recalibrated, some axes couldnt be assigned, etc etc

I really cannot imagine how you got into such a mess. There's nothing magic or clever about any of that in FSUIPC. It just does what you ask -- it sounds like you were misunderstanding some of the indicatiions.

I misunderstood nothing, I proceed exactly as I succesfully did before installing that bloody Control Manager, and as I did after uninstalling it.-

It confirms what was said in other threads about some incompatibility between the CH Control Manager and FSUIPC

If the CH control manager is assigning FS controls, then you cannot assign them also in FSUIPC, though you should be able to calibrate any axes assigned to FS controls by any program. The axis assignments in FSUIPC are simply done by those axes which FSUIPC can see changing. The only way they cannot be assigned is if FSUIPC cannot see them changing. In FSUIPC3 that could only be because the CH Manager does not support the standard Windows "joystick" interface. In FSUIPC4 is seems more unlikely as it would mean it doesn't support the "DirectInput" interface.

I dont know how the CH manager works, I didnt even opened it, the only thing I did was calibrating my Yoke, pedals and quadrant in the new Windows screen modified by CHCM.-

Regards

[soldano]

Sorry

I my last mail I didnt manage to separate the quotes, please read the whole message.-

[Pete Dowson]

I have no idea either, but it happened, I found all the axes changed

I can understand them needing re-calibrating in FSUIPC, but surely the Manager program didn't re-direct axes to different Windows axes, i.e. swap them all about? That would be crazy. If ity did that then you'd certainly need to delete the [Axes] sections or else have a right mess to deal with.

I refered to the "aircraft specific" box, which of course should be checked by me, it happened only with the Learjet, as everytime I opened the FSUIPC screen, found it unchecked, not with other aircraft also configured as aircraft specific.-

There's an "aircraft specific" box for Axis, Calibration , Buttons and Keys tabs, so saying it is the aircraft specific box again doesn't clarify anything I'm afraid. But in any of those cases FSUIPC would not (could not) specifically distinguish a Learjet from any other aircraft, it only goes by the name which is saved in the [Axes.] heading for the settings. If it thought there was no specific settings then the name couldn't have been matched.

Regards

Pete

[soldano]

As I was in doubt, reinstalled the CH Ctrl Manager, used it only for calibrating, and it happened again, I found all the axes changed.- So I deleted the ini and then I could assign new axis and buttons OK.- As some problems with buttons appeared (i.e trackir hotkeys), I uninstalled the CM and returned to normality.-

Thanks for your replies

[Pete Dowson]

As I was in doubt, reinstalled the CH Ctrl Manager, used it only for calibrating, and it happened again, I found all the axes changed.- So I deleted the ini and then I could assign new axis and buttons OK[\quote]

Weird that is should reassign axes itself! I don't like things like that. I wonder why it does such things?

I uninstalled the CM and returned to normality.-

I must say i can't blame you for that. I think I would do the same.

Regards

Pete