Some in-cockpit knobs don't rotate

rrohde · December 30, 2015

Not really a bug, as the knobs do work, however, it seems as if some knobs that are meant to rotate (e.g., heading bug, radio frequency changers, etc) have to be clicked instead - which is rather tedious and not ergonomic.

It would be nice if all rotaries could be manipulated using the mouse wheel, while all push-buttons and rocker switches could be clicked (left/right respectively).

Thank you! :thumbup:

Azrayen · December 30, 2015

I think that it was implemented so that:

- step-by-step knobs are to be clicked left/right

- analog rotary knobs/rheostats are to be rotated through mouse wheel

This is DCS standard AFAIK (except for the left/right choice: DCS standard is left=counterclockwise, Razbam did reverse that).

Edited December 30, 2015 by Azrayen

rrohde · December 30, 2015

Have to say, though, that turning the heading bug on the HSI by clicking (instead of using the mouse wheel) is a real chore. Not sure if that was intended?

Flagrum · December 30, 2015

I found some inconsistencies as well - but haven't really payed much attention to it. It was more some kind of "intuition does not match reality" (i.e. misclicked/scrolled as the switch did work differently than I was expecting/used to)

I remember seeing a document (by ED?) which listed all the different types of buttons and switches and how they are to be implemented in DCS (left-click, right-click, etc.). That was not too long ago, but I can't find it now ... was it mentioned in the 2.0/1.5 bugs section ... damn, can't remember.

Anybody knows what I am talking about ... this doc should probably the base for fruther testing here ...?

derelor · December 30, 2015

...

I remember seeing a document (by ED?) which listed all the different types of buttons and switches and how they are to be implemented in DCS (left-click, right-click, etc.). That was not too long ago, but I can't find it now ... was it mentioned in the 2.0/1.5 bugs section ... damn, can't remember.

Anybody knows what I am talking about ... this doc should probably the base for fruther testing here ...?

See

http://forums.eagle.ru/showpost.php?p=2597009&postcount=2

and

http://forums.eagle.ru/showthread.php?t=156638

dotChuckles · December 30, 2015

Yep. Having to click 90 times to command a turn. Fun!

A small thing though. Otherwise I'm loving it.

Azrayen · December 30, 2015

Have to say, though, that turning the heading bug on the HSI by clicking (instead of using the mouse wheel) is a real chore. Not sure if that was intended?

Well, to be honest I'm not even sure this knob should rotate the heading bug.

