and if so, have they committed to fixing it?  

I DID research the internet, the latest progress reports and schedules for Microsoft, Youtube etc..  and I'm not clear. it MAY be out there but I did search before asking.  thoughts?

What heading bug issue?

apologies if not clear enough - where due to toggle switches and other items, in conflict with the way the sim was designed, change in 10% increments vs 1% at a time if certain switches or toggles are activated such as lights, avionics etc on yokes, controllers etc

@Bert Pieke

 

They don't have a habit of confirming all the issues or publishing the complete bug list. Only the dozen or so of bugs with highest number of votes from the official fourm is published AFAIK.

Edited January 8, 20215 yr by Steku

It would be splendid if Asobo were to acknowledge, and more importantly FIX this issue.  It has been plaguing us since FS9.... and "the complete re-write" would have been the perfect time to dump this flooding issue.

Fingers x'ed!

C

I've never seen this.

1 hour ago, cavaricooper said:

It has been plaguing us since FS9

That's not my experience. I've run a 200-switch home cockpit since 2014 and it never 'plagued' me. In fact the first I knew of this problem was when people started to complain about the combination of MSFS and the Honeycomb Alpha yoke. This is, in fact, a win for Honeycomb Aeronautical, since their yoke has has brought to light a problem that was, in previous ESP-derived sims, vanishingly unlikely to be noticed.

The present problem is a collision of two different design issues, one of which is new to MSFS. Okay, it looks like the simplistic implementation of acceleration for controls such as the HDG bug may always have been there, but nobody noticed because it wasn't a problem. The particular circumstances under which it would be problematic almost never occured, and hence it was a defensible design. The problem is that MSFS has introduced auto-repeat when a switch is held down. This is why MSFS behaves differently than P3D and FSX (and reportedly also FS9), and it breaks toggle switches.

So. All they need to do is put it back how it was, with auto-repeat being an option on any given switch assignment.

In another thread a Honeycomb person was here saying they have brought it up with Asobo.

Funny that the Partnership video proclaims "100% compatibility" when it's bugged in the stock configuration.

What good is a "Partnership" when you can't get 1 bug fixed that impacts your hardware....the same hardware MS gave out to the "influencers" to generate the pre-launch hype storm.

Edited January 8, 20215 yr by marsman2020

1 hour ago, marsman2020 said:

In another thread a Honeycomb person was here saying they have brought it up with Asobo.

Funny that the Partnership video proclaims "100% compatibility" when it's bugged in the stock configuration.

What good is a "Partnership" when you can't get 1 bug fixed that impacts your hardware....the same hardware MS gave out to the "influencers" to generate the pre-launch hype storm.

Exactly. I’ve turned to Vjoy and spad.next for my configuration. I try not to use the built in sim control of the settings. 

I don’t think there is much Honeycomb could do as essentially their  controllers are just switch boxes with some axis inputs.  Fs2020 gotta get their programming right 

And I’m sure this problem is with any controller that has permanently on rocker switches but the honeycomb controllers just highlight the issue because there are so many of them

But to be honest once set up with vJoy and Joystick Gremlin it is almost perfect & a blast to use

I’m loving it and it’s well worth the time spent to setup & use vJoy & Joystick Gremlin but I can imagine the disappoint for people expecting an out of the box compatibility and not have the technical acumen to set up and use the workarounds

Here is my solution <Click>

Edited January 9, 20215 yr by Stona
Added link

9 minutes ago, Stona said:

I don’t think there is much Honeycomb could do as essentially their  controllers are just switch boxes with some axis inputs.  Fs2020 gotta get their programming right 

They could provide their own free utility which uses SimConnect to control the switch positions in the sim and allows them to remain unmapped in the MSFS controls dialog, and which doesn't require complicated setup.

They already have a 'connector' utility that controls the landing gear lights by reading the SimConnect variables from the sim and controlling the lights, so they've already written most of the code needed for such a fix - it's just adding some SimConnect writes instead of reads.

Given that "100% compatibility" is promised in their Partnership video, this is what I would personally expect as a customer.

But they have taken the position of "we've notified Asobo of the bug and that's all we are willing to do".

It's put me off buying their hardware to be honest.

Edited January 9, 20215 yr by marsman2020

Alpha testers have been pounding on this issue since well before release. It honestly boggles the mind that Asobo hasn't acknowledged (at least publicly), much less addressed this bug. @MarkDHI know you did a nice deep dive video on this root cause, but I submitted a similar detailed analysis in Alpha. I guess until more people upvote the bug on the official site, it will continue to be ignored.

Asobo can't even be bothered to fix incorrectly mirrored textures on the 787 and instead spent the last update messing up the perfectly acceptable textures on the DA40NG so it broke 3rd party mods, and swapping the naming of the PFDs on the DA62 so that broke 3rd party mods. 

I'm doubtful they will ever acknowledge or fix this.  Attention to detail is not their strong suit.

4 minutes ago, marsman2020 said:

Asobo can't even be bothered to fix incorrectly mirrored textures on the 787

No the problem is that they are spending too much time on making things pretty instead of making things work.