POSSIBLE TIP?

One thing I have discovered is that when loading a new flight, or even more so when using the developer mode "resync" function after a tweak, I have to remember to fully move each control to the stops and especially the left/right ailerons before flying. If I don't then the flight model and autopilot behave in a strange way. Example, when flying the a320 if I just gently rotate the aircraft then engage autopilot and select an altitude the a/p goes wild and overshoots every selected altitude. If I first move all the controls, including rudder to each extreme stop then engage the a/p it behaves.

Edited September 22, 20205 yr by robert young

3 minutes ago, regis9 said:

I spent a few flights wondering why my “stupid” autopilot kept on failing to hold altitude and was trying to kill me.  Then I realized the button on my yoke that was bound to change between internal and external views was also bound to autopilot disconnect in the Brunner software that runs the yoke.  So basically every time I changed views I inadvertently turned off the autopilot.  

Turns out some(one) was stupid, but it wasn’t my autopilot!

I had a lot of problems with AP when I mapped an unused throttle axis on my CH Fighterstick to the trim axis.  The CH hardware has some 'noise' in it (the input values tend to change back and forth by +/- 1 if you watch the raw data).  I think this was causing the sim to read the new trim value from the axis and overriding the AP trim.  This caused all kinds of fun mishaps with vertical AP killing me in various ways.  I remapped trim to 2 buttons and it went away.  The sim should be smart enough to ignore any trim axis inputs while the AP is managing the trim...or at least the AP should respond by resetting the trim it needs, not killing the pilot....

It would be really useful if there was a way to show a Dev Mode overlay that showed all of the inputs the game is receiving and acting on, so people could rule out control misconfigurations as the cause of some of these strange behaviors.  Say a running graph of each axis and a list of button presses.

Not saying there aren't bugs here - there surely are a lot of bugs - but some more data collection would help us provide better bug reporting.

2 minutes ago, robert young said:

POSSIBLE TIP?

One thing I have discovered is that when loading a new flight, or even more so when using the developer mode "resync" function after a tweak, I have to remember to fully move each control to the stops and especially the left/right ailerons before flying. If I don't then the flight model and autopilot behave in a strange way. Example, when flying the a320 if I just gently rotate the aircraft then engage autopilot and select an altitude the a/p goes wild and overshoots every selected altitude. If I first move all the controls, including rudder to each extreme stop then engage the a/p it behaves.

good info...

5 minutes ago, robert young said:

POSSIBLE TIP?

One thing I have discovered is that when loading a new flight, or even more so when using the developer mode "resync" function after a tweak, I have to remember to fully move each control to the stops and especially the left/right ailerons before flying. If I don't then the flight model and autopilot behave in a strange way. Example, when flying the a320 if I just gently rotate the aircraft then engage autopilot and select an altitude the a/p goes wild and overshoots every selected altitude. If I first move all the controls, including rudder to each extreme stop then engage the a/p it behaves.

I've noticed this as well. It's almost like the sim does its own 'auto calibration' of the axis inputs in addition/on top of the Windows DirectInput device calibration.  Running all axes back and forth before flight does improve the consistency of things for some reason.

The main problem I'm having is with the elevator trim. This has been an issue from the beginning for me.

On the Saitek yoke,

Flight Control Surfaces\Control Trimming Surfaces\Elevator Trim Up (nose up) is mapped to A2 (rocker switch under the left thumb), and nose down is mapped to A1.

In every aircraft from FS9, FSX, and P3D, this works perfectly. My expectation is that I can relieve back/forward pressure on the yoke by clicking the switch up and down incrementally. For example, In the NGX and every PMDG, Default, QW, Aerosoft, Carenado aircraft, this works great. In MSFS, I get no reaction or violent movements, but if I click it a couple more times, I get full up or down making for a wild ride. It seems to be completely unpredictable to know what it is going to do aside from it be predictably bad. You can eventually get things to settle down, but if you add speed, for example and try to re-trim, things go wonky. I can be at a stable trim nose up at 300fpm climb, and if I increase the throttle, I get nose down even as I'm trying to trim up. To me, this doesn't seem right - nose up and more speed should result in a steeper climb, not nose down.

When I search by input to check for other assignments tied to those switches, I'm not seeing anything else mapped to them.

Not sure what the issue is here. User error is always possible, but it doesn't seem like that is the case here.

14 minutes ago, duckbilled said:

The main problem I'm having is with the elevator trim. This has been an issue from the beginning for me.

On the Saitek yoke,

Flight Control Surfaces\Control Trimming Surfaces\Elevator Trim Up (nose up) is mapped to A2 (rocker switch under the left thumb), and nose down is mapped to A1.

what do you mean by rocker, is it a HAT switch ? when you do a search for it does it say Joystick POV ?

1 hour ago, FPStewy said:

Been flying the van lately without a problem, what are you experiencing ?

For me, the AP won't capture the altitude anymore, just keeps going and going...

2 hours ago, stubbornswiss said:

- I have the latest version of the FlyByWire A320NX, the 'Tooltips-SeeThrough' add-on, the 'NoToolbarHandle' add-on, as well as the folders for

Is that the mod to remove tooltips or is it a mod to make them somewhat transparent. If the later, could you point me towards it.

Here ya go.....

https://www.reddit.com/r/MicrosoftFlightSim/comments/ipdrir/i_think_ive_removed_the_tooltips/

You get both... remove or resize and make somewhat transparent.

Edited September 22, 20205 yr by stubbornswiss

I have never bought a game with so many bugs and which is so poorly optimized, I hardly dare think about what will happen after the next patch.

3 minutes ago, Ixoye said:

I have never bought a game with so many bugs and which is so poorly optimized, I hardly dare think about what will happen after the next patch.

I'm willing to wait it out but now the question is, are they going to put a skeleton crew on fixing this now and moving to other projects. Also a big part of the problem was the sheer hypocrisy of YT promoters saying absolutely nothing about this and still don't but they got their clicks and promotions.

3 hours ago, FPStewy said:

Trust me I understand your frustration, and I don't have anymore problems with the AP or Heading, the AP works and the heading bug works, the problem with the AP which was discussed and solved is that there are to many buttons/keys assigned to the AP just disable them all except the button/key that you want for the AP as for the heading disable anything that has a toggle assigned to your yoke for example lights, battery, mags ect...

Hi, so if i only use the mouse for AP operation, is it safe and better to avoid problems to delete all keyboard assignments to AP?

3 minutes ago, kapitan said:

Hi, so if i only use the mouse for AP operation, is it safe and better to avoid problems to delete all keyboard assignments to AP?

basically what I did personally was that I wiped all assignments from my, keyboard, throttle and honeycomb yoke and redid them one by one and everything is fine, I don't have any issues.

 

Edited September 22, 20205 yr by FPStewy

2 hours ago, FPStewy said:

what do you mean by rocker, is it a HAT switch ? when you do a search for it does it say Joystick POV ?

On the yoke, under the left thumb below the hat there is a switch that goes up and down. Push up and you get button A1, push down and you get button A2

6 hours ago, C130FE said:

The heading bug still will only move 10*

You can work around this issue by subsequently pressing the heading knob when the desired heading is reached. It takes most aircraft some time to turn 10 degrees.