StewCal

This was a first for me: Was on a stable approach on the ILS 24R approach into LAX this morning when I disconnected the autopilot at about 1000 ft and suddenly nosed over and plunged into the ground. NTSB investigating...

I think that there is definitely an issue that I'm sure that they will address. I find that if you're expecting it you can press the approach button again and it will reconnect.

I've noticed on the official Majestic forum that others are experiencing the same thing issues with the autopilot on approach. I've also noticed repeatedly that while hand flying ILS approaches if you follow the flight director for glideslope guidance you will get into trouble. I think the flight director logic for approaches needs some tweaking. Works good for departures though.

Last night I was on a perfectly stable ILS for 16R into Reno and the autopilot switched to Wings Level, Pitch hold. I pressed the approach button again and it went back to Loc, GS...

I can never get the doors to work. I was so excited that I got the cargo door open once only to incur a delay because I couldn't get it closed.

I discovered today that if you switch the HSI source to the right side and then back it will "reset" or turn off the flight director.

Same happens for me. Just choose go to airport in the menus if the plane jumps and it should settle down in the same spot. One extra step but seems to solve the problem. I'm sure they'll fix it eventually.

PAKT runway 11...

I've had the issue of GS changing to Pitch Hold during a stable approach with glideslope and localizer captured and good speeds. I've also had it switch to Pitch Hold and then back to GS with the flight director making crazy pitch commands. For example, I've fallen a little low on the glideslope and the Flight Director will command 60 degrees nose up or a full deflection of the pitch cue. The flight director seems fine during departures and climbs.

Ah! That makes sense. It is pretty hard to keep the speed stable in my experience. I'll try harder. Thanks...

Have had an issue doing ILS approaches. All is fine and then the autopilot mode switches from GS to Attitude hold. This then makes following the flight director a little squirrelley (sic?). Am I doing something incorrectly? Any help would be appreciated. Also, is there a way to turn off the flight director? Can be a little distracting if your not using it for guidance at the time...

One must remember that in real life your copilot will be calling out the necessary speeds etc...

I've been primarily flying the NGX of late with my PFC yoke and throttle console set up through FSUIPC. I was fooling around trying to set up my controllers to work with the Q and was wondering if it is possible to use FSUIPC to send axes to FSX or should they be assigned in FSX before using the Majestic control panel to do the calibration. Didn't have much luck in the limited time I had this morning. Any tips or tricks would be appreciated.

I had never had an OOM until after I used "Word Not Allowed's Tweaks". The culprit is the LOD setting. 6.5 will almost guarantee OOMs. If you have the LOD=6.5 setting in FSX.CFG set it back to 4.5 and you won't have anymore issues.

Well, I'm back. After having done a complete reinstall of everything I finally decided to try FS2Crew once more. Foolishly however, being under the impression that System Mechanic no longer caused the problem with FS2Crew I reinstalled that too. Guess what? I can not get the voice version to work. This has been so frustrating. Any new insights?

Direct TV

I've provided the United/Continental info to PMDG but they have not updated the files yet.

Much of the equipment depends on when the aircraft was delivered. Callouts and such should be the same.

If you have UAC enabled turn it off completely. It has caused me issues in the past.

Try reversing the axis.

No hubs. The controllers are plugged into the connected directly to the motherboard. I've swapped them around. I'll have to check the drivers. Thanks.

You can click on "my pc" to see my specs. I've tried all of the stuff mentioned on the other threads to no avail. Just curious...do you have all of the latest updates installed including the optional ones? I'm trying to decide if I have a hardware issue or if an update is causing my woes. There have been a couple of other people using windows 7 that have mentioned issues in the Windows 8 threads. Because of the Winows 8 issue I suspect that an update might be causing my problem. Just trying to ascertain how many Windows 7 users are having issues.

I'm jus trying to figure out just how many folks are experiencing the Joystick disconnect issue with Windows 7 and if so, when did it start. I started having issues in November. I'm trying to figure out whether or not this is an isolated issue or whether a significant number of people are having this issue with 7. I'm tempted just to reinstall windows 7 and FSX without installing any updates to see what happens. Any input would be appreciated.

You need a registered copy of FSUIPC. Just uncheck the controller box in FSX then enter FSUIPC and assign the axes then calibrate. You can assign buttons too. There's a bit of a learning curve but there is extensive documentation. When you use FSUIPC to assign your controllers, if they dissappear you can just enter FSUIPC then exit and they come back. Still aggravating but you can continue flying. I hope we can find out what's going on here.

I removed all three last night. I really thought it would work but I still lost the controls on the next flight. I'm going to look at the rest of the updates from that time period. Something changed in November and the updates seem a logical place to look.