winged532

Try the Carenado Cessna 185 Bush version. Its for FSX but works well in P3D.

Milviz 407 is a dream to fly in P3D. I fly it with a Saitek yoke and rudder pedals. You can set it down on a dime.

Definitely not! Did you actually install the textures from REX? That would be the first thing to check.

This is what solved my OOM's, as suggested here on the P3D forum. Before doing this, I could not even load a flight at EGLL using Aerosoft EGLL Extended and ORBX UK scenery with the Milviz 737-200. As soon as I had it all selected, my P3D crashed with an OOM. Now, however, I am able to fly extended tube flights all over without any OOM's. The trick is to create a startup scenario via the scenario menu...selecting the departure airport, aircraft, and clear weather, then saving it and shutting down P3D. The culprit seems to be using the Vehicles menu to choose your aircraft at the startup screen. Once you do this, VAS goes to hell quickly. By creating the startup scenario, you bypass the Vehicles menu. Seems to be a flaw in the current 2.4 version. Now, I start up Active Sky Next first, load the scenario, and every thing works without an OOM. This is not my idea, but I thank everyone on the forums who came up with this, because I have not had a single OOM since following this schedule.

Get real world flight routes from Flightaware actual flights, then create those routes in FSX.

Dazkent, My system is very similar to your specs, except I have a 4790 and two SSD's, one small one for the OPS and a large one for P3D. This is a dedicated system I built in August of 2014 solely for Flight simulation. It is not overclocked, and runs a stock 4Ghz, with aircooling. Operating system windows 7. Before I installed anything on the rig, I used the setup guides available here to optimize and verify that all the internal components worked as they should. This took a lot of time and effort, but I was determined to satisfy myself that I did it as well as possible this time. Only after this did I start installing P3D v2.4, Orbx products, and P3D aircraft. I do not have any config mods at all, except for high mem. NONE! As a result of this, my simulation runs a consistent 45+ frames (or much more) with NO stuttering whatsoever! This is with A2A accusim aircraft and Milviz 737-200, and most settings set extremely high. I do not use AI aircraft very much and this is one consideration. It does not matter if I am in windowed mode or full screen mode, my frames remain the same and I have NO stuttering. I am convinced that if you are able to setup and verify that your computer is running correctly using the available guides, and you can use SSD's to reduce info access time, that it is very possible to have P3D v2.4 run superbly and eliminate all stuttering. I am not a computer expert...but I have used the resources available here on Avsim to get my flight sim rig to run totally to my complete satisfaction. More and more often I FEEL, (not know), that a lot of the problems people have are due to trying to (over) mod their software with config changes...I myself have done these things in the past, and I could hardly ever remember what combinations of changes I made in the past and what state my system was currently in. Now, I do not spend any time with all that. Just happily fly in my beautiful P3D world.

If possible, upgrade your graphics card to the 770. It has lots more processing units for the small extra cost. All else looks great.

I had a similar AP problem that I traced back to some settings in OPUSFSX that seemed to confuse my AP and Simconnect timings. Newer versions of OPUS give the user latitude to adjust the amount of time that Simconnect has to reconcile calls by addons. Here is what I did to fix my AP problem. 1. Click on the Configure button in the main OPUSFSX window 2. Next, in the Dynamic Head Movement (DHM Options) section, click on DHM-VC Views button 3. See the six sliders - go to the bottom right slider and move it left to zero, and below this slider adjust DOF to 1, and Delay to 10 Thanks go to others that gave me this lead. It fixed the AP problem that I had with all of my addon aircraft. Hope it fixes your problem too.

That is correct. They say that if you want to swap paints, first swap to a different model, then swap back to the model you want, with the paint you want.

LOL Well done!

Ryan, I did what you suggested, substituting the Task Manager items Memory Usage, and Peak Memory Usage for Working Set and Peak Working Set, for both the original Aircraft folder with all my addons, and the modified Aircraft folder containing only the stock aircraft and the NGX. According to your predicted behavior, there was no substantial difference between the memory values with either of the Aircraft folders. I flew the same flight for about 15 minutes, each performed normally. I moved through all the outside views, opened all the 2D windows, interacted with the CDU, zoomed in and out with the VC, and panned around the VC in all directions. In both flights the Memory Usage, and Peak Memory Usage pretty much stayed in lock-step, with Memory Usage settling a little under Peak Memory usage: Flight #1 with Modified Aircraft folder: Memory Usage 1,377,377 Peak Memory Usage 1,414,932 Flight #2 with non-modified Aircraft folder: Memory Usage 1,423,122 Peak Memory Usage 1,476,312It stayed similar to this during both flight, altering slightly. The interesting thing that I discovered, however, was when I minimized FSX to the task bar to access my desktop, during flight # 1. When I returned FSX to full screen, my Memory Usage had dropped to 677,000! It stayed around that level until I closed FSX. I then proceeded to start Flight # 2. Upon minimizing FSX to the task bar, and then returning FSX to full screen, my Memory usage also dropped, this time to 587,000. It also stayed around this level until I closed FSX.Now, I am not that tech savy to know if this is important or not. This was simply an observation. I did not have any panel freezes with either of these flights. Both departed from the same stock airport and used the same flight plan and configurations. I wish I knew more about why my FSX and NGX are working now.

