Litjan

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

We are looking into this! The interim solution here is to not fly another airplane but only ours . No seriously, we shall fix this ASAP. Cheers, Jan

Ooops - I didn´t check myself if they worked...back to Tom! Thanks for the heads-up, Jan

Hmm, ok - thanks for the heads up. Will check that out! Cheers, Jan

Nothing changed that should affect TrackIR, I think. Jan

Hi Bluedleta737, the VNAV descent planning can get pretty wonky - please consider it a WIP. We are going to improve on it. For now it works ok on simple routings (long enough, no weird restrictions during descent), but can be off for other cases. Just like in the real airplane, take everything the computer hands you with a grain (or tablespoon) of salt. Cheers, Jan

There is currently a bug in X-Plane where the cockpit instruments reflect the "landscape" outside the cockpit, and not the cockpit itself. Expect the reflections to even get better with the next X-Plane update. Cheers, Jan

It could well be that the reflective surfaces in the cockpit make you use more than the 2 GB of VRAM that you have - this would severely slow down the framerate. In this case you can try to lower your resolution setting in the X-Plane rendering options menu. With 2GB of VRAM your current VRAM use should not be more than ca. 1.8GB or so - or you risk severe slowdowns. Cheers, Jan

Hi - the progress page and waypoint time and fuel calculation is still WIP and will not work right all the time, yet. Cheers, Jan

Hmm, this is weird...

ok, we are investigating and should have a solution soon... Jan

Can you try to run without the "show vortices" option enabled in the preferences menu and see if the issue persists? Thanks, Jan

We will investigate - try to disable your "draw vortices" function in the preferences menu for now? Cheers, Jan

Not surprisingly. We didn´t change anything pertaining to that issue. Workaround for now: Don´t use the IXEG view presets, save your own presets in X-Plane (use ctrl + numpad to save, numpad alone to recall) Jan

Hmm, Ben/Cameron may have more insight on what is happening. Possibly an installation path issue? Jan

XP 11 problem, will be fixed with next beta. Roll back to stable version (i.e. no VR beta) to get the lights back or wait for next beta. Jan

Cameron is sleeping right now - he will be able to look at stuff tomorrow. However - if windows is not giving you permission to access, this is most likely a problem on your end. Possibly try to run the process as administrator? Cheers, Jan

Thanks - to save yourself the trouble of reporting all the bugs that are not fixed (yet) you may want to read the list of fixes for 1.21. If your favourite bug is not on the list, it is not fixed. Cheers, Jan

This is an X-Plane fault with the VR beta and will be fixed with the next update to X-Plane. Jan

Hrm... out of ideas, really (also on windows, and havent heard this one before). What if you detach the AirFMC? Maybe it is blocking the keys somehow? Jan

No, the log would not show anything, I think. As far as I know, the buttons on the CDU are using exactly the same "click" technology as other buttons in the cockpit (like the AP buttons, for example). Does zooming in to the CDU help? Are you using a 4K resolution? Cheers, Jan

Very odd - as you know, we haven´t had any update for a while (yeah, I know...), so I would expect the problem to be on your end (new drivers, new OS version, new screen resolution, some mouse-pointer option change, etc.) Cheers, Jan

We override the X-Plane fuel slider settings - so you can´t really refuel in the air. Sorry. Cheers, Jan

That is correct!

Hi, while I haven´t checked explicitly for ENGM, a lot of times STARs and TRANSitions nowadays live "side by side". It is not like in the old times (or in the US) where you have a STAR TRANSITION - then - STAR - then - TRANSITION - then - APPROACH - then - RUNWAY. IF you look at EDDF, for example, you have many PSA STARs (starting at PSA), but also many PSA TRANSITIONs (starting at PSA). If you choose a PSA STAR and then a PSA transition, the STAR will be erazed again. Cheers, Jan