GTA 5 0.351

[robi29]

I think I had the same bug. I don't know if this bug affect MSAA too, because I discovered the bug when MSAA was broken (in early 0.350 version). Look at the "nextgen" and "first_NG" modifiers in timecycle_mods_1.xml file.

It's a fix for my mod below:

Not working:

Code: Select all

<modifier name="nextgen" numMods="0" userFlags="0" />

Working:

Code: Select all

<modifier name="nextgen" numMods="1" userFlags="0">
    <lens_dist_coeff>-0.001 0.000</lens_dist_coeff>
</modifier>

[random23]

ok, i installed kb4100347 windows update today, rebooted my pc and this is my skylighting performance now: https://imgur.com/a/ULSErCE
Note how gpu load jumps from 43% to 99%, it was about 15% difference before the update. (gtx 970, i5 3470, windows 10 1803)

Weird, but it seems that only skylighting performance is affected, everything else is fine. I wonder if anyone else can confirm.

UPD. Previous 0.351 enb binaries are a little bit better, ~30% gpu load difference. Still bigger than i remember.

[ENBSeries]

Those values means nothing on practice, only graphics developers can have some useful info.

[random23]

Well, on practice it means huge fps drop though I just thought it would be more usefull to illustrate the difference using gpu load and not actual fps count.

[random23]

Did some more testing, uninstalled kb4100347 update, didn't get my performance back. I'm either stuck with it or it wasn't the update that caused the issue in the first place. I don't know what else i can do, but skylighting with latest enb binaries gives me huge fps drop.

One last question: does it make sense that "high resolution shadows" option affects skylighting performance?

[ENBSeries]

Yes, shadow resolution is the direct reason of cache misses and performance drop, because shadow space used to compute ao. I'm searching now the way to decrease resolution without producing bugs.

[lomerta]

I think I had the same bug. I don't know if this bug affect MSAA too, because I discovered the bug when MSAA was broken (in early 0.350 version). Look at the "nextgen" and "first_NG" modifiers in timecycle_mods_1.xml file.

It's a fix for my mod below:

Not working:

Code: Select all

<modifier name="nextgen" numMods="0" userFlags="0" />

Working:

Code: Select all

<modifier name="nextgen" numMods="1" userFlags="0">
    <lens_dist_coeff>-0.001 0.000</lens_dist_coeff>
</modifier>

Thanks, I use other modifiers in "nextgen" except that one, I added your line but zeroed and still not working, I don't really want to use that lens distortion with any other value than 0... I guess I'll better wait until those bugs with timecycle modifiers and framescaling are resolved.

[robi29]

But the value cannot be zeroed. Write -0.00001 and you won’t see any lens distortion

[ENBSeries]

Those bugs will never be fixed, because i will not install any mod for gta5 and i do not support frame scaling.

[lomerta]

But the value cannot be zeroed. Write -0.00001 and you won’t see any lens distortion

ok, removed all my lines (which I'm not happy with but for the sake of testing) and put yours only, still not working.
Another timecycle maybe?

@Boris you know timecycle editing is essential in any GTA title, we are not talking about installing some random mod but you are the boss.