VLJ510

What's this default scenery you speak of?

Well real world pilots not only have hours on home PC simulators (if that's their thing), but more so high-end level-D simulators where they are tested on emergency situations on a regular basics. I'm sure they would not be in the cockpit if their employers doubted their ability to handle any and all situations and had tested them beforehand in a controlled environment.

Well now you're speaking further past the topic as to why you're changing PSU in finding out why you're getting this problem. Sounds like problems exist past FSX. First speaking it sounded like your process of elimination fixing this only involved FSX/PMDG and the fact "everything else was changed on your rig accept the PSU & SSD" as the problem left and only FSX/PMDG was effected; not overall PC booting problems, etc. Knowing that, you may have a PSU problem. However I still think you'll have the problem you're having inside FSX when you get that running. I've been running this PSU in my sig for 5 or 6 years! Also I'd beg to differ in what a high-end CPU is, (not saying mine is anymore as its 4 years old, but at the time was marketed as a high-end CPU) and that for its time a 2700k was a not high-end CPU compared to the range of what was on the market then at the time (lots of people ran that CPU all over the FS and overall gaming community. Indeed was good bang for your buck and a good overclocker, but was never marketed as a high-end CPU) and 3770k is (in my opinion) a mid range CPU where again, your bang for the buck is good, but not a high-end CPU when the 3960x, 4960x are marketed as high-end CPUs with Intel black labels and 3930k, 4930k marketed as lower high-end CPUs. For the LGA 1155 socket, that CPU (3770k) was high or the highest, but doesn't really stand out as a high-end CPU in regards to how Intel markets it CPUs and what was on the market at the time it released.

First I'm not saying you're wrong... I have a surge protector that monitors the power specs. FSX never uses over 600 watts so its not a taxing amount of watts for something not to be getting the power it needs. Internally it might be something with the PSU, but I doubt it and if its the problem, there are a fair amount of people with PSU problems making this happen where FSUIPC save, etc, etc didn't fix. Has PMDG reached out to these people with the problem to sort it out?

Well I think its equal in the scene that if 100 people are running high-end hardware and 100 people are running pretty acquitted FS hardware, the amounts of people having problem 'X' are same in ratio just about; that goes for this problem too, not just high-end systems are seeing this hiccup. As well so many variables are in play, its hard to point a finger when problems like this arise and the community chimes in to help. And throughout my MSFS history (back to 98) I've had my fair share of problems and seen people on weaker systems run stronger. Really I just wanted to chime in with some threads I've seen on the topic where people having this problem have had their problems fixed, as well that I'm running the same CPU with a 30+% overclock and all is good. Saying that, I'll say others here run the 980x in the 4-5GHz range and are going fine. And even higher end rigs then all of ours here posted so far not seeing this and sure some that are too. Now it seams everyone is looking at their hardware. Maybe delete/disable UT2 (or whatever traffic add-on) and see if that rids the problem, run FSX in DX9, etc. Because I own UT2, but got rid of it as it got in the way a lot and used some frames I wanted back and run in DX9 and don't have this problem and get 100% smooth gameplay with the NGX and 777 in stressful simulation; of course minus the AI traffic. I also don't use virus software on my simming rig as its just used for FSX and video editing GoPro videos so I don't have that variable in play. Lastly like you I'd think high SSD/HDD activity doing this. But many here are also running normal 7,200/10,000rpm HDD and SSD who also get this problem.

I don't have this problem with NGX or T7. My specs are in my sig. I don't use any AI traffic and running in DX9. ALso using ASN with REX textures. Saying that hasn't it been said that FSUIPC saving in flight can make these freezes happen. Seams to have worked for some: http://forum.avsim.net/topic/420194-no-more-pauses-or-freezes/ This guy seamed to have fixed his problem, same problem you're having but with the NGX: http://forum.avsim.net/topic/350779-strange-freeze-then-un-freeze-problem/

First forum rules ask you sign your real name to get forum support. Secondly it sounds like an activation issue, you'll likely need to contact PMDG support via their ticket system for assistance. http://support.precisionmanuals.com/Main/Default.aspx

I want to fly the 777 today, but seeing (and knowing) soon the plane will be this much better has me spoiled just seeing it. I so want to fly this service pack.

For a longer 737 flight I like KTPA or KFLL to KLAX or KSFO -- For ETOPS flights I like PANC to PHNL, PHLI, or PHKO. Or KLAX/KSFO to the Hawaiian Islands. For a mid range 737 flight I like KMDW or KBUF to KFLL or KTPA For a short hop good for limited time in the 737 I like KTPA to KFLL or KLAX to KLAX or KSFO. If you have a bit more time KPHX to KLAX or KSFO For the 777 I only fly long flights. I like OMDB to KDFW, KLAX, or KSFO. For little less time in the 777 I like VHHH to CYVR, KLAX, or KSFO I fly a lot of routes but these are the ones I do most. The reason why is because I enjoy the third party add-ons from FlyTampa, FSDT, and FlightBeam

It means you're below the glide slope to the point the GPWS is warning you. I'm sure others can go more in depth.

LOL, they sure did. I'm always looking on the northern hemisphere, or really just other links within that page.

I've done about 4 or 5 polar route since the 777X released. Now not that it matters but I also check space weather as they do in real life. https://sites.google.com/site/acnetworkweather/home/space-weather Everything within that page can shows graphs or explains the info within the graphs and even has a calculator provided by the FAA to see how much radiation one might have over the course of a flight.

Yes, I've flown from KLAS to PHNL then down to NTAA, turning around flying back to PHNL, then on to KDFW and landing at KFLL. Over 20 hours no problems. You say, 'reasonable expectations'. I do so with a higher then reasonable expectation, I do so with 100% certainly I'll make it from A to B. My typical flight is 14-16 hours for the 777 (DXB-LAX SFO-DXB etc) and there is no way I'd waste my time (as I'd expect most) to plan then execute a flight if I had any doubts if I was going to make it or not. While sure some people here have had or do have stability issues I would say most don't worry about OOM errors, CTD, or the stability of their FSX machine in flight. Surely those that have been around MSFS for some time and have a reasonable amount of PC knowledge. If that were the case many of the well known community member would have their own post about these problems about not being able to complete a typical 777 flight. Has there been some OOM error posted. Yes, but 10 times outta 10 it looked to me they were being overzealous with their settings. They only had to dial things back a bit to fix the issue, not go the route as you and with complete absence of entire settings to achieve their goal of OOM error free/CTD flights. For the OP, I know I flew into JFK from HGK this afternoon on the Canarsie approach for 13L at no lower then 25fps without shutters with an Intel/Nvidia setup so the OP is not a global one.

