Litjan

No, I can not confirm that behaviour - on my side the APU is running fine. Please check if something is interfering, like maybe you have no fuel? Cheers, Jan

Will check that out, thanks for the heads-up! Jan

I have similiar hardware to you - but my framerate is fine. Try to fly with a default aircraft like the 737-800 and see what your framerate is with that? I am fairly certain that the addition of cockpit reflections and the new gizmo version is not taking you down to 50% of what you had before. Cheers, Jan

I like to fire at the latest possible moment - more bullets on target and he doesn´t have a chance to get away. Also make sure that you make your approach with the sun in your back! Seriously: Nothing has changed with regard to localizer interception. If you have questions about this or are not sure how to do it, watch the tutorial movies. The plane behaves exactly like the real one, so if you are stalling while intercepting the ILS, you are most likely doing something wrong. Cheers, Jan

Thanks, Pierre, others have reported this as well. We are looking into the cause, for now the solution is to not fly another plane in the same session before switching to the IXEG 737. Sorry for that inconvenience! Jan

Thanks for the report! Are you running on Mac? We had another report from a Mac user with unresponsive FMC keys. Wonder if there is a pattern here... Cheers, Jan

Hi Steff, the problem is that the plugins still load (and cause the conflict) - disabling them afterwards through the menu does not help. To really test you would need to prevent them loading when X-Plane loads up - this can be accomplished by moving them (temporarily) to a different folder (like the desktop). Cheers, Jan

No idea - this seems like a windows problem?

Yes, this broke when we fixed the stick shaker actually working when it should...will be fixed in next update! Cheers, Jan

Hi Steff, we are investigating a possible problem with the code that pops up when you have a lot of plugins running. Try a reboot of X-Plane and then see if it still happens? If so, you could try (to troubleshoot) to disable some other plugins and see if that helps - as an interim solution. I have never seen the problems mentioned, but I am running no plugins except for gizmo. Cheers, Jan

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