why when approaching at KORS in P3D my computer always crashes after a fall of FPS to 2 or 3

 

In FSX, same sccenery, all is fine, full stop landing at 25 fps

 

 

I tried deactivating all addons except ORBX and still it crashes on approach, right on top of Sucia Islands

I'm also having problems with some of the Orbx - KAPT / Jackson Hole. Orbx is going to release an update to make all of their scenery compatible with v1.4 - All of my Orbx scenery worked

fine in v1.3

cthiggin

makes sense

It worked fine in FSX with same addons still active

 

So it has to be a mismatch up to P3D

do you guys have the latest fsuipc.dll versin installed ? Maybe those crashes are g3d.dll related !? Have you checked it in the event viewer ?

 

Carsten

I have a payed version, 4.85, which is further ahead than what is available on the site, which is only 4.84

 

Should I do a reinstall to the earlier 4.84?

 

and.... How do I use the event viewer?

Just download the latest dll from his forum.

 

http://forum.simflight.com/topic/66139-updated-modules/

 

Sent from my HTC One X using Tapatalk 2

OK I installed that latest fsuip listed in there

 

But it still goes from a fps of 2 to 22 then 3 then 17 the 3,,,, on and on

until it freezes up

Does the scenery get huge artifacts before completely freezing? If so, it sounds that you are finished with your available VAS and you just nearing OOM. That should't crash the whole computer, though.

not the hole computer

Just P3D

which should not crash by OOM at that time, it does seem to stall and acquire a Gig of RAM usage, then freezes, eventually crashing.

I have 16G RAM and 2G VRAM

It gets to 2.8G P3D usage (not total) then while gasping for air (fps), suddenly seems to jump to 3.6G of P3D usage (7.8G total) which seems to be my OOM for P3D

Actually it only did the memory jump once so far

 

This behavior only occurs on final; at KORS

I get other OOMs due to the 32-bit limitation but I am aware of its climb as I monitor idividual app and process usages using a freeware called Sysinternals process explorer app

 

WE NEED A 64-bit sim

OK, now I don't quite understand (may be because I'm not natively english). So, you say that your P3D crashes at the point where your P3D process has 3.6GB of acutal memory usage? I'd bet that if it goes there, your VAS is finished and you suffer OOM. Why? Because in 4GB VAS you need to have all your modules that your P3D process needs. Kernel, soundcard, controllers and so on don't run without memory and thus mapping to same VAS. I go down almost precisely when process gets to 3.2GB and at that point VAS is the 4GB.

I often exceed 8G total usage of which

FSX would go to 4G itself

So I monitor it and if it gets too close I either save the situation for a restart or I cut back on scenery if I am on final, which is when it usually happens, as I like to fly into well refined airports

FSX would go to 4G itself

Either VAS or physical, you are out of memory, dude.

 

In fact I see it impossible, that FSX process (or P3D) would go to 4GB physical and still work, because there is no room for the OS anymore. I'm not saying that you are lying, but if that is what a) task manager shows to you in the moment of crash or b ) that is the amount of VAS from some process explorer, then it is 100% sure that you are run out of VAS.

I mentionned earlier that I have 16G of RAM

I mentionned earlier that I have 16G of RAM

It doesn't matter. As P3D and FSX are 32-bit applications, they can't use more than 4GB address space for physical RAM or virtual address space and the one that matters is actually the last one.

In fact I see it impossible, that FSX process (or P3D) would go to 4GB physical and still work, because there is no room for the OS anymore....

 

THAT is what made me say I had 16G