I have v1.31 of the A318/9 and A320/321 installed in P3Dv3.3.5 and I am constantly having problems with the autopilot disconnecting by its self. This happens normally in the cruise phase when flying a constant heading, speed and altitude, it also has a tendency to disconnect during the descent phase as well. The audible alarm goes off each time but only sometimes is the "auto flight off" announcement made. When the AP is manually disconnected the announcement is made every time. To recover the situation I simple press the AP button to re-engage the autopilot ("autopilot is going on" is always announced). This happens every time I fly any of the buses and does not occur on any other aircraft (PMDG 737ngx, 777 or iFly 747, Twin Otter etc). This has been occurring for some time now and was also happening when I used P3Dv3.1 and P3Dv3.2
I have recently uninstalled the aircraft and re-installed them as per Mathijs Kok "Do This" recommended procedure from the Update section of this forum but with no success. I have checked my Saitek Pro Flight Yoke inputs, calibrations, null zones etc (even the joy stick in the cockpit is not moving and is steady when the fault occurs).
I have approx. 31-35FPS when in the cruise and I have disabled AS16/ASCA (and ASN previously) but the autopilot still disconnects. I have over 850 on-line flying hours with BAV on the airbuses and consider myself to be a pretty competent bus pilot (I followed the tutorials from the outset). Please see the attached screenshot when the AP has dropped out.
My system specs are; W10, i7-5960X 3.00GHz, 32GB Ram, 2x Titan Blacks, 1TB SSD 840 EVO and 500G SSD 840 EVO drives.
Any assistance to resolve this very annoying problem would be greatly appreciated.
Tom going thru tons of documentation doesnt explain a simple airbus generated plan it should not look like this - you show me what you get - take you 2 mins to do - something is very wrong here and you have a avoided my request for help - I tried the font fix for windows 10 and that didnt help
As a matter of fact I go to the trouble to post a picture of all of those redistributes and you didnt answer that question ? same old answer
" the step by step guide" thats not the problem - need someones help willing to help - not happy
seems like Version 3.35 has somewhat killed the new layering methods introduced by LM. We have tested 3.33 and it works
without problems, but not 3.35. My problem is, I can change whatever I want: it will remain an unpredictable behaviour of the ground polys flipping above others.
Glad to see you found the culprit !
Yesterday evening i spent a few hours fiddling around with "all" available P3D settings, just to see if any changes would cure this issue, guess what : without success
Actually it´s the only airport i´m having this problems with, your other releases work great.
Let me know if you want me to try / test any files or if you need my exact specs, i´ll be glad to help you .
Das gleiche hatte ich auch diese Woche. Mach mal ein Update auf die neueste Version vom Airbus Neo. Zudem hatte ich genau die Anzeige so, als mein Airbus nicht Aktiviert war!
Wichtig, nach dem erneuten Aktivieren den Airbus neu laden.
thanks for your post. The good news is that I can reproduce the error on my system, but only for the RWY. Yellow taxiwaylines remain normal.
I´m actually checking it, seems to be a problem with the new Z-Layering of ground polys. Since LM will cut
the use of Asm ground polys in the future they substituted it with their own system, which I used, but it seems to cause some problems
depending on ______ ?