Litjan

Hi sdflyer - the only explanations for this I could come up with is some input to the "yaw" or "tiller" axis from your hardware, so check your hardware setup for this? Or maybe you have really gusty winds set up that rock the airplane sideways? Or maybe some lua script or other addon adding signals to those axis´? Anyone else with this problem? If all else fails, remove all other addons and try vanilla X-Plane (11.50 beta should be fine) to rule out other influence. Cheers, Jan

There are already datarefs on the aircraft for the volume of the radios (default X-Plane). You can access them with dataref editor, so I think that should be possible. We will make the little knobs that "turn" for volume also affect that dataref in a future update. Cheers, Jan

Normally the camera positions should not get erazed...I think.

Always "on", please. (There is not a huge difference, but you can notice the perf numbers being slightly off if you don´t enable it). Once 11.50 is out of beta we will "force" the EFM to always on in our .acf file. Viele Grüße nach Kölle, Jan

Just run the installer, it will overwrite the necessary files! Cheers, Jan

Thats the spirit!

Hmm, ok - may be an initialization thing...maybe its a five-minute fix, I can always slip these on Tom´s list if he doesn´t watch. Just gotta be careful, last time I did this we ended up with 3 weeks of rewriting the FMS procedure loader!

Yes, cargo doesn´t complain...but there is still a lot that can go wrong, especially when carrying lifestock... Cheers, Jan

Yeah, I know that the sounds are not always playing nicely when in external view...but I don´t think we will overhaul the sound engine (which would be needed to fix these quirks) before we do the port to FMOD. Lots of bigger and stinkier fish to fry, sorry! Cheers, Jan

Hi Sebastian, I think X-Plane captures the high-altitude aspect fairly well. It does not calculate the changing of true altitude with different temperatures, that is probably the biggest thing missing in mountain flying (remember the old saying "In the winter the mountains are higher"). The main aspects of high altitude operations is higher true airspeed (needs longer runways and wider turn radii in flight), and also less engine thrust and higher N1s than at "lower" airports. This is both modeled well. The autopilots landing performance is tuned to sea-level airports and while it will land "safely" at higher altitudes, it may not land gracefully. Of course our autoland code is not as refined as the one in the real aircraft, but I can tell you that the real airplane doesn´t land beautifully with autoland quite often, either (both Airbus and Boeing). Its not like some super-pilot is kissing it at 1000 feet. Its more of a "playing it safe" landing... Another aspect is starting the engines, you will see that the APU puts out less pressure at high altitudes, so reaching the desired N2 for fuel introduction takes a bit longer. In the 747 at Mexico City we could "only" start one engine at a time and not run a pack at the same time due to this effect. Also do not forget to set up your landing elevation in the cabin pressure controller correctly. If you forget this, the plane will land pressurized (not allowed) and when moving the FLT/GRD switch to GRD after landing the pressure will be dumped immediately, creating a very high rate-of-climb in the cabin. Also remember that on longer flights TO a high-alt elevation you want to set the landing elevation to 6000 feet until starting the descent - that way the cabin altitude is not really high during the whole flight (may cause medical problems with the passengers). Yes, they will have to suffer the same thin air after they get out and have medical problems then - but then its not your problem anymore . Cheers, Jan

Hi Jesse, Should be very very soon! Hang in there! Cheers, Jan

Glad its "working" for you as well. The airport looks really nice - but just the fact that a small airport like that is 1.2 GB in size... speaks bounds. I am sure the dev meant well, and maybe he can throttle back on the mesh for his next airport (or even update this one). Thanks for confirming the fix, Jan

Thanks for reporting back with your solution!

Hi Ian, try this: Turn off the WXR system switch (above the weather radar tilt knob on the center pedestal). I believe that Ben Russel had the right idea. We "poll" the elevation data of the mesh for, well, elevation data. We use it to drive our terrain display and also the ground returns of the weather radar if tilted too low. Now it seems (have to verify) that the mesh included with ENGS is extremely detailed...this makes the polling of the data so tedious, that the computer slows down every few seconds when we update our elevation map. Cheers, Jan

Just so that no one can say I didn´t test 1.32 long enough...

Good morning Russ, well, that is also a solution, of course - yet we will keep on our toes regarding this one and see if we can find out more. After all both of these products are sold at the same store and should really be working together... Thanks again for working through this with us and sorry for the trouble this gave you, Jan

Hi Steve, yep, we had our share of woes with that folder and went from forgetting it in the installer to having it in the installer but not getting it installed to finally getting it installed, but without the "s"... So 1.32 will see another valiant attempt at getting it right! Sorry for the trouble this caused you! Cheers, Jan

Weird!

For what its worth: 11.50 beta 14 was just released and runs pretty stable for almost everyone. And you can always roll back if it doesn´t work out for you. Cheers, Jan

Ah, ok...yeah, that would be interesting to know if it changes this. I saw your thread in the scenery forum...we are pretty busy with getting 1.32 out of the door, but once that is done - if we don´t have a solution by then - I will get that scenery and try here. Cheers, Jan

Uncheck the "Use Vulkan" in the graphics tab

Did you try in OpenGl as well?

Hi Alex, this does "sound" weird! It seems that your computer does not stop to play a (some) sounds, I have never heard of that before. However - I would still ask you to apply the "standard troubleshooting protocol" found here: ...especially the part about (temporarily) removing all other plugins. Since your bug is so reproducible, this should give you quick results and I would like to hear what you find out. Cheers, Jan

I think we did have some complaints of incompatibilities... are you running the very latest version of SkyMaxxpro? I think 4.9.5 just got released a short while ago. I also could not spot any trace of SkyMaxxPro in your log.txt that you posted initially, so I could not ascertain the version number you are running. Cheers, Jan

Thinking about this...lets also see if we get another report on this - or I will go and buy that scenery to try myself!