VAS use is horrible in the 777.  Loading up EGLL V3 and the PMDG 777 i have about 1.3Gb left.  Try lowering your LOD, mine is set at 3.5, if you have REX use the lowest quality clouds, dial back the cloud layers, maximum of 3, turn down the AI traffic around 15%, turn off any road / boat traffic.  As suggested above turn off FTX.

Ian,

 

Thanks for the support. Yeah, I start the 777 with something less than 1.7 GB of VAS and it degrades rapidly along the flight. My REX clouds are already of low quality and the AI traffic 5%, when not in VATSIM.

 

I won't turn off FTX - more than 50% of my library entries. Sincerely, between the 777 and FTX, I stay with FTX.

 

FSX is an expensive hobby for me, as golf is for others, and keeps one side of my life bearable.

 

Best regards

 

 

FSX is an expensive hobby for me, as golf is for others, and keeps one side of my life bearable.

 

I hear you Heron, it's not the fault of PMDG, truth is we need a new simulator able to make use of the latest computers. It's heart breaking to have a 8 year old sim that doesn't understand SLI or large memory amounts.  Nothing we can do for now.

Not for me. It's stable and smooth so far, with ORBX FTX Global, and the PMDG 777 200 and 300, RealAirs, Carenado B1900d, Majestic Q400.

 

I also use it with Aerowinx PSX - again smoother and CTD-free compared to my previous experience with FSX Gold ( GFWL install ).

 

So far, none of the P3D versions I tried gave me the same stutter-free experience, and I had problems with P3D as a visuals generator for PSX, so, at least for me, FSX-SE was a blessing :-)

 

In my case another factor that probably contributes to the additional smoothness, and better graphics quality, is also the use of DX10 mode, through Steve's Fixer.

Monteiro,

 

Tudo bem?

 

Thanks for your reply. It's great to know someone can fly the 777 within FTX environment. Let separate things here. I fly any aircraft smoothly along all my commercial sceneries, textures and weather. I also use DX10 Steve Fixer, which gives me outstanding effects and shadows along the cockpits.

 

All I wanted to do was just finish a 777 flight after n hours of flight.

 

Grande abraço,

Best Regards,

Well, really not my experience, so, not a joke but rather a friendly advice... even if not understood as such by some forum members...

I tend not to tell people to do exactly what I wouldn't do, as I tend to give my advice based on my own experience, looking forward to see them prove useful. I believe that's the spirit around here ?

J.,

 

That's because you do not fly the PMDG 777 in long haul flight that last more than 4 hours.  If you do, you will experience the terrain and g3d crash with FSX-SE.

I have found that if you use the FSX-SE and use only the recommended tweeks that they offer, you will have a very stable platform, minus the Orbix scenary.  I do not understand the reason to have micro detailed terrain and such whne you are at 30,000 feet, unless you would like to look at the details as you crash into a mountain side!  Airports with detail, got it, but Bucks Creek Family Park along your flight path, I just do not get.

 

 

All I wanted to do was just finish a 777 flight after n hours of flight.

If you do, then turn off some sceneries that are not used then.  The ORBX stuffs are for below 10000 FT flights anyway.  There is only one way to deal with OOM and that is to lower the VAS usage.  When you don't fly the 777, turn the sceneries back on.  FSX is a 32bit application, and if you don't want to reduce VAS, then there is nothing much that can be done.  You did ask for a solution, did you not?  I am afraid that there is no fixes, just compromises.  May be one day when P3Dv2 is 64 bit, then you may have your wish, but why deny the flight just because all sceneries have to be on all the time?

I did not mean your advice in particular was a joke. Far from it. You're indeed being helpful and constructive, and it is applauded.

 

What I meant as from my own experiences with repeated CTDs caused by the infernal terrain.dll, which others have also experienced, FSX-SE was a joke to me as it currently stands.

 

Comprehendo?

 

Compreendido :-)

 

I hope you can sort it out. My install is rather easy to manage because I have so few add-ons installed, no AI traffic, only one scenery ( Aerosoft Madeira )...

 

Thx for the post vc10!

Monteiro,

 

Tudo bem?

 

Thanks for your reply. It's great to know someone can fly the 777 within FTX environment. Let separate things here. I fly any aircraft smoothly along all my commercial sceneries, textures and weather. I also use DX10 Steve Fixer, which gives me outstanding effects and shadows along the cockpits.

 

