Litjan

And it will stay the only solution until we make the XP11 compatibility patch. We can not add the needed information to the XP10 .acf file, it simply has no datafield for it. So I suggest trying again, maybe you are missing a simple step? Jan

Just you, I think.

No

Roger!

The crashes (where you see the console window pop up with a red error message) should be fixed mostly for XP10 and XP11 alike with 1.1. Jan

That update is very far ahead and I hope that we can finalize it shortly! It will also contain some "Ninja-Fixes" to some XP11 problems (like sliding aircraft) - but it will not make the aircraft fully compatible to XP11 yet. Cheers, Jan

XP11 is not released. It is the rc1 (release candidate), not final. And once it is final, you can expect it to take (a few) months until the port is complete. Cheers, Jan

You are wrong - XP11 rc1 is out - this is the "release candidate" and may be declared the final version - if no further bugs are found. It is not final yet. But yes, you can certainly hope for a usable version - it will take a while to port to XP11, though. Jan

I don´t think so.

Hmm, make sure there is not something else going on - maybe an axis assigned to the "tiller" by accident or some other preferences screw-up. I can taxi and fly the 737 in pb15 "mostly" just fine - and have to work really hard to recreate the "sliding". So it may be something else... Cheers, Jan

No ETA on the patch. The only way of avoiding this is not going slower than 5 kts - the plane should handle ok above that speed. Jan

I will add a fix to the upcoming patch 1.1 that should avoid this behaviour. We have our own ground-model in XP10 that overrides XP´s default model. Austin changed a lot of things in XP11 to make the aircraft behave better when stopped, and also when taxiing very slow. This messed with our override. I have changed our override so that it only kicks in when going faster than 3 kts - this should avoid those problems, so you can use the IXEG in XP11, even though it is not "officially supported" yet. Cheers, Jan

Because that is not coded. Real pilots don´t divert! Cheers, Jan

Ok - the bug was more obvious on that second movie you sent - I agree that the movement looks weird - slipping sideways like that. I am not sure what is going on with XP11´s friction model, but the default 737-800 is behaving pretty good, I think. If you want to get Austin to look at the problem, you need to illustrate it with "default aircraft" - he won´t look at 3rd party stuff. We will see what is going on with our model and XP11 at a later stage (when porting), and we will just have to deal with the way XP11 handles things. If we need to re-do our ground model, so be it. Thanks for pointing this out, though! Jan

I don´t quite know what you would expect to see in this scenario - with one engine going full power? This is exactly what I would believe the real plane would do, too. That being said - I also see the weird "plane stops in very slow turns" in XP11pb15 - it is important to know that we override X-Plane´s steering system with our own plugin, so I am a bit surprised to see the change. Maybe our plugin isnt working anymore due to a variable/dataref change, we will investigate when we port to XP11. For now its a bit harder to make very tight turns, but not impossible (just need more thrust)... Jan

Thats true, Morten, I didn´t think about that!

Yes, airport looks excellent! We are planning to issue patch 1.1 "shortly" - no promises, though. It should fix a lot of the "gizmo crash" bugs - but will not make VNAV better. But we have not forgotten and will work on that after making the plane compatible with XP11. Cheers, Jan

Yes - but this does not apply for the 737 as it has no geardoors that would extend when trying to raise the gear (all gear doors and fairings are already extended when the gear is extended). But I think they also keep the windshear procedures the same to maintain commonality with other types - so transferring to another aircraft would not require to relearn this procedure in such a substantial way. Jan

No such luck . Anyway, the VNAV is not able to handle complex restrictions and has some bugs, this has been known and stated many times on these forums, so your bug report is neither surprising nor telling us anything that has not been known widely for many months. For now use V/S and FLCHG. Cheers, Jan

That is the reason. Jan

I think (reading from your log.txt) that your computer is not set up according to the rules of Fengh-Shui. There may also be an influence of earth-rays or simple bad karma. I have heard of cases where computer mainboards were evil sorcerers in a former life, and are therefore prone to malfunctions.

I don´t remember, but I may have some documentation and a few cockpit videos at home that I can check Cheers, Jan

No, it does not need an update, and future updates will not adress this. I am sure that it is something that is going on with your computer, especially if it happens mostly after 2 hour flights. You can post your log.txt from the X-Plane main folder here, and maybe we can have a look if you run a conflicting plugin. Cheers, Jan

It never worked on the FO´s side. Cheers, Jan

Make sure to bring some Licher Bier!