Der Michel

Yep. Appr VNAV is totally bugged.

I also mentioned this in one of my posts. No idea what they mean with that Changelog entry. But if it is what we see here….

Yeah, airport/ground chart is not the same as the data required for the ANF.

Looks like corrupt file. Are you running the Marketplace version? Have you tried to reinstall it local? Not sure if SU2 does allow it. But SU3 (released to be soon) should allow to download local Addons from marketplace.

Microsoft has a contract with LH Systems for the LIDO Charts and NavData. Not for the Airportmaps. They are not included in MSFS2024.

Hi, if you have a sidewind component, rudder input (trim) is required to turn the aircraft slightly into the wind to keep your desired heading. This will result in different airflow above both wings and also some airpressure on the forward side of the vertical stabilzer. Both will result in some induced rollmoment. To compensate that rollmoment you need also input from your roll control surfaces. Spoilers 3-7 are also used for rollcontrol (not only the ailerons). Maybe that is what you see in your screenshot. A screenshot from the ECAM F/CTL page and ND in that situation would be great.

DXGI DEVICE HUNG is something we know well from P3D times. Graphic Driver related. In the past it was one possible solution to set the TDRLevel in the registry. Just google for DXGI DEVICE HUNG, bunch of results.

Hi, after the long weekend I want to sum up and clarify some points: In the first I was really frustrated when I opened the topic, because of my first flight experience after the latest fix. I'm very thankful to the dev team for their countless work to improve the plane. The number of fixes in each update proof that. But that number of fixes and we have now 12 of them and the current state is also one reason why I'm so frustrated. Sometimes it feels like 2 steps ahead and 1 back. Let's face the current VNAV for the approach, which seems to be broken. How can that be released? Basic approach types can't be flown, because of wrong and bugged implemented FLS. I stop now, because I don’t want to do a rant. As said, I'm thankful for the team @ iniBuilds. Keep up the work. I just hope that all the basic stuff gets fixed soon. I don't care for abnormal in first place, but all implemented systems should work as intended by Airbus in normal situations. I from my side I will try to post/report as much as I can. But with all the bugs I reported now, I don't have time to check every one, if it's fixed or not after another update. It would be really great, if we can get a "logged" tag and if the dev team can add a "version number" or "fixed" tag, if the report is fixed and positiv tested by the test team. Yeah, that would mean a second bugtracking system. Or just add the forum link to the fixed item in the changelog (I assume you have the link already in your bugtracking system). Thanks and kind regards

Maybe caused by the last fix? changelog 1.012: FIXED: Arrival Runway is now part of MISSED APPR + VSD ending too early [2024 only, 2020 in production] For this APPR the KEWR29 has to remain green!!!!! If the RWY is part of the APPR coding in NAVDATA it's always green. There are APPR, when the MAP is prior the Treshold and the RWY is not coded in the APPR navdata, then the RWY is not part of the F-PLN but also not part of the GA, because then the RWY is not indicated in F-PLN. The F-PLN is really easy...just indicate, what is in the NAVDATA coded. If the Runway is coded or not, is independent from the white runway at the ND.

The circles arround the WPT at ND should match the colors of the asterix at the FPLN. Are the constraints met or not?

I know for sure that LIDO has coded a constraint of +834 for COPKO in the NAVDATA. Jeppesen doesn't have that. I also know that the constraint is indicated at the ND in reality for this approach. KEWR29-Y RNAV (RNP) My setting is sim default. So why is the constraint missing?

BTV is indicating TOO SHORT without reason

So many bugs in just one approach....some already covered in other posts and not mentioned in the following list 1. VNAV calculation at F-PLN...wrong...sorry but why is the VNAV ignoring the constraints? TETER +3000, GIMEE +2500, JIMLO +2500 2. VD complete wrong because of VNAV 3. ND missing VD bracket 4. PFD missing LDEV, VDEV and RNP AR --> FSL was deselected --> shouldn't be necessary (nr.6) 5. ND missing LEG RNP message: at this position: "LEG RNP 1.00" 6. I had to deselect FLS manually....RNAV RNP can't be flown with FLS in reallity--> greyout the associated button!! 7. LEG RNP missing at F-PLN 8. KEWR29 should be part of the active FPLN and green! The Route I used: KBOS/4R PATSS7 PATSS DCT NELIE FLOSI4 KEWR/29 I deleted the wpt after NELIE to TETER manualy.

Line between RWY and COPKO is missing

ND is missing the (RNP) behind the APPROACH