Well that's easy to be explained really, just a fact of numbers and statistics. If more FSX users have an Intel CPU; witch they do. I don't know the numbers, but its very high % over AMD I'd be wiling to guess. That its a gimme that you'd hear more problems coming from a Intel users. Doesn't mean its the CPUs fault when like a cake there is a lot of ingredients at play between FSX now-a-days between everything that gets thrown into its use. As for tweaks. I ran my sim rig since April 2010 with no tweaks, things weren't always as smooth or the highest FPS I felt I could achieve. Using the tweaks now, the three or four I use make a big difference in flying anything anywhere near or at 30fps without cutting things out like autogen. Speaking of cakes, sounds like your cake without icing on it. No autogen! Would hate to fly the Canarsie into JFK on your rig no matter how nicely you say it runs it likely looks the opposite. To each there own I guess, but no autogen may make things run nicely like a Ferrari with a primer paint job. I'd take it, but I wouldn't settle for keeping it as is. I want to to look and run well.

I'm replying because I feel for you. On my first PMDG 777 flight from KSFO to OMDB I got a OOM error on final, then again on my second attempt of the same flight near same place on final. After the second OOM error I knew I had to readjust some stuff. As I never had OOM errors with any PMDG software before or any other add-on for that matter. So what I did was lower LOD back to 4.5 (Some have boarder-line cried about the possibility having to do this) Lowered cloud res from 4096 down to 1024 (no biggie and I see you've done this as well) and lowered autogen down one from max I also use the tip the James tossed out in the first post, but this was after I already corrected the problem. It may work on OOM errors, but I did as I saw some extra frames. Since doing what I've done I've had many long haul and ultra long haul flights no problems and not one OOM error since then. A look at your FSX.cfg would help as someone else said. Good luck.