Jump to content

Archived

This topic is now archived and is closed to further replies.

winged532

Panel Freezes Gone after doing this!

Recommended Posts

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

Share this post


Link to post
Share on other sites

That seems overly complicated.All I did was stop using custom liveries and start using the default NGX livery, and I haven't had a freeze since.

Share this post


Link to post
Share on other sites
That seems overly complicated.All I did was stop using custom liveries and start using the default NGX livery, and I haven't had a freeze since.
Same here.

Share this post


Link to post
Share on other sites

I dropped the CLS airbus A340 ( It is a terrible sim in comparison to PMDG) and I have only had ONE panel freeze since. I may drop the CLS DC-10 as well ( I sorta like the '10 though) and see if I get better performance. I will say this, I have a GPU acceleration option on my Quadro 5600 and I have disabled it. When I enable it, it hurts performance and caused a crash. With it OFF, I have had almost NO problems. I have gradually moved my sliders very close to max, I am running 35% traffic and I always use downloaded weather. Last freeze occurred when I was trying to change ILS runways while descending for landing. I was using the FMC heavily and thats when it froze. I havent had a freeze in 7 or 8 flights. We'll see tomorrow.

Share this post


Link to post
Share on other sites

Note,there are two types of panel freezes in the VC. One is a memory issue, and is frequently accompanied, by some other anomaly, such as graphic coruption or reduced scenery detail, and possibly a OOM, or a CTD. The other is a focus issue. (Some other aircraft have this issue as well.) That is if you move the seat back too far, you can no longer click on the panels controls. This can also happen with movement with EZDOK. When this happens, the gauges will still function and controls on the 2D panels will work, just the VC controls won't. To correct this, just move your view position closer. Remember move not zoom. Then it should work again. So if your gauges function, but you can't click any knobs or buttons, try this, before you assume it's a memory panel freeze. You may save your flight. If the gauges freeze, it's most likely the memory issue.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

I didn't have any ctd or freezes until I loaded up REX. Now I get them almost every flight(panel freezes) I had 1 freeze when I first installed NGX without REX. But that was it just 1. Now I have them all the time. Very frustrating indeed. I hope by lowering the settings it will help, but that's defeating the purpose. REX is awesome and makes every flight delightful, especially with NGX...if I can get it to stop freezing..... Rick Otolo

Share this post


Link to post
Share on other sites

I'm still using the first version from day one,(no hot fixes installed) and have 91 hours on it to date. Since first flight, I have only had 2 fatal errors. Those were both due to logitech popping up a window telling me my mouse battery level was critical.I can fly over ORBX scenery with max sliders (except around KSEA where a CTD happens anytime with any plane) and as long as I keep my butt in the cockpit with out switching views, I can get 3-4 hour flights without any issues.

Share this post


Link to post
Share on other sites

I have 33.7 hours since I reloaded NGX and HF3. One freeze and I moved sliders (mesh complexity etc) to max. Losing some FPS over LIRA on departure, but no crashes and another great 3.6 hour flight to Norway.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Guys - this doesn't sound logical to me. FSX doesn't load all the aircraft in your aircraft folder into memory - only the one you're actually flying and ones that are assigned to AI aircraft that are active in the world. The idea that using the House livery doesn't make sense either - it's no different from any of the other liveries aside from what's actually painted on it. The House livery is actually larger than many of the airline ones even.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

FSX itself during loading goes through and "catalogs" so to speak which aircraft are there for creating the aircraft select screen. (it does this by scanning the aircraft.cfg entries) It is not actually loading all those airplanes into memory as if you were running them in the sim. That's my point. Correlation doesn't equal causation - I have nearly every major addon aircraft installed on my own FSX setup and I have never seen a panel freeze. I could just as easily claim that it has nothing to do with the aircraft folder based on that. Here, if you want to do a concrete empirical test - do this: 1. Open up Task Manager and go to the Processes tab - go to View/Select Columns and enable Working Set and Peak Working Set. These most closely approximate the amount of VAS FSX is using aside from video memory. 2. Run FSX in both of your configurations (with the other aircraft in the folder and without) - run the exact same flight each time to minimize any variables. Note what the working set and peak working set values are throughout the flight. If your assertion is correct they should be massively larger with the aircraft in the folder.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Ryan, I've read what you've posted so far, and I absolutely disagree. I'm not disagreeing with the logic, I'm disagreeing that custom liveries play no part in the freezes. When I first bought the NGX, I flew the Delta -800WL.I got a freeze 1 out of every 3 flights, and ALWAYS right after exiting the runway at my destination. After hearing feedback, I switched to the house livery and I never had a single freeze since I made that switch. I've flown maybe 15-20 flights since I switched to the house livery. Not in any of those did I get a freeze. Tonight, I downloaded and installed a custom Delta livery also for the -800WL.As soon as I landed at my destination, and taxied off the runway, *BAM*...panel freeze. In my opinion there is absolutely no way it's a coincidence.

Share this post


Link to post
Share on other sites
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
Hi Mike, Thanks for the tip! I have tried all (to date) fixes for this issue. I have even gone so far as to remove and re-install FSX+acceleration and try a flight with the default aircraft, IE C172, B737 and even the Trike! Even with absolutely no addons installed, I get a CTD within 15 NM of KSEA. All my flights south from CYVR have to be done VIA the TATOOSH VOR down the west coast of Oregon and California to arrive at KSFO. Even using FS9, I experience this exact issue. Instead of making MS Flight, maybe they sould have just revamped FSX and made it more stable, added multi core support and de bugged it. huh.png

Share this post


Link to post
Share on other sites
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
And you'll also be able to see the might Boeing 747 grazing the wild pastures... This mighty animal likes to gather around in medium sized group, for protection. Come mating season, you will see the big male 748 flaunting their 4 engines and massive tail to impress the much smaller 747SP females. Unfortunately, today's ever increasing fuel prices might one day bring this mighty beast to extinction. You can help them by donating $1 to the "save the 747 Jumbo" Wildlife Sanctuary. Or you could buy one today and take care of it in your back yard. All you need is 10 hectares of land and at least 10.000ft of runway so that this majestic beast can run wild, and you can adopt your for just $300 million today.

Share this post


Link to post
Share on other sites
Ryan, I've read what you've posted so far, and I absolutely disagree. I'm not disagreeing with the logic, I'm disagreeing that custom liveries play no part in the freezes. When I first bought the NGX, I flew the Delta -800WL.I got a freeze 1 out of every 3 flights, and ALWAYS right after exiting the runway at my destination. After hearing feedback, I switched to the house livery and I never had a single freeze since I made that switch. I've flown maybe 15-20 flights since I switched to the house livery. Not in any of those did I get a freeze. Tonight, I downloaded and installed a custom Delta livery also for the -800WL.As soon as I landed at my destination, and taxied off the runway, *BAM*...panel freeze. In my opinion there is absolutely no way it's a coincidence.
Curious... Is there any difference in the way you load the Delta skin, vs thePMDG? IE: when you run the Delta, do you load the PMDG, and then the Delta,or do you load the Delta first thing?I've never had a problem using the other liveries, but I always only choose oneversion no matter which one I choose. IE: my start up flight is the Lear 45,and when I run the 737 NGX I only choose the one I use. I never choose thePMDG version, and then switch to other livery.I'm wondering if maybe you might be loading the Delta in a slightly differentmanner than the PMDG? Say as in using a PMDG paint as the startupflight, and then switching to the Delta?I realize the results tend to back up what you say, but I'm still with Ryanas far as thinking there is no logical explanation for this. The texturesare all the same size. There should be no difference at all, with maybethe slight exception of possibly a change of equipment that might usemore memory. And even that would seem unlikely being as I've tried allthe various versions of equipment and never have had a problem.IE: different MCP, different standby instruments, etc..Anyway, this is very weird.. I've flown several different liveries andnever had a problem with any of them. I fly the Southwest versionmost of the time. But also have the Continental, United, Delta, andAmerican.. Never a problem with any of them.As a test, I would make sure to load each one in exactly the samemanner.And the best way to do that is use a startup flight with a default FSXplane, and then choose only one version of 737 NGX for each flight.Never "double dip" the loading by loading the house paint, and thenswitching to the Delta. Even that should not be a real problem, butit possibly could cause more memory to be used by the time you getthe 2nd one loaded. Just a theory anyway..

Share this post


Link to post
Share on other sites

If you believe that certain liveries are prone to CTD then maybe it's the ini file. Perhaps it's a combination of one or more of the variables that trigger the CTD at a certain point. Note that all of the House liveries do not have an ini file.

Share this post


Link to post
Share on other sites

I think that would make more sense than the textures themselves. But.. I think all the inifile does is select the equipment that usually matches what that company uses.Seems if that had a code bug, I would have seen it on mine by now.But, renaming the file, or moving it out of that folder would be a quick way to test.You would just have to manually set the equipment to match that company if youwanted everything to be the same.My theory was maybe they are loading the new paint, after first loading the PMDGpaint, which might possibly use more memory if it had to load twice as many texturesin a short period of time.I don't know how long it would take to flush the initial files from the memory.That's why I say to load a stock plane as the startup flight, and then load thepainted 737 NGX without loading the PMDG version. That would eliminate thatas a possible issue. But, trying it without the ini file might be worth a check too if that doesn't pan out.Myself, I've never had any trouble with one using an ini file, and the Southwestplane I fly most of the time uses one. I do use my own custom panel state though.. Also, I'm usually flying the Southwest plane, but I don't use the EFIS classic type setupmuch like many in the real world do.I prefer the PFD style display.. To me, it's less cluttered and easier to see everythingat a glance. :/Most utoob vids show the EFIS "classic" style display..But... I have seen one video of a Southwest plane that was using the PFD style.This led me to wonder if the Southwest pilots get to choose which they prefer.. ?Anyway, I use the PFD version, but I use the older backup instruments, as mostall of those seem to use. I've been using the Collins MCP.

Share this post


Link to post
Share on other sites

I'm pretty certain PMDG mentioned somewhere that it wasn't a good idea to load an NGX and then swap paints from anywhere but at the main menu when first loading the sim, probably exactly for this reason or for proper initialisation or something like that.

Share this post


Link to post
Share on other sites
... The idea that using the House livery doesn't make sense either - it's no different from any of the other liveries aside from what's actually painted on it. The House livery is actually larger than many of the airline ones even.
Actually, it does, as some liveries comes with certain company options preconfigured, I believe at least the American and the Delta livery comes with accurate company options preconfigured.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

×
×
  • Create New...