[REPORTED] Cockpit switches: little inconsistencies & misc. problems

Hello,

I had some fun with this wonderful aircraft :)

So much that I started to do the same reporting as the A-10C for the cockpit switches, to make sure they're consistent and easy to use. I'm perfectly aware it's still in beta, so you may already know most of it, please bear with me.

Here are my findings so far, let me know if that's worth going further.

Below, by "analogue" I mean knobs that can be turned with the mouse wheel, or by maintaining the left mouse button and moving the mouse up/down.

I'm using this spec as reference: http://forums.eagle.ru/showpost.php?p=2597009&postcount=2

(*) case of most protective covers

(**) case of most knob switches, not all of them though

(***) same as (**) comment for 3-way switches

Hope it helps. Don't be fooled by my fussiness with the manual and the switches, I think it's great already as it is in beta, just wish to help a bit with what I saw to make it even better :)

Inconsistent input logic already reported as ticket #33056.

OK, good!

I've just seen that the PCN (or even INS) wasn't fully implemented yet, that's what I thought. Scratch what I mentioned about that in my previous post.

Inconsistent input logic already reported as ticket #33056.

Do you know whether the report covers the logic between right and left mouse clicks? AFAICT the M-2000C has this consistently reversed as compared to all other modules. E.g. on rotary switches, right clicks should be clockwise, left clicks should be counter-clockwise. The M-2000C Radar Mode Selector, among others, works the other way around.

I'm just asking because I'd be willing to compile a list of all buttons and switches that come to my attention, but if this is already (indirectly) included in the ticket, there'd be little use of doing double work. ;)

Agreed. Mostly it's limited to the A-10 and the M-2000C, but a few other modules have the left/right "backwards" relative to what I think of as natural, at least.

Do you know whether the report covers the logic between right and left mouse clicks? AFAICT the M-2000C has this consistently reversed as compared to all other modules. E.g. on rotary switches, right clicks should be clockwise, left clicks should be counter-clockwise. The M-2000C Radar Mode Selector, among others, works the other way around.

 

I'm just asking because I'd be willing to compile a list of all buttons and switches that come to my attention, but if this is already (indirectly) included in the ticket, there'd be little use of doing double work. ;)

Erm, that's what I was asking when starting this thread. But apparently they are aware they have to review all this, hopefully soon because it's really disturbing. But yes, all knob switches are reversed apart from these three I think:

- INS Operational Mode

- EW Mode Selector Switch

- Gun Target Wingspan

(except those which aren't implemented yet, of course). Same with the 3-way switches, except a few like Bomb Fuse Selector Switch for example.

And then there are some ugly cases like the TACAN Mode select implemented as an analogue knob, and the HSI Heading being implemented as a switch.

Agreed. Mostly it's limited to the A-10 and the M-2000C, but a few other modules have the left/right "backwards" relative to what I think of as natural, at least.

... or relative to the specs linked in the 1st post. I think those aircraft should have consistent controls.

Erm, that's what I was asking when starting this thread.

Obviously. ;)

Unless I missed it, your post doesn't include the Radar Power Switch (which I mistakenly called "Radar Mode Selector" in my previous post), or does it? That's why I asked if the devs are looking into the whole buttonology or "just" the ones you listed. :thumbup:

No, it doesn't, but what I mean is I already asked whether it was worth going further, and derelor didn't seem to say so. Since he gave this "spec" and already helped with the same issue on the A-10C, he must know how those switches are supposed to behave anyway ;)

If only we could see the tickets, that'd be easier.

If only we could see the tickets, that'd be easier.

Agreed!

I wouldn't be surprised if the knob/mouse interaction had some amount of influence from Falcon BMS ;)

...

- tacan knob to select tens: wraps around too early between "1" and "12" (minor)

...

hello,

Not sure it's the same issue,

I don't see "00" or empty for the tens. when i send argument value "0" the Tacan goes to "1".

How do you select channel X5 for example ?

I think it's missing "00" on tens !

Thx,

hello,

 

Not sure it's the same issue,

