Help with Axes please!

[Kosta]

Hello,

So, my first attempts to calibrate my joystick over FSUIPC, and somehow it doesn't work.

I did everything it said I had to do. I unassigned everything connected to joystick in Assignments of FS9, I disabled the joystick (though I do have FS Force running with my Sidewinder FF2) in Options-Controls, I assigned Axes to FSUIPC Calibration, I managed to nicely calibrate them all in the Calibration-Menus, and then I sat in my LVLD-767 and voila - I press AP, it doesn't follow it, and when I try flying manually, it's jerking around, I can't possibly handle the aircraft. Seems like it either doesn't understand the commands OR there is a conflict somewhere.

Assigning commands over FS9 menu is working like a charm. But why do I have FSUIPC registered then?

Help is much appreciated :)

Thx

Kosta

[Pete Dowson]

So, my first attempts to calibrate my joystick over FSUIPC, and somehow it doesn't work.

I did everything it said I had to do. I unassigned everything connected to joystick in Assignments of FS9

Well, let's stop there for a moment. If you want to CALIBRATE in FSUIPC, why unassign things in FS? FSUIPC will easily calibrate anything assigned in FS. You only need to unassign things in FS if you want to ASSIGN things in FSUIPC, and why would you want to do that?

I disabled the joystick (though I do have FS Force running with my Sidewinder FF2) in Options-Controls

If you want force-feedback you most certainly CANNOT use FSUIPC for assignments. Delete your FSUIPC.INI file and start again. Just use FSUIPC for calibration, as originally intended. The axis assignments facility is an advanced option for folks using multiple controls who want automatic changing when they swap aircraft, or need axes to do other things like press buttons or send keystrokes. FSUIPC assignment can be more efficient than FS assignment, but it certainly doesn't support force feedback, and since it bypasses FS fror most everything (that's why it is more efficient) it will also fool some of the more elaborate add-on aircraft.

I managed to nicely calibrate them all in the Calibration-Menus, and then I sat in my LVLD-767 and voila - I press AP, it doesn't follow it, and when I try flying manually, it's jerking around, I can't possibly handle the aircraft. Seems like it either doesn't understand the commands OR there is a conflict somewhere.

From what I've heard, the Level D aircraft does its own thing with the axis controls from FS. Even if you assign axes in FSUIPC you have to assign them to FS controls, not direct to FSUIPC, otherwise it won't see them. You can, of course, make such assignments aircraft specific.

Assigning commands over FS9 menu is working like a charm. But why do I have FSUIPC registered then?

Maybe because you wanted to use its facilities? Why DID you buy it if everything was "working like a charm"? I cannot read your mind, I don't know what you wanted to do. Sorry.

So, why ASSIGN in FSUIPC? What did you want to accomplish that way? What is wrong with using the more precise calibration, long the mainstay of FSUIPC facilities, without using the relatively new and rather specialist facilities of FSUIPC assignment?

Even so, since it was all working like a charm beforehand, why try to mess it up? Why not just continue as you were before? I don't understand.

Regards

Pete

[Kosta]

Hi Pete,

Thank you for you answer, and my apologies for not making everything clear.

I was little pissed off, because I just brought my Saitek Yoke back to the shop for refund, just to come home and not being able to set up my FF2 back as it was.

The yoke wasn't working as it was supposed to (random button pushes), and some other problems. I was attempting to assign axes over FSUIPC, because I had extra throttle quadrant from Saitek, which I wanted to set up for reversers, and also spoilers and flaps onto another two axes. That is why I set up everything to work over FSUIPC, as it has been written in the readme that it can be done. It was working with PMDG 747 (almost OK), but not with LDS.

Now I know that it's the aircraft problem and not yokes.

Still the random button pushes, broken axis and lots of dead-zone pushed me to make a refund.

But now I do understand what's going on in the background.

Oh, and btw, I am NOT using forces from the sim. I have FS Force, which generates forces on its own. It's completely independent from FSUIPC.

Thx

Kosta

[Pete Dowson]

I just brought my Saitek Yoke back to the shop for refund, just to come home and not being able to set up my FF2 back as it was. The yoke wasn't working as it was supposed to (random button pushes), and some other problems.

Oh, yes. A lot of folks have mentioned that. In fact I added a special facility to ignore transient button presses especially to get over those spurious ones (see the Dowsnloads announcements above).

I was attempting to assign axes over FSUIPC, because I had extra throttle quadrant from Saitek, which I wanted to set up for reversers, and also spoilers and flaps onto another two axes. That is why I set up everything to work over FSUIPC, as it has been written in the readme that it can be done.

Yes, it certainly can. Maybe best, though, for add-on aircraft, is to assign normal flight controls and throttles through FS. Flaps and extra reverser axes can be assigned direct in FSUIPC, giving you more options. you can assign everything in FSUIPC, with the main controls and throttles going via FS and the flaps and reversers, or even just the reversers (which aren't provided directly in FS) direct to FSUIPC.

Certainly for force feedback I think you need to assign the main axes in FS. Because of the way FS "picks up" controller axes, it may be best to keep all axes on each controller either through FS or through FSUIPC, not mixing them. If FS does start contorlling axes which FSUIPC is also controlling then things will go pretty horrible, many jerks and changes as each does its own thing.

Oh, and btw, I am NOT using forces from the sim. I have FS Force, which generates forces on its own. It's completely independent from FSUIPC.

Ah, okay. That should make things a lot simpler, then.

Regards

Pete