Litjan

Yeah, its still a major nuisance and I am sorry that you experience these crashes. I am not quite sure why you get hit so hard, for the most part these crashes have dwindled down to almost zero, it seems. I will try to recreate the crash you reported and then we can fix it for the next update. In the meantime you may be able to avoid this issue by going a slightly different way about entering the alteration, maybe changing the runway first, then the STAR/transition or the other way around. If there is a way you can determine which exact sequence causes the crash, that would be helpful, too. Since it seems to happen to you basically on every flight, maybe you can catch the occurance (with the keys you are pressing) on a short video, these are usually priceless in hunting the problem down. Are you using Navigraph or Aerosoft nav-data? Sorry for the trouble, Jan

Hi Fesi, to avoid this happening: Don´t load the aircraft in a setting with really cold ambient temperature or really cold temperature in the cabin - the AUTO mode may overshoot the temperature limit. If you get the warning, set the temperature controller to full cold (auto), then press the trip reset switch If you get the warning again, set the pack mix valves to full cold (manual mode), then press the trip reset switch. Now set the temp indicator to DUCT, then slowly feed in more warm air (to avoid overheating the duct again). Check PASS temperature from time to time and once the temp is >5C you can go back to AUTO For what its worth, I never get the pack trip warning when flying - so there may be something unusual about the way you operate the pack controls. Cheers, Jan

Hmm, ok - at least we figured out what the conflicting add-on is. Just wish that they would both run together without problems...for what its worth I haven´t seen the "leaking decals" before, so maybe this is just of temporary nature... Cheers, Jan