I don't see "00" or empty for the tens. when i send argument value "0" the Tacan goes to "1".

 

How do you select channel X5 for example ?

 

I think it's missing "00" on tens !

 

Thx,

I confirm it's apparently not possible to have channels < 10. That's probably what is on the "Pending update fix list" (- Fixed TACAN range units).

Also, going from X to Y takes too much mouse wheel rolling, it's a bit of a pain (especially since it's hard to select X/Y and tens, as it is hard to select front and back knobs in general in this aircraft).

i thought "Tacan range units" is for the display in HSI..

Maybe, I didn't follow that one.

In that case there's another problem, though I think that those channels are currently not used on the available maps. Still, a bug.

[REPORTED] Cockpit switches: little inconsistencies & misc. problems

Maybe, I didn't follow that one.

 

In that case there's another problem, though I think that those channels are currently not used on the available maps. Still, a bug.

X5 is a channel used by a tanker in mfm missions...

Cédric

TACAN panel issues are already reported (#33289).

Please create one thread per issue in the future.

Little update as follow-up with 2.0.1.49921.15.

Some of the knobs are still turning the wrong way in 2.0.1:

- INS mode selector

- INS parameter selector

The HSI course selectors acts erratically when holding left mouse button and moving the mouse up and down.

So does the barometric pressure calibration knob.

The ADI height adjust doesn't seem to do anything(?).

The selective jettison switch goes through its protective cover (and is quite hard to catch). The A/B emergency cutofff switch does too. The FBW test switch also. The FBW channel 5 switch too. The Fire extinguisher too. (I'm pretty sure most of them were fine before).

Also noticed than the "communication menu" event, when bound to a joystick, actually triggers the nose wheel / IFF interrogation instead. Now communication is only possible with the keyboard \ key.

Also:

- Closing the cover over the anti-skid switch, when it's turned to OFF, visually flicks the switch to ON, but according to the warning light it doesn't affect its function.

Also noticed than the "communication menu" event, when bound to a joystick, actually triggers the nose wheel / IFF interrogation instead. Now communication is only possible with the keyboard \ key.

Try rebinding both functions, that did the trick for me.

Mapping Next WP (Object) and Prev WP (Object) : Can't change WP ; doesn't work in 2.0.1....

Cockpit interaction

Little update as follow-up with 2.0.1.49921.15.

 

Some of the knobs are still turning the wrong way in 2.0.1:

- INS mode selector

- INS parameter selector

 

The HSI course selectors acts erratically when holding left mouse button and moving the mouse up and down.

 

So does the barometric pressure calibration knob.

 

The ADI height adjust doesn't seem to do anything(?).

 

The selective jettison switch goes through its protective cover (and is quite hard to catch). The A/B emergency cutofff switch does too. The FBW test switch also. The FBW channel 5 switch too. The Fire extinguisher too. (I'm pretty sure most of them were fine before).

In 1.5.3.51218.38, those knobs and protective covers are still wrong. The HSI course selector does not work at all.

So is the HUD altimeter selector switch.

Also, this seems to put the canopy in a bad state:

- close canopy completely

- click on rest

- put in lock position

- click on rest => after the rest is not clickable

- put in neutral (not locked)

=> rest cannot be clicked anymore

I don't know whether those problems are known, whether I should still report them... ?

Just FYI there should be no such thing as an HSI course selector. The knob next to the HSI does not move the green course indicator in the real aircraft. They will be working on it but it's fine that it doesn't do anything at the moment. It was only misleading.

Just FYI there should be no such thing as an HSI course selector. The knob next to the HSI does not move the green course indicator in the real aircraft. They will be working on it but it's fine that it doesn't do anything at the moment. It was only misleading.

Thanks for the info, good to know!

Right, it's the additional vector, not the heading.

Which leaves the other problems, I hope they'll be acknowledged at some point. My concern is they're left out and we end up like the A-10C, wondering for each switch whether it's behaving correctly or working in reverse.

Perhaps I ought to create a new thread, the [reported] in the title is probably misleading.