LukasBA

On the 747 you, as you correctly state, want to reduce thrust as much as possible to increase enginelife, but there is not really any specific rules (AFAIK) to when and how to use it. For example: having a TO2 with 34 degrees assume could be the same as a TO1 with 48 degrees (hypothetical numbers, I don't have the EFB in front of me) the main difference, as I think you state as well is from what thrust setting the VMCG & VMCA is calculated. VMCG is calculated always from the full thrust setting, so with TO1-48, your VMCG will be calculated from full TO1, with TO2-34 it will be calculated from full TO2. The EFB should take VMCG limits into accounts though, and give you the right derate for the specific conditions. TO2, is good for 3 engine operations, but not exclusively. on the RR TO2 is used all the time in real life. It's just easiest. If I have a VMCG limited runway I would also use TO2 if possible other conditions taken into consideration.

If anyone else has this problem. The solution is to change your regedit. It is a Simmarket fault. google the issue with simmarket and the solution can be found

I have the same problem. No one else is experiencing this?

It is an interesting observation, and you are partially correct. There are two types of fuel pumps The one PMDG is referring to is the old one, which is not used too many places. thats the type that doesn't turn off by itself when empty. PMDG modeled that into the Aircraft where FS2CREW has modelled the new one (Where it turns off by itself) Looking into my up to date FCOM2 it is not a requirement from Boeings side to turn the pump off with 500 kgs. left, so must be something PMDG has added. As for what to do, my company, back when we had them turned off one pump and opened crossfeed with 1000 kgs. left, and then at the first sign of Low Pressure switch the pump off, close the crossfeed and open the other pump.

TEMP selectors set so each one of them points on one of the different numbers. Thats a good setting to start out with EFB=Electronic Flight Bag, aka IPAD or something. Airplane mode selected (Just like a phone) And stowed so it won't interrupt the takeoff

It is of course not highlighted in my FCOM but as the airplane i fly don't have that configuration that is obvious. I am pretty sure you can't go that high at least with the -800 (You may with the -700 but it takes some very extreme messures like landing Flaps 15), and with the small amount of airports that are located that high , it didn't seem like a big priority. But the solution is simple. do the TEN checks yourself and then ignore the FO if he calls. That's how I would tackle it the real world is not always all SOP either

Well, the thought had crossed our minds what to do, but it can get settled real easy The 737 is not approved nor able to safely depart from an airport with an elevation of 10000 or above, so we didn't bother making it more complicated than SOP3 already is, by diverting from reality I am afraid you must either do the TEN CHECKS yourself, or go with one of the other SOP's when flying from high altitude airports

Just at another time when you have capacity on the approach after the FAF

So! I found a mic... While non precision approaches is not modeled so far, the procedures are not that tough... There are some differences with the way you brief, but I will leave that out. The first major point comes with getting established. Two NM before reaching the "decent point" (the point where the FMC uses an angle to determine descend) the PM (FO in FS2CREWs case) will call "Approaching descend" you then have three things you need to do. Select the MDA rounded up to nearest hundred on the MCP, verify you are in VNAV and press speed intervention, you then make the call "XXX FEET SET, VNAV PTH, SPD INTV" When then crossing the FAF you say "FAF XXXX FEET, NO FLAGS" PM will respond "ALTITUDE CHECKS NO FLAGS" You then descend, you configure just like an ILS at 1000 feet REAL LIFE!! you select missed approach altitude, BUT you can not do that in NGX, As when the ALTITUDE KNOB reaches your current altitude NGX will go in "VNAV ALT" which the real one (at least the one we use) doesn't, so leave that out of it. When you have contact you can disconnect, ask the FO to "recycle FD" turning them off and then on, and then land. That's a non presicion approach with VNAV

Really it is the exact same thing that they do in the Airbus They just have a switch for it and its called "Nose Stearing off" In the 737 we are not so lucky, so the only way to stop the Steering is killing the HYD.

Not officially, just plain situational awareness.

HI Holly71 I have taken the liberty in looking up in our SOP since your your question came up. The newest SOP ways without any doubt "Odd level +100". Now some pilots may have the practise to set MAA+100 because it is easier (just 100 feet extra) and, hell, it is not like it is ground breaking for your flight safety, but it is not standard SOP. Odd level+100 is.

No :huh: Aer Arann ?

Working for that (hopefully) same Irish company, I will confirm that it is ODD level + 100... Turlad, I also always set 3100.

So i'm not quite sure what you're suggesting. I should keep OS and FSX on SSD and storage files on Caviar Green?

Well, its not an old one. It's an WD Caviar Green with astonishing 2TB. So its not a bad drive, but nealy not as good as my SSD(Which by the way is an Intel520) So far I have a little over 120Gb after FSX installation for add-ons. I guess it will go for some time, or what?

Hey Guys I need to ask a quick question. I have two drives. A normal Hard Drive, and an 180Gb SSD. I have installed Windows on the SSD, which means there is about 135Gb left on the drive. Where would FSX give me the best experience? on the SSD or on the conventional harddrive? Best Regards Luke

This is mostly a question for Bryan. I have had the distinguised pleasure of being the owner of several FS2Crew packages. My first package was the LevelD 767, and something about this package has really knocked me out, with its different features, and i'm kinda sad these features are missing in other add-on's for example things like calling the operation center, and checking the flight controls with the FO, and asking the FO to seat the cabin. I really miss stuff like that in the never editions, espicially the NGX version. Howcome these were not included? is it an SDK question? Best Regards Lukas Agerskov

Hi everybodywhile I'm very seriously considering buying the fs2crew NGX, I would like to do some research before i buy, as i'm pretty low on money at the moment.Therefore my initial question is, as I own the Ifly version of fs2crew:What is the difference between these versions?are they identical, or does the NGX version have something the Ifly doesn't?Best RegardsLukas Agerskov :)

Well Actually i changed the motherboard, but to the P67 instead :) seemed neat

