GrayGhostVA

You outdid yourself with this one, Bryan. I'm loving it so far. I just have to get used to contacting the ground crew and hearing myself talk back...

I hadn't thought until that time to let the IRS's align I had just assumed there was an issue and they wouldn't, but yeah if you get the same warnings then it must be how they are supposed to work, has something to do with the alignment process I'm sure. You're right ether PMDG fixed an issue or this was a late addition for better realism.

All right so I started a flight in a default state, switched the IRS's off, waited a couple of seconds and turned them back on. The warnings still popped up like they have been. So this time I tried letting the IRS's align and I entered in the current GPS position, and when the IRS's aligned the warnings went away. Which brings me back to an earlier question I had that I was just doing something dumb, but is this supposed to happen normally? I've flown this aircraft for many many hours and I've never had this happen as far as I'm aware, is this something that was added in one of the recent updates?

Sorry, switching the IRS switches from Off to Nav, to begin the process of aligning. As soon as each IRS begins to align (IRS time to align +7 mins pops up on on the ND), I get the three warnings in succession. Have not yet even entered a position into the FMC. I haven't tested it yet with APU power but I've been on External power.

Hello all. I'm having a problem where when I turn the IRS's to NAV, as each one starts doing it's thing I get >FMC RUNWAY DIS, then >GPS LEFT, then >GPS pop up sequentially on the EICAS. I've tried to search for this issue but I get posts with either a problem displaying FMC Runway Dis or GPS, never all three. I'm hearing that it most likely is broken panel states, so I loaded the flight up in default and made my own panel states, but I still get these errors. I have updated my airac cycle, I've updated the nav database and magdec, I've tried loading up a panel state and literally turning the plane off and on again, but no dice. I'm running on Prepar3d v4. I'm hoping this is something I'm just stupidly doing wrong so I don't have to bother anyone making a support ticket. -Sean Lewis

I saw a picture somewhere of this airline in a right-hand turn onto runway 13, and I just had to recreate it. I'm loving this bird so much. (I took this screen shot while I was using instant replay so the wing flex is borked.)

Thank you very much!

I was wondering if anyone had, or has made, a different or consolidated set of printable procedures for the T7 besides the one that comes with the FCOM, as the one in the FCOM is un-printable and has way too many variables for planes and configs that we don't even have (until we see the -300ER and so on.) It's kind of a pain having to scroll through pages upon pages on my iPhone because there are 2-3 pages of engine start procedures when we only have the GE90's. I looked on Avsim but I've really only been able to find procedures for the old PSS, which has much different (and IMHO, incorrect) procedures than the actual FCOM calls for. Do I need to wait for FS2Crew to be released? I know they'll at least have something. Or, god forbid, do I need to make my own? I unfortunately don't have the time for that. Thank you.

I'll have to check that out.

JS4100. If you use the loadsheet to fill every seat on the plane he's near the wing on the right side.

Well this is... Interesting. I was flying around with the J41 today and I had a full load, every seat filled. I must have looked at all the passengers tons of times over the years since I've owned the J41, but I never noticed this guy... To anyone who's familiar with the popular Valve game Team Fortress 2 will instantly recognize this face, and especially those glasses. Coincidence? Probably. I'm going crazy? Most likely. Though I'd like to believe for whomever was in charge of putting/making the skins on the passenger models, we know what their favorite class was. :wink: Has anyone else noticed this and I'm just late to the party?

I return with (mostly) good news! Just did a flight from Heathrow to Dublin and the sound issue I had a month earlier didn't occur, even when I was switching screens and everything. My only issue was that right in the middle, FSX decided to crash. I'm /pretty/ sure this was the J41's fault, I'm having a lot of issues with it. The IAS hold makes the plane go out of control and FSX almost always crashes... I think I might have accidentally touched the "Headset" button a bunch of times or there was an issue with the sound driver that it decided to use and it just got confused. I touched neither and it worked perfectly. Appart from the crash.

FSX's DX10? Off, definitely. AFAIK it wasn't even finished or something, more like a "Here's what it will look like when it's released!" sort of thing, so it takes a huge chunk of resources for not a lot of results. I actually did just recently re-install FSX and I haven't done that yet.

I've heard that ADF2 is not modeled in FSX or something weird like that? I can't confirm that so take it with a grain of salt. This is why the ADF2 on the 737NGX have little "INOP" stickers on them.

It's a 2GB card. The second moniter was one that wasn't being used anymore so I set it up so I could have Flight Sim related apps (TOPCAT and whatnot) and Firefox on the other screen and still have FSX flying on the main screen. I don't remember if it did, but I'm going to assume that it didn't. I didn't set it to bypass that waypoint and I didn't have a SID set. It should have been DIRECT to MADEP on the CDU.