[Some Issues of The Axis Assignment]

1 hour ago, Pete Dowson said:

Ah, you are looking at the Calibration pages. If you assign in P3D, you can calibrate in FSUIPC. But if you want FSUIPC to handle the device you MUST assign the axes in FSUIPC! Please do refer to the user guide. 

P3D does some automatic assignment, but often gets it wrong. FSUIPC does NOT automatic assignment. It lets you use your devices as you see fit.

It really is importnat to read the relevant sectionso of the User Guide. Pictures are provided too!

Pete

 

I always assigned axes for my joystick and throttle in FSUIPC’s “axis assignment” page. Supposedly once I move any of the axes, there should be a number/parameter shown in some boxes in that page, and then I assign an action for that axis.

However, there is no number/parameter shown when I move the new yoke (i.e. the movements of the axes of the yoke are not detected at all).

Thanks very much!

Anson

[Some Issues of The Axis Assignment]

40 minutes ago, Pete Dowson said:

There's no "ACE" device seen by FSUIPC because there appear to be not entries for it, either in the Registery, or in the list known to the Windows Joystick interface. That is unless it is this one:

Product= Plasma-MM2
       78    Manufacturer= Beta Innovations

Wouldn't an ACE device feature "ACE" somewhere its identity?

If it is that device, it appears to have these connection:

Details: Btns=64, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R65535,U65535,V65535,X65535,Y65535,Z65535

i.e 64 buttons and 6 16-bit high resolution axes. 

I note from the Joyscan file that there are two devices with that identity, but one doesn't respond to Joystick interface reads, nor does the interface give valid informastion, like that above, for it.

If that isn't the ACE, but another one which you have working (I can't tell if you have any assignments since you didn't provide your INI file), then I'm afraid the ACE is simply not a device known to any interface FSUIPC understands.

Pete

 

Thanks for your reply. Sorry I forgot to mention that the yoke is identified as "Plasma-MM2", that means your guess was right.

Actually if I do the calibration in P3D controller setting page, the yoke can function properly. But back to FSUIPC,  the axes cannot be detected unless I check "enable controller" in P3D. I wonder if FSUIPC to some extent "links" to P3D to acquire some controller information...

However I still prefer to calibrate the yoke via FSUIPC because this is what I have done for my throttle and joystick. 

What can I do so that I can calibrate it via FSUIPC?

Anson

[Some Issues of The Axis Assignment]

Dear Pete,

Greetings! I just purchased a new yoke from ACE which requires no driver. I guess since there is no driver but just plug and play, the axes need to be calibrated either by Windows controller setting or P3D or others, otherwise their movements cannot be properly detected. Now I want to do the calibration via FSUIPC. 

However, all the movements of the yoke cannot be detected in FSUIPC's "axis assignment" page when I move the yoke (no number/parameter is shown in the interface).

Then, in FSUIPC's "joystick calibration" page, with "enable controller" option enabled in P3D setting page, the numbers in the box "in" and "out" did change but with delay (e.g. when the yoke is already physically centred to neutral position from full left/right, the number is still changing and after a few seconds stop at 0). 

However, with "enable controller" option disabled in P3D setting page, the number stays at 0 and will not change even if I move the yoke. 

I would be thankful if you could help! My log and Joyscan file are attached.

Thanks very much!

Anson

FSUIPC5.log

FSUIPC5.JoyScan.csv

[[P3D v4.1] Simconnect Issue with FSUIPC 5.123]

The updated version works like a charm! Thanks Pete!

[[P3D v4.1] Simconnect Issue with FSUIPC 5.123]

Dear Pete,

Greetings! I am writing to consult about the issue of FSUIPC. Having got the Windows 10, P3D and FSUIPC 5.123 clean installed, every time I start my sim there will be a pop-up message "Cannot operate! Something wrong with SimConnect library...Memory problems detected! Operations restricted". The log has been attached to this post. That contains a error message:

1063 Exception 5 "VERSION_MISMATCH", Ref 1, Version 1.0: Open: SimConnect Version incorrect!

I would be thankful if you could help. Thanks so much!

Anson

FSUIPC5.log