GoFlight MCP AP question. FSUIPC registered.

[jbmaster]

Hi,

I have a GF-MCP module running on a Vista 32-bit with FSX and Wilco Airbus Series v.1.

I have a registered copy of FSUIPC, latest version.

However, the AP Altitude knob has a problem I cannot fix: when I rotate the knob, the values on AP Altitude indicator do not follow the knobv rotation exactly (2 knob positions = 1 value added in AP indicator).

What can I do to fix it?

Thanks.

John Pereira

[Pete Dowson]

I have a GF-MCP module running on a Vista 32-bit with FSX and Wilco Airbus Series v.1.

I have a registered copy of FSUIPC, latest version.

However, the AP Altitude knob has a problem I cannot fix: when I rotate the knob, the values on AP Altitude indicator do not follow the knobv rotation exactly (2 knob positions = 1 value added in AP indicator).

What can I do to fix it?

Isn't this a matter for GoFlight support?

If you've programmed it in FSUIPC (why?) then you probably need to program both the "press" and "release", as most rotaries send an "off-on" and an "on-off" alternately, hence the two "clicks" to the next "press".

Pete

[jbmaster]

Thanks for your message.

I tryed that too. But the problems start inside the Options Box of FSUIPC (that's why I contacted you): when I start programming the knob, I turn the knob once and nothing happens to the Joy# and Btn# fields. Just at the second "click" I get the knob information Joy# 149 Btn#29.

The same happens if I try to do the same rotating the knob on the oposite direction (just the second "click" shows Joy# 149 Btn#30.

Once programmed, I rebooted FSX and when I opened Options Box of FSUIPC I needed to do 2 "clicks" in order to show "Joy# 149 Btn#29"...

That knob works perfectly on other add-ons...

John.

[Pete Dowson]

Thanks for your message.

I tryed that too. But the problems start inside the Options Box of FSUIPC (that's why I contacted you): when I start programming the knob, I turn the knob once and nothing happens to the Joy# and Btn# fields. Just at the second "click" I get the knob information Joy# 149 Btn#29.

The same happens if I try to do the same rotating the knob on the oposite direction (just the second "click" shows Joy# 149 Btn#30.

Once programmed, I rebooted FSX and when I opened Options Box of FSUIPC I needed to do 2 "clicks" in order to show "Joy# 149 Btn#29"...

Yes, all that is exactly correct, and what you would expect for a knob which clicks once for "on to off" and again for "off to on". It doesn't matter at all how many times you have to click it to have it recognised in the dialogue! Why do you think that is of any relevance? Think of it like a toggle switch -- FSUIPC will see it when you toggle it on, but not when you toggle it off. The dialogue is designed to work that way to avoid false readings. All it needs to do is see it, and it IS seeing it as you just said!

That doesn't mean you cannot program it for for "press" and "release" EXACTLY as i explained!! :-( Why didn't you just go ahead and do it instead of making life so complicated for yourself unnecessarily?

Regards

Pete

[jbmaster]

As I started to say in my previous message, " I tryed that too".

Nothing changed.

[Pete Dowson]

As I started to say in my previous message, " I tryed that too".

Tried what too., exactly? You need to be more specific.

You only described what happens in the FSUIPC dialogue, which is completely irrelevant. You have not once said you programmed it for the same action for both press and release, as I suggested, and nor have you stated anything about any results of doing so.

If the dialogue detects the Click turning the button it sees from off to on, as you say it does, then FSUIPC, whilst running normally, will most certainly also see the "on to off". It cannot actually detect one without the other -- you will notice that it is a logical absurdity for it to be otherwise.

Therefore, if you have, as you say, "tried" something, it most certainly cannot be what I suggested you try.

You say "that knob works perfectly on other add-ons...", and it sounds, from what you've said, that it will work perfectly in FSUIPC. It is just that, unlike most other add-ons, FSUIPC is much more flexible, providing more options -- in this case a separate capability for switching off to that for switching on -- , and these are evidently confusing you!

I'm sorry that I only do support in English, as I feel sure that the problem here must be one of communication, and perhaps English is not your natural tongue?

Regards

Pete