bob34

I had to make sure the mic switch was yellow near comm1 on the radio panel. Only then could I transmit on vpilot.

would these simconnect issues be a valid reason for erratic vnav behavior in the 777? The behavior in v3 has been very -unPMDG-ish.

For what it's worth, I've been struggling with FTX Global Base issues and 777 issues since v3 on what is normally a very stable setup. Despite getting super high performance from v3, I've had stability issues with all kinds of LOD settings. I think you're on to something Lee. I have tomorrow off, so I deleted everything from my HDD (v 2.5, FSX SE, v3.0) including appdata, programdata, documents etc.. and cleaned my registry. v3 is being installed under the cleanest possible conditions I could make. I'll fly the 777-200/300 on several legs before I add in Global Base, then I'll give them both a good workout tomorrow and over the weekend before I start adding in my other 3rd party apps. Let's see if these two get along, because I suspect they don't. I'm on Windows 10 x64. I'll follow the topic since I've been troubleshooting this as well. Thanks for posting.

Joe - what does hydraulic pressure do for you on a windy day? Do the control surfaces stiffen up so the wind isn't pushing them around?

Completely makes sense.... and yeah, the finger happy pilot thinks because he's done it 500 times he won't miss anything. So to conclude, we put the electric switches ON before engine start rather than after?

Most engine start procedures I've seen and followed have both Engine Hydraulic Pumps ON - and both Electric Hydraulic Pumps OFF Then I stumbled on this YouTube video and noticed he has the two left switches OFF and the two right switches On while starting Engine 2. See it at the 1:30 mark in the video: https://youtu.be/ae20L78imO4?t=1m20s Is he doing it right? Is he doing it wrong? Does it matter? What's the difference? I thought the engine pumps should always be on to preserve the solenoid life... perhaps that's trivial. Anyway... the video made me curious.

Hi Jeff. I had the same problem in FSX, fixed it by setting my sensivity all the way to the left (I believe), But then it returned when I migrated to P3D and installed the 777. I couldn't get it to work in P3D, so eventually I did a fresh install of FSUIPC, then mapped all my controls through FSUIPC and deleted them out of P3D. Play with the sensitivity first, because it's easier, but if that doesn't work, FSUIPC mapping might be an option. I have Saitek Yoke, Throttle, then a flight stick too. Also, check if you have a joystick with a throttle, make sure it's down to zero or you'll have a conflict. That's happened to me as well.

I clicked the installer and it automatically said it's updating version 6436 to 6461. Didn't have to do a thing.

When I stopped using tons of AI traffic and started flying on VATSIM, the stability of FSX suddenly went through the roof. My headaches went away with the removal of AI traffic. I know that's not a good option for many, but perhaps if you can't figure it out, turn your traffic down to 0 and see how well your system performs. A large commercial AI traffic package running at 40% traffic was the culprit in my case.

The fix was in my registry. I did a search for PMDGOptions.dll in my registry and removed the entry I believe. It's the only thing that worked. This is a very old topic and I don't remember the details, so proceed with caution. I believe I messaged Ryan about the fix which he already knew about as well.

Good point Max. It's about making a choice which product will continue to be developed and supported because it's not a small financial decision to change our minds if companies will release separate P3D and FSX versions. It's just a decision I have to make and PMDG decision not to have a license migration or dual license woke me up to the fact that products will not be cross compatible forever. Lockheed and Dovetail will take the software in their own direction and cross compatibility will diminish. So I'm at a crossroads right now. I want the most solid platform with a large choice of realistic add-ons in the future. I'd hate to put all my money behind P3D only to find their licensing is prohibitive for consumer developers. At the same time, I don't want Dovetail to turn FSX into Microsoft Flight either. I have time to think it over... Yep. Been there, doing that, use it a lot and find it completely stable (knock wood). I probably would have deleted FSX if the PMDG products were straight away compatible with P3D.

Now comes the hard decision. Do I migrate from FSX to the Steam version, and eat my investment in P3D, or do I eat my MD-11, 737, 747, 777 investments and commit to P3D all the way. I have this weird feeling that Lockheed Martin could walk away from P3D any time they wish and not even feel it. It's hard to gauge their level of commitment to the product. I really like the way P3D looks, but something just doesn't add up when it comes to a company like Lockheed owning this software and making it available to the public. I guess I have a few weeks to think it over before the price gets jacked up.

A poll would have been perfect. It would have been easier to tally and combine with all the other wish list threads and became an instant market analysis for PMDG. I would like some CRJ's and ERJ's that actually work. The airports are crowded with these planes and I want to fly them PMDG style. You know.... with logical and tested code used to program the airplanes.

Took the Queen out of the hangar after a long rest and setup KFJK - EGLL and noticed a problem I've seen before, but couldn't remember what caused it or how to fix it. The flight is going well, but I'm tracking the course from the left and off the magenta line by about 3 to 5 miles at least. It crosses the waypoint with a few s-turns, but manages w/out losing the autopilot. ASN weather - PFPX for the flight plan. Smooth wind is off in FSUIPC and I have very little turbulence set w/ ASN. IRS's have been properly aligned and I have the latest AIRAC installed. I realize there's a strong tailwind, but since that screenshot, it is now directly on my tail and wouldn't have been causing that kind of offset anyway. The only other thing I can think of is F1's registry repair fix which I might try after the flight. But until then - does anyone recognize this problem and have it pinpointed to save me time troubleshooting? Setup - FSX, Windows 7, ASN weather, PFPX plan, latest FSUIPC.

