sandpatch

Hmm, when I retried this I totally broke the left FMC. I only accepted a single letter in the scratchpad and it didn't show me warnings. I did come to some rte finishes since I pretended to be on a patrol mission and I did stretch the FMC to it's capabilities. It feels as if I have come further than any beta tester so I will just give up here. This is more than a quick fix to solve.

Yeah, that was the way I remembered it so I did it. I can try again soon and I'll report back

Yeah, I thought so too but when I entered a new cruise altitude it would jump back to the descent page...

I have searched in the forums but without success. I tried flying a tactical mission with the poseidon where I climbed to a cruise altitude, descended on the tactical area, flew around and would return. I wasn't able to get the plane to return to climb/cruise mode. Is there a procedure to reset the system so it will accept climbing again?

Uninstall the NGX and then install it again.

Found the solution! When installing the update I just selected "repair" instead of uninstall. When repairing the OC says that you have the correct version even though the P-8 Poseidon isn't there. What I did was that I uninstalled the NGX packages and installed the new ones. Then the Poseidon popped up. If you are unsure, as vonmar said, it has an own folder in the "Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes" folder. Thanks for the help Vonmar Regards, Manfred

I do not have it there... I tried to "repair" instead of reinstall it. Going to try that now

How can I get it? I don't have it in the livery downloader of OC and it is not in fsx...

Oops, got mixed up with the NGX. Rob is absolutely right. The perf pages disappear so to make them reappear a new crz altitude is required in the init page.

Yes, that is correct. The plane goes into descend mode. One way to fix it is by going in the perf menu and press previous page. That should show the crz page. From there you can re-enter the crz altitude.

No one?

I apologize if there is a tread about it but a quick search didn't help me. I have a CH fighterstick and a pro throttle and I would like to have them perfectly calibrated. Unfortunately the original windows software is quite crappy and doesn't really help me calibrating in dead zones and so on. I would like to use FSUIPC but the problem is that PMDG doesn't want to use FSUIPC calibration, is there an alternate program or software to calibrate joysticks? Regards, Manfred

It is not possible to force it to overfly without having it written in the SID or STAR. You can check out this tough http://forum.avsim.net/topic/238089-md11-fmc-how-to-force-the-11-overflying-a-waypoint/. Especially post 8 and post 11

Upload it to imgur and post the link

Copy past from a previous post: FMC Lat/Long Coordinate Coding Posted 05 May 2011 - 09:42 PM N latitude, W < 100 degrees longitude = xxxxN (eg: 6040N = 60N 40W) N latitude, W > 100 degrees longitude = xxNxx (eg: 50N20 = 50N 120W) N latitude, E < 100 degrees longitude = xxxxE (eg: 4507E = 45N 07E) N latitude, E > 100 degrees longitude = xxExx (eg: 12E21 = 12N 121E) S latitude , W < 100 degrees longitude = xxxxW (eg: 1041W = 10S 41W) S latitude, W > 100 degrees longitude = xxWxx (eg: 05W60 = 05S 160W) S latitude, E < 100 degrees longitude = xxxxS (eg: 0233S = 02S 33E) S latitude, E > 100 degrees longitude = xxSxx (eg: 14S11 = 14S 111E) Example: (taken from KLAX to YSSY United flight on FlightAware) Quote PRCH9 DINTY DUETS 3300N 13000W 3300N 13500W AXELE 3000N 14800W 2800N 15500W 2500N 16100W 2100N 16500W 1500N 16900W 1000N 17200W 0400N 17500W ARTOP 0600S 17500E 1100S 17000E 1500S 16700E 2100S 16300E 2700S 16000E MISLY B580 IFFEY MARLN From the above route: 3300N 13000W = 33N30 3300N 13500W = 33N35 3000N 14800W = 30N48 0600S 17500E = 06S75 1100S 17000E = 11S70 1500S 16700E = 15S67 It's fairly simple to remember. It's either a North latitude or a South latitude, paired with West or East longitudes; NW, NE, SW, SE. If the West/East is greater > 100 degrees, the letter modifier will always be in the middle of the fix (xxNxx) If the West/East is less < 100 degrees, the letter modifier will always be at the end of the fix (xxxxN) North lat + West long = N as the modifier letter ( xxxxN / xxNxx ) North lat + East long = E as the modifier letter ( xxxxE / xxExx ) South lat + West long = W as the modifier letter ( xxxxW / xxWxx ) South lat + East long = S as the modifier letter ( xxxxS / xxSxx ) ------------------------------------------------------------------------------------------- To code in custom Lat/Long corrdoinates it depends on the values of the Lat/Long. In your case, the coordinates will be entered like this: 5700N 10000W = 57N00 5930N 09000W = (not sure about 5930N 09000W but 5990N = 5900N 09000W) 6100N 08000W = 6180N 6300N 06000W = 6360N 6300N 05000W = 6350N 6200N 04000W = 6240N 6000N 03000W = 6030N 5700N 02000W = 5720N I have used this coding repeatedly in the 744 and MD-11 FMC's crossing the ponds. I had this question myself several years ago and was lucky enough to find the post that I qouted above. (I copied it for my own future use.) Hopefully this will answer your questions.