All I wanted to do was just finish a 777 flight after n hours of flight.

 

Grande abraço,

Best Regards,

 

Abraço Heron :-)  So, you are also experiencing those OOMs :-(  See ahead please...

 

J.,

 

That's because you do not fly the PMDG 777 in long haul flight that last more than 4 hours.  If you do, you will experience the terrain and g3d crash with FSX-SE.

 

Well, one of my long haul flights (FQMA - LPPT) must have actually lasted more than 4hrs, even using PMDG's cruise Control. 

 

But tonight ( against my energy saving principles, meaning I'll have to spend the next night at the light of some candles ... ) I will program a long haul, KSFO - LPPT flight. I will leave it there for the whole night, in the morning as I wake up I will check how it's going and report back... The flight will continue after I leave to work - is there a pause at TD option in the 777 ? 

 

 

But tonight ( against my energy saving principles, meaning I'll have to spend the next night at the light of some candles ... ) I will program a long haul, KSFO - LPPT flight. I will leave it there for the whole night, in the morning as I wake up I will check how it's going and report back... The flight will continue after I leave to work - is there a pause at TD option in the 777 ? 

Monteiro,

 

I think yes, there is a pause option before T/D somewhere I can't remember. Sorry.

 

But I think the problem is not fly the T7 2 or 12 hours. The problem is within the T7 approach or final. All my OOMs were in these phases (FPSUIPC VAS death alarm). Rarely, I could land and taxi to the gate. Most times things ended on final.

 

During the flight, it seems the VAS is slowly consumed by clouds variation, storms and even switching views to go outside the plane I heard is a real VAS killer. When approaching, normally over a city, the proximity of terrain triggers autogen features, eating up the remaining VAS. Loading an eyecandy addon destiny airport should do the coup de grace on VAS. Hey, this is just my theory.

 

Vu Pham,

 

I told ya, I do turn off any airport scenery other than depart-arrival.

 

Best regards,

Cannot fathom this FSX-SE at all.

 

Set up as per the Avsim Basic FX tweak. And where previously I was getting a pretty high FPS standard default scenery, all of a sudden flying the T7 EBBR-CYYZ, I am now getting FPS of 1-3.

 

Sublime to silly!

Rick,

 

from memory I believe the tweak guide does not include the 

 

[JOBSCHEDULER]
AffinityMask=<value based on processor and HT state, 14 in my case with an i5 without hyper-threading...>

Obrigado o Senhor

 

That was one of the first things I amended in the cfg.

 

Going to re-boot and re-try the flight again, and report back later.

 

EDIT: Now, I am really baffled. Did nothing other than a re-boot, re-loaded the Saved Flight and now my FPS are up to 30s-40s!! Eh? All I did was disable the Auto-Save from FSUPIC v4 Registered.

 

Will report on any G3d.dll or terrrain.dll CTDs when I approach Canada's Northern territories. Fingers crossed.

What is FSX-SE??? I use pure FSX + Acceleration Pack.

Most of the recent discussions are in regard to issues with FSX-SE (the steam edition of FSX that was recently released). My apologies for indicating FSX-SE in my comments.

 

You have the exact same system as mine (same hardware anyway). I use the fsx and NVidia settings shown in the AVSIM FSX Configuration guide. I recently removed my overclock as it has been recently giving me issues but I still have just as many fps as when I had it overclocked to 4.2GHz. Still I run out of VAS about 2 hours into a flight. I could go much, much further if I stayed at FL 280 but all of my flights are around 1-2 hours. I have about 2GB's of VAS as I near the approach at my destination but, as I turn into the approach VAS is running low and I'm suddenly down to less than 1GB of VAS left. By the time I touch down, my VAS is down to 300 MB's. Soon after landing, the sim freezes or CTD's with an Out-of-Memory message. I also use the FSUIPC utility to monitor my VAS and, after the crash, I can retrieve the FSUIPC.log and review the VAS usage. What was taking me down was my photoscenery as it was loading throughout the flight and in States I wasn't even near. I now load just the HiRes Chicago MegaSceneryEarth where I take off and the HiRes Virginia MSE scenery. The space in between is covered by GEX. That allows me to have 500 plus MB's at landing at KIAD and taxiing to the gate. I even see some improvements in VAS after landing. I also downloaded and installed UTX USA 2.0. I ran the same flight between Chicago and KIAD and had a crash just as if I had a lot of photoscenery installed. Disabled UTX, no problems. Right now I'm fiddling with those settings as some settings use a lot of resources. I also should state that I use ASN for weather and ProATC-X so the co-pilot can get me to my destination safely. I also use the PMDG 777-300ER as my test vehicle. I have saved several of my FSUIPC logs and renamed them based on what was loaded during the flight. I then analyze the VAS usage and then look for ways to make it better. It's the only thing you can do too as there is no magic bullet or tweak that will change VAS usage. Only if you have a 64 bit application will you have almost unlimited VAS usage (8 terabytes by default). FSX and FSX-SE will never be converted to 64 bit. That will be a total impossibility. X-Plane has already been converted and we don't hear too much about their crashes. It has been rumored that Lockheed Martin will convert P3D to 64 bit but that product is totally based on the FSX engine too and there is some question whether they can do this without changing the code (Microsoft will not allow anyone to change the code).

 

When I get a crash in FSX (and I do occasionally), I know exactly what caused it. In some cases it has been my unstable overclock but mostly it is what I have loaded and in some cases, my configurations. For instance, I fly mainly with the LOD_Radius at 6.5 which is above the maximum default of 4.5. I also use 4096 with the Texture_Max_Load parameter. I also own REX4 Texture Direct. If you changed the texture resolution settings in this program to also show 4096 and texture compression for low, high/mid level clouds to 32 bit, you will have problems as these settings take up a massive amount of resources. That's what I did when I first purchased the product and I crashed almost immediately. I have mine set at DXT 5 and 32 bit for wave animation (which I'm going to remove as I don't use REX for wave animations). For my texture resolutions, I put them at 1024 except that I raised the low level clouds to 2048. I let the setting in my FSX.cfg - Texture_Max_Load=4096 handle that load. But, if those settings are high too, then your computer will crash no matter how low your settings are in the FSX.cfg. Certainly, depending on what's loaded during a flight and the flight duration, you may not have a crash for some time but it will eventually crash.

 

I heard a lot of people are having problems with FTX Global, Vector, and OpenLC Europe. Those programs are basically the same as my GEX and UTX V2.0. Now I can fly okay with just GEX loaded but not with UTX too.

 

Lastly, there are many reasons for unexplained crashes. I mentioned a bad overclock can do it (without getting a BSOD). Hard to detect unless you do see a BSOD but, if your overclock is unstable, FSX will crash with unexplained reasons. Might even freeze up too. Best to remove the overclock and bring back some system stability. This is why it makes CTD's so frustrating. So many reasons for it to happen. The power supply in your computer will cause crashes too if there is not enough power at the time FSX needs a lot of resources. I have a 750 Watt PSU and so far that has not been a problem but there are many who have SLI setups and many monitors and maybe their PSU is not powerful to run all of those operations. The code in FSX just does not take advantage of the latest high powered CPU's and memory. So, maybe it is best to simply quit this flight simulation hobby and move on to something else like Truck or Train Simulation where the code takes advantage of the power of our computer system. For me I live with the occasional crashes. They are getting fewer and fewer as I understand how I can raise my sliders and set other configurations for a particular flight plan. I don't think I can use the same configuration for every situation/flight plan. Think this is one reason why Microsoft set up a way to save fsx.cfg settings for various situations. Hopefully you can investigate and find a solution like I did.

 

Best regards,

 

 

I also use the FSUIPC utility to monitor my VAS and, after the crash, I can retrieve the FSUIPC.log and review the VAS usage.

Jim

 

I too have the registered latest FSUIPC. Where do I find this in FSUIPC? Looked at all the tabs, cannot see anything related to VAS monitoring. Maybe I'm looking in the wrong place?

 

Thanks.

Jim

 

I too have the registered latest FSUIPC. Where do I find this in FSUIPC? Looked at all the tabs, cannot see anything related to VAS monitoring. Maybe I'm looking in the wrong place?

 

Thanks.

Hi Rick,

 

Page 3 of the AVSIM CTD Guide (located at the right side of this forum under Hot Spots) has the guidance for setting up the registered or unregistered version.

 

Best regards,

Thanks, Jim.

 

Still managing a round in your wintry weather?