ENBSeries

Fallout 4 (TES With Guns)

ShadowBoost - FPS Dynamic Shadows modification
Binaries are here http://dev-c.com/fallout4/shadowboost/
Nexus purgatory page http://www.nexusmods.com/fallout4/mods/1822/?

Increases performance by automatically adjust drawing distance of the shadows depending from frame rate and desired frame rate.

Oh my god thank you so much

A very effective way of seeing it work it's magic is by limiting FPS with ENBoost and watching the shadow distance increase, decrease. Very nice.

Users reported bug which appears as unchanging shadows distance if current frame rate is locked (f.e. 60 fps) and target frame rate is same. It's a complicated issue, because deadzones in measurements helps to prevent shadow distance jump back and forward (oscillate), but at same time deadzones produce the issue. Exit deadzones and increase distance to check when (if) fps will start to decrease automatically - produce ocsillation. I'll try to fix this asap, but out of ideas right now.

ENBSeries wrote:Users reported bug which appears as unchanging shadows distance if current frame rate is locked (f.e. 60 fps) and target frame rate is same. It's a complicated issue, because deadzones in measurements helps to prevent shadow distance jump back and forward (oscillate), but at same time deadzones produce the issue. Exit deadzones and increase distance to check when (if) fps will start to decrease automatically - produce ocsillation. I'll try to fix this asap, but out of ideas right now.

I'm able to stop the shadows from adjusting just by limiting FPS to 30 (max is 50) and toggling that. Eventually the shadows stay at minimum distance. The culprit could be RTSS frame limiting to 50 with min FPS in ShadowBoost set to 50 as well.

ENBSeries wrote:Users reported bug which appears as unchanging shadows distance if current frame rate is locked (f.e. 60 fps) and target frame rate is same. It's a complicated issue, because deadzones in measurements helps to prevent shadow distance jump back and forward (oscillate), but at same time deadzones produce the issue. Exit deadzones and increase distance to check when (if) fps will start to decrease automatically - produce ocsillation. I'll try to fix this asap, but out of ideas right now.

So the workaround is making sure the target framerate is set lower than your max framerate?

And what if we're using ENB's frame limiter? I set ENB's frame limiter to 40 because I never get near 60. Should I be setting my target frame rate to 35?


...Or am I misunderstanding the issue entirely?

Hey Boris,

Thank you for suggesting this "tool". Needless to say, with your Fallour 4 ENB you are again made a marvellous job! Congrats!
Asked my question at Nexus as well. Maybe I missed something, but do not find the answer. I mean reliable answer, not just what Google find.

So:

"fShadowDrawDistMax - max value of shadow draw distance, it will never go above this value in the game, default = 15000.0

I have now at 20000.0000 default Ultra settings. Which value is max, for till "reasonable" to gain this value?"

If this value stands for fShadowDistance=20000.0000 and fDirShadowDistance=20000.0000 at Fallout4Prefs.ini(?)


Thank you!

Boris, you've solved a problem in two weeks that Bethesda could not solve in seven years.

I am very impressed, amazing work.

I play with a 30fps cap. Setting the minimum FPS to 28 was fine; when in dense areas, ShadowBoost landed me @ 28-29 fps. Going to try setting it to 29.

I play with a 30fps cap. Setting the minimum FPS to 28 was fine; when in dense areas, ShadowBoost landed me @ 28-29 fps. Going to try setting it to 29.

why do you want to do that ?
if the shadowboost has to change settings on a 1 fps difference it would be constantly changing the shadow distance like a madman.
that will only hurt performance imo.

i think it works best if you just give it some space, like 45~60 (if it's capped at 60).

ofcourse i could be wrong again, just thinking out loud here.

i think it would be setting your shadowdistance to 2000 when it goes to 28 fps, and then back to 15000 when you have 29 again, would be awful too see.
or the code must be compensating by changing it more gradually inside a loop or something.