Fallout 4 0.355

[lomerta]

Thanks for explain, that's exactly what I meant.

I have a problem using ENBParam_COLOR4 works only with UIWidget="color" but not with UIWidget="vector" or UIWidget="vector4"

I wouldn't mind using color if it didn't translate itself to RGB/HSV instead of keep the raw params...

is there other way to use float4 without color in UIWidget? I think I tried them all already

[ENBSeries]

Good Vector4 is not exist as some UI element in middleware which i am using for editor, so nothing gonna change if you just make several variables.

[SQr17]

I noticed a performance issue in my game where in some interior areas (such as those in Diamond City) there are sudden large FPS drops (~60->30s) when looking in certain angles. Only seems to happen with Self-Intersecting AO enabled. The thing is the FPS drops go away as soon as I open the ENB overlay interface, and comes back as soon as I close it. I haven't tested the issue extensively, but possible locations to test this are in the Home Plate, near the workshop or the Dugout Inn, near the bar.

I am playing the game on UHD res, on a 1080ti. Has anyone else experienced something like this? Looking for some insight.

BTW, issues aside, Self Intersecting AO + IL does look pretty fantastic. Great stuff, thank you, Boris.

[ENBSeries]

This drop sounds like a normal vsync behavior for me. When hardware unable to perform fast enough to fit refresh rate, next frame is waited without drawing. Anything can be the reason for such issue if no enough room by performance left to suit that one frame. And diamond city with many other places in the game, have very bad bottleneck about draw calls, that's why shadow boost was made and various suggestions to decrease drawing distance.

[SQr17]

*facepalm* I completely forgot I had the ENB Vsync on. Disabling that and enabling the frame limiter does get rid of the sudden FPS drops.

Still, it is a bit strange that the FPS drops don't happen with the ENB overlay open.

Thanks for the tip. Much appreciated.

[--JawZ--]

Hi there Boris,

I've been going back to modding Fallout 4 again.
And I noticed this issue, that Adyss presented here, it's a very annoying bug. And I don't see how reverting back to the 0.307 algorithm would hurt.

Can it be done for testing purposes at least, to see if it actually is visually more buggy than the current implementation of the detection of interior and exteriors?

[ENBSeries]

I said that dont see it, so cant fix before that happen. And i will not revert back.

[--JawZ--]

Ok fair enough, but I can supply a save with instructions on how to reproduce the effect?

[ENBSeries]

I had savegame, but didnt see bug. You can try of course.

[--JawZ--]

Ok here are the files then;
https://drive.google.com/open?id=1ZRboG ... _6LsP8WIzO

It includes the following files;
enbseries.ini - With exaggerated values between Exterior Day and Interior Day
PILGRIM2.esm - Edits done in this mod allows the detection issue to be seen. Only Fallout4.esm is required to run it
PILGRIM2 - Main.BA2
Save1_00000000M_Commonwealth_000009_20190105202210_1_2.fos - The save file, should Appear as "Beacon Hill 0h 09min" in the load game menu
Fallout4.ini - And just in case it might be related to some .ini settings, I included the ones I used while I encountered the detection issue
Fallout4Custom.ini
Fallout4Prefs.ini


When you have loaded the save game, enter this console command;
fw 1a65e5

This is in the weather the interior detection issue happens, and it happens if you look up and down.
Also to note, this is an altered weather from the included mod. So it might have something to do with either weather records or imagespaces. I'm not sure though as I couldn't find any specific record while removing edits done by the mod, one by one.