Jump to content

Litjan

IXEG
  • Posts

    5,673
  • Joined

  • Last visited

  • Days Won

    412

Everything posted by Litjan

  1. Because that is not coded. Real pilots don´t divert! Cheers, Jan
  2. 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
  3. 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
  4. Thats true, Morten, I didn´t think about that!
  5. 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
  6. 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
  7. 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
  8. That is the reason. Jan
  9. 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.
  10. I don´t remember, but I may have some documentation and a few cockpit videos at home that I can check Cheers, Jan
  11. 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
  12. It never worked on the FO´s side. Cheers, Jan
  13. Make sure to bring some Licher Bier!
  14. No, you have to send me one of your homing pigeons, and I will let if fly to you with a message about the new update when its done! Jan
  15. Yes, you will get a notification by email.
  16. Yes, we are fixing a couple errors in the LNAV code that would cause this. I think you should see almost all of these gone with 1.1. For now, keep watching the AP like a hawk!! Cheers, Jan
  17. Hmm, let me guess, you are using XP11 and you are not reading many forums related to XP11, right? Here, let me help you with that: http://forums.x-plane.org/index.php?/forums/topic/110304-ixeg-737cl-and-more/&page=2#comment-1134164
  18. Hi Jan, Thanks for the kind words - I know some planes are affected, and I know that the "default" aircraft in XP11 will be working fine again in the next beta... The payware aircraft will be updated when XP11 is final - Ben Supnik told everyone to wait until then. Cheers, Jan
  19. Working on it! Au revoir, Jan PS: Day before yesterday fixed some bugs with Nils on the TCAS (some online-traffic staying fixed in position relative to aircraft, erroneous RA´s when X-Plane AI aircraft spawn....) Yesterday fixed a bug with Tom relating to aircraft not flying straight to first point on SID´s with long, straight initial segment (like LFPG 27L RAN1AD, for example)...
  20. Yeah, we override the setting that X-Plane provides (at least we try to) - happy to see that you got it sorted. Jan
  21. XP11 not supported yet. Cheers, Jan
  22. We may revisit this at a later stage. The problem of A/T not setting correct thrust in some conditions is also on the review list. Thanks, Jan
  23. Thanks for the nice feedback! We will need to re-tune the aircraft when XP11 is "final" - if you feel REALLY enterprising you can do this: Disclaimer: All this at your own risk. Don´t come crying if you *** up your aircraft and run out of activations because you need to re-install your messed up aircraft file. FIRST: MAKE A COPY OF THE .acf file!! Run the aircraft in XP10 at a certain speed and altitude, i.e. 5000 feet and 250 kts. Output "drag" to your screen. Note the value. EDIT: At 250kts, 5000´ and 100.000lbs (45.450kg) this should be 6460lbs of drag. Open the aircraft in Plane Maker for XP11 (root folder) and browse to Standard/Fuselage/Section Play with the value for "body coef of drag" (you will need to increase it) until your results for 5000 feet and 250kts match up with XP10 (6460lbs of drag) The results for other speeds won´t be perfect (since the shape of the drag curve has also changed for XP11) - but will get you back into the ballpark. Jan
  24. XP11 is not officially supported. Lots of changes to drag, so this is not surprising. Jan
×
×
  • Create New...