Leaderboard

TCAS CleanUp for the IXEG 733. This script is ment for version 1.2. IF you have problems with TCAS targets not disappearing while using IVAO, VATSIM or PILOTEDGE, then this script may help you. If you dont have any issues, dont use this script. This script will only run when you are connected to IVAO, VATSIM or PILOTEDGE. If this script helped you with stuck TCAS targets please leave a comment below. Requirement: - You will need FlyWithLua installed - XP10: http://forums.x-plane.org/index.php?/files/file/17468-flywithlua-for-xp9-and-xp10/ XP11: http://forums.x-plane.org/index.php?/files/file/35579-flywithlua-for-x-plane-11-and-10-windows-linux-mac-os-x-version/ Installation: - copy IXEG_TCAS_CleanUp.lua to [X-Plane]\Resources\plugins\FlyWithLua\Scripts Download: - http://forums.x-pilot.com/files/file/1060-tcas-cleanup-for-the-ixeg-733/

You mean @tkyler? Otherwise, no, tyler does not exist.

I have the same setup and problem than you (2 networked pcs running a copy of xplane each master/salve, multiple aircraft including the ixeg) master pc is ok, slave pc screen shakes goes crazy when at a speed. while the aircraft is stopped there is no sync problem. this problem started by xplane 10.46 (i do not remember the exact version) when laminar did a rendering engine improvement i have found an easy workaround to fix the problem. 1. You load the master and the slave sim with the ixeg 2. Wait for both sims be ready 3. On the slave mache select a different aircraft, it will load and revert back automatically yo the ixeg because the master machine will tell to load the ixeg again problem fixed. i do not know the technical details what the problem is, why loading a second aircraft and switching back on the slave solves the issue. What is reset that fixes the sync problem note: not any aircraft fixes the problem, you will have to try. On my case i do use the Saab340 for the trick. It solves the problem. Crazy as is but it works If someone else has a better understanding or solution of the problem i am also interested to hear.

The included manual with the aircraft has the answer, document file '2-interface guide.pdf' over the COROUTES section. -the flight plan should reside on a folder named 'coroutes' under the 737 root folder -ixeg supports .fpl format (filename no more than 10 characters length) -to load go to the FMC press RTE page 1, type on the scratchpad the filename (with no extension .fpl) and press CO ROUTE softkey note: make sure the airac cycle used to create the route and the airac cycle loaded on the fmc matches, otherwise you risk the fmc will not recognize waypoints, airways, whatever

Make sure that the altitude fields in the legs page are set. I flew from SLLP to SPJC via ELAKO6 ELAKO UA304 JUL UM415 REMUS DCT CEDRO CEDRO5 and the hight setting for ELAKO was blank and VNAV wouldn't engage. After setting the altitude for ELAKO it worked just fine.

Hi Russel, I did change my password yesterday and had no success. Just tried writing on the notepad and copying into gizmo and guess what... It worked. Thank you for your fast reply.

If you are still going CWS mode time to time, please move the CWS nullzone slider all the way to the right (that is what i did on my saitek times and problem completely solved). I am unsure if monitoring the red bar is an accurate measure, i doubt potentiometer spikes will be reflected there for being so minimal in time. For the VNAV thing, there may be issues certainly. If you share all the details, origin/destination airport, route, sid, star, transitions, all perf init data, etc. to replicate your exact flight i can try it

Had some big issues lately converting DateTime (c#) to a format that can be read by an API for a Jquery based calendar, was lots of fun and ended up using the moment library.....

That may have been a result of your last landing...

Complete flight from KBOS to KLGA with the IXEG 737-300 v1.1 in XP11. It's working almost perfectly.

Hello All, This will serve as a formal forum announcement that we have released the version 1.1 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.1 for you. 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: Added TCAS. Just like in the real airplane, it will show various types of traffic (PROX, TA, RA) and the relative altitude, plus voice callouts and visual aids to avoiding RA traffic. The panel should work as the real one, including TA only, ABV/BLW, STBY, etc. Improved EGPWS. This is enhanced over 1.0.7 - the modes (1-5) should work a lot more closely to how the real modes work, including submodes (i.e. 4A, 4B). There is also a terrain-look-ahead feature that will alert when approaching terrain higher than the aircraft. New panel, new switches, new TERRAIN ON light. New INOP label for FO´s terrain display. Opening cargo doors with door annunciators and 3D cargo holds modeled. Eyebrow windows including selectable sunshade panels (select in preferences menu) Opening cockpit door Now showing current active waypoint distance and ETA on EHSI upper corners in MAP and CTR MAP mode Added increase/decrease map range datarefs A multitude of fixes to FMS stability and LNAV drawing and performance Several texture fixes INOP label for the logo lights if winglets fitted Autopilot fixes (autothrust gain, logic of MA buttons, GS arm logic, cleanup of FMA modes in some circumstances, FL CHG pitch behaviour in MACH regime with turbulence) Several rare gizmo crashes fixed for switches and levers Fixes to headings and bearings shown on FIX INFO and LEGS page (now show correct magnetic tracks) Ground power not showing anymore when booting in turnaround state Fixes to default transition altitude not always showing correctly (still just a crude east/west division) Added realistic way to operate approach speeds on APPROACH page Added failure flag to altimeter when not electrically powered Improved EFIS symbology when IRS units not aligned Fuel gauges now show "lbs" when imperial units are selected LNAV tracking accuracy improved (no more offset flying) Ground model "Ninja fix" when using airplane with XP11 (no full XP11 compatibility yet) Solved numerous situations that would cause the FMS to produce soft crashes in the Gizmo console The aircraft will likely work in X-Plane11, but we do not officially support it and it may not be truly accurate numbers as you would find flight model wise in X-Plane 10. This is just enough to get by and allow your enjoyment in XP 11. A separate XP 11 update will be released at a later point. 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.

On the photo the door to the cockpit is open and closed. View from the salon. From the cockpit is normal.

Going straight to XP11 wouldn't be much fun for our XP10 customers that bought in good faith with the expectations of updates for the sim we advertised we were selling for. XP11 support will come.. It's relatively trivial from what I've seen to make the plane work in XP11, fiddly yes, but not too hard. It's almost impossible to back-port from XP11 to XP10. And then there's the subject of focused efforts. We're sure as a team that focusing our energies on fixing our bugs will be the most beneficial over the long haul. Short term it's a little frustrating but think of the progress the other devs are not making on their core product by continually tweaking the same fiddly things over and over that will soon be left alone for years. Systems depth doesn't create itself. Immersive touches won't either. The physics tweaks will take countless hours of repetitive testing to adjust. Should we really be doing that potentially every week and stalling other things so that we can dance to Laminars whim? Hopefully when X-Plane 12 comes around Laminar will take at least one page out of Lockheeds book and work more closely with third parties so we can all have a launch party together.

@Morten has clearly outlined why this is not the case here: @partTimePilot has posted a fantastic and very clear guide on how to fix it in less than 2 minutes here (which should probably be stickied for the time being):

A year to get an update and still not compatible for Xplane 11 !!!, a shame give ... I feel cheated and I will do my best not to recommend them ....

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