Fallout 4 0.282 ENBoost

[FiftyTifty]

Decided to peek at the settings inside the Fallout4.exe file, and I found some rather interesting stuff. Namely, there are several settings to do with async compute.

Here's what I've found for :Display and :General. http://pastebin.com/FkXU9EyJ
Though I'll paste the [Display] section here.

Code: Select all

[Display]
bMainRenderInDeferredContext=1/0
fMaxFocusShadowMapDistance=0000.0000
bMultiThreadedRendering=1/0
bMultiThreadedRenderingDFL=1/0
bMultiThreadedRenderingFWD=1/0
bMultiThreadedRenderingPPM=1/0
bMultiThreadedRenderingPPLD=1/0
bAllowMergeInstancing=1/0
bMergeInstancingOnAllCombinedMeshes=1/0
bShowMarkers=1/0
bActorSelfShadowing=1/0
bAllowShadowcasterNPCLights=1/0
fNoLODFarDistanceMin=0000.0000
fNoLODFarDistanceMax=0000.0000
fNoLODFarDistancePct=0000.0000
bShaderCache=1/0
bAsyncResourceCopies=1/0
bEnableCameraCache=1/0
bForceAllRenderTarget=1/0
bDo30VFog=1/0
bImageSpaceEffects=1/0
iTrilinearThreshold=0000
fMipBias=0000.0000
bEnableWetnessMaterials=1/0
bMeshCombinerMaterialComparison=1/0
bUsePreCulledObjects=1/0
bSinglePassDirShadow=1/0
fBlendSplitDirShadow=0000.0000
bForceIgnoreSmoothness=1/0
iMaxFocusShadows=0000
bComputeShaderDeferredTiledLighting=1/0
bZPrePass=1/0
bVolumetricLightingForceCasters=1/0
bUseAutoDynamicResolution=1/0
bHDRinCS=1/0 ; Probably to do with the Geck?
fAOLightingStrength=0000.0000
fAOBlurSigma=0000.0000
bUseAsyncComputeAO=1/0
iDirShadowSplits=0000
fTAASharpen=0000.0000
fTAAPostSharpen=0000.0000
iRenderPassCacheSize=0000
bSimpleLighting=1/0
bCompileOnRender=1/0

Any idea if there's a benefit towards using the following settings in particular, or are they just broken leftovers from Bethesda's tests?

Code: Select all

bAsyncResourceCopies=1
bUseAsyncComputeAO=1
bComputeShaderDeferredTiledLighting=1

On a different note, is it possible to remedy the 64hz bug through ENB? Oblivion, Fallout 3 & New Vegas had the Stutter Remover mods, which replaced the renderer's GetTickCount functions with TimeGetTime.

Sadly, Fallout 4 (and Skyrim) have no such mod, which means iFPSClamp must be used. Which is shitty, because it causes slow-mo when the framerate drops below iFPSClamp's framerate.

And as a request, a setting to disable the head-ache inducing Eye Adaption would be a god send. I forgot how terrible it was in Skyrim, due to religiously using ENB. I swear, Bethesda wants to cause migraines.

Anyhow, keep up the sweet work. Game's not even been out a week and you've already fixed the horrendous character lighting.

[Bonnie Lass]

Can't you just fix the 64hz bug by putting the fps limit to 58 in enblocal?

[Bonnie Lass]

Hmm, that's curious. For me, Fallout is not limited to 30 FPS in fullscreen mode , even without ENB. The built in vsync in Fallout 4 seems to be triple buffered, such that the framerate doesn't 'snap' to 30 or 60, but can fluctuate between those two.

Anyone else out there having a similar experience with this 30FPS cap in fullscreen?

Plenty of people are - in fact I've never heard of someone NOT having the 30 fps cap in fullscreen.

[FiftyTifty]

Can't you just fix the 64hz bug by putting the fps limit to 58 in enblocal?

No. You're still dropping those frames.

Admittedly, if you're able to get a constant 50-60fps, you're not really going to notice the bug too much. But for those of us on lower framerates (e.g I push my system for the eye candy, aiming for 30fps minimums, with 30fps being my cap), the 64hz bug is horrendous.

[Miguel]

Hi,

With version 0.282 the game crashes every 10 to 20 minutes mostly while editing settlements if ApplyStabilityPatch is set to true.

If it's set to false the game is much more stable (no crashes in more than 2 hours of gameplay and crafting).

This happens to me and a friend.

[Madpaddy]

No FPS cap at 30 that ive seen, mine my sons and none of my friends have that problem all running at 60fps full screen.

[ENBSeries]

Jay_ombie

Do I need to like in Skyrim disable Antialiasing and Anisotropic Filtering ?

It's not Skyrim, right?

Vsync in enblocal.ini have dependency from game present interval data. But internally vsync have two control variables which passed from game, so it's hard to tell how exactly it works with all combinations unless you try. My videocard/driver have vsync bugs anyway and i told about this issue many times, testing it is impossible for me. And vsync option in Skyrim mod is not the same kind as in GTA 5 and Fallout 4.

FiftyTifty
And now expect new stream of bugs at Bethesda forum because of players dirty hands
Don't touch multithreading setting anyway and do not change sometihng you don't know for sure, other users may start writing guides for unstable configs and destroy compatibility with future versions of ENBSeries. And remember, it's Bethesda game, nobody guarantee any of the setting works or tested.
I can replace timer with higher precision version of it, but never seen any improvements in Skyrim by doing that.

Anyone else have crashes like Miguel have?

[Jay_ombie]

Well, okay - skip the Skyrim reference bit. I mean as in the ENB Wrapper do I need to disable any game related graphic options from the games menu if I use this ENB for Fallout ?

[Bonnie Lass]

I am a little confused about the RAM stuff you put on the front page of your site.

Does using ForceVideoMemory potentially prevent Fallout 4 from using a swap file? I use a SSD and I'd rather it not get all screwed up by constant reads.

I do plan on upgrading my computer but I'm waiting for the Black Friday sales.

[Dorak]

Decided to peek at the settings inside the Fallout4.exe file, and I found some rather interesting stuff. Namely, there are several settings to do with async compute.

Someone already made a ini dump.

http://pastebin.com/Yrrpwy0E

But like Boris said, i think these parameters are just here for general knowledge more than anything else. I start to see more and more "guides" and people that claim that some of these parameters are basically Jesus and fixed all their issues and shit like that.

Fact is they have no idea what these parameters do, other fact is most of them are placebo at the very best, crash inducing at the very worst. Also some people like to think that because some specific tweaks worked on Skyrim, they will work on FO4. While it's the same engine, we can rightfully expect that some work was done on the backend, thus making "what worked before" irrelevant.

Game is unoptimized as absolute fuck, and i'm struggling to keep more than 50 FPS in urban areas (special mention for Corvega Assembly Plant) on a 4790K and a 980. Nothing you can do about it except waiting for an hypothetical performance patch, but i doubt it will happen.