Radar cursor axis controls

[some1]

Cursor control using joystick axis is not proportional to axis deflection, but rather "on/off" like with simple buttons.

 

Also the cursor can't be moved horizontally and vertically at the same time.

 

Radar joystick is not animated.

[some1]

Happy bug anniversary. :holiday:

 

All issues still present in the latest version.

[some1]

Looks like I'm talking to myself here, but the issue is still there.

[frosen]

24 minutes ago, some1 said:

Looks like I'm talking to myself here, but the issue is still there.

 

Haha I hear you at least 

 

Yes, I also noticed that the cursor is not moving on both axis at the same time. Some weeks ago I thought I should make use of my old joystick as a radar stick but with the very rudimentary implementation atm, I quickly binned that idea...

 

(I saw an old IRL Viggen video where the cursor clearly moved along both axis simultaneously so I'm also positive it's a bug.)

[LazyBoot]

Can confirm I'm also seeing both issues...

makes it really hard to make precise edits when you can't vary the speed of the cursor.

[Machalot]

This has bothered me ever since I learned how to do radar fixes. I assumed it was a cheap mini joystick on my throttle, but it's good to hear you other users have the same complaint. Now is the time to get HB's attention! 

[LazyBoot]

@IronMikeAny chance you guys could add this to the list of things to look at? It's making it really hard to put accurate fixes on the radar with only 1 cursor speed.

[IronMike]

15 hours ago, LazyBoot said:

@IronMikeAny chance you guys could add this to the list of things to look at? It's making it really hard to put accurate fixes on the radar with only 1 cursor speed.

 

Thank you for pinging me. Added to the tracker for further investigation, I hope we can improve it.

 

EDIT: quick feedback, should be possible, our apologies this flew under the radar for so long! PS: if any of you can share the vids mentioned above, would be nice, so we can try to match the bahavior. Thank you all!

Edited October 5, 2021 by IronMike

[MYSE1234]

@IronMike

This video @ 12:12 is one of few videos of it.

It's not the same symbology, but should be the same hardware behind it.

https://youtu.be/sGJCFt3wK6c

 

 

Edited October 5, 2021 by MYSE1234

[rogorogo]

funnily enough I immediately noticed this bug AS A DEFINITE BUG on my very first glance at the Viggen module.

It may or may not also be peripheral related, for example "some" coolie hats on "some" peripherals or "some" axis translators on "some" peripherals may actually be able to successfully bind and translated the INTENDED diagonal input (clarification: comment restricted to the peripheral input, not actual function of the actual stick and its digital representation).

That even the working "axis' " seem to be boolean even when bound to a granular control peripheral and/or axis makes it just even stranger.

Alternatively, this is some arbitrary typo bug that just has not gained enough traction, is not "on the nose" enough to be a priority or even noticed... thus it lingers on... for 4+ years.... and not even a commenting out of the cul-de-sac binding item line ( 4x " // " which takes about... 28 seconds?) as a mitigation surfaced.

Edited November 21, 2021 by rogorogo

[Machalot]

This was specifically mentioned by Cobra from HB as a being fixed in the upcoming patch. 

 

Edited November 21, 2021 by Machalot

[LazyBoot]

1 hour ago, Machalot said:

This was specifically mentioned by IronMike as a being fixed in the upcoming patch. 

I believe it was Cobra, not IronMike

[Machalot]

9 minutes ago, LazyBoot said:

I believe it was Cobra, not IronMike

Corrected. Thanks. 

[IronMike]

Fixed, indeed.