Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/13/2017 in all areas

  1. Another solution of the pushback in XP11 is to use this brand new and nice animated pushback plugin created by one of the users here (skiselkov) - https://github.com/skiselkov/BetterPushbackC/releases Here is a video demonstration of a pushback of 737 v1.2 with this plugin:
    4 points
  2. Hello All, This will serve as a formal forum announcement that we have released the version 1.2 update for the Take Command! IXEG 737 Classic. All customers who have purchased the IXEG 737 Classic up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the IXEG 737 Classic from today forward, your purchased download will already be updated to version 1.2 for you. This update brings full X-Plane 11 compatibility. It will also work in X-Plane 10. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original IXEG 737 Classic download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: X-Plane 11 compatitibility issues fixed (APU works, engine RPM) Utilizes new X-Plane 11 features like ground vehilcle attachment points, thumbnails for aircraft selection, better categorization in X_-Plane 11's user interface Re-enabled IXEG pushback system being able to turn in X-Plane 10 Added material properties to outside of aircraft for X-Plane 11 Liveries updated for nicer X-Plane 11 look Added cockpit reflective surfaces for X-Plane 11 Increased light strength for cockpit lights in X-Plane 11 Flightmodel & aerodynamics recalibrated for X-Plane 11 changes Improved weather radar in X-Plane 11 version (no more erasing on sweeps) Reduced flashing rate of cockpit warning lights in X-Plane 11 Added a lit cabin at night that dims for takeoff and landing Cockpit door now operable and opens from both sides Minor fixes and additions to 3D model and texturing Changed all script files to automatically recognize which X-Plane version they run in As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    2 points
  3. This is intentional. Use the default X-Plane 11 pushback if using XP 11. Turning only works with our pushback in XP 10. Turn off IXEG contrails.
    2 points
  4. very cool, will give it a try, thanks for sharing
    1 point
  5. Pushback issue solution checked and confirmed, no problem at all. What about the PROG Page issue ? Best Steff
    1 point
  6. Yes. This is fine. You can activate three machines at the same time. When you try and activate number four it will ask you to deactivate one of the other three.
    1 point
  7. Well, that doesn't change anything. The alternative is the consequence you just experienced for taking the shortcut.
    1 point
  8. Thanks for the info guys. My apologies to the xEnviro team should they ever see this. Enjoy your flights!
    1 point
  9. I wish I even owned it! But no, I'm serious. Nothing installed except for B737 and X-Plane...
    1 point
  10. Starraider, Try turning off the contrails and see if that works.
    1 point
  11. yes, this is a known limitation of current vnav implementation. anytime you see a waypoint on a SID/STAR having double altitude constrain you need to go to the legs page and adjust the constrain altitude manually. vnav will be reworked entirely as said by the developers
    1 point
  12. Nice turn-around on this update! Thanks!! I only wish the installer wouldn't overwrite my nav data... Cheers all
    1 point
  13. No one said anyone was having an issue. I'm not sure why you even tried to make a suggestion for some software that won't integrate or do what we need it to or what our own coded software already does. There's new code being built for future updates, including this one. Morten already discussed that in this thread, and that's all there is to it.
    1 point
  14. Hi Tom, excellent post and all your observations were spot on! The reason for flaps 15 is the ability to fly a missed approach with flaps 15 without having to use the alternate system (electric engine) to retract the flaps during the go-around. Also interesting may be the fact that you had 10% of quantity remaining in the B system - this is due to the intricate "standpipe" design of the hydraulic supply lines in the hydraulic reservoir. If you have a rupture in the engine-driven-pump circuit (most likely due to engine failures), this highest standpipe will only drain so much fluid overboard, with enough remaining for the electrically driven pump. Should there be a rupture in that system (as in your case), the fluid will drain to the lower standpipe - with enough remaining (ca. 10%) to supply the automatic slat system via the PTU, should the need arise (stall while at flaps 1-5). In a real airliner you would probably divert to the nearest suitable airfield with declaring emergency, after all you are out of redundancy (the standby hydraulic system doesn´t really count) - but in a simulator it is acceptable to continue, of course . But you can see that even loosing half of the hydraulics is pretty much a "non event", piloting wise. You land with flaps 15 and are limited to CAT1 - legally. Plus there is a startle if it happens while you are on autopilot B, which will disconnect with the warble. Technically you could still do an autoland with a single autopilot and the flaps extended via the alternate system to 30 or 40. This would fall under the "emergency authority" of the Captain, and would only be done in very dire circumstances (inability to reach an alternate airfield with CATII or III weather prevalent). Cheers, Jan
    1 point
  15. A little story from my last flight. Had a interesting flight yesterday between LSZH (Zurich) and ESSA (Arlanda) during a VATSIM event, when a failure was triggered. Its fun to (try) troubleshooting and find out what has happend without looking at the logfile or the failures menu. (All picture is taken on ground just to illustrate) I had about 400-500nm left on my flight to ESSA when I got this master caution. I obvious have some issues with flight controls and the hydraulics. So my next step is to look at the overhead panel. The first I notice is that both hydraulic pumps for SYSTEM B is indicating LOW PRESSURE. And I noticed the indicators for the flight controls, but my main concern was the hydraulics. So I checked the pressure and quantity for SYSTEM B and confirming that I have a total loss of that hydraulic system. So I was thinking, what to do, what to do. I had no problems flying the aircraft with the autopilot. And everything else worked fine. My next step was to check if the QRH was covering this issue. And it did. Luckly for me. First two steps is to set SYSTEM B FLIGHT CONTROL SWITCH to STBY RUD and set both hydraulic pumps for SYSTEM B to off. So far so good. Still flying. And I made a decision to continue my flight to my destination as planed, it was after all a nice VATSIM event with alot of traffic. I started planing my next steps. What system have I lost ? How do I handle that ? The QRH says this. Systems that are handled by SYSTEM B is. Outboard flight spoilers. Autopilot B. - No issue for me, flying on Autopilot A. Yaw damper. Alternate nose wheel steering. No issue SYSTEM A is covering Nose wheel steering. Normal brakes. SYSTEM A have to handle the brakes, and that means that Autobrake is INOP. Manual braking only. SYSTEM B is also covering flaps, so alternate flaps have to be used. The QRH says I should plan for a FLAP 15 landing. Not sure why, but could be performance issues with a go around or if I lose of a engine, since I cant retract the flaps with the alternate system. Active runway for landing at ESSA this night was 01R (2500 meters). I did ask ATC for 01L (3300 meters) for landing, but it was denied (shame on you ATC) So 01R it is. Winds calm. VREF with FLAPS 15 was 144knots + 15. So my approach speed would be 159kts. The QRH says that alternate flaps extension from flaps 0 to flaps 15 takes 2 minutes. So had to plan this and make sure I was able to set flaps 15 in time. On the approach. At < 230kts I enabled the alternate flaps. Set the flap lever to desired flap position and extend flaps on maneuvering speed schedule using the alternate flaps position switch. Landing checklist: I was able to set the flaps in time and the landing went fine. You can learn so much from the failures IXEG have made availble for us. And a 2 hour "boring" flight from A to B can be pretty busy when you need to start troubleshooting and flying the aircraft at the same time. Pretty sure I was doing a lot of mistakes, but it was great fun From the logfile. The flight on vatsim: https://vataware.com/flight/5926fe4253523315c9000008
    1 point
  16. Still no sign of 1.2 What's taking xAviation so long ?
    -1 points
×
×
  • Create New...