pbrad74

The fact that we don't get acknowledged, something simple really, is a huge turn off. Something. "Hey, we're not fixing it", or "We see your post and working on it". Anything would be nice.

That would be a shame because so many people are still using 2020 because of the problems in 2024.

Just 2 of us I guess

Anyone?

Unfortunately this did not solve the issue. It looks the exact same.

There are some pretty severe speed bumps on taxiway F, between G and M. Will post photo(s) when I am done with this flight.

The most recent version fixed this problem for me. I've done at least a dozen flights since v1.0.9 was released and is performing much better. Do you have the latest version or did you buy from the MS Marketplace?

If you did that's great! You've got nice system too. MSI Laptop, Intel i7-10875H @ 2.3 GHz, 32GB Ram, nVidia RTX 2070

V 1.0.9 seems to have fixed this problem I was having. So far, two flights in after the recent update, the altitude calculations are correct. Thank you iniBuilds.

I am not experiencing this at all.

Figured I would make another post about this. After filling out INI A, then FPL pages, the SID's and STAR's have the correct speed and altitude constraints. However, after completing INIT B page, altitude assignments in between the constraints are crazy. See below. There is an altitude restriction of FL220, then it wants me to climb again before reaching the next altitude restriction of FL140. Not sure if iniBuilds is aware of this or not.

Same

I might be mistaken but, the most current version for xbox hasn't even been released yet, that would make it a MS issue. As PC users who bought the aircraft directly from iniBuilds and not the marketplace, we get the most current version immediately upon release. Marketplace users have to wait until Microsoft decides to update the marketplace. Xbox version is V1.0.7, check to see which you have.

Gobbly gook, nice! Didn't think anyone used that term besides me and Matthew Colville. Yes, I am using Navigraph and the current AIRAC 2402 cycle. I haven't done a flight with the A300 stateside in quite some time though so I will try tomorrow and see how that works. It might just be messed up for that region? I don't know, just taking a guess at it.

On final for LTFM RWY 17L.