Possible new VAS issue in v3.4

[zap737]

Well, confirmed. 378.57 is causing a VAS leak. ...

Kosta, do you mean Nvidia drivers 378.49 ? I don't think there is 378.57, or is that a Beta driver ?
Also, try Nvidia drivers 376.33 as they solved a VAS issue on the PMDG 747 V3.
See here: http://www.avsim.com/topic/503393-747-v ... s-not-747/

[Kosta]

Well, confirmed. 378.57 is causing a VAS leak. ...

Kosta, do you mean Nvidia drivers 378.49 ? I don't think there is 378.57, or is that a Beta driver ?
Also, try Nvidia drivers 376.33 as they solved a VAS issue on the PMDG 747 V3.
See here: http://www.avsim.com/topic/503393-747-v ... s-not-747/

Yes there is, it's a Hotfix driver, that should have fixed the memory leak. I found it by googling...
I know about 376.33, I am only now on older drivers, as for one I don't play extremely current games and for P3D it's really one and the same I guess. And I don't use SLI.

[dikkeduif]

I did the same flight LOWI - LEPA again but without FSP and VAS stayed pretty stable the whole flight.

Without FSP
LOWI 1380000
RESIA 1161312
BORDI 1109736
RIXOT 1043000
LEPA 950000

With FSP
LOWI 1380000
RESIA 1190000
BORDI 832364
RIXOT 759000
LEPA 659000

I guess the only difference I see is that with FSP the memory drops faster, since it has to load those additional meshes. But all in all, I don't see so much difference to when I'm flying with FSP.

[Kosta]

Guys, since two days I did some flights, now didn't really change much, but I get pretty consistent and really good VAS-performance with 372.70. Also running latest HF3.

[Humpix]

dikkeduif - well, this looks exactly like our problem.

VAS is generally higher with mesh (a few MB), but it should also drop in the same rates.
Or, in other words to proof that, the freemeshes and the new NG meshes work exactly like that, BUT not so the 2010´s meshes:

Drops without FSP
218MB
51MB
66MB
93MB

Drops with FSP
190MB
357MB (See above, at this point you should only have a ~ 51MB drop)
73MB
100MB

On this route it is not a big problem, because you only hit one "VAS drop spot". On other routes you hit more than one, which eats up 300MB each spot...

So I suggest to stop using 2010´s meshes an go to the NG meshes, which are not cheap btw., but the best you can have - Or use the freemeshes, which are as good as the 2010´s.

[Kosta]

On this route it is not a big problem, because you only hit one "VAS drop spot". On other routes you hit more than one, which eats up 300MB each spot...

A stupid question maybe, but can you prove it? Can you actually fly a route that does that, and OOMs based on the mesh?

[Humpix]

Nope, because I already use the new mesh and I dont want to mess up my sim again.
You just have to believe me, or not :)

But I remember a good place for that effect, it was between KTCL and KSHV - I fly this route sometimes with the Cessna for VOR training. I remember that this route was impossible. Started with ~1200MB VAS and end up with OOM somewhere in the middle... (btw. this would be a good crosstest - fireing up my sim. If I am right, this should work now :)

[Kosta]

The point of my question was if one knows where these places are, and how many there are. Because one would have to fly over it. So, without knowing that, it's a really only a moot point.

But I guess now it's useless to try, as you say it works good with FreeMeshX mesh?

Let me know the outcome.

[Humpix]

Jep - your right. But sadly I dont have all these positions, because when it starts, I did not even think about that it could be the mesh. With the FreemeshX or FSP NG´s the problem is fixed for me, and hopfully I could help someone else.
C'est la vie

For me, now I can do all of my trainings again without think about the sim and I swear by the holy 42, I will never never touch any update (Prepar3D, NVidia, Windows) again. Until there comes a much much better x.. version ;-)

So lets go flying!

[dikkeduif]

I guess I'll try out freemeshx for my mesh needs :) I don't feel like paying for a new version of the mesh from FSP.
Does FSP have a support forum? I can't seem to find it.

[Falcon60]

I'm new here but I have seen screen captures with RAM and another interesting items displayed on screen in the sim, is there a script or something that makes that data appear in the simulator on screen?

[Kosta]

I'm new here but I have seen screen captures with RAM and another interesting items displayed on screen in the sim, is there a script or something that makes that data appear in the simulator on screen?

There are indeed different things.
If you are refering to the VAS counter, that is coming from an FSUIPC.
As for "items", you're gonna have to be more specific.
Some things can be turned "on" in prepar3d.cfg, but as I said, little bit more specific.

[tooting]

12 pages, 12 and yet the vas drain issue is still obvious in some areas and not others.

Maybe Lm one day might admit by tinkering with fsx they have actually made it unstable. I can fly mco to lgw but not the other way around unless the Flight goes nowhere near the Canadian landmass. Years on we are now blaming HT, ndivia drivers and spot viewers, one day some one will actually admit it's a buggy unstable sim.

[Saldo]

12 pages, 12 and yet the vas drain issue is still obvious in some areas and not others.

Maybe Lm one day might admit by tinkering with fsx they have actually made it unstable. I can fly mco to lgw but not the other way around unless the Flight goes nowhere near the Canadian landmass. Years on we are now blaming HT, ndivia drivers and spot viewers, one day some one will actually admit it's a buggy unstable sim.

No issues here ...
Never had them. Very stable sim.

https://youtu.be/KVtX0NMgsO8

[tooting]

So just because one person says I dont have an issue doesnt mean there isn't an issue.

I'm sick to death of people blaming each other, pmdg, p3d, ndivia, orbx etc etc . I always base the theory on facts and not feels. 12000 hours on vatsim and the leak happens in one certain area and its big issue.

I understand theirs money money involved here I can see why a major defence contracter doesn't want to put its hand up and admit to an issue that effects the basics of the software. But all this bollocks has been going in from the start