Leaderboard

And in the interim/as a backup plan just calculate your descent manually. Take your altitude in FL numbers (i.e. 330) and divide this by 3.3 (=100) to get the nautical miles to fly. It works the other way around, too, of course (i.e. at 50NM distance remaining you should be at 16.500 feet). This is valid for a normal descent schedule of M.74/280/250. Real pilots run this calculation in their head constantly, even during a VNAV descent. Cheers, Jan

Just checking as I have never read the advise to turn of the firewall. Windows defender, yes - but you don't need to switch off Defender. Just create an exclusion for the X-Plane folder.

by 3.3 FL 370 / 3.3 = 112NM away for your ball park descend point.

Hello IXEG Team, made a flight with v1.21 and observe the speedbrakes have not longer effect on speedreduction nor sinkrateincrement In v1.20 it was all o.k.

Ok, made a flight this morning from LFBD to LICJ. All went like a charm. Everything looks in fine working order. In my case, this update has given me a little FPS increase... go figure! I would love to see VNAV DESC fully working, as it seems to work just as with previous version, but nothing I can´t manage with a LVL CHG or VS descent. All in all, a great product! Cheers!

I can assure you that such is not the case. Gizmo has had no direct clashes with SASL since 2012. Dan loves to use this as an excuse, but if I'm going to call a spade a spade, we can chalk this one up to bad coding on his part. There are plenty of other SASL add-ons that co-exist just fine. Dan's just being lazy and placing blame where he sees fit because he likes to whine. This is normal for him.

You would be out of luck by disabling, yes. You would not only be disabling SkyMaxx Pro, but also Real Weather Connector in the process. When you disable SkyMaxx, default clouds take over. The config panel still works, but the SkyMaxx Pro clouds do not render. I haven't received any e-mails about a Kodiak issue, but out of curiosity, what happens?

Glad you got it sorted!

As VNAV code is changed this will likely change, because I believe it's supposed to be like other Boeing's, but for this product, to get proper VNAV calculation you MUST close the loop by filling out the entire flight plan.

Most common issue arises when the STAR arrival procedure contains orders like cross this waypoint above xxx & below zzzz. The FMC will always read them as cross them above zzzz resulting on a very late T/D. While VNAV is rebuild just to some briefing of the ruoute and altitude constrains, if wrong, simply type correct constrain on the scratchpad then override by pressing corresponding right soft key on the LEGS page. note: this also apply for SIDs. Always scan for those such kind of altitude constrains and make the corrections on the legs page. You will be fine. hope this helps

I fly the A32F in the real life as well (for 6 years now) and I got the FF320 on its last beta batch release. I only did a quick visual circuit and it`s a very good airplane indeed, but I think it still have some work to do on the flight model, ie: the landing quite unrealistic, lacks the ground effect and FBW`s flare mode. I will post my impressions on their forums as soon I got time for it. I fly simulators on PC since the FS5.1 (about 24 years now) and today I can say for sure the IXEG flight model is the closest to the real feeling of flying a jet airplane!