Hi GuysThanks a bunch for all the replies. I've decided to buy a Desktop instead of a laptop. My (so far) chosen:I7 2600K 3.4 Ghz (most likely to be overclocked)Gigabyte x58 MotherboardGTX 560 1Gb8 Gb Corsair DDR3 RAM500 Gb WD harddisk60 Gb Mushkin SSD (for FSX use)750 W PSUWill this be enough for PMDG NGX and Orbx with resonable frames?Best RegardsLukas

Hi all.I'm considering buying a new computer, and it stroke me: How many Ghz is really neccesary to run FSX with good frames, when you already have four cores?The one i'm considering is the I7 2,22 Ghz. Quard Core. But is that enough?Best RegardsLukas

Hi Bryan.I've tried a couple of flights now and it works.However it has worken all the times when i speak "flaps XX green light" but does have problems when i say checked", but I have only experienced it once out of three flights and it works when i speak "flaps XX green light"Thanks a lot for the help :=)Best RegardsLukas Agerskov

okay here is the CVRSim Clock (15:58:04) - Captain: thank youSim Clock (15:58:08) - Captain: preflight checklistSim Clock (15:58:10) - Captain: tested one hundred percentSim Clock (15:58:13) - Captain: normal autoSim Clock (15:58:15) - Captain: onSim Clock (15:58:17) - Captain: autoSim Clock (15:58:19) - Captain: checkedSim Clock (15:58:21) - Captain: setSim Clock (15:58:22) - Captain: cutoffSim Clock (15:58:28) - Captain: openSim Clock (15:58:31) - Captain: yesSim Clock (16:03:03) - Captain: before start procedureSim Clock (16:03:23) - Captain: thank youSim Clock (16:03:32) - Captain: before start checklistSim Clock (16:03:34) - Captain: closed and lockedSim Clock (16:03:39) - Captain: fourteen point zero unitsSim Clock (16:03:41) - Captain: kilogramsSim Clock (16:03:43) - Captain: onSim Clock (16:03:44) - Captain: lockedSim Clock (16:03:46) - Captain: setSim Clock (16:03:49) - Captain: setSim Clock (16:03:51) - Captain: completedSim Clock (16:03:54) - Captain: free and zeroSim Clock (16:03:57) - Captain: completedSim Clock (16:04:00) - Captain: onSim Clock (16:04:03) - Captain: start engine oneSim Clock (16:04:38) - Captain: cockpit to groundSim Clock (16:04:51) - Captain: start engine twoSim Clock (16:05:13) - Captain: cockpit to groundSim Clock (16:05:27) - Captain: flaps tenSim Clock (16:06:05) - Captain: before taxi checklistSim Clock (16:06:07) - Captain: onSim Clock (16:06:10) - Captain: onSim Clock (16:06:12) - Captain: offSim Clock (16:06:14) - Captain: autoSim Clock (16:06:17) - Captain: continuousSim Clock (16:06:18) - Captain: checkedSim Clock (16:06:20) - Captain: one twoSim Clock (16:06:22) - Captain: r t oSim Clock (16:06:25) - Captain: idle detentSim Clock (16:06:27) - Captain: checkedSim Clock (16:06:29) - Captain: clearSim Clock (16:08:17) - Captain: before takeoff checklistSim Clock (16:08:19) - Captain: setSim Clock (16:08:21) - Captain: setSim Clock (16:11:40) - Captain: runway entry procedureSim Clock (16:12:37) - Captain: takeoffSim Clock (16:13:18) - Captain: gear upSim Clock (16:13:34) - Captain: select l navSim Clock (16:13:36) - Captain: select v navSim Clock (16:13:53) - Captain: climb thrustSim Clock (16:14:27) - Captain: set flaps up speedSim Clock (16:14:31) - Captain: select command aSim Clock (16:14:49) - Captain: flaps fiveSim Clock (16:14:52) - Captain: flaps upSim Clock (16:15:05) - Captain: after takeoff checklistSim Clock (19:58:33) - Captain: descent checklistSim Clock (20:07:05) - Captain: approach checklistSim Clock (20:07:31) - Captain: flaps fiveSim Clock (20:08:09) - Captain: flaps tenSim Clock (20:09:42) - Captain: flaps fifteenSim Clock (20:09:44) - Captain: gear downSim Clock (20:10:10) - Captain: flaps twenty fiveSim Clock (20:10:41) - Captain: flaps thirtySim Clock (20:11:11) - Captain: landing checklistSim Clock (20:11:14) - Captain: continuousSim Clock (20:11:16) - Captain: armedSim Clock (20:11:17) - Captain: downSim Clock (20:11:21) - Captain: checkedSim Clock (20:11:29) - Captain: nextAt this point being the eight time i just went back to the approach screen and then forward to the landing screen again not running the checklistSim Clock (20:13:07) - Captain: landingSim Clock (20:14:15) - Captain: okay to clean upSim Clock (20:24:06) - Captain: select taxi light off

Hi BryanI have experienced a problem with the ifly voice commander. Everything works fine until final approach when i speak "landing checklist". he talks I respond, but when we come to the "flaps" item, after I respond he just keeps saying "flaps".no matter what I respond to the flaps he continues asking about the flaps. I have tried: Set, Checked, Next, 30/40 set, 30/40 green light, even "restart checklist"its like the first officer loop with "checked" in the LVLD 767I have flown with voice commander eight times now, and it has happen every time.I Hope you can help :)Best RegardsLukas Agerskov