i see no difference

Same here. Tried those entries last night, and there was no difference in the amount of VAS I had left after loading. I didn't try a full flight, but I'd be surprised if it made a difference on my computer based on what I saw.

I realize those config settings are suppose to be the defaults but for some reason me setting them in the config file physically has made all the difference between a stable VAS flight and a dinging OOM mess.

 

Hi Brian, so far you seem to be the only one who sees the effect. Just for interest: have you tried to delete the entries to see whether your OOM are back?

Same here. Tried those entries last night, and there was no difference in the amount of VAS I had left after loading. I didn't try a full flight, but I'd be surprised if it made a difference on my computer based on what I saw.

 

For me it's not about the amount I loaded in with.   That did not change.  With my settings I typically load in with about 800 megs remaining.  The problem with before my settings change is I would bleed my VAS to death and then when I would arrive my destination airport I would drop 150-300 depending on the complexity of the airport and then dings start and usually OOM CTD.    With these settings on in the CFG file and no other changes, I am seeing my memory stablizing at around 450 megs during the flight but it doesn't drop at all when I arrive at the destination airport.  It may change like.. 50k here and there but it stays solid.  I have no idea what is going on but it's pretty awesome in my case.

 

I am testing a fully loaded Autogen/LC flight now from KRDU to KMDW.  Both payware airports with GEX/UTX for LC and Vector.  75% AI traffic.    I am at cruise now with 470megs left.  Now the true test will be to see if it stays around that when KMDW comes into view with all that Chicago autogen popping in.  IF it does stay solid, then I have no doubt this is working for me and I have found my solution until we see a 3.5.x

 

As to turning these tweaks back off... I am almost afraid too.   What if the sweet spot doesn't come back?  There are several things I can think of that are happening under the hood now to explain this stability in my VAS but they are probably all wrong but I don't want to jack with it.  It's working for me now and I am a happy flier again.

 

So to reiterate.  I don't see MORE VAS on start up over not having those tweaks in the CFG.  What I see is the ridiculous VAS bleed being staunched, allowing me to complete my flights.  I will report back IF I gate to the gate at KMDW.   If I OOM I'll report that too.

 

EDIT:  Nope...  even with this tweak with Very Dense autogen and 1k textures I couldn't make the gate.   I was just about to touchdown on 31C when the textures all went black and the last of the VAS was used up.   It was a very slow bleed down from 350megs to 57megs remaining at the time.  I would have CTD the second the airport came into view without this tweak though.   Damn...   if that stupid Optimize_Textures garbage wasn't eating up VAS I probably would have made it but I refuse to turn that tweak to 0 as I need it for the extra FPS boost in the 737NGX.    Ah well... I prefer Photoreal flying in a tube liner anyway.  I have no use for 12000 trees at FL 380.

For me it's not about the amount I loaded in with.   That did not change.

 

Yeah, sorry, I misread your post last night.

 

In any event tonight I did a flight (CYVR-CYYZ in the 77L) that I've found very consistent in VAS usage with 3.4 and I couldn't tell a difference with those tweaks. I always end up with about 350MB remaining after landing in Toronto and that's what I ended up with this time as well.

 

FWIW, I've also seen a slow increase in VAS usage later in a flight. For example, when flying VHHH-CYYZ, I start with 1.5-1.7 VAS remaining at VHHH, it stabilizes around there during cruise, then a few hours outside of Toronto it slowly decreases down to the 350MB number I mentioned when landing. I've always figured that was down to it loading scenery, but TBH I never paid much attention to VAS until in previous P3D versions so I have no idea if anything has changed on my end. 

My own experience using the .cfg entries from Kuragiman was a savings of about 100MB. (without entries landing with~240MBs left, with the entries, I land with ~350-370 MBs)

My test flight has always been a circuit around KEWR with the 777 and RAAS enabled. (You can disable RAAS for more VAS savings if you need to)

 

Hope everyone finds a setting that works...

Has anyone else had this issue with flashing effects? 

 

Has anyone else had this issue with flashing effects? 

 

 

Hi Josh,

 

Yes I did, particularly on the AI boat wakes. I have the latest Nvidia driver and suspect it, since I did not notice any such thing before. Which driver are you running?

 

Kind regards,

 

PS: I am considering rolling back.

Hi Josh,

 

Yes I did, particularly on the AI boat wakes. I have the latest Nvidia driver and suspect it, since I did not notice any such thing before. Which driver are you running?

 

Kind regards,

 

PS: I am considering rolling back.

 

I am using the latest Nvidia driver 375.63

Has anyone else had this issue with flashing effects?

 

Did you delete the shaders folder as suggested after a driver update? Haven't seen this flickering issue on my rig...

Hi Josh,

 

This effect looks to me very similar at what you get with PereciptFX active, the "engine jet wash effects" I can notice taxing with big liners throttling-up in cold wx (but not so pronounced).

If this is the case, maybe re-installing it (I assume you updated 3.4 content) solves the problem but I'm just guessing here.

 

Hope you may find the root cause.

 

Cheers,

 

EDIT: disregard Josh, I noticed just now that you were talking about AI traffic. 

Did you delete the shaders folder as suggested after a driver update? Haven't seen this flickering issue on my rig...

 

Fresh install with P3Dv3.4. After the issue arose, I did a complete uninstall and reinstall including deleting the shaders folder. Same thing happened. Only addons I had afterwards was just the NGX and the 737 Immersion pack. 

The same thing happens to smoke effects, and boat wakes. I just updated Nvidia drivers from 375.63 to 375.70 without remedy. In fact, if anything, it was worse.

 

I rolled back to 373.06 and it fixed the flashing for the effects files. Doesn't seem that anything else is broken.

 

Kind regards,

Stephen, nice seing you around dear!

Stephen, nice seing you around dear!

 

Hello David,

 

The pleasure is mutual! Long time old friends with lots of history here!

 

Kindest regards,

I had an OOM on my regular route from EGLL to EKCH which i have tuned for ages because i fly this stint alot so i was a little surpriced. Those airports is the only one activated in P3D.

 

My settings are really basics to the middle and i normally land with about 400mb left. No Vectors.

 

I would really like to hear from you about a specific memory issue i seem to have leaving London behind.

 

This issue if i can call it that also happened with FSX and in the same spot.

 

Try out 27L or 27R and the BPK7G (27L) departure and monitor your vas as you are about 5-7nm from TOTRI. You should have London City and the airport away from you but as asoon as i hit this spot VAS is dropping 250-300MB

 

I can reproduce it every time . What on earth is loading when London is way back ?

 

I took of with 1GB VAS left and at this spot i was down to 550mb and the VAS never recovered

 

 

Thanks

Michael moe