Litjan

Same as before - 25% linearity, 0% artificial stability. Jan

Working on a fix for that as we speak (type) - just hold on for a little bit longer. Jan

I would say hold off until I tell you which sounds we specifically need. No point in doing all this work and then us not really needing it. Cheers, Jan

No, I can not confirm this. The 1.21 update is suitable for both XP10 and XP11.1x+ . The installer contains different versions of the aircraft and will install the correct set for your simulator version. Most improvements are for both XP10 and XP11 users, but some (like the adjustment for flight dynamics or the added cockpit reflections) are only valid for XP11. So both groups of users benefit from 1.21. Cheers, Jan

Yes, I can confirm your observation. Weird. I will investigate and see if we can fix this. I remember we had some problems with that before, its an initialization problem, which is never quite easy in X-Plane... Cheers, Jan Edit: Workaround for now is to start the APU really quick (or enable the ground-power)...

I just tried and it works fine, there. Watch for the mouse to become a little hand when over the switch, then grab and pull to left or right. Nothing has changed wrt the auto-brake... Cheers, Jan

Ben will provide a new version of gizmo soon that is curing a bug and also provides a checkbox so you can select if you want the old style (higher fps but some spikes) or the new style (lower fps but more smooth). You may want to experiment with that when its out. Cheers, Jan

Hi Tchou, 46.022 kts, eh? That must be some derelict testing mode that Tom was using, he gets tired of waiting for the plane to arrive... I will try to recreate your scenario and bug, thanks for the report! Cheers, Jan

We will take a look, thanks for the headsup! Cheers, Jan

Hi Max, yeah, thanks for the kind offer - we are looking at converting the sounds to FMOD in the future and will probably have the need to get some sounds again or some new ones I missed back then! Cheers, Jan

You can check the remaining alignment time if you set the switch to STS (time in minutes) Jan

That is certainly an option. Jan

Thanks a lot and those may come in handy. For what it is worth, I recorded the sounds we use in a real 737 with a high-level stereo sound recorder Cheers, Jan

I am sure you have waited long enough for the IRS to align? It takes about 13 minutes (like in the real plane)... Nothing was changed with regard to the IRS code between 1.2 and 1.21 Jan

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