Leaderboard

Oh, there may not be 32 days in May in the UK. But then again, you guys drive on the wrong side of the road, too...

Just wanted to thank the developers for the 1.1 Patch, there is still much to be done but the added functionality and crash fixes are a big help. It also looks like the engine oil pressure readings are more accurate, has anything else been tuned that is not in the log? I just finished a flight in the 737 and even with a few missing features it is my favorite addon to fly at the moment. By the way, today I decided to watch some of the old videos and blogs describing the systems modelling from several years ago when this aircraft was still not released, and it was a good reminder of just how much behind the scenes detail that has been put into this addon. If you haven't looked at these before or in a while check them out, it gives you a new appreciation for the ixeg 737 and may help you wait while they continue to add more functionality.

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/

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

Recently got this one. Unsure if it's correct

Must be Theresa May...

Well, as you just noted yourself, XP11 still has it's flight model problems as well Not all your observations are correct, but we have come a long way on the XP11 update and once the v1.1 release dust has settled work will continue.

I second this. Thank you so much for this excellent aircraft!

Important information on the latest Gizmo and it's new features in this video - MUST see!

I may be reading this wrong, but is my FMS showing May 32nd?

Good evening, do you know when the cabin lights will be added back in? I'm not too concerned about the "quality" of the cabin, but the plane looks unrealistic without interior lighting. I know they were once in the plane, but I don't know why they were taken out. Many thanks.

Many Thanks guys coroutes in ixeg 737 classic folder solved my problem JC

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.

Is it possible that I can give instructions how to amend the cabin file in order to get easy cabin lights ?

First post edited. New file for the 1.1 release.

I don't expect this much... I just did never try those insane setting up to 100.000 so this is my first try and I wanted to know if this result is normal. So thank you,Denco, I think you gave my the answer and I'm fine with it. I usually use default (4900 sqkm) setting but I will try higher visibility range once XP11 has been futher optimized by Laminar.

Thanks Tom - so easy when you know how! Much appreciated.

Unselect "Notify me when my license is updated". You find the preferences on the Gizmo tool tray on the right side on your screen. I also have seleceted "update license at sim start"

Rumor. There was something wrong with the very first few downloads of 1.1 (some files missing), so X-Aviation sent out an email to those affected. This may have started the "patch" for 1.1 rumor. We are, however, looking at re-instating the hotfix mechanism for "code only" patches, but that is still in the future. Jan

We may actually leave the cockpit-door thing as it is - as a reminder of the philosphical questions in life. How things can look different from other perspectives. How a door can be open, but at the same time closed. How things are not always what they seem to be...

Yea, cabin is still under construction, will get fixed

That yellow CWS P mode on the annunciator means what i was speaking to @WR269, the aircraft entered Control Whel Steering Pitch mode becuase the pilot is manipulating pitch and overriding the systems. Off course you are probably not manipulating anything, this is your yoke/joystick potentiometer sending noise and the aircraft "thinks" you are trying to regain control. EDIT: @Morten was faster

Stolowski, look at the PFD horizon. To the right you see in yellow "CWS P". Control Wheel Steering Pitch. The aircraft is in CWS mode now, so you will not be able to activate other vertical modes. As mmerelles suggested. There are two ways you could have entered this mode 1. Accidentally bumped into your yoke while the AP was on 2. You hardware is sending signals "spiking" it should not. Try increasing the NULL zone in the joystick settings in XP to prevent this from happening. M

Time and computers is a remarkably complicated subject. Check out this list; http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time

Some screenshots from around europe

Ok, went to make the video tonight and then it hit me what I was doing wrong. If you want to manually set N1 you have to pull out the adj knob on the N1 gauge and set desired N1 and leave knob out. It worked perfect! To use FMC desired N1, Adj. knob must be pushed in and parameters entered into FMC via the CDU. Sorry for the confusion. RTRFM !! lol Rob

Understood, but it was very much a wide issue....no matter what flight, what route. I never loaded a flight plan, always entered it manually. Always entered SID and STAR before departure. Always started Cold and Dark. No Disco items in FMC, no issues whatsoever. When the issue started, I was unable to engage VNAV until about 20,000ft....later flights i could not engage at all. Funnily enough, LNAV engaged without a problem, but VNAV refused....nothing in vertical navegation worked, Altitude Hold, Alt Select, Vertical Speed of FL CHG, not one of them worked....if I had autopilot on and flying on LNAV...if I pressed any of the vertical modes above, autopilot would disconnect. Very strange. I removed all plug ins, reintalled countless times....nothing worked. When I installed the new 1.1 on a brand new version of XP11, the very first flight I did had VNAV disconnect 3 times in flight, but the autopilot did not disconnect....I was able to re-engage VNAV and flight continued. I reinstalled the IXEG once again and have done 2 more flights repeating the original, and the issue has not happened again so fingers crossed I have it behind me.

It's a mechanism to prevent PAX from seeing pilots operating the chemtrail pumps. It's a feature.

removed NOAA, set SMP4 to max, all seemed fine in quick test flight last night, was getting FPS mostly between 28-38 with the odd dip, this was at night and in daytime.....

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.

The new 1.1 Installer does not create the directory "coroutes" inside the Aircraft-Folder. So if you are wondering why you can't export from whatever program to the IXEG, just create the folder <X-Plane>\Aircraft\X-Aviation\IXEG 737 Classic\coroutes

Ja, deleted the attachment a minute later, sorry for the hazzle, i didn't realy think about it.

You are totally right, of course - and that is why we will have a full compatibility patch for XP11 "soon". And your intention with attaching the .acf file here was ment well, I know - but we would rather not have this sort of thing in the "official" support forum, for two reasons: 1.) People downloading it will assume that it is an official "patch" or whatever. No matter what kind of disclaimer you put up, some people have a hard time reading what they don´t really want to acknowledge. 2.) All the files that you have in your X-Aviation/IXEG737 folder are copyrighted and can´t be shared without written consent. Cheers, Jan

That's correct. X-Plane 11 is at your own risk. From a code perspective we alleviated what was causing issues taxiing around. For those adventurous enough to dabble in 11 and not care about flight characteristics, you can have some fun then.

Yeah, don´t get me wrong, I also want the FMS to be able to do programmable holds - it just wasn´t possible to get that done for 1.1. The dev-time we got on FMS was devoted to fixing what is already there and to make things more stable. The holds are definitely up very high on the to-do-list and will most certainly be done for the next patch (after the XP11 compatibility patch). For now, here is how you can do "manual" holds without too much of a hassle: Use the FIX page to enter the relevant fix. Add the inbound course as a radial. You can also use enter a distance to give you a cue when to turn back in (1 min outbound at holding speed is roughly 5NM). Now use HDG SEL to fly the hold you manually drew onto the EHSI map. No need for timing, WCA calculation, etc.It won´t be as precise as a computed hold in LNAV, but this will certainly keep you in the holding area and the controllers off your back... Note that the radials shown on the FIX page will be correct for 1.1, there was an error (magnetic variation) before. Cheers, Jan

Not being able to enter holds should be a top priority in my book, especially since online ATC fairly frequently asks pilots to enter holding patterns when the skies are busy. Without it the aircraft is pretty much limited to offline flying only. Regardless, I'm still looking forward to getting the 1.1 update.