Hi Antares, you are right, the TACAN (DME) and VOR should also be displayed at ranges 10-40. At 80 and up only "high altitude navaids" are being displayed. This is with the EFIS NAVAID switch being on (tuned navaids are green, unused cyan). When the switch is off, only the used navaids are shown in green. Try to "tune" SY on the VFH radio and see if it displays in green then. I am unable to verify this right this second... I will add the bug you found to our database. Edit: I just checked and ALF isn´t showing when tuned, either :-( Cheers, Jan

This is what it looks like on my end:

The "engine age" should not affect climb rates and cruise performance at all. You would see different EGT and N2 for the same N1 in a differently "aged" engine, but the certified performance will not change. If you find a regime where the plane does not perform as you would expect, I would ask you to specify that, including a screenshot with a stabilized climb, showing dataref output of: weights temperature altitude airspeed engine thrust so I can take a look at that. Thanks, Jan

Hi, yes, I can see that in your pictures. Can you make sure that you run the latest graphics-card drivers, please? I don´t see this on my end - not sure what could be causing it. Are you using any third-party programs that could affect this (changing/enhancing textures, colouration, etc.)? Let me know if those two suggestions helped any! Cheers, Jan

The high oil temperature is a known issue - we don´t model the oil temp ourselves (using standard X-Plane) and something must have changed. It is purely cosmetic, though - it should not cause an engine fire. To avoid getting "failures" you can switch those off in the failure menu. If you have failures enabled, they are totally random, X-Plane does not model failures do to engine exceedance. The only failures you would get due to exceeding a limitiation would be flaps torn off at high speeds (there is an extra option for that) and tires blown for overstressing them laterally. Cheers, Jan

I think that we have a fix in 1.21 to make the "other way" also work. So go ahead and try that and please let me know if it doesn´t work! Cheers, Jan

Hmm, I don´t think we changed anything regarding the brakes. If you have an axis assigned to brakes, I would expect that to override any brake value you assign via dataref. The whole braking system is pretty much "standard X-Plane". Note that there are some "system states" where we "fail" the brake to emulate no hydraulic pressure being available. Cheers, Jan

Yeah, that vibes with what I heard about the -200. When I started flying the -300/400/500s in early 96 we still had some -200s (or "Bs", as they were called at our company). I didn´t get the conversion required to fly them, as we were phasing them out at that time. But the Captains really love them, and didn´t hold much regard for all that "modern electronic gadgetry" that the "Classic" entailed then . Regarding the trim wheel - it should not sound in manual flight UNLESS the speed trim function is active (high power settings, flaps not up). Please let me know if the trim runs at other times. We model the "mach trim" effect, but without actually moving the wheel. You can switch to outside view and do your walkaround (hit C) - or at least pretend to. We don´t model the gauges on the hydraulic reservoirs, brake wear pins or other things you might pick up on a real walkaround... Cheers, Jan

Glad to hear that you like it! Especially coming from someone who flew the real aircraft. There are many many different configurations of the 737-300. Everything from instrument panel configuration, different avionics, airline specific setups - heck, at Lufthansa we even had the switches on the overhead work "reversed". Naturally we developed the aircraft according to the aircraft we had access to. We have some user preference (steam gauges, eyebrow windows), but mostly the aircraft is "just the way it is" . I remember when we got aircraft in our fleet with different audio-selector-panels or the new MCP with buttons for the AP, instead of the engagement paddles. First you think "well, this is total crap" - but eventually you get used to it. I think I was spoiled with how much commonality we had in our fleet, I am sure there are operators where every aircraft has it´s own little "character" and setup. I fly the A320 family now, and the range of configurations from our old A319s to the new NEO 320s is staggering... Cheers, Jan

Thanks for reporting back. The "many monitors" feature that X-Plane 11 brought has indeed some pitfalls - and they seem hard to troubleshoot, since the results vary from monitor to monitor... The thing I hate most is that there is no way to exactly specify the size of the window I want to run (i.e. exactly 1920x1080). Sure, you can set that up in some preference menu, but you must use a calculator to specify the start and end pixels... really? Cheers, Jan

Hi Vitaly, as Cameron said, try the new "garbage collector" setting in gizmo, it works great for me. I run a similiar processor and have a very smooth experience, also in VR. The stutter when "changing flightplan" is due to your antivirus software interfering, please create an exception for the X-Plane folder and it will be perfectly smooth. Cheers, Jan

Hi CptIceman, I have added the 1000 foot chime to the list of requests. Shouldn´t be that hard to implement, but it will definitely create some puzzled looks when people view the preferences . There is currently only a chime when you approach your altitude at an excessive rate. And of course the regular altitude deviation warning. Cheers, Jan

Hi Popcorn, happy to hear that things work out better now! For initial descent you can use VNAV, but keep a close eye on it and it´s calculations. For the final approach you must use MCP SPD and either LOC/GS (for ILS) or V/S for NON-PREC or RNAV approaches (using LNAV or HDG SEL). VNAV is not certified for approaches in the 737-300...and while it would work on the real one, it does not (yet) in ours. Cheers, Jan

Hi Chad, as a first measure, increase your "Autopilot CWS deadband" in the preferences menu, please. I think that your joystick isn´t centered properly or "spiking" and this will kick the autopilot out of CMD. Cheers, Jan

Just for kicks, try to run X-Plane in windowed mode and see if the problem persists, please. Cheers, Jan

Hm, very weird. It should hide as soon as your mouse-pointer is not at the left side of the screen anymore. Are you using multiple monitors? Are you running in windowed mode (and have the mouse pointer out of the x-plane window)? Cheers, Jan

Hello riccardo, yes, the stall warning TEST does not work - we broke it when we fixed the actual stall warning (stick shaker) to work again. This will be fixed in the next update. The cargo doors work, the service and entry doors do not work yet. Thanks for the nice words! Cheers, Jan

The orange speed cursor should be set to V2 exactly - this is what you would fly at an engine failure. The plastic bug marker should be set at V2+15 (this is the safe speed to make turns with bank >15 deg). You should actually fly about V2+20 during initial climbout. Jan

Hi Bjorn, nothing was changed on the engine modeling since "forever" - in fact not even with the advent of XP11, as we calculate thrust in our own module. N1 required to taxi depends on weight, slope and temperature - values in excess of 40% seem excessive, though! Judging from the V2 set up you must have had a pretty high grossweight, though. As a matter of fact, to have a V2 of 162 the plane would need to weigh about 70tons... The engine´s acceleration depends on the engine "age" - which is randomly set between sessions. We did this because real engines rarely accelerate equally well and also show slightly different parameters (EGT, N2, ...) for the same N1. Cheers, Jan

Hi Ted, the "mousewheel" rotation is an often requested feature and we definitely consider adding it in the future. Cheers, Jan

Hi Ted, this seems to be the case for some 4k users, not for others. We have not been able to find out what causes this. The workaround seems to be to run in windowed mode, as you found out. There is a program out there that allows you to run in "borderless window" - so it looks like fullscreen. To my knowledge there is no advantage in X-Plane running in full screen vs windowed mode (not like in the old times where running full screen would give you better fps in most games). In addition, it is much easier to work on other things (beside your X-Plane session) when in windowed mode. Cheers, Jan

Hmm, just tried in 11.20vr5 and everything works well (Oculus Rift)... Cheers, Jan