Issue ASN16+ASCA GPU Load at100%, bad FPS

Vasily

New member
Hello;
Just wanted to ask, do any of you experience any bad FPS with ASCA+ASN16 with SP1 Beta? Anytime I look at clouds or I get denser cloud coverage, my GPU load goes up to 100% and causes lots of lag... .
Thank you.
 

Vasily

New member
Also, ASCA or ASN2016 SP1 Beta does result in MUCH higher VAS use in P3D (And thats with textures set to 512x512 DXT) I hope that this issue will be fixed in the official release version.

Many Thanks,
 

ankh21

New member
Do you use any form of supersampling antialiasing? Even my 980ti will jump to 100% if i use more than 4x sparse grid supersampling.

Matthias
 

ankh21

New member
Yes, indeed, that was my idea...but even without Nvidia Inspector, there are some "tweaks" that may overload the GPU. But it seems to me you are using an unaltered prepar3d Setup?!

Matthias
 

Vasily

New member
Well... I do use two tweaks: Affinitymask and FFT, thats it. Nothing else.
I really hope that ASN team will further improve performance of ASN 16 and ASCA.
Many Thanks,
PS. It would be very nice to hear something from the ASN team about this issue.
Kind Regards,
 

JordanJ

Beta Team Member
Hello,

Are you using P3D, FSX or FSX-SE? If you are using P3D what version, and how did you install that version (Full install, client only, client and content, etc).

Thanks!
 

Vasily

New member
Hello;
Thanks for your replay. I'm using P3D v3.3.5 at the moment. I was on V3.4 and then 3.4+ hotfix. 3.4 has some serious memory issues. I have upgraded from 3.3.5 to 3.4 with the client only then same way to the hotfix. I rolled back to 3.3.5 by doing a client and content install/ uninstall. Under 3.3.5 the performance of the sim is better (memory management and FPS). As far as ASCA+ASN16 there are big differences and I mean BIG in terms of VAS and FPS. GPU load under v.3.4 in mediocre weather plus some overcast gets maxed out. Under 3.3.5 the GPU goes up to 92/95 , in addition the memory hit from ASCA or AS16 is substantial. Under 3.4 I could takeoff from (for example KSTL) and in 3-5 minutes get ProjectFly and FSUIPC warning regarding VAS. Under 3.3.5 at least I can complete a flight.
I strongly believe that some serious optimizations to your clouds and weather engine are needed. Please dont take this the wrong way, you guys are still the best weather system generator out there! I really hope that before the official SP1 release of ASCA and ASN you guys will do further optimizations to your engine.
Btw, my system specs are as follows: I7 4790k @4.4, EVGA GTX970 FTW+, 16Gb Corsair ram, Win10, 64bit.... P3D runs on its own 500 Gb SSD.
Many Thanks,
Looking forward to hearing back from you soon
 
Last edited:

kterz

Developer
Staff member
Hi Vasily,

the problem of VAS (and performance) is specific to 3.4 and it's something that LM are aware of and are investigating. Unfortunately, not much we can do at this point.

One thing worth asking all claiming they have worse performance with SP1, is whether they always use live weather. Cause in the northern hemisphere, "average cloud coverage" during the last month increases significantly during November and so do the support issues about low frames. This is consistent all these years Active sky is in development. So, one thing all of you could try is to use historical weather (from e.g. September) and see if the perceived frame drop persists.

It is important for us to clarify if indeed something has changed in SP1 as regarding frames and how many of you are really affected (and most important why). If we don't get enough info on what is the real issue, we have no chance of of fixing it
 

tommchale

New member
I too have noticed a drop in performance since updating to ASN16 & ASCA. ASN was fine, I had no issues running it on my PC with P3D, PMDG777, add-on airports and ORBX Global/FTX England.

The performance issues I experience cannot be pinpointed to an exact moment/time so it's hard to keep track, but at random stages throughout the flight, the frames severely drop and the whole thing becomes a slide show. This happens for around 5 minutes then things go back to normal. No sign of anything particular happening outside weather wise either to blame it on, its purely random. I've noticed it mainly over the atlantic, but i'm on my way to Doha at the moment from LHR and i've just had it happen over Turkey?

Disabling AS16 rids the issue and the performance jumps straight back up.

I've also noticed the performance drastically reduces during stormy weather with precip - I know this is expected but it never reduced as much as it does now in ASN. My AS16 settings are mirrored on my ASN settings and no hardware changes have taken places, apart from REDUCING some sliders in both P3D and AS to enable a smoother ride during this november weather.

Tom,
 

Maytrics

New member
Hello;
Just wanted to ask, do any of you experience any bad FPS with ASCA+ASN16 with SP1 Beta? Anytime I look at clouds or I get denser cloud coverage, my GPU load goes up to 100% and causes lots of lag... .
Thank you.
I struggle with the same problem. Yesterday I took a 1 hour flight, when I was established on final approach I got crash to desktop with OOM.
 

littleDave

New member
Have the same problem with VAS since the second SP1-Beta, too. Flight was from KDLH-CYYZ on 2016-26-11 15:00:00 UTC with the PMDG 777-200, no airport scenery, OpenLC NA installed using Prepar3D v3.2.

First I flew with the second SP1-beta but I got an OOM on final. Then I reinstalled the first SP1-beta and did the same flight again and could land even without the memory warning bell of FSUIPC. If I recall correctly, the VAS-usage of the second flight was more than 300 MB less than the first one. I used the same AS16/ASCA settings for both flights and did not change any P3D-config
 

tyrodes

New member
I saw the same thing (FPS wise) when I upgraded P3D from 3.2 to 3.4. In my case, I also see it with ASN+ASCA turned off with similar (as best can) cloud conditions. Do you also? Just curious, because I suspect some other, non ASN+ASCA, component of cloud rendering has significantly changed (for me) between P3D 3.2 to 3.4.
 
Top