Maybe somebody can shed some light on this fault code I got.  Is this from an OOM or something else?

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ntdll.dll, version: 6.1.7601.18205, time stamp: 0x51db9710

Exception code: 0xc0000005

Fault offset: 0x0002e41b

Faulting process id: 0x2338

Faulting application start time: 0x01ceaa3ad6a49b16

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: 6292f9be-1633-11e3-87a6-180373425176

This is not good, if you take a look at PMDG777 forums, there is a thread "PMDG 777 issue tracking thread". OOM errors are classified like "Not real issues - please don't repost these". 

 

OOM errors and VAS are not new for me. I have pretty high graphics settings but i never had OOM with other planes. I read through 777 manuals, and there are only 2 PMDG VAS usage reducing recommendations left for me, - autogen and water. I don't agree, and i don't want to do this. If i reduce water, i'll get flashes for example. I know there are some option to reduce VAS greatly, but i am too happy with my current settings, and i finally have a very smooth and good looking SIM.

There should be something to do with 777 eye candy in order to reduce VAS - lower textures or something like this. Maybe option to use virtual cockpit only if that would be a great improvement and nothing else can't be done. But 777 VAS usage is not a false issue. This was important to watch, 777 is a long hauler. 

'B247NG', on 05 Sept 2013 - 06:55 AM, said:

I don't know what happened last night with FSDT CYVR, if happens again i will probably avoid that airport

 

Again, nothing to do with CYVR. Its all cummulative to what you load.

 

 

Heres some tests guys. The mileage varies depending on what your FSX settings are but pics below are using LOD 5.5 with 1024 clouds. Sliders are all maxed except mesh at 5m and my AI setting is at 70%. I also do have FTXG. I restarted FSX for each pic. AG is set to very dense

 

This is the Trike and Makoua Congo. Essentially in the middle of nowhere. No other airports to load or AI.

 

 

777 in Makoua Congo. VAS goes from 987mb to 1.7GB. Around 700mb increase. Just as Ryan says.

 

 

Trike at CYVR. Using CYVR because everyone blames it as the cause. 2.1GB. This is NOT mean that CYVR is 1.1 GB given that the trike in Makoua is 987mb. Its because Orbx PNW is loading as well as a heavier overcast, plus surrounding cities, and AI. Still 2GB is great.

 

 

777 in CYVR but with no Orbx PNW loaded

 

 

777 CYVR with everything loaded.

 

 

The same principles apply to wherever you go. Its no one airport, scenery or aircraft. Its the combination of them all and who got loaded first part of the VAS and the last part.

Well unfortunately I use all my addons and I shouldn't have to disable stuff to fly a flight.  Never had to before.  Like I said I'll check out that LOD radius thing-a-ma-jig.

 

 

 

You mean uncheck areas you won't be flying through?  I have a gazillion sceneries and to do this before each flight is ridiculous.  

 

Ridiculous or not, it works...

Photoscenery is he worst. If you're not flying over the photoscenery, definitely disable it. No messing with the scenery config. Use the scenery library in fsx or use a program called scenery config editor to enable and disable sceneries before loading fsx

 

this solved my OOM problems with the NGX and the MD11...

Try this - seems to work on my system.

 

In FSX.cfg file, find [sCENERY]

 

It might already be present, but if not add:

 

DAWN_DUSK_SMOOTHING=0

 

It reduced memory usage by 400 Mb and frame rate didn't drop because it was dawn/dusk in the sim.

 

The situation that caused 8 FPS yesterday didn't occur and I maintained 30+ FPS all the way to touchdown. In total over 3 hours flying testing this.

 

Best regards,

Robin.

It happened today with Fly Tampa airports too, so it's not about FSDT CYVR only. It usually happens on 5-6h flights.

.......
 

I think PMDG will probably do something here to reduce VAS usage, NGX was not perfect before many hotfixes and service packs, and this usually happens with all complex simulations, i am patient...

 

That's a scenery issue then. There are two sources of memory leaks:

 

* Empty texture folders

* Landclass files in a scenery folder with a corresponding texture folder

 

Fixes:

 

* Delete all empty texture folders

* Move landclass files to a seperate scenery folder with NO corresponding texture folder.

 

Best regards,

Robin.

LOL! Looks are deceiving my friend.

 

