[X52 Axis not recognized.]

First please excuse me for :

• [*:465c3]Not being able to explain my problem in a really clear way,
  [*:465c3]My really bad english

And thanks for your really quick answers, I'll try to explain the issue more clearly now.

FSUIPC doesn't recognise it where? In the Axis assignment facility (FSUIPC 3.60), or only in the Joystick Calibrations? If it is the former, then it seems like it isn't one of the standard 6 axes supported by the Windows joystick API (X Y Z R U V).

In Axis assignments... it work perfectly for all other axis but not for this one. I push "rescan" then move it, and this one is the only where this do nothing at all.

What puzzles me about what you say, though, is what you mean by FS displaying it but not making use of it -- how can it "display it" if you cannot assign it? Or do you mean you assign it okay, but it doesn't operate the thing you've assigned it to? If the latter then all that means, probably, that FS has got the sensitivity set to zero -- go to the Sensitivity slider and move it full right. Whilst you are there, move the null zone full left.

No, null zone is not defined at all, it just show as set but do not operate... I can set it but don't have any effects. I tried to set this axis into my Saitek profiler and it work, so I reset these settings and made it back being a normal axis... but change nothing.

If that makes FS work with it, then it should also make FSUIPC's calibration section see it.

It don't and what I want to say is that with X52 axis on throttle, FS is able to assign those but isn't able to... use them. They are defined in assignments but do not have any effect.

François Houlbrèque

[X52 Axis not recognized.]

Hello,

I use X52 Saitek Joystick and I got a problem with the Throttle upper rotary axis wich is recognized by FS but not functional (FS display it but don't make use of it) and is not recognized at all by FSUIPC

This is the ONLY axis not recognized. All others are.

Here a screen to show you the reotary selector in blue.

[Little problem with updates of NAVAIDS.]

Hehe as I said... oh did I forgot ?... it's what I made but FSNav still show the default runway in front even it show the new one in list...

[Little problem with updates of NAVAIDS.]

Hello,

I'm using IVAO and some nice guy on this network released a set of files for my country, with all updated airports AFCAD BGLs (new navaids and other ILS or runway ident modified).

My problem is that, if I really put the BGL at the first priority, when he set some new runways (with same heading but different name, some changed from 15/33 to 14/32 or things like that), if the database show correctly the new one, it still show the old oneso FSNav show the original one on mouse over, not the new one.

HOw can I get rid of that ? Thank you !