I think Clifton (LM) meant to say he has NOT been able to replicate the issue

 

That is really bad news. That basically means that we can expect no fix from LM, doesn't it? Kind of sad as v3 had been so impressive when it comes to VAS management. Now all those problems again...

 

 

That basically means that we can expect no fix from LM, doesn't it? Kind of sad as v3 had been so impressive when it comes to VAS management.

 

You shouldn't jump to that conclusion ... memory issues can come from just about anything, one "possible" issue that can't be replicated doesn't mean other issues can't be found and resolved ... LM ARE working on trying to find the issue.  Could be anything from adding VR support to Multi-Channel to you name it ... the most likely suspects are obviously changes from version 3.2 to 3.3 to 3.4.  The SimConnect claim by 3rd party dev suggests the issue was present in P3D V2 ... so obviously it probably NOT something that is causing excessive VAS.

 

Cheers, Rob.

You shouldn't jump to that conclusion ... memory issues can come from just about anything, one "possible" issue that can't be replicated doesn't mean other issues can't be found and resolved ... LM ARE working on trying to find the issue.  Could be anything from adding VR support to Multi-Channel to you name it ... the most likely suspects are obviously changes from version 3.2 to 3.3 to 3.4.  The SimConnect claim by 3rd party dev suggests the issue was present in P3D V2 ... so obviously it probably NOT something that is causing excessive VAS.

 

Cheers, Rob.

 

Ok. Good to hear that they are still looking for the cause of the issue. So let's keep fingers crossed...

 The SimConnect claim by 3rd party dev suggests the issue was present in P3D V2 ... so obviously it probably NOT something that is causing excessive VAS.

 

I don't anyone has  proposed that the SimConnect exception issue has anything to do with lost VAS. To date, only the developers of SODE and TacPack have demonstrated that the exceptions appear to propagate among SimConnect addons. And that's only an issue if an addon is trapping exceptions of a certain kind and expecting that those exceptions were generated by that same addon.  It's a problem if on addon "broadcasts" exceptions to every other addon, but until LM can confirm that, it's not really of any interest to the average user.

 

EDIT:

 

One minor correction, FSDreamteam has also reported this issue:

 

http://www.fsdreamteam.com/forum/index.php/topic,13668.msg105608.html#msg105608

 

and also claims that it could have something to do with OOMs:

 

http://www.fsdreamteam.com/forum/index.php/topic,14441.msg106274.html#msg106274

 

I'm just quoting here, so I have no idea whether that is true or not.

Guys, I know I don't write too much on the forums, but I read almost daily. I am sorry for the VAS issues many are seeing. I am personally set with  P3D V 3.3. Having said, this may I suggest the following:

 

... I believe P3D is a great Sim. However, don't launch yourself and install every (every) update that comes your way. (Wait a few weeks to see if there's any problems). And if you do, then before doing so, do what I have done. I have kept a back-up of every previous versions in case something major comes up (major as in a major problem). And, please don't just update. read the list of new "updates" and see if you really (really) need the updates.

 

Yes, someone might argue; 'But the updates are important cause P3D said, they are."  Well, could be true. But... relax...wait...see...read.. and wait.. then, proceed.

 

cheers,

 

Joe

Guys, I know I don't write too much on the forums, but I read almost daily. I am sorry for the VAS issues many are seeing. I am personally set with  P3D V 3.3. Having said, this may I suggest the following:

 

... I believe P3D is a great Sim. However, don't launch yourself and install every (every) update that comes your way. (Wait a few weeks to see if there's any problems). And if you do, then before doing so, do what I have done. I have kept a back-up of every previous versions in case something major comes up (major as in a major problem). And, please don't just update. read the list of new "updates" and see if you really (really) need the updates.

 

Yes, someone might argue; 'But the updates are important cause P3D said, they are."  Well, could be true. But... relax...wait...see...read.. and wait.. then, proceed.

 

cheers,

 

Joe

 

Joe, you know what will happen, when 3.5 comes out, people will install it 5 microseconds after it is available. Then there will be a deluge of posts telling us about the add ons that no longer work, the crashes, the lockups, the poor FPS, the VAS issues,  where can I get a copy of 3.4, etc. etc. It happens very time. Go figure.... :wink:

 

 

's a problem if on addon "broadcasts" exceptions to every other addon

 

Exception processing is typically a "global" bubble up event ... but what I think I'm hearing is that the developers have no way of determining if the exception is theirs or someone else?  I'd be surprised if exceptions can't be identified by source (most exception should have a stack trace) ... but if that's not the case, I can see how that would be a problem.

 

I ran some additional VAS testing on build 14800 today, not sure how useful the data is, but here are my results:

 

 

Here is my VAS test procedure at static location:

 

 

Here is my very short FPS test flight:

 

 

Link to Graphics settings files for VAS and FPS test:

https://drive.google.com/file/d/0Bw0Q-fAfEZwybTJ2X0hxcDBWUzg/view?usp=sharing

 

