fixed Reticle depression axis is not absolute

[Xupicor]

In a module where iron bombing is so reliant on the depression tables you would think a reticle depression knob would be important to get right. However, unfortunately, the binding for an axis for sight depression is not working as you would expect it to. You have to keep the knob centered for the in-cockpit knob to keep a fixed value. Any deflection on the physical knob and you get a constant movement of the in-cockpit knob, the speed depending on the amount of deflection from the center point. Surely this isn't right...

Can we get a properly working absolute value sight depression knob?

[MadKreator]

29 minutes ago, Xupicor said:

In a module where iron bombing is so reliant on the depression tables you would think a reticle depression knob would be important to get right. However, unfortunately, the binding for an axis for sight depression is not working as you would expect it to. You have to keep the knob centered for the in-cockpit knob to keep a fixed value. Any deflection on the physical knob and you get a constant movement of the in-cockpit knob, the speed depending on the amount of deflection from the center point. Surely this isn't right...

Can we get a properly working absolute value sight depression knob?

I'm currently developing a helios profile for the f-5 and the  Reticle Depression Knob only works as a rotary encoder, not a linear axis. I do find it odd that it since in clickabledata.lua its simply a "defaulit axis" leading me to believe a linear axis/ potentiometer should work, but it doesn't. Full step change moves the sight one degree... I just tested it binding it to a rotary encoder on my throttle and it does work as it should ( essentially the same as binding a button for increase and another for decrease).
I DO agree with you that a linear axis would be more feasible for most users as most hotas setups don't necessarily have an abundance of rotary encoders....except for my STECs, which is oddly loaded with them lol

Edited May 4, 2024 by MadKreator

[Xupicor]

I've got 19 rotary encoders here, but the one knob that's most closely placed to where the F-5 depression knob is in the pit is an analog axis.

I know I can just bind any one of the rotaries I have. I'd like to see the axis work properly, though.

[NineLine]

I am not seeing the OP's issue anymore, so unless I am missing something I think this is ok. 

As I understand when assigned to an axis (in my case I assigned to a slider on my WINWING throttle) people were seeing movement when making adjustments off '0'? Is this correct?

Let me know if I am missing the issue and it's still present. Thanks!

[vgilsoler]

On 11/6/2024 at 9:30 PM, NineLine said:

I am not seeing the OP's issue anymore, so unless I am missing something I think this is ok. 

As I understand when assigned to an axis (in my case I assigned to a slider on my WINWING throttle) people were seeing movement when making adjustments off '0'? Is this correct?

Let me know if I am missing the issue and it's still present. Thanks!

It is still happening. Only when the axis is at the center the value is fixed. When you move the axis to both ends the knob is turning around endlessly.

[Flappie]

It's reported internally.

[Flappie]

Things were improved with today's update.

However, I wonder if the new behaviour is normal: the knob starts moving when the axis is at 45% ("35", "34",...), 50% gives "0", then 50% to 100% ranges from "0" to "200".

[nairb121]

16 hours ago, Flappie said:

Things were improved with today's update.

However, I wonder if the new behaviour is normal: the knob starts moving when the axis is at 45% ("35", "34",...), 50% gives "0", then 50% to 100% ranges from "0" to "200".

That seems like reasonable behavior to me - since the reticle depresses far more than it elevates, the alternatives would be to have the 0 point almost at one end of the axis, or for the motion to be wildly non-linear. Since many HOTAS/control panels have dials with center detents, having 0 depression at 50% makes the most sense to me.

[Flappie]

Thanks for your feedback. I agree.