Litjan

Oh yeah... - you can move them right back in after testing!

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

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

Thanks! Jan

Sure, sure - keep it coming!

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

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

And which data provider? Navigraph or Aerosoft? Thanks, Jan

Now THAT is an excellent hint, Tom! I was able to confirm this behaviour, and we will fix ASAP. Jan

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

Thanks for the report - always good to have some more examples to test at - quick question, which navdata (type and cycle)? Jan

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

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

Just checked - and while its not 0 on my end, it is pretty low (like 20kg/h). I don´t think that the fuel-flow would be as high as on the ground (ca. 400kg/h), as the windmilling is more than enough to keep the engines turning and its more about not flaming them out... but I will see if I can get some real-world data and tune this. Jan

Happy to hear that! Happy go-arounds, Jan

Ok, will check that - never noticed (which doesn´t mean anything ) Thanks for the report. Jan

Following along with a big smile - you guys are doing a great job and I can´t wait to try it soon! (Busy busy busy with the bugsquashing and my tax-return ) Jan

And it is! Of course that is already on our list - but it´s a texture change which can not go into a hotfix. Jan

Moin Matthias, from one bean-counter to the other : You are right and it happens to me, too. I think we were trying to make it a bit easier if the clickspots don´t move with the switches, because often you will then have them move in front of other clickspots... especially when looking from an oblique angle. So the logic was like this: Moving click+drag for those switches that have more than 2 positions, clickspots at the "base" for those that only have two positions (click-to-toggle). Once you get used to this (and memorized which ones are 2 vs 3 position) it works pretty well - especially if not trying to click from an acute angle. But I agree that it is not 100% intuitive. We will see what we can do in the future - but we´d have to update all switches at once, not only a few, because it would get even more confusing... Jan

You might be triggering the "rejected takeoff" mode. We made the autothrottle disconnect if you pull the throttles back during takeoff - so that you can stop if you have to. If you have a spikey joystick or move it back and forth during the takeoff run, this might happen. Try to push the throttle all the way forward while the autothrottle still advances the thrust levers, and see if that helps? We havent changed any logic related to that between 1.0.2 and .3, though. Jan

1.) Check all conditions for takeoff warnings 2.) This is probably a bug. We will need to implement a proper FMS-reset for the turnaround state. You can work around for now by doing a "gizmo reset" when parked. Jan

Dr nerdrage is right - you will not see the "max N1" (except for the double-carot). You can check it on the TAKEOFF REF page. Preview versions had that wrong. You only get an N1 display if you set the carot manually by pulling out the knobs. Jan

Hmm, a lot to clear up here. I suggest that you work your way through the tutorial videos one by one - I have sworn to myself not to teach someone fly the 737 here in the forums. Do the tutorials, and you will have a much better idea where you went wrong. Everything you are asking here is explained in them. Just for info - from your post I can see that the airplane behaved just like it should. Good luck and have fun, Jan

Also be aware of the fact that the position must be "pretty much correct". Otherwise it will not be taken by the IRS - this is a modeling limitation - otherwise we´d have to go to the length of keeping track of a "false" position with everything that entails (MANY ramifications...) While this may look like a shortcoming, it really isn´t much of one. The real IRS will also reject false positions (comparing to last known position, comparing latitude to current turn-rate of earth) and will also correct a wrong IRS position very soon through GPS (or DME) updates... Jan

Hehe, thats why I like TXKF! And it loads in a flash... Ok, thanks for the report. We will look into all the sound problems - I still believe it was worth to make the sound engine more careful about using too many resources - as some people have started hearing sounds that weren´t there before. And I am sure we will irong the new problems out real quick... Jan