Litjan

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

Thanks for taking the time to do this comparison, Tom! I am not much of an "audio" guy - but there certainly is a difference. I am sure it is fine to replace sounds in your folder with other sound-samples that you like better. If the wind.wav from default airplane is something you prefer, go ahead and replace the custom sound we provide (make a backup of it first?). Does this help? Cheers, Jan

Very odd. Are you in the air or on the ground? Jan

It is a known bug that we still try to reproduce (so far no success). If you want to help, you could make a short video of what you do - start with loading the aircraft, so we can see every step (everything might be important...) Thanks a lot, Jan PS: Oh, and if you report a bug - please use the BUG REPORT forum - it is pure luck that I saw your post here

Hi Jim, if you flew the real things (especially 757s should be in the same league) then you are an authority on that issue to me! I will double check our deceleration times and distances - just make sure (this has bitten me before) that your joystick throttle is calibrated to go all the way back to idle stop. If you are on autopilot and autothrottle then this should be no issue. Thanks, Jan

Yep, too late for that .

Hi, you can test if it is the wind sound - boot up cold+dark, then set the wind to 99kts. Do you hear it? Jan

Hi Benjamin, no, we have not checked the code per se - if there was a problem, then it would surface for all computers running it - not just for a very limited number. It´s not that we are saying that it would be impossible - just very unlikely and of course we have other more pressing issues affecting a larger number of users. We know that there can be a problem during a MOD stage when windows defenders is on and checking the X-Plane folder. We are accessing the navdatabase constantly during the MOD stage, and windows defender is "checking out" every one of these accesses... But in that case your FPS drops every 2 seconds, but runs fine in between the drops. What I saw in the video with regard to your problem looks very different. And it can´t really be a problem with all Macs, as 50% of our dev team is using Macs and haven´t had any problems. Tom did have a "general slowdown" problem, but that was cured with the cooling pad, however I think that this will not affect your problem, since it isn´t global but only tied to a certain situation... Jan

Genau !

Thanks for the reports, Benjamin and Bruce. I really wish there was an easier way to test if the OS is the problem. Upgrading to a new OS is not a small thing, I know that. Maybe you can wait until Benjamin reports back how things worked on his machine with the newest OS? We´ll get there! Jan

Thanks for the links! I will watch them in a bit (wife on my case to go grocery shopping... real life keeps intruding! ) Jan

Unfortunately I can´t play it with either media player or VLC Can you guys please try at TXKF airport? I suspect that using a custom airport or mesh could have something to do with it... If we can isolate the reason, it will be easy to code around it, I am sure! Thanks, Jan

It could also be that these callouts are not getting triggered due to a complex computational situation - i.e. the condition "at 2500 RA" not lasting long enough for the code to catch it - can you do me a favour and try at TXKF? Thanks, Jan

I could say "we are simulating that the pilots put on their noise-compensated headsets now" - would that make you feel better? (but it would be a lie...) We will check, Jan

Thank you, Phlippe, and sorry if I came across a bit snappy. We worked very hard on getting the flightmodel as close as this - within the confines of the simulation platform. I am sure you know what a battle this can be. Then it hurts a bit if someone says "you are good, but not perfect!". Of course we are not perfect, but I don´t think it is possible to be perfect with any of these simulators. We had to twist, bend and tweak many aspects of X-Plane´s default flightmodel and engine model, and in the end it will always be an approximation. From a pilots perspective I can only say that it is very rare to have an airplane that flies exactly according to the book. There are so many variations influencing this (atmospheric conditions, engine age, manufacturing tolerance, ...) and we are often surprised how much/little power an airplane needs in a give situation. If we are within "almost 1 degree", "a slight gap" and "acceptable tolerance" coming from someone as knowledgable as you - then I am happy . Of course we can tweak and improve - but for now we have bigger bugs to stomp and crashes to hunt down... Merci, Jan