Shouldn't P3D have been optimized and rely better on the video card and CPU at the same time, compared to FSX? Then why all these problems with OOM and lower fps?

I have a feeling that the OOMs are because P3D pushes ESP to a new level graphically, and with the level of addons people are using (complex scenery + complex aircraft + complex weather + FTX Global + Vector etc), 32 bit is just not enough to cope. I guess FSX managed better for some because the base FSX does not push the VAS as high as base P3D.

 

In simpler terms,

 

P3D VAS = P3D base + xx addons

FSX VAS = FSX base + xx addons

 

As P3D base is (probably) a higher hit on VAS than FSX base, with the same addons the P3D total VAS will be higher.

 

My logic might be completely wrong but that's my theory.

Shouldn't P3D have been optimized and rely better on the video card and CPU at the same time, compared to FSX? Then why all these problems with OOM and lower fps?

Video cards and CPUs have no effect on the use of VAS whatsoever. Part of the reason this is an issue is that half the people worried about it have very little clue what the issue actually is.

 

The end issue is that you have 32 bits worth of 1s and 0s that you can actually put in a box. Once you fill that box with 1s and 0s, if you put one more 1 or 0 in it - boom! Doesn't matter if that box is in an apartment, a mansion, or Ferrari, if you overfill the box, it's gonna explode.

I've run into VAS issues with all the 32b platforms. My two cents on the subject is that I think P3D actually cleans up after itself as evidenced by the increase in VAS remaining after leaving my origin airport (an add-on of good to high quality).  My own impression is VAS issues are not worse in P3D than FSX but about the same.  The frustration level is higher with P3D because we are all hoping for, to continue Kyle's metaphor, a Ferrari with our Nissan budget.

Hi Kyle,

Your usual very apt description that well illustrates the 32-bit concept.

Cheers, Richard

Noticed no issues whatsoever with LR or ER in P3D 2.5. Also running ASN beta SP2. Right now on a way from RPLL to OMDB.

 

Although i haven't seen any crashes my Windows report says this:

 

Description

 

 

 

Faulting Application Path: D:\P3D\Prepar3D.exe

 

 

 

 

Problem signature

 

 

 

Problem Event Name: BEX

Application Name: Prepar3D.exe

Application Version: 2.5.12943.0

Application Timestamp: 54e39da6

Fault Module Name: PMDG_777X.dll_unloaded

Fault Module Version: 1.0.0.0

Fault Module Timestamp: 54d55b4b

Exception Offset: 0019ca80

Exception Code: c0000005

Exception Data: 00000008

OS Version: 6.3.9600.2.0.0.256.48

Locale ID: 1033

Additional Information 1: 9c8b

Additional Information 2: 9c8b06537576af0baff1c489813d846f

Additional Information 3: 310d

Additional Information 4: 310d9f830bae353231ee1eee97bcc077

 

 

 

 

Extra information about the problem

 

 

 

Bucket ID: 58b785abd45f189b8309721e8f2c27b0 (81815290439)

Any ideas? Thanks!

 

 

Problem Event Name: BEX

 

Buffer overflow error, a programmers nightmare to track down.  More help on google, but last time i ran into this creature I never figured out the cause.

well both errors occured at the same time above BEX and the APPCRASH. Though i don't recall P3D crashing with the 777 midflight session or upon exiting, which the later usually happens with FSX.

 

Description

 

 

 

Faulting Application Path: D:\P3D\Prepar3D.exe

 

 

 

 

Problem signature

 

 

 

Problem Event Name: APPCRASH

Application Name: Prepar3D.exe

Application Version: 2.5.12943.0

Application Timestamp: 54e39da6

Fault Module Name: PMDG_777X.dll_unloaded

Fault Module Version: 1.0.0.0

Fault Module Timestamp: 54d55b4b

Exception Code: c000041d

Exception Offset: 0019ca80

OS Version: 6.3.9600.2.0.0.256.48

Locale ID: 1033

Additional Information 1: 4db5

Additional Information 2: 4db5d0172c9a30cda7618711bf071dec

Additional Information 3: f89b

Additional Information 4: f89b132779d87413b66ce0936c7a45d2

 

 

 

 

Extra information about the problem

 

 

 

Bucket ID: fe3503a2d734e1e0e078995e9ff3852d (73891722042)

Ivan, you have not experienced the errors that the event viewer is reporting? Do the date/time for the errors correspond to your session?  Odd.

Ivan, you have not experienced the errors that the event viewer is reporting? Do the date/time for the errors correspond to your session?  Odd.

Yeah, that was two day ago, on Sunday, 12:15 PM, P3D was running fine, no crashes or OOMs. I saw these error reports by accident, because i had the FSX crash LOL upon exiting with 777.

Last night though, on my flight from Manilla to Dubai I had an OOM on the  final approach to Dubai. I can't blame my P3D settings, 'cause they are all medium set, or the 777, what contributed to an OOM is me selecting all the sounds of 777 to be loaded. I will check later today again without the preloaded sounds and report.

 

Good morning from cold and sunny Croatia!

You are going to get about 200-300mb if you set your PMDG FMC sounds to "selective" and if you deactivate RAAS in the xml file you will get another 300mb additionally.

You are going to get about 200-300mb if you set your PMDG FMC sounds to "selective" and if you deactivate RAAS in the xml file you will get another 300mb additionally.

I've read that before about RAAS coudl you copy and paste just how to do that again pls.

 

Not heard about the Sounds one before again can you give more info on that?

Sounds

http://forum.aerosoft.com/index.php?/topic/84776-vas-egll/#entry607424

 

 

 

RAAS

Just like it has to be done with the FSX

http://forum.avsim.net/topic/420821-how-can-raas-be-permanently-disabled/#entry2795866