either some of you guys are lying about setting

 

Come off it! .... what a daft statement. 

Come off it! .... what a daft statement.

alot of guys here lie about settings and fps and VAS. These are the ones with a bias and you can see it in their posts when anyone says something negative about p3d. When I see people saying they complete a 10+ hr flight from say FlyTampa dubai to fsdt JFK with all these addons in the pmdg 777 with these high settings, I just smh.

I never CTD or OOM in P3D. I have plenty of ORBX addons running (FTX Global, Vector, OpenLC Europe, FS Gobal FTX) with other addons like ASN and Aivlasoft EFB. All of this while flying a PMDG 777 or 737NGX. On Windows 8.1

 

So although I don't doubt the OP has a real issue. it's related to his setup/config. There is a balance to strike between visual candy and performance and the OP  hasn't reach that balance yet.

It sounds ridiculous but its starting to seem like your hardware have an impact on VAS. On my transition to P3D I have encountered an absurdly high VAS usage, making the game completely impossible to play. I too monitor VAS with Process Explorer and now I'm going to share some images and settings for you, and you can decide for yourself. 

 

The worst airport I can power up is definitely FlyTampa Copenhagen. In FSX:Steam, I could fire up the NGX with FS2crew, GSX, ASN, FTX Global+Vector+OpenLC with relatively high settings (LOD radius 5.5 and autogen density set to very dense) and start with approximately 2800-2900 MB of VAS used already. No worries, since it always dropped on departure (maybe because of the DX10 fixer or the improvements in the Steam edition. In addition, I didnt back down any Vector settings at all. All textures were 1024 however.

 

Now, in P3D, I start up with 3400 MB with these nerfed settings posted underneath:

 

 

 

 

 

 

 

 

And this is of course with LOD radius of 4.5 + 1024 textures ONLY.

Improved VAS usage??? Well, you do you explain this? I've wasted weeks on this now and I'm very close to switching back to FSX:Steam. P3D is unflyable because of the horrendous VAS usage, even with low settings like this  :(  :(  :(

It sounds ridiculous but its starting to seem like your hardware have an impact on VAS. On my transition to P3D I have encountered an absurdly high VAS usage, making the game completely impossible to play. I too monitor VAS with Process Explorer and now I'm going to share some images and settings for you, and you can decide for yourself. 

 

The worst airport I can power up is definitely FlyTampa Copenhagen. In FSX:Steam, I could fire up the NGX with FS2crew, GSX, ASN, FTX Global+Vector+OpenLC with relatively high settings (LOD radius 5.5 and autogen density set to very dense) and start with approximately 2800-2900 MB of VAS used already. No worries, since it always dropped on departure (maybe because of the DX10 fixer or the improvements in the Steam edition. In addition, I didnt back down any Vector settings at all. All textures were 1024 however.

 

Now, in P3D, I start up with 3400 MB with these nerfed settings posted underneath:

 

 

 

 

 

 

 

 

And this is of course with LOD radius of 4.5 + 1024 textures ONLY.

Improved VAS usage??? Well, you do you explain this? I've wasted weeks on this now and I'm very close to switching back to FSX:Steam. P3D is unflyable because of the horrendous VAS usage, even with low settings like this  :(  :(  :(

I still have fsx steam installed. Some flights I can complete in p3d with the 777, but it all depends on the airports I'm using. I also get crazy micro stutters using the ngx, but every other plane is smooth. For right now I use p3d to do vfr flying around orbx area where it really shines. 

 

I have not idea how people are saying vas was improved. How can it be if we have to start the flight and set everything up, then save and restart the flight from the saved file. I never have to do that with fsx se

I still have fsx steam installed. Some flights I can complete in p3d with the 777, but it all depends on the airports I'm using. I also get crazy micro stutters using the ngx, but every other plane is smooth. For right now I use p3d to do vfr flying around orbx area where it really shines. 

 

I have not idea how people are saying vas was improved. How can it be if we have to start the flight and set everything up, then save and restart the flight from the saved file. I never have to do that with fsx se

 

If you stop focusing on the problem you are having one second and try to focus on a solution. The rest of the community doesn't have this problem. Can you please start by posting your full system spec and your prepar3d.cfg.

If you stop focusing on the problem you are having one second and try to focus on a solution. The rest of the community doesn't have this problem. Can you please start by posting your full system spec and your prepar3d.cfg.

what problem are you referring to? I'm not the only one having stutters and oom problems. I've already given up trying to fix p3d. I rather spend my time flying. I use fsx for the heavies and p3d when I want to crank up the settings and fly low and slow.

 

My system is an i7 4770K @ 4.7ghz, GTX 970 and 16gb ram. Moderate settings when running pmdg planes. Small GA planes and I bump up autogen to very dense. LOD at medium

Micro stutter is cause often by overclock cpu and pinned core. I got a similar setup as yours and I have no such issue, all of it @ 1440p while I have other apps running on additional screen. I am not denying you have a problem, I am denying your claims that P3D is not optimized or worst in vas than FSX.

either some of you guys are lying about setting or something else is going on. P3d does not release VAS. I monitor my VAS with process Explorer and I watch my VAS increase or stay the same.

No lies whatsoever, I also watch my VAS with process explorer and I do see memory usage going up and then coming down as the airport fades into the distance.  Something else is eating your vas.  I do use FT CYUL and with PMDG777 starting at the gate memory is at 2.4 GB as soon as I at cruise it dropped to 2 GB, went up to 2.5 GB and landed at 2.6 GB.  Like I said I had no problem.  Believe or not is up to you, I have no interest in talking up P3D I just reported what I have.  My P3D looks better than FSX ever was, flying smooth and no issues.  For some others plenty of problems, I have no idea why.