Want proof CPUs mis-behave when overclocked? It is used to conduct cryptanalysis. By overclocking the processor you can make it do things it shouldn't. If an overclock was as simple as you say, there wouldn't be any difference over a normal processor when attacking a system this way.

 

I could go on for hours how there are MULTIPLE clock sources within the processor, and that they do not scale linearly with the clock speed you play with, if they change at all, leading to mis-timings within the processor itself, and odd things happening even though the system may appear to be running normally.

 

Sir, I know what I'm talking about when I say overclocking is bad for your health.

 

Best regards,

Robin.

 

Good one, it almost sounded like you were serious ... :rolleyes:

Try this - seems to work on my system.

 

In FSX.cfg file, find [sCENERY]

 

It might already be present, but if not add:

 

DAWN_DUSK_SMOOTHING=0

 

It reduced memory usage by 400 Mb and frame rate didn't drop because it was dawn/dusk in the sim.

 

The situation that caused 8 FPS yesterday didn't occur and I maintained 30+ FPS all the way to touchdown. In total over 3 hours flying testing this.

 

Best regards,

Robin.

 

That's a scenery issue then. There are two sources of memory leaks:

 

* Empty texture folders

* Landclass files in a scenery folder with a corresponding texture folder

 

Fixes:

 

* Delete all empty texture folders

* Move landclass files to a seperate scenery folder with NO corresponding texture folder.

 

Best regards,

Robin.

Interesting, are there any (visual) downsides of this tweak?

Not that I noticed.

 

Best regards,

Robin.

Good one, it almost sounded like you were serious ... :rolleyes:

 

I am. :mellow:

 

Challenge: prove me wrong.

 

Best regards,

Robin.

That's a scenery issue then. There are two sources of memory leaks:

 

* Empty texture folders

* Landclass files in a scenery folder with a corresponding texture folder

 

Fixes:

 

* Delete all empty texture folders

* Move landclass files to a seperate scenery folder with NO corresponding texture folder.

 

No. If i had some of this issues, it would happen with other planes too. It happens with 777 only - no issues with NGX, MD11, Concorde X and Maddog.

 

P.S. - it happens with other sceneries too if flight is about 5-6h. 777 uses VAS more then other addon planes. I don't have scenery issues, i don't have empty texture folders, i know how to set and mantain my PC and FSX. All unused sceneries are disabled, 1024 DXT optimized REX clouds, no AI, no road traffic etc, etc...

Quote:

 

There is also a disturbing trend of Intel users having problems. Many are seriously overclocking their processors which is not good anyway, but after all that they still complain of 10 FPS. I suggest the processors are not liking the overclock.

 

 

This is a completely baseless statement. I've been running overclocked for a year now and never once had a BSOD or crash related to overclocking.  Ever.  With the right cooling, overclocking is not the cause of any of these problems here.

I just posted this answer for a similar question so I am going to just paste it here too and hope it helps.

 

I got the same stuff right after I landed at Dubai with my brand new 777. Make sure your scenery order is set in order which really helped me get rid of OOM issues. My order is something this (starting from top):

 

1. Mega Airports

2. Complex airports then others

3. VFR sceneries

4. Photosceneries

 

Try it out. Good luck.

Try this - seems to work on my system.

 

In FSX.cfg file, find [sCENERY]

 

It might already be present, but if not add:

 

DAWN_DUSK_SMOOTHING=0

 

 

Wow dunno how you figured that one out but seems to work haha.  I haven't had any OOM problems yet but always good to have a bit of overhead.  Previously parked at OMDB with the 777 running was seeing about 2.6gb used.  Down to 2.28 with that one tweak.

 

Sitting on the ground now an hour before dawn to watch the transition and make sure nothing looks weird.  Thanks!

Wow dunno how you figured that one out but seems to work haha. I haven't had any OOM problems yet but always good to have a bit of overhead. Previously parked at OMDB with the 777 running was seeing about 2.6gb used. Down to 2.28 with that one tweak.

 

Sitting on the ground now an hour before dawn to watch the transition and make sure nothing looks weird. Thanks!

What is the visual effect in fsx when setting this to 0?

 

Sent from Samsung Galaxy Note 2

 

 

Don't know yet, that's why I'm parked watching the sun rise

Interesting comment, Robin. I make most of my VFR flights at dawn, because (IMO) that is when FSX looks its best. I will try that DAWN_DUSK_SMOOTHING=0 trick, and see what happens.