orlando011124

Hi, My love story with the A320 V2 has been a trouble one. First impressions were quite good. Some flights later and after one of those periodic updates trouble started. Some random failures but too frequent. Gave up and not more dates with A320 V2. Back to FBW. Now more updates,new flights and some more rigorous tests. it improved a lot. but sometimes a strange behavior happens again. Tried some help with MSFS forum to no avail. They do not happen in all flights, not easily reproduced. As the first (strange) behavior was MY FAULT, I hope you can help or give some tips. First thing I noticed was an inconsistent climb rate. My fault, found that A320 V2 uses CI in the flight profile calculations. As I import the FP's from Simbrief I would put some random values in the MCDU for CI. Neither A320 original or FBW uses that as a parameter. Now for what I am experiencing. Please note that it happens frequently but not always. ----On Managed MODE refuses to accept the descent altitude. Nothing happens when I press The ALT button. Sometimes it accepts going Open Descent and later return to Managed. Sometimes I have to select VS before going back to Managed. ----MD Shows correct constrain altitudes and MCDU wrong ones. Then Descent and Arrival is mess. ---- Managed Mode: On Approach the PFD shows the constrain for second next Altitude constrain and "forgets" the first. ---- Once I pressed the "Disconnect GPU" on the EFB and a few miliseconds later I was over flying the airport !!! (that button never pressed it again). Can you help me on these? I would like to keep dating this A320.