Anyway, you have another way of rotating the bug (and this one I'm sure is correct):

With AP engaged, use left/right trim hat.

Flagrum · December 30, 2015

See
http://forums.eagle.ru/showpost.php?p=2597009&postcount=2
and
http://forums.eagle.ru/showthread.php?t=156638

Yes! Thank you!

But then this thread is a duplicate as the issue(s) is/are already reported. Razbam will take that document as base for the fix or should we add possible new findings to the list Redglyph had already posted in that other thread?

rrohde · December 30, 2015

Well, to be honest I'm not even sure this knob should rotate the heading bug.

Anyway, you have another way of rotating the bug (and this one I'm sure is correct):
With AP engaged, use left/right trim hat.

Interesting. Going to try that!

So, what else might that knob be for then?

Azrayen · December 30, 2015

Setting the "vecteur additionnel", defined by a delta from the active waypoint (I think from memory). Must check.

rrohde · December 30, 2015

Anyway, you have another way of rotating the bug (and this one I'm sure is correct):
With AP engaged, use left/right trim hat.

That works beautifully. :thumbup:

But is the stick supposed to move then as well? It does... Considering it's under AP control?!

EDIT: Not sure if glitch, one-off, or feature, but at one time, when using the left trimmer to move the heading bug to the left, it snapped right back to North when only briefly moving the trimmer to the right. Also, when moving the bug to the right, and then the trimmer to the left, it snapped right back to North. However, this only happened to me once out of three tries, and I don't know if that's a setting or a glitch. Thoughts?

Edited December 31, 2015 by rrohde
One more thing...

Azrayen · January 8, 2016

Have to say, though, that turning the heading bug on the HSI by clicking (instead of using the mouse wheel) is a real chore. Not sure if that was intended?
Well, to be honest I'm not even sure this knob should rotate the heading bug.

Anyway, you have another way of rotating the bug (and this one I'm sure is correct):
With AP engaged, use left/right trim hat.

I can confirm that what is (currently) called the "heading bug" of the HSI is not that.

The heading index (green) is only about the AP, and should only be controlled through the trim hat left/right when the AP is engaged.

The knob serves a very different purpose, it's a bit complicated, will take time to explain later (and in a dedicated topic), but basically IRL it is used to set an offset waypoint from a TACAN beacon.

EDIT: Not sure if glitch, one-off, or feature, but at one time, when using the left trimmer to move the heading bug to the left, it snapped right back to North when only briefly moving the trimmer to the right. Also, when moving the bug to the right, and then the trimmer to the left, it snapped right back to North. However, this only happened to me once out of three tries, and I don't know if that's a setting or a glitch. Thoughts?

It snapped North or straight ahead?

Straight ahead is logical, when you engage/disengage AP (via the AP standby trigger most of the time) then AP heading is reset to straight ahead.

++

Az'

Edited January 8, 2016 by Azrayen

spiddx · January 8, 2016

It snapped North or straight ahead?
Straight ahead is logical, when you engage/disengage AP (via the AP standby trigger most of the time) then AP heading is reset to straight ahead.

++
Az'

It snaps to North. No AP Standby is involved.

To reproduce:

Instant Action Free Flight Day (1.5)

Initial Heading is 035

Engage Autopilot (mode doesn't matter)

Move Desired Heading Needle to 300

Once there immediatly change direction to 330 (while plane is still turning west) => Green needle snaps to 000

Observations:

- This only happens when the green needle crosses the 000 heading, doesn't happen for example if you want to go from 150 to 200.

- If you caused the bug (?) once it is then no longer needed to cross the 000 heading. It then happens across the whole HSI spectrum.

- Maybe related to this? http://forums.eagle.ru/showthread.php?t=157331

spidd

rrohde · January 8, 2016

It snapped North or straight ahead?
'

Always North!

Toertchen · January 8, 2016

This is DCS standard AFAIK (except for the left/right choice: DCS standard is left=counterclockwise, Razbam did reverse that).

Will RAZBAM change it to "DCS standard" or is that RAZBAMs decision?

spiddx · January 8, 2016

For the next update we've fixed it so it conforms to DCS standard. I'll look into the other things mentioned in this thread.

:thumbup:

grunf · January 8, 2016

I'll look into the other things mentioned in this thread.

Please don't forget the altimeter pressure setting knob. :)

grunf · January 8, 2016

Already added in! Just haven't had a change to update the pending fixes list.

Great! :thumbup:

spiddx · January 8, 2016

I just noticed another probably related thing:

When you overfly a waypoint heading 030 and the next one is 330 for example, the waypoint caret on the HUD points to the right side instead of the left. The same happens vice versa. The caret jumps to the correct side once the airplane's heading goes past north.

For some reason the simulation really doesn't like going over that 000 heading. ^^

gospadin · January 8, 2016

I just noticed another probably related thing:

When you overfly a waypoint heading 030 and the next one is 330 for example, the waypoint caret on the HUD points to the right side instead of the left. The same happens vice versa. The caret jumps to the correct side once the airplane's heading goes past north.

For some reason the simulation really doesn't like going over that 000 heading. ^^

yea, they seem to be missing an ABS() or a %360 in their code

Edited January 8, 2016 by gospadin

spiddx · January 9, 2016

Glad I could help. :)

Azrayen · January 9, 2016

the waypoint caret on the HUD points to the right side instead of the left.

Just a sidenote: the Δ should not be a waypoint caret (I know it is now in DCS, it's an implementation error).

Nevertheless, keep reports coming, like CptSmiley said :)

Sign In

Some in-cockpit knobs don't rotate

Recommended Posts

rrohde

Azrayen

rrohde

Flagrum

derelor

dotChuckles

Azrayen

Flagrum

rrohde

Azrayen

rrohde

Azrayen

spiddx

rrohde

Toertchen

spiddx

grunf

grunf

spiddx

gospadin

spiddx

Azrayen

Recently Browsing 0 members