Many aviation thumbrules here: http://www.peter2000.co.uk/aviation/misc/B737mrg_thumbrules.pdf

I am not sure what you ask but activating the alternate often causes problems on the MD11. Simply stay away from it.

Just to make sure, did you have a small plane loaded before you switched to the MD11? Something like the trike or a Cessna.

Yes you did that correct. You may have used a different takeoff procedure than most of us here but the plane has to stop at the FCP altitude, both in prof and level change mode. Tot eh push pulll thing. You do not pull in prof mode but for it doesn't really matter at the moment. The plane should stop! I got a question, is it if even the autopilot is on? I had a plane once that had a great autopilot, the problem though was that the plane never listened to it. No matter what I entered the plane totally continued uncontrolled. It didn't control any surface at all, just appeard to be controlling it. Might that be the case here?

As you said you are doing everything right. Have you tried the registry repair tool at flight 1? http://www.flight1.com/view.asp?page=library If that doesn't work I will suggest a most extreme solution http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx. It's a pain in the *** but I don't think there is anything else at the moment... Manfred

Try http://imgur.com/, it is the easiest file sharer out there. Just want to say that the super low pitch is way off. I usually have 5-6 pitch up, sometimes I come to 3 pitch up but that is very unusual. Have you tried to disable REX yet? Just go for a totally wind free flight... Also disable all weather both on FSUIPC and FSX weather settings. No turbulence or any kind of that stuff. Manfred

You are a dumb **** the solu... Just kidding This is one of the most unusual things I have heard. Never heard of an MD11 flying in space, better contact Houston space center :rolleyes: As I have understood the weather is fine meaning normal temperatures and winds.... The only thing left is that the game somehow is corrupted. It would be nice if you could post a screen shot but my guess is that you actually do everything right. What I guess is that something else heavily interfering whit the game. Have you tried turning of add-ons as FSUIPC and REX. Just go with the plain old FSX stuff. For some reason the FSX registry repair tool does some wonders and sometimes fixes crazy errors. Reinstalling the MD11 itself might be a good idea as well. I would begin with these steps and lets see what happens. HTH, Manfred

Possibly ATIS. But you should enter the info after you have contacted ATC...

You can always click on the LSK button right of the waypoint, it will open a nice little menu where you can enter such info. It is very strange though, /3000 should do it... Just speed xxx/ just altitude /xxx both xxx/xxx Or as mentioned, press the LSK right of the constraint. HTH, Manfred

I looked around a bit harder and there is a lot of info in the systems manual. Also in the QRH a bit below the "GEN BUS_fault" there are generator faults. All of them end up in "continue flying with generator inop". Looking at the systems manual it looks as if the AC bus 2 is only connected through the GEN bus 2. Even turning on APU and ADG would remove the ability to energize AC bus 2. This means that there is a fault in the system that can't be fixed and thereby a loss of redundancy. Anyway all of the GEN buses connect to respective AC bus. Looking at the QRH it makes sense now because each of the faults give a "Land at the nearest suitable airport" message. Might actually also be because the GEN buses also are the lone providers of respective cabin AC bus. I guess that this will make the passengers loose some internal electrical as well. Look at 50.3 in the systems page. There are some good diagrams showing how the system works. As it seems the GEN bus is the thing that connects the AC bus to the rest of the AC system. That means that if the GEN bus two is off the entire AC bus 2 is put out as well. My guess why they didn't build in two extra is simply because of weight and cost. It is a quite rare event and might actually be easy to exchange. Regards, Manfred