I am using WinXP, and Working Set and Peak Working Set are options that are not aviailable to me

Many thanks for all your efforts and the willingness to share!

Then, why does it work for me? Why does my FSX load in one-third the time it took before? Why have I been able to fly three, nice long flights, using all the features of FSX and the NGX, when it was impossible to compete one flight without a freeze before? It may not make sense to you, but the proof is in the pudding, so to speak.

Try turning off your antivirus when you are flying, or exclude anything that you are using for FSX.

Ricky76, try this: Just move some of your addon aircraft folders into the another folder in your SimObjects folder. For example, your PMDG747 folder into the "Animals" folder, so it doesnt load when you start up the sim.Then try to fly around KSEA and see if it helps. You are just freeing up some memory space for FSX to use by doing this. If it doesn't help, just move the folder back to the Aircraft folder, No Foul, No harm.Mike Illian

This was not a lot of work to do. Took me about 3 minutes to setup. Now I can fly any livery of the PMDG that I like, not locked into the PMDG livery. All my other aircraft are easily available, If I want to fly one of them I just use explorer to move the folder back into the Aircraft folder. I continue to fly free of panel freezes, fully utilizing all views and the CDU in flight. Works for me!Mike Illian

Being one of those experiencing continuos panel freezes, I want to share what seems to have fixed the problem for me. This was an idea which I must credit to someone here on the forum, but I forget who it was. His suggestion concerned FSX having to load a lot of third party airplanes, thus eating into memory space. Seemed reasonable, and since I had a ton of addon aircraft, I decided to try his suggestion. I renamed my Aircraft folder to "~Aircraft", and created a new Aircaft folder, copying and pasting only the stock FSX+Acceration aircraft, plus the PMDG737NGX. Lo and behold, that solved my panel freeze problem. I have flown 2 flights, fully utilizing all features of the NGX without any freezes. One flight was 1.5 hours from KATL to KMSY, and the other was a 1.8 hours from CYYZ to KBNA. Three of the airports were stock, with KATL being and addon. I Used the CDU enroute to make route changes due to the weather, and had real world weather enabled. Intel QuadCore 9550, 2.83, 4GB, 8800GTX, WinXP.Mike Illian

This sounds like the classic panel freeze so well documented here in the forum. For me, I can only fly by not interacting with the CDU. This seems to be a common item with many experiencing panel freeze. Why? I don't know. I hope it is solved in the SP1.

For the US, I use Flightaware. Go to the departure, and arrival airports, and get the latest weather, so I know which runways to use. Then search the latest flights database for actual routings being used commercially, Build your flightplan from there.

I tried six times to fly a flight from KATL to KMSY, about a 1.5 hour flight. The first two flights resulted in a panel freeze about 12-15 minutes into the flight. The third flight resulted in a CTD after about 1 hour. The next three had panel freezes soon after takeoff. In trying to analyze what might be causing these freezes I tried many things that I suspected might be involved. On the seventh flight, I decided I would not interact with the CDU in any way during the flight. I would not even look at it!!! The only thing I did with it was load fuel. I did not even adjust the payload. Once I did that I kept my hands off it. Of course I had no flight info in the displays, so I used FSCommander on my second monitor to give me nav guidance. I used the MCP and autopilot for the entire flight for direction, altitude, and speed control. Upon arrival at KMSY I used autoland for the landing. My framerates, and everything else in FSX and the 737NGX worked very well. I have concluded that interaction with the CDU is causing my panel freezes. I don't know what action or actions specifically is doing it. I would be interested to know if anyone else having panel freezes can successfully fly a flight without using the CDU, and be successful at it as I was.In all other regards, this plane is amazing. I hope the developers are able to solve this problem.Mike Illian

Awesome share, thanks a bunch.Mike Illian

Yes, I have done everything the manual suggests. Still trying to make some changes. I am stopping some .dll's from loading, including FSUIPC. Will report back after some test flights.

No I did not send a ticket. There are plenty of tickets already sent on this problem. It is random when the freeze occurs. I cannot reproduce them. I have a lot of third party addon aircraft that tax my older system, but do not make the sim unflyable like this one. I use XP with a quadcore 3.0, 4GB ram, 8800GTX. Not state of the art but completely flyable. I have had freezes at stock airports and with addon airports. I was able to fly into Aerosoft EHAM with no problem in the tutorial, although it froze on the first try. Totally random. Go figure. Something in the code is not right. I am frustrated and mad at myself for spending $70 on this one.

I bought this aircraft after hotfix3 was updated. To date, I have completed three flights out of about 15 tries. All of my unsucessful flights were due to panel freezes. No CTD's. I have tried everything I could find in the forums to eliminate the freezes without any luck. I cannot find any common items that seem to cause the freezes. So, after spending the most money I ever spent on an aircraft, I am going to uninstall it, and call it my bad misforutne to have bought it. It is just TOO frustrating to spend 30 minutes setting up a flight and have it end with a freeze. I am happy for all of you who are not having any problems with this addon. I wish I could be with you, as this plane would otherwise be amazing. I hope that PMDG is capable of solving the freeze problem. They have such a good reputation that I did not hesitate to buy it originally. I just doesn't work for me. Mike Illian