Litjan

Thanks for the report, Michel! Sometimes there is an (erroneous) certain turn direction specified for a waypoint (like "right turn after CRI"), we will check the database to see what it is all about. Jan

Hi and happy you got it to work - for the lagging please add an exception of the X-Plane folder to your virus-scanner (Windows Defender, Avast, etc.) - that should stop the lagging. Jan

Slide them all the way to full. Jan

Not a glitch - this is the N1 limit indicator and not the flight-phase indicator. It shows what maximum power the engines COULD go if needed. Not this model. The SPD INTV and ALT INTV are features that are not available on all Classics, and we chose to omit them to keep things a bit simpler. Jan

Maybe it is a bug - but at least not our fault...

Can´t really say anything about how these guys do it - except that I wouldn´t do it . It IS possible that they are running a higher FMS standard that will not allow A/T activation on the ground, I simply don´t know. Jan

Yeah, this is an issue we are still having - the symbols will be drawn on the straight line between your airplane and the next waypoint - we don´t take curvature of the magenta into account yet. It is on the list of things to eventually get to, for now you can just fly "direct to" the current waypoint again when you are flying straight to it and the T/D should be on the magenta... Jan

Hi and thanks for the kind words! We have a thread here: http://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v10/ that is attempting to warn people of the things we are still missing. I am going to update this thread with every patch until it is all stricken out . I also flew DI´s Tornado (including Desert Storm) and about every FlightSimulator out there since the mid-80s (remember MicroProse? Jane´s? F-16 Combat Pilot?). The secret with Tornado was to manually fly below 100´ - no SAMs would ever launch! Happy flying, Jan

You know I am not allowed to drink something to calm my hands when flying.... Jan

Yes - the first push of the TOGA button will set a reduced go-around power. You can verify this by the FMA showing GA. Pushing a second time will give you full go-around power (N1). Jan

Hi, The PFD and EHSI will go monochrome when the cooling airflow (avionics supply and exhaust fans) gets too low. This happens when a generator bus is not powered. The monochrome mode will keep the display from overheating - this is the way it works in the real airplane. To cure this, you can switch the fans to "alternate"... The cabin rate of climb should not oscillate - we had some problems with that before and it might "jitter" a bit, but should not oscillate. The outflow valve should be "almost closed" for normal cruise conditions. I don´t think we will model the PMC switch, it would be pretty complicated to get right and it is not used in normal (or abnormal) operation. It would only be used in case of an EGT limited engine or if the PMC of the opposing engine fails. No worries about nitpicking, I rather enjoy discussing features of the 737 at this level! Cheers, Jan

No. This is no NG. Don´t press anything on the ground, except for TOGA when you want to take off. The autothrottle will happily go to full thrust for a number of modes, VNAV being one of them. THis is also the reason that the procedures are VERY specific about not arming it until you line up on the runway. Happy flying, Jan

There is quite a bit potential for user error, here. You need to enable the receive button and turn up the volume, be within reception range,... It always worked for me, but I rarely check the idents... The NDB and RMI tuning works just fine. Jan

I am not sure, but I think there was an update to some of the JarDesign plugins that caused a clash with ours... Jan

No, these values are slaved to the X-Plane date. You need to change those in the X-Plane menues... Jan

Hi, I think we have seen this some times already - I think the reason was an incompatible gfx chip (onboard Intel)? Jan

Hi Chock, thanks for the comments and trying some of the "deeper stuff"... 1.) I am not sure what is going on with your display - it is in the "power saving monochrome mode", but it should go back to full colour after you power the lost bus again with the APU - or switch the air fan to alternate. I can not see your overhead panel in that shot, so it is hard for me to see what is going on... 2.) Correct, we did not model the stab trim brake. I will add it to the list - at the time I didn´t want to risk the developer in charge sending me an anthrax letter if I come up with YET another thing influencing the trim system. And I figured - oh well, no one will know about this and figure it out... I guess I was wrong . 3.) Are you running the air-conditioning system on AUTO or MANUAL mode? In AUTO it should avoid the duct overheat pretty well, note that the temp sensor takes the total temperature (pack supply PLUS return air from recirculation fan), so to really get a sense of the pack outlet temp you need to switch off the recirculation fan. AND then take into account that there is a bit of a sensing lag - the duct temperature sensor is not the same as the pack outlet temperature sensor (which will trip the pack). The AUTO mode can have a tough time if the temperature in the cabin is VERY low - it will drive the pack valve to full hot in response and then get over the 88C before it can drive it back down. This will happen if you reboot in the air at high alts (the cabin temp gets set to ambient, so could well be -50 or so), or if you power up the plane after it was parked in Siberia over night... In this case I recommend going to MANUAL mode first, put the pack valves about mid-way and then wait for the temp to stabilize (recirc OFF). Then gradually edge to WARM until you supply +70C or so. After the cabin gets to +15, you can go back to AUTO. Please keep testing our model and report all your findings. We are happy to take everything into account and tune where needed and warranted! Thanks, Jan

Good to know - the ground spoiler shutoff valve is connected to the right strut, iirc, so touching down on the left wheels only will not cause the ground spoilers to deploy... Cheers, Jan

You have many plugins running that are suspect and that have caused problems with our plane in the past. You can help us by removing all plugins from the plugin folder (except gizmo, pluginadmin and xplm, then reboot and try again. If there is no more crash, please add the plugins you are running back one by one, and take not of which one causes the crash when paused. I would suspect it is one of your custom airports-plugins, but it could also be JarDesign (he has some updates!) or the 124th ATC... Please let me know what you find out - we are working on an improved gizmo version that will co-exist better, but we need to find out which plugins conflict. Thanks, Jan

Hi George, I know that this is an option that airlines can set by adjusting some pins in the E&E compartment of the plane. I will put this on the list of feature requests, even though I firmly believe that flying with track up is wrong, wrong, wrong and doing the devils work! Cheers, Jan

Sorry to hear about the issues - but happy to hear that you are flying our plane exclusively! I hope this can be figured out, Jan

Hi Lawrence, I think this is an X-Plane limitation - we are mimicking X-Plane´s ADF functionality, and it does not allow selection of half kiloHertz values. This is akin to the problem of being unable to tune .025Mhz spacing on the com radios, but this has been adressed. Hopefully the .5 ADF thing will be, too. Thanks for the report, Jan

Correct, it is on the list - there is just a bunch of small stuff like this to wade through and we try to be a little more thorough about adding fixes now, doing a bit more testing as well, This slows things down. It would be easier to fix stuff, run a quick test and then release it into the wild with a hotfix, but we had some backlash because we broke some stuff in the process and people would frown upon the small steps backwards way more than be happy about the big steps forward. A small request to the OP (jolmos): If you think you spot a bug (like you did), then please post so in the "bug report forum". It´s reason for existence is that people should report bugs in that forum. Thanks! Jan

Hehe, I will take you up on the drink! No worries and keep the reports coming! And I am happy for every problem resolved . Jan