Litjan

The ground effect bug is fixed in 11.10. Contrails and water textures are not part of any near future updates. Jan

Yeah, really have no idea what could have caused a big jump like that. Variation in airspeed/altitude could be explained by: Sudden shift in environmental conditions (pressure, wind) Icing/malfunction of pitotstatic tubes But this is the first report we got in that regard, so I can´t really say with certainty what happened. Let me know if you see it again, please! Cheers, Jan

This is not up to us to say, as we don´t make XEnviro. Cheers, Jan

The only thing that I could think of is that you are not running the hydraulics - they are required to steer the nosewheel. Other than that the steering should just work like in any other aircraft (try the default 737). Cheers, Jan

Hmm - are you using real weather or a weather plugin?

Hi Jürgen, I run a EVGA Geforce 970 with 4GB VRAM on an Acer S277HK monitor. I have a second monitor attached as well (Samsung SyncMaster 214T). I run X-Plane as a "Windowed simulator" and my second monitor is set to "unused". Cheers, Jan

We don´t model failures as a feature. The few you can find now are remnant from our internal system-modeling tests that we decided to make available for everyone. So consider them a goodie, and the "missing ones" not really missing ;-) A few of the default X-Plane failures work as well. We plan to add more failures in the future - after completing the basic aircraft (FMS, 3D cabin, ...) Cheers, Jan

I run on a 4K monitor - and the knobs work fine. I do run in windowed mode, fairly big, though. Cheers, Jan

Thanks for the nice words! Happy flying! Jan

They didn´t ask much for our old 737s (- engines and other reusable parts)... but shipping and handling was expensive, and my wife wouldn´t let me put it into our garden :-( Jan

This is what the reain effects look like: Cheers, Jan

I want one of those! Very nice!

Hi Bob, that smacks like a problem with the Virtual Aviation MCP, then. I am not familiar with the device, so I can´t tell you about any problems or pitfalls with it. Maybe there is a dedicated support forum or you can open a new thread here that is aptly named (maybe in the cockpit builder/hardware subsection) - there are some more knowledgable people around that may have an answer on that. To make a video, you can use the built-in movie-maker in X-Plane, it saves the quicktime movie in \Output. But those movies grow quick in size... Cheers, Jan

Hi, first time I have heard of that problem. We don´t really have any "bend arrows" in our cockpit - you manipulate the knobs by moving the cursor until it turns into a little hand, then click to "grab", then move the mouse while holding down the clicked button. There are some instances where the default-style "turn arrows" of the old 2D cockpit we used to have "bleed through" (I don´t know why), but they don´t have any function. Cheers, Jan

Hi Bob, I would really have to see a short movie of that happening to let you know whats going on. I am almost certain that it is intentional (yet unexpected by you) behaviour - we have had thousands of people operate the aircraft for well over a year and this is the first time I heard anyone have that problem. There are several cases where the speedcursor will move seeminly "on its own" - what you describe sounds like its a "runaway" problem where you grab the cursor, and then loose view of it (the sim considers that as holding and not letting go) and then move the mouse wildly, maybe trying to manipulate something else - but really just moving the speed cursor "to the stops". Again, a video would say more than a 1000 words, any chance of capturing a short one for me? Cheers, Jan

Hi Bob, your joystick is spikey and sends commands - so the AP "thinks" you want to override it manually and disconnects (as in the real aircraft). To cure this, increase your CWS Deadband setting in the preferences menu. Cheers, Jan

You cant sustain 1200 at that altitude - use FL CHG or manage your climbrate carefully. Jan

Here is a pic of my 737 climbing with ECON speed (Mach 0.73) at the same weight: My guess is that you failed to switch to MACH during the climb - eventually the IAS is equal to MMO (maximum MACH no.) and the plane will use all of its energy to "push" against the subsonic boundary and eventually stall due to MACH effects (airflow stalling). Maybe you also got too slow - this will also kill your climb rate. Jan

You had a grossweight of 55.6 tons - that is close to the maximum takeoff weight. The aircraft should be able to go to a maximum altitude of FL350 at that weight, so 340 should have been possible. It sounds like you didn´t manage your engines or airspeed during the climb correctly - we would need a bit more information (as Morten said) to find out why the plane stalled. Cheers, Jan

Did you somehow move the camera out of the window? I can only imagine this happening if X-Plane still thinks you are in "inside" view. Try clicking shift-4 or so to go to an outside view. Cheers, Jan

Hah, maybe we can make a deal with our customers to only add wingflex and opening doors - and just leave the FMS as it is? I think Tom would go for that!

For what it´s worth, the plane is perfectly flyable without FMS and it´s navdata, too. I suggest to take a look at the training videos we ship with the product, they describe "basic" navigation in detail. Unless you fly online, having accurate navdata is really not such a big deal. Cheers, Jan

Hi - "delicious" is a first, I like it! It describes the feeling of flying the real aircraft very well, too ;-) There is really no way to legally update the navdata-cycle. But buying a single update isn´t terribly expensive (ca. 10 Euros). Maybe we can negotiate with Navigraph to include a slightly newer nav-data package with one of our future updates, we well see. Cheers, Jan

Hi axmiha, the ability to do consecutive flights was added later in the run of our product - and it is a very complex procedure code-wise, resetting a lot of variables. It is also very hard to test, because obviously it takes a lot of time... So it is quite possible that you discovered a hidden bug in our calculation, somewhere, probably unique to your situation. We are planning to overhaul the whole VNAV calculation for a future update, especially to make the descent calculation more reliable. Therefore it would not much much sense to chase the quirk you encounter, as the whole architecture is going to change. As a workaround I recommend to "reboot" gizmo after you park. Just click the little "flash" symbol on the right pop-out menu, then set up your plane again for the next flight. As for your "turn around" mode problems, could you specify what you encounter? Cheers, Jan

Happy to hear that, Lee! The users having a great experience is what drives us! Cheers, Jan