In fact is has gotten worse - at least for me. Until now I could use the WT-CJ4 mod and change all autopilot values with the mousewheel in 1.000’ increments and by left-klicking with 100’ increments. After SimUpdate 3 I had to delete my gearup/geardown bindings on my Thrusrtmaster Warthog throttle, because that’s what’s sending constant input - Thanks Asobo - if you couldn’t fix it, why didn’t you leave it as it is?
So, if you watched the Q&A. Sincere apologies of Martial that he did interpret this question for another bug. So not fixed yet, but they are working on it. Just a little bit patience and we can be happy with a fully working Honeycomb!
I did post yesterday about the possible confusion about this bug and what they’d talked about in last Q&A:
Discussion: Sim Update 3 (1.14.5.0) - #701 by CptLucky8
But I don’t understand Martial’s relating this bug to the Alpha Yoke, because it is not just a problem with this yoke but a more general problem rooted in the control acceleratoin logic (so it seems) and very similar to the same bug present already in the FS9 code base.
After watching the Q&A today and seeing this issue mistakenly linked to the Alpha yoke by Martial and Jummivana, I want to again reiterate to anyone from Asobo reading this:
This is a problem that goes beyond the Alpha yoke. This issue has to do with how MSFS’s code handles all forms of inputs that are being held down. A global acceleration variable is being turned on instead of a variable linked only to the input that is being held down.
Just to highlight how this isn’t just an Alpha yoke issue, you can replicate this issue using nothing but a keyboard (see my original post). If the person or persons in charge of fixing this issue think it has to do with just the Alpha yoke, they are unlikely to get to the root of the problem and that is worrying.
2 Likes
So, if we don’t want to add FSUIPC or re-map the switches on our yokes, we have to wait for Asobo to understand that that this is their issue and not Honeycomb or Logitech’s issue?
I haven’t used the sim in about 3 months hoping that it would be in a more ready state. But, that may not be the case. I guess, I put it back on the shelf again for awhile.
2 Likes
I came here to say this… how is this not talked about more? The bug got worse. Single clicks with the mouse no longer allow us to move in 1 degree increments. They made the problem worse!
1 Like
Microsoft and Asobo should be ashamed of themselves for the quality of their product. At least they sucked up Working Title to get some people on board that know what they’re doing. The only good thing about this simulator is the graphics, period! Systems are awful and flight dynamics are pitiful. It’s not bad for a game I guess, but its not much of a simulator. I’ve been a pilot for 46 years and have been in a lot of aircraft and not one in this game measures up. SORRY
2 Likes
I may be wrong, but after the move to hire the WorkingTitle Crew I begin to feel a lack of competency at Asobo for the simulation aspects of the game. Don’t get me wrong - they have built a great foundation from the environmental perspective and I’m not bashing them, but I did not see fundamental progress when it comes to such issues as this obvious bug - and you know best there are a few more - , at least not considering the 200 people they pretended to be working on it.
What disturbes me is the move to integrate these WT guys into their internal environment instead of opening the sim further so more 3rd parties like you can get involved in improving the product.
1 Like
I’m not a programmer but it’s obvious that the only thing working is buttons. As soon as I bind any function to one of the many switches on my Thrustmaster Warthog throttle (not some totally uncommon peripheral imho), the increment bug appears. What I don’t get is how this can go unnoticed for Asobo - don’t they have peripherals with switches at their facilities?
2 Likes
Just to clarify: As a rule of thumb, ANY joystick peripheral with ANY “always on” switch (aka not a momentary button) bound to the sim will cause the issue. On the alpha, that just happens to be all the panel elements (switches, magneto selector and toggles) while everything on the yoke handle is just fine because it’s all momentary.
3 Likes
Any mapped button can cause it, just keep it pressed.
This might also explain why in the previous Q&A he was saying Force Feedback is implemented while it is not.
I’ve posted the question for yesterday’s Q&A but it seems it was not high enough in the list because it was not talked about at all: Live Dev Q&A: Guided Question - #15 by CptLucky8
And the Parking Brake lever of the TCA Addon too, it also send a constant input when parking brake is set to ON. Not to mention the Ignition Knob when set to IGN/START.
Will there be a fix? I worked fine before sim update 3…
1 Like
Since the update 3 … I have this bug of 10 degrees increment with speed and heading, what a pitty, it was perfectly working before update 3 … this update is really starting to drive me mad and i’m clearly losing patience.
3 Likes
same here once u click autopilot it happens
Ok, so I had time to loose instead of flying (thanks microsoft) … I tried the workaround for the people with honeycomb alpha yoke, and I had to remove
- All Magnetos Buttons assignements
- All light Buttons assignments
- All Electrical Button assigments
- All avionics button assignement assignements
Removing the buttons I was thinking please, I hope I have not to remove, flaps, trim, view or autopilot disconnect …
Now it’s working, I have 1 degree increment … yeeaaah, bought a powerful yoke to finally remove all cool assignements thanks again microsoft and asobo.
4 Likes
That’s crazy that you had to do that!
I’m fricken loving the vJoy + gremlin solution!
I’ve got it working perfectly with lots of extra functionality by prorating an assigned shift button
Couldn’t care less If they fixed it because the ‘condition’ statements in gremlin gives me so many options
I’ve noticed that this same bug also effects trim as well as the heading.