If everything is clean at 7.5 - what are you looking to gain beyond that? And if P3D ignores anything over 6.5, I would imagine 6.5 is the default - and as CB suggested above, there may be zero difference between 6.5 and 7.5 due to 6.5 being the limit. I'm curious what you find as I'm struggling with blurry ground textures but can't get to my PC until tomorrow.

Personally, I think PMDG's forum has become a horrible experience for many folks who have questions. The best place to discuss PMDG's products is on other sites and forums where the stress levels are much lower and PMDG's lapdogs aren't waiting to bark at you for asking a question or criticizing the product. I've been on these forums for 10+ years and I've never felt compelled to tell anyone to read a manual, search a previous thread, or say "it will be ready when it's ready". And when I see these self appointed forum monitors driving their post counts up with useless quips, I feel bad for the guy who just wants an innocent question answered. I'm glad people are starting to complain and push back on the "veterans" that have nothing better to do than judge every post. If every valuable answer they give is followed by 10 useless sarcastic responses, the forum would be a better place without them.

I've been tweaking - as usual - FPS on my sytem and have a consistent 30fps using the settings Ryan posted for Nvidia Inspector on the 4Xs settings. CPU = 4.0ghz 8-core GPU = Nvidia GTX 660 VAS monitor has me w/ 1500mb free - so no issues there. I have 30fps outside the aircraft. In the VC if have a frustrating 9 to 15fps - over land, over water - doesn't matter. When I open a 2d popup in the VC, such as one of the FMC's - FPS jumps up to 25. I doesn't matter where I drag the 2D popup, I have a big FPS increase wiht the 2D window open. Any logical explanation for that? By the way, I have 8fps in the performance section for the VC displays. Help/suggestions? Thanks.

I've been tweaking - as usual - FPS on my sytem and have a consistent 30fps using the settings Ryan posted for Nvidia Inspector on the 4Xs settings. CPU = 4.0ghz 8-core GPU = Nvidia GTX 660 VAS monitor has me w/ 1500mb free - so no issues there. I have 30fps outside the aircraft. In the VC if have a frustrating 9 to 15fps - over land, over water - doesn't matter. When I open a 2d popup in the VC, such as one of the FMC's - FPS jumps up to 25. I doesn't matter where I drag the 2D popup, I have a big FPS increase wiht the 2D window open. Any logical explanation for that? By the way, I have 8fps in the performance section for the VC displays. Help/suggestions? Thanks.

For those running WideFS, you can watch your VAS on your remote machine by installing the LUA vas_monitor.zip. http://library.avsim.net/search.php?SearchTerm=VAS_Monitor.zip&CatID=root&Go=Search

As mentioned above performance factors weight/weather/climb ratings could cause that, and even more so if there's no ceiling/constraint on the SID. @ or above, I believe VNAV will exceed it, not just meet it. VNAV does not always mean the smoothest climb/decent for you and the passengers. All those factors Rob mentioned should go into the pilot decision to use VNAV or other methods. I've heard from many real pilots VNAV is less than perfect.

I don't have the SID in front of me, so what are the two altitude constraints?

After another day of troubleshooting and re-creating, I'll mark this solved as it seems to be a unique problem. Simply put, the simulator or airplane stopped responding to input from the autopilot or controls. No aileron, rudder, or elevator commands from the sim were making it to the airplane. Not even the autopilot. So the airplane drifted off on its own. This happened about 2 hours into the flight. Best guess: I'm guessing it's an OOM problem, but with the HIGHMEM fix in my .cfg file, the problem manifests itself in stranger ways than simply giving an OOM and crashing the sim. I changed my textures in the .cfg file from 4096 to 2048 and I backed my AI traffic down to 30% from 40%. I've had 3 successful flights since then. I still welcome any comments or insight. Thanks and Happy New Year.

Hi Craig: This isn't a lockup. This is the autopilot and controls not responding. UPDATE- I did a 2nd flight with the 747-400 and the same thing happened in the same spot - about 200 south of COLOR waypoint (south of Prince Edward Island). UDPATE 2 - It just happened in the 777 as well in just about the same spot - same exact symptoms. Autopilot is on, but not response. Yoke controls - no dice. HDG Select - nothing happens. Plane just keeps flying with no guidance. Mouse yoke - nothing. Mouse yoke/Saitek Yoke - nothing. HDG select moves the flight director, but the plane doesn't follow. It just keeps flying along. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Switching to another brand of aircraft doesn't fix the error. I'm in the C-172 (without restarting) and I have no track IR, and no control inputs, and the simple autopilot isn't working either. Something on my PC has to be messing with simconnect or something in the sim. I noticed I can't get to FSUIPC or PMDG through the pull down menus when this is happening as well...

KATL - LEMD - FSX and ASN (Win 8.1 - but don't jump to conclusions) flying 4X up the east coast and I notice the aircraft drifting off the nav line. I bring it back to normal simulation speed, change to heading select mode and nothing. Autopilot is unresponsive to any input (hdg select, flt-chg, vert speed), so I disconnect autopilot and the yokes aren't moving. Not with joystick, not with mouse. I also realize track IR stopped working. No view change through Track IR. Control panel showed all my hardware working - and frankly, if the autopilot in the PMDG wasn't responsive to any inputs, then there's a connection problem in the sim happening somewhere. I could drag the throttles forward with the mouse. When trying mouse-yoke option - nothing moved. So I'm ruling out my hardware. Has this happened to anyone? Does it seem like a simconnect issue? Maybe something induced by 4x or the evil windows 8.1? Curious to hear. Thanks...

I hope you take a nice break and spend time with those who are important to you. It's been a busy year. Here's to 2014. Cheers. I really appreciate what you do and how you do it.