Jump to content
The simFlight Network Forums

Throttle problem (eaglesoft CitationX 2.0 with FSUIPC4.827)


Recommended Posts

my aircraft is eaglesoft CitationX2.0

And

My FSUIPC ver is 4.827

When I install new 4.827 FSUIPC

Idle power of Throttle is 50% incorrectly.

But

at 'C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini'

When I change 'AxesWrongRange=No' to 'AxesWrongRange= Yes'

Idle power of Throttle is 24% ordinarily.

this option (AxesWrongRange= Yes) is good.

But, I Feel little different than old version FSUIPC.

FADEC of ver 4.827 is some much sensitive.

when I am front of Runway for Landing. I control Throttle very little up ~ down

But, FADEC make power to T/O-mode.;

too sensitive.

Edited by heaye
Link to comment
Share on other sites

When I install new 4.827 FSUIPC

Idle power of Throttle is 50% incorrectly.

Compared to what other version?

When it is at 50%, what is the OUT value in FSUIPC calibration? You should ve calibrating for 0 at idle unless you are using the "no reverse zone" option.

How are you assigning the throttle? In FSUIPC or in FS, and if in FSUIPC, by which method and to which control?

When calibrating in FSUIPC are you correctly following the steps to calibration? Are you using a reverse zone on the throttle, or using the "No Reverse Zone" option?

this option (AxesWrongRange= Yes) is good.

But, I Feel little different than old version FSUIPC.

FADEC of ver 4.827 is some much sensitive.

There is absolutely no difference in what FSUIPC does. There is no sensitivity adjustment in FSUIPC at all -- that is part of the aircraft modelling.

The correction to the incorrect axis offset values was made in the middle of last year, long before 4.827, and the problem it fixed was reported by no one until that point. It seems that bad programming practice had led some aircraft implementers to simply assume the bug was correct and that the documentation was wrong, so for over 4 years no one bothered to tell me! :sad:

All that "AxieWrongRange=Yes" does is to restore this old bug so that the obscure and infrequently used offset returned to its same, old, bad faulty value.

There are no other changes whatsoever in how axes are reflected in the offsets, not in any of the other axis assignment and calibration facilities. If you have a complaint about a specific aircraft you will need to go to their support.

Pete

Link to comment
Share on other sites

:)

Thanks Pete Dowson.

I solve my problem.

I am not english-speaker, and my english skill is very low.

so I do not set any option in FSUIPC. I only install FSUIPC.

But, THis is my mistake.

I Must had set something.

now. I set these 'Axis Assignment' and 'Joystick Calibration'

and. All is good. My problem is solved.

Tip.

I must delet default-Throttle-setting of FSX

because, FSX-setting clash FSUIPC-throttle-setting.

Thanks.!!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.