Jump to content

Litjan

IXEG
  • Posts

    5,709
  • Joined

  • Last visited

  • Days Won

    423

Everything posted by Litjan

  1. Whoa, that was a "difficult birth", as we say here in Germany . Happy that mother and child are well, happy flying now! (You waited long enough!) Jan
  2. I think there is nothing that prohibits this function on ground, too. Except that usually the airplane doesn´t climb or descend much when on the ground . However - if you are RIGHT on the edge of triggering this function, and the pressure changes, or you taxi downhill, or the plane settles a foot during "spawning", you might very well get this alert. I am not sure why you can´t enter V-speeds after that, it might be a different bug (unable to access TAKEOFF REF page) - we have yet to investigate the erroneous switch to "air mode" while the plane is still on the ground. Likely an initialization problem, like Tom suspected. Jan
  3. Thanks for the nice words! - if you select R-TO from the N1 LIM page, without entering a TASS first, you don´t have reduced thurst, and therefore I would expect TO to display. Jan
  4. Good to hear that!
  5. Are you sure the IRS is aligned (position entered and accepted, no flashing ALIGN, etc.)? Can you double-check, please? Thanks, Jan
  6. Get me one, too, will ya? Implementing a "quick align" function is on our list - it will probably not be on the PREFERENCES list, because I think this should be something like "recharging battery". I don´t want to teach users bad habits, i.e. waiting with the align process until they are ready to taxi. If you "mess up" you have to admit and go to that special "failure" menu to fix it . But making someone wait for 13 minutes because of a simple (newbie) omission is a bit harsh, I agree. Cheers, Jan
  7. I wouldn´t be so sure!
  8. Thanks, Marshall - I think we have a fix for that in the next update! Jan
  9. Thanks for the reports, everyone. I think we have a fix for this in the next update! Jan
  10. If you are on windows, set an exception for windows-defender so the X-Plane folder does not get scanned. Try if that helps.
  11. Thanks for the report - known issue and we are working on that! Jan
  12. Oh yeah... - you can move them right back in after testing!
  13. It should - I will check that - and checked, it doesn´t. This jibes with the other bug we received, fueling the ctr tank doesnt work, either (unless an engine or APU is running...) Jan
  14. I suggest to look at your many plugins running - we don´t even have a sound like that. And since our plane can´t jump to lightspeed, we don´t really need an astromech droid... To troubleshoot the offender, remove all plugins from the plugins folder (just disabling them in x-plane is not enough), then reboot. Jan
  15. Thanks! Jan
  16. Sure, sure - keep it coming!
  17. Another request for people without altitude callouts: Can you please try (if not done already) the callouts without ANY (not only soundmaxx or JAR) other plugins, except for gizmo? This means physically removing them from the plugins folder (you can copy them back later), rebooting X-Plane completely. Thanks for any feedback, Jan
  18. Wow, quite the documentation! Thanks for making it - I probably didn´t even know about this so exactly! Yes, we can probably adjust and improve - I am not a sound guy, as long as the switch makes a believable sound I am happy. I put this on the list (its wayyyyy down there, though ) Jan
  19. And which data provider? Navigraph or Aerosoft? Thanks, Jan
  20. Now THAT is an excellent hint, Tom! I was able to confirm this behaviour, and we will fix ASAP. Jan
  21. Yep, it is on the list - once Tom is back in business, we will look at it and possibly add another logic-check to avoid that premature switch to "air" mode. Jan
  22. Thanks for the report - always good to have some more examples to test at - quick question, which navdata (type and cycle)? Jan
  23. I don´t think that you should use buttons and axis-assignment together. It might work, but there is bound to be fighting and collsion between the two. Jan
  24. Yes, we see that, too - and I confirm that it is a bug. We get it randomly, and think that it is a complex computational situation during the initial loading of the aircraft. For now the workaround is to use the PREFLIGHT menu again and set the amount of fuel you want - or at least a bit to keep the engines/APU going and then later use the GROUND SERVICES menu to fuel the aircraft. Jan
×
×
  • Create New...