It is fixed, that is what the 4 step AC process did for me, fixed my VAS leak.

Oh ok, I thought you were going to try to find the cause of the leak.

Like some dll maybe.

 

Also, are you going to send this info to PMDG by means of a support ticket.

 

Since they have the code for the 777 maybe they can further investigate?

Or do you think this leak is so unlikely to occur to others and that has more to do with your personal hardware/software combo than with the PMDG777?

 

 

Oh ok, I thought you were going to try to find the cause of the leak.
Like some dll maybe.

 

Technically possible (with a lot of expensive tools), but not practical ... could take weeks, months, even years.

 

 

 

Also, are you going to send this info to PMDG by means of a support ticket.

 

Unlikely, it appears to be part of a known FSX bug.

 

 

 

Or do you think this leak is so unlikely to occur to others and that has more to do with your personal hardware/software combo than with the PMDG777?

 

Anytime a 3rd party developer places something in the DLL.XML there is the potential for VAS leak ... there are just so many ways to introduce a memory leak (Simconnect and more).  The EXE.XML should not cause VAS issues.

Once I find a problem I just have to understand it. I am also going to try this route with the NGX.

 

I'm the same way with things, that's why I very rarely ask questions on this forum. I have been a trouble shooter all of my life. When I run into situations where I haven't got a starting point,there is the net.

Will be looking to see what you come up with on this matter.

My PC is a 3930k at 4.6 on an asus sabertooth x79 16GB of ram, an asus 680gt. Temps under stress never go above 61c with the corsair h110i cooling the cpu, my room is airconditioned. My op sys drive is a samsung 840 512GB SSD and FSX resides on a kingston 128 GB SSD.

I run OPUSFSX, PFPX, EZDOC, and FOLLOWME. I have REX Essential Plus, and Active Sky 2012 but these last two are not being used for OPUS and PFPX take care of their slots currently.

I've done two flights so far, currently enroute on my third. I got a FSUIPC VAS warning departing FSDT KLAX and the entire flight to EDDP I sat on a fine line of almost getting an OOM. Departing EDDP for VHHH it was high-ish due to weather, but it backed off when I got out of it and was fine. Departing VHHH it was even lower and as I cruise over the pacific now it is sitting at 2.2 GB. I suspect when I arrive into LAX it will shoot up and I'll get another warning. 

 

That said, I have no real issue with anything until I get into a demanding scenery, like FSDT KLAX (Flightbeam KIAD was perfectly fine for me, but I think they've just mastered the art of optimized scenery). I think the issue is a texture thing maybe. I'll try changing some settings to see.

 

I'm curious what the difference would be if I could lower the resolutions like I can in the NGX..

 

 

I didn't install the RAAS option...

 

aw s@*t, I did even though I already had RAAS installed. I did check it to ensure any needed modifications would not be hampered. I did see couat using up tp 600mb.

 

 

That said, I have no real issue with anything until I get into a demanding scenery, like FSDT KLAX (Flightbeam KIAD was perfectly fine for me, but I think they've just mastered the art of optimized scenery). I think the issue is a texture thing maybe.

By coincidence I have been playing with my Nvidia Inspector settings and have gone with an AA setting (AA_MODE_METHOD_SUPERVCAA_64X_4v12) that I found in the forums which I really like. However it is a bit challenging to my GPU (1.5g GTX580). To get to the coincidence, I have been monitoring my GPU percentage use quite closely and noticed that when at the gate (close to the terminal), at FSDT KLAX & CYVR I am at just about 95% usage. this drops to 75% once I am pushed back and taxiing. When at Flightbeam KPHX (Comparable to KLAX or CYVR I would think), I am at about 75% GPU usage at the gate and even lower on taxi. So for a relatively new dev in the scenery business, I'd say they are doing very well.

 

Regards,

 

P.S. saving for a 3g GTX780 by the way. That AA setting is a keeper.