Level D 767 & Cap Sim 757 issues

[park86]

I set up a/c specific settings for each, I use a ch eclipse yoke and ch 6 lever throttle q. Similar settings work great on stock fs 737, 747, Lear, CRj and others but wierd things are happening with the 767 & 757. First I went in to fly and the throttle lever 1 initiated reversers and spoilers and the auto pilot doesn't work in either plane. I double checked settings, reasigned and recallibrated but still had the same problem. Then I looked at the ini and noticed that only axis assignments were made for those planes, no joystick callibrations so I copied the js calls from a 737, pasted them below the axis assignments and renamed to the specific plane and that seemed to solve the throttle/reverser/spoiler problem. But I sill have one with the autopliot in both planes is not moving the ailerons or elevator. It does hold the speed. I read on the level d forum an old post saying that he had the same issue (in early 09) and his only fix was to let fs control those axis. So my questions are: 1) why didn't the callibrations post to the ini? 2) can I set up a specific a/c axis assignment to where fs controls the axis? Is the the middle option "send to fx." rather than to fsuipc assuming that IS the problem? 3) Am i the only one on the planet experiencing this?

[Pete Dowson]

I set up a/c specific settings for each, I use a ch eclipse yoke and ch 6 lever throttle q. Similar settings work great on stock fs 737, 747, Lear, CRj and others but wierd things are happening with the 767 & 757. First I went in to fly and the throttle lever 1 initiated reversers and spoilers and the auto pilot doesn't work in either plane. I double checked settings, reasigned and recallibrated but still had the same problem. Then I looked at the ini and noticed that only axis assignments were made for those planes, no joystick callibrations

if you assign axes in FSUIPC in the "direct to FSUIPC calibration" mode, then naturally they have to be calibrated or nothing will happen. If you assign them instead to the FS controls then calibration in FSUIPC is optional.

But I sill have one with the autopliot in both planes is not moving the ailerons or elevator. It does hold the speed. I read on the level d forum an old post saying that he had the same issue (in early 09) and his only fix was to let fs control those axis.

It is possible that assigning direct to FSUIPC calibration is bypassing the way in which those particular aircraft handle the autopilot. It sounds like they intercept the FS controls, and of course you are bypassing those. That doesn't normally matter with the built-in FS autopilot as it cuts off the external influence itself.

However, it does also indicate that your axis controls are continuing to send enough changes to override the aircraft A/P inputs. That sort of jitter is unwanted. If your axes are so unstable, the one way round is to use a larger dead centre zone when calibrating, and take care not to move them out of that zone when on autopilot. FSUIPC doesn't do anything with axes which aren't moving, and that would effectively silence their inputs.

The other altenative, for those aircraft only, is to assign, in FSUIPC still, to the FS controls instead of direct to calibration. You should still be able to calibrate in the same way. It's just a little more inefficient, that's all.

So my questions are: 1) why didn't the callibrations post to the ini?

Without knowing what you did I can't say. The INI is updated the moment you press OK to confirm changes and exit the options. Maybe you made the calibrations, but then thought of something else, went to a different options tab, and ultimately pressed Cancel or escape, so not saving any changes made during that complete visit.

2) can I set up a specific a/c axis assignment to where fs controls the axis?

Yes, as described above.

3) Am i the only one on the planet experiencing this?

I've no idea, I don't know everyone, and they've not all written to me one way or the other (thank goodness!) ;-)

Regards

Pete

[park86]

Thanks. You may have been right on the distraction. That happens alot. i tried reassigning the yoke to fs but that did not do the trick so it may be the callibration dead zone. Can you eleborate on that and help how to set that up?

[Pete Dowson]

You may have been right on the distraction. That happens alot. i tried reassigning the yoke to fs but that did not do the trick

Strange, because what the aircraft coding sees then is EXACTLY the same as when the axes are assigned in FSX. Assignment in FSX sends the exact same controls to the same places. Sounds like those aircraft have something wrong with them. Maybe you're missing some updates?

... so it may be the callibration dead zone.

Which would be the same with normal everyday FS assignments.

Can you eleborate on that and help how to set that up?

Follow the numbered steps in the section on calibration in the user guide. You set 4 values for all centred axes -- minimum, centre low, centre high and maximum. The 'dead' zone is the range between the two centre values, so you control exactly how wide it is during calibration. If you've never noticed this then you probably have never actually calibrated, but merely accepted the default values which are always wrong -- they may be close, but they are still not YOUR hardware's values.

Similarly the minimum and maximum values should normally be set slightly away from the end stops on the lever, to make sure you can always reach the end values despite any small variations (temperature, humidity, dirt, voltage, etc, all affect joystick readings).

If you follow the documented steps, these things will fall out.

Regards

Pete