Comments on: Joystick Features Coming in X-Plane 11.30

By: Ilan Kreitmann

Ilan Kreitmann — Sat, 06 Oct 2018 13:04:03 +0000

In reply to Tyler Young. Force feedback that is exactly the case.... Thanks for answer !

By: Tyler Young

Tyler Young — Sat, 06 Oct 2018 01:04:27 +0000

In reply to ilan Kreitmann. Uh... without knowing why it needed to be connected to a Windows machine in the first place, I can't say. This is the first I've heard of this rather bizarre setup. (I assume it's a hack to get force feedback working? If that's the case, then no, a custom curve won't help.)

By: ilan Kreitmann

ilan Kreitmann — Fri, 05 Oct 2018 22:26:08 +0000

hello,
I had a longer correspondence with a Brunner engineers about the usage of the CLS-E NG FORCE FEEDBACK YOKE. For using it with my iMac27 it needs to be calibrated through the steady connection to their special Windows software (using a Win partition on iMac or permanently a second Win machine). Will it be possible to calibrate the Brunner yoke from now on (XP 11.30) using the support for setting custom curves on any axis type as you mentioned ?

By: Ben Supnik

Ben Supnik — Fri, 05 Oct 2018 12:35:51 +0000

In reply to Chris Collins.

Yeah, I don’t see X-Plane containing a ‘native’ decoder for the low level “quadrature” encoded stream. For hardware like the GoFlight radios, the board on the GF device itself decodes the stream, keeps an 8 bit ‘count’ of current offset, and publishes the count over HID, and this seems like a more reasonable approach. So I don’t see cockpit builders who are using an Arduino and rotary encoders getting out of having to program the Arduino a bit. 🙁

By: Ben Supnik

Ben Supnik — Fri, 05 Oct 2018 12:33:31 +0000

In reply to Tyler Young.

Someday we may have a real interface to this, but it would be a major piece of new functionality. When Chris rewrote the _low level_ joystick support in v10.10 (building the foundation on top of which Tyler built all of the profile support, .joy file support, etc.) he set up the sim to accept multiple categories of input streams. So we can, in theory, someday allow plugins to register devices for which the plugin simply registers callbacks to provide data.

This would not be the same as just writing to the axis – you’d be creating a “physical” axis that would need to then be mapped to pitch – although your plugin could hint good defaults for configuration. But this is a major piece of work that is not started and is not on the short term road map at all.

By: Tyler Young

Tyler Young — Thu, 04 Oct 2018 12:53:43 +0000

In reply to Ricardo Pallavidino.

By: Ricardo Pallavidino

Ricardo Pallavidino — Thu, 04 Oct 2018 05:42:20 +0000

In reply to Tyler Young. Ohhhhh yes, that will be sooo good, thank you

By: Alex

Alex — Wed, 03 Oct 2018 22:19:27 +0000

In reply to Tyler Young. Thanks!

By: Tyler Young

Tyler Young — Wed, 03 Oct 2018 22:05:59 +0000

In reply to Ricardo Pallavidino. Yes to both! The mouse will be unaffected by the curves you set on your joystick's axes, so that's easy. To set up the joystick, you would set two custom curves (one on the x axis, one on the y), and simply set the topmost portion of each range to 60% of the max.

By: Ricardo Pallavidino

Ricardo Pallavidino — Wed, 03 Oct 2018 21:57:07 +0000

Hi Tyler,

Thank you for this great new feature!

Here is my case: I use a mini joystick in my HOTAS as a POV camera, mainly when checking runway position turning base and final at the pattern. Problem is that range of this minuscule device now is 360º horizontal and 180º vertical which is way more then I need and makes it very sensitive.

Question 1: Is this new feature allow me to set this joystick axis like 60% lower then the camera range so I could have like 200º horizontal and 90º vert range?

Question 2: If this is possible can I keep still using the mouse to get full range for POV?

Thanks

Ricardo