Link to Flight files:

https://drive.google.com/file/d/0Bw0Q-fAfEZwyN2ZZXy1Sc3U2RG8/view?usp=sharing

 

Link to FRAPS timeframe files:

https://drive.google.com/file/d/0Bw0Q-fAfEZwydWVSV1BmYzFvTGc/view?usp=sharing

 

Points of interest to me were:

 

1.  Items 1 - 4, changing texture caps from 4096 to 512 made no difference to VAS usage, but did reduce VRAM usage

2.  Items 1 and 9, about 200MB VAS difference going from 8 real cores to 4 real cores (AM 170)

3.  Optimize Parts is aircraft specific but does indeed seem to help PMDG with FPS at the cost of a little extra VAS

4.  AM 170 seems to work better all around

5.  Oddly AM 14 (3 cores) used more VAS than AM 170 (4 cores)?

 

Cheers, Rob.

 

EDIT: I'm in the process of doing KSFO to KLAX flights (video) to see if I can confirm VAS is not being released from departure airport.  I did a flight from KSFO (FB) to KSEA (default) and KSFO VAS never released.  I have also been providing LM this information and will continue to do so.

Thank you so much Rob for your efforts to help us ID if there is a real problem.  I believe there is.  I tried another flight today from KMCI to KLAS with 1k textures on, LOW Autogen, Dense Custom Scenery.  I had 800 megs with the PMDG 737 at the boot up of the sim.  By the time we started engines 30 minutes later VAS had fallen to 662megs remaining.   I am about to push from the gate.  Will report and what is left when I hit KLAS.. IF I hit KLAS.  My first attempt was a failure right out the airport with MegaSceneryEarth loaded for 7 states  (That was pushing it to be sure).  I had 400 megs left rolling down the runway.    Using GEX P3D and UTX 2.1 USA now with moderate settings in UTX and late of VAS hogging features shutoff.     When I booted with the Photoreal setup I started with 500 megs and had 400 taking off... that would not be enough to complete the flight so I aborted on the climb.      Booting up with UTX/GEX I had 800 but down to 662 as I said just waiting for push back.  It will continue to bleed.. it always does when I fly with UTX/GEX on.   I will eventually bleed out of VAS....  

Never did I have VAS issues with my setup.

I use photoscenery + custom AG on top of it at very dense.

Water at high. HDR on etc.

 

What I do not use is an aircraft that is heavy on the system like the PMDG 777, as I use the Prosim cockpitsuite .

I don't think it's appropriate to blame PMDG, he he there were no problems with the previous versions--never

1.  Items 1 - 4, changing texture caps from 4096 to 512 made no difference to VAS usage, but did reduce VRAM usage

 

Does this mean, we do not longer need to restrict our sim to 512 textures? Was this change from 4096 to 512 simply done inside the prepar3d.cfg or did you really replace the relevant textures? If not, it does not surprise me, as I already read years ago that no matter what setting you have inside your config, the textures will be loaded as they are, meaning: if you install for example those 4096 cloud textures from REX, they will be loaded, even if you cap your config at 512.

Can all of you who get constant OOMs please confirm that you have Hyper-Threading turned off? 

Can all of you who get constant OOMs please confirm that you have Hyper-Threading turned off? 

 

Confirmed on my end.

I had mine on and off,no difference whatsoever regarding vas.

I can confirm however, the VAS in 3.4 is indeed higher than in v3.2. 

 

Strange thing is, I can do what I want, I don't get OOMs or even near them. I wrote down some VAS after the landing in various areas, done with the 737-800NGX PMDG and FS2Crew. 

 

Flights with Addons and VAS in use at the end after landing.

 

Overall used Addons:
PMDG 737 NGX

FSFX Immersionpack 737
FS2Crew Reboot NGX
GSX
ACARS systems from my airlines.

FTX Global
FTX openLC EU
AS16 + ASCA
 

Flight: KIAD (FlightBeam) -> KDEN (FlightBeam) VAS in KDEN 3,32 GB
Flight: EDDM (Taxi2Gate) -> LEPA (SimWings Aerosoft) VAS in LEPA 3.21 GB
Flight: LEPA (SW AS) -> LKPR (AS Prag) VAS in LKPR 3.38 GB
Flight: KDEN (FlightBeam) -> KSFO (FB KSFO HD) VAS in KSFO 3.15 GB

Flight: LPPR (TropicalSim) -> EKCH (FlyTampa) VAS in EKCH 3.41 GB

... continue monitoring. 

 

please note, I don't fly with traffic. All trafficsliders are down to 0.

 

Here are my settings in P3D.

 

My System:
Intel 3930k @ 4.2 GHZ
16 GB RAM
GTX 1070

 

I have a clean P3D.cfg, no tweaks. Only UseGlobalTerrainView = True. I don't have any PTA or something like this. I tuned the HDR file a little bit for myself. 

 

Let me know, if you need more information.