Hoffie3000

There is a point what you can check too. The Option page 2/2 of DAVE show the option "Use Ground Friction Tweak" Contrary to the text in the tutorial this option should be deactivated. See also documentation Vol3_Tutorial, capter 3.6, page 12

Question: What Aircraft? Please post the flightplan in kind of: Airport/Rwy - SID - Waypoints - STAR - AirportRwy

3 flights with A319 cfm 1 flight with A319 IAE Fortunately, the descent behaviour, at least of the A318/A319, has improved significantly. Three flights with the A319cfm and one with the A319IAE and TOD were perfectly calculated for all four approaches. Even the ASPA4W-STAR with the Altitude constraints (LOWW-->EDDF), which was difficult for the buses up to now, was flown off flawlessly and quite evenly. Now the Dev can treat themselves to a beer😎 The only flaw I see is the climb behaviour of the IAE version of the A319 in "Managed Mode". While with the same weights the cfm version masters the climb to e.g. FL340 without any problems, the IAE version's climb rate to FL340 above FL220 decreases very much and goes down to approx. 500-700ftmin. But after switching to the "Selected Mode" I was able to increase the climb rate to 1500ft/min without any problems, without reducing the speed. regards, Wolfgang

First flight with version 1.2.3.1 and I was really pleasantly surprised, the TOD was well calculated, it sank first with about 4500ft to reach the 340 KIAS target Speed in descent and then normalized. I didn't need the speedbrakes for the first time Let's see what the other flights show

Nice diagram, but too little further information to judge. What engines has the aircraft? CFM or IAE engines? Flight Level and Speed? How did you log the data?

Nun, jedes Flugzeug hat eine aircraft.cfg. Diese kann man mit dem Editor öffnen und bearbeiten.

Es handelt sich um die fsuipc.dll im Modules-Ordner des FSX. Wenn Du kein Zusatzprogramm hast, dass diese .dll benötigt, kannst Du diese einfach löschen, oder umbenennen. Ansonsten die .dll aktualisieren.

Today I have another flight from ESSA --> EDDF at FL380. Again passing KERAX at FL110. Now the difference between theorie and practice: Theorie: TOD should be 81nm before KERAX. Bus calculate TOD only 52nm before reaching KERAX. So the Bus was 29nm to late starting descent and ends in the well known extrem sink rate. For me, the descent looks behaved like in the picture. Please excuse the crooked line 😎 Red line should be the best descent phath. The blue line show the actual Airbus behaviour.

Hello Bob, that was the flight plan: EDDH (Rwy23) to EDDF (Rwy07L) AMLU9B AMLUH UM852 HLZ T157 KERAX KER07N Alternate: EDDK Distance: 334nm + 80nm (Alternate) FL320 Cost Index: 80 ZFW: 55.1 / 20.1(ZFW%MAC) Pax: 124 Cargo: 5000kg Fuel: 6509kg Trim: Up0.9 Airbus FMC normally calculate with the whole KER07N-Transition. But ATC online will see your Aircraft always at FL110/KERAX for better spacing and pick up planes to final Approach. So I was set manuell for KERAX: 320/11000 But the nm difference between theory and practice can also be seen in every other flight. This is not limited to this route. Regards, Wolfgang

Fortunately, the first flight (EDDH-->EDDF) went without problems. The most striking are the changes in the colours of various numbers. With the exception of the well-known "flaws" I didn't notice any new errors. You can update to this version with a clear conscience. The "flaws" I noticed: The vPilot client (for VATSIM) is still not recognized if you load the Airbus directly from a saved "Turn Around State", or "Cold Dark State" in P3Dv4.4. But after reinstalling the Airbus, the "Taxi State" is active and vPilot is recognized there. Ok, if you know it, you do the known workarounds, but it's strange that after such a long time it still doesn't work. Even the old 32bit Airbus could do it. Descent behavior: Nothing has changed to good, the bus at the TOD still goes into a more or less violent nosedive, with sink rates >6000ft/min. I looked at the map and measured why the bus is doing this and now I know that the bus has no other possibility with the current programming. If you compare the distance from TOD to a given waypoint and FL, in my case KERAX /FL110, then the bus starts about 19nm too late with the descent! So it has to go into a quasi dive to reach the desired FL at the given waypoint. You can use the formula: (Flight Altitude,ft/1000)*3 calculate the TOD quite practically and usually comes to sink rates of about 2000ft/min -> 25000ft/min depending on the wind. In this case the distance is to KERAX/11000ft: TOD calculated, red arrow: (32000ft altitude- 11000ft KERAX)/1000) *3 = 63nm TOD Airbus calculated, yellow arrows: approx. 44nm This results in a difference of 19nm between theory and practice and is the reason for the strange descent behaviour. I am sure, if you give the bus more distance for the descent, the descent behaviour will change positively. Regards, Wolfgang Translated with www.DeepL.com/Translator

If both Anti Ice activated, Wings and Engines, you get exact 35% N1. If you activate Wing Anti Ice only you get 30% N1. Check it.

Really a strange Problem. Are you still on P3Dv4.2 and where are the Install-Folder of P3Dv4? P3Dv4.4 is stable. Some people have only partially updated their sim and get some probs. The suggestions is a full install of P3Dv4.4

I flew your flight - BUF7.GEE AUDIL RKA.HAARP3 - twice with the CRJ7, with the result that both flights were normal. As approach I chose once the RNAV Z Rwy22 and the second time the ILS Z Rwy22, both were flown off flawlessly. Only during the RNAV approach the ILS frequency did not turn in automatically. But I'm not sure if that's the way it should be. The manual input solved the problem. In general, the CRJ´s is sensitive to high speed turns with SID and STARS, they like to lose course and don't come back to it. But if you consider that, the CRJ´s SID and STARS fly off well. Do not mix different Approach routes like RNAV and ILS. With the screenshots you can compare your settings: KBUF Chart: "TAKEOFF RUNWAY 5: Climb heading 055° until leaving 3000. Thence..." Take off 190KIAS - climb 3000ft thence activating Autopilot (Speed 190KIAS and NAV was preselected at ground) After positive sign of route intercepting increase speed up to 250KIAS. climb normal intercepting RNAV Z Rwy22 (speed should be 250KIAS, I know ) final Regards, Wolfgang

Hallo Oliver, ich wundere mich gerade, da bei mir ENBR nicht im Vector Tool auftaucht und damit auch keine Höhenkorrektur stattfindet. Die SODE-Gate sind bei mir ok. Hast Du die letzte Version von SODE installiert, oder ist noch irgendwo ein zweiter AFCAD aktiv? Gruß, Wolfgang

Are you both at the latest CRJ Version 1.2.3.0 ? Normally it works fine if you set LDG ELEV during cruise. I have only probs during descent if I forgotten to set LDG ELEV in time. Your screenshot shows a CALT from 19000ft. Thats way to high.