Litjan

You may have internet connectivity issues reaching the download server. This can happen if your computer is behind hardware (usually router or switch) that somehow does not play well with the connection. I have once solved the issue by plugging my network cable directly into the DSL modem (bypassing a second router) and then it worked. You can also try to connect to the internet somewhere else (like a WLAN) to download the patch if the above does not help at all... Cheers, Jan

I think building a cockpit would be a great hobby - I have two left hands (with all thumbs), so it isn´t for me... I think, though (apart from the fun of building it) that the future is in VR. I would just build a seat and flightcontrols mimicking the real ones (so you can grab them by reaching for them in VR). Probably a lot cheaper than building the cockpit, a LOT less trouble (getting everything to work) and you also get the benefit of being able to really lean and look out the window like you can in a real airplane (not with just a few screens giving you all sorts of trouble, too). So yeah, my personal opinion - the days of home-cockpit building are counted. At least as far as trying to create a realistic flying experience. It can still be fun if you like tinkering. Cheers, Jan

Arthur is right. The DRM (= digital rights management = anti-piracy protection) allows you to install this on 3 different computers. Once you want to install it on the fourth, you need to lock (= type FREEZE) on one of the previous three. Now this computer is locked up forever for the IXEG - we do this so people can´t swap the plane with friends and family at will. If you locked the computer you try to install it on (maybe by accident) you can submit a ticket to the X-Aviation customer service system and - depending on the credibility of your story - MAY get the machine unlocked. A second option is to wait until you do a major hardware upgrade. This counts as a "new computer" and you can install your version again. Cheers, Jan

Hi Doug, it is normal for the pop-up menu to be triggered by bumping into the left side of the screen edge. We have recently set up a command that you can assign to some button or key (via the X-Plane setup menues) that enables the user to trigger this window pop-up with a button or key, so maybe that is accidentally triggering for you? Once the menu is visible, you can not click any of the cockpitcontrols behind it (this is intentional, so you don´t click any switches by accident while trying to change values in the menu). I hope this clarified how it works, Cheers, Jan

Yes, I encourage everyone to check for this as well - it would be nice if we could identify some pattern of hardware/software/add-on combination that triggers this! Cheers, Jan

Hi CptBurgos, yes, it is normal for most departures that you load into the FMS. They create a "conditional" waypoint (in brackets), because the departure usually requires the pilot to fly straight to a certain altitude and then turn onto the departure route. Unfortunately the calculation of "WHEN" the aicraft gets to this altitude is still very crude and does not apply the correct elevation of the departure airport. It only calculates how long it would take (roughly) to fly rom sea level to 3570 feet (in your case), not taking into account that the plane is already at 3170 feet. This will be fixed in the VNAV updated. Cheers, Jan

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