BethINI (by DoubleYou)

[magician16]

I can't seem to get FOV to stick for Fallout 4. It always reverts in some form with Bethini. I always have to use "fov 95 95" in CC every game start. If I use "fov 95" it reverts even when in CC. Does others have similar experience?

[Rebel47]

So you set your specified fov in Bethini, then you load up the game and change it again ? I've always changed my fov with Bethini and never had an issue with it not sticking, if you are changing fov in both ways (bethini and CC) then your likely overriding one and just breaking stuff that needn't be broken

[magician16]

So you set your specified fov in Bethini, then you load up the game and change it again ? I've always changed my fov with Bethini and never had an issue with it not sticking, if you are changing fov in both ways (bethini and CC) then your likely overriding one and just breaking stuff that needn't be broken

No, FOV option doesn't work for me in bethini. If I set it 90 in there I notice in game it is not 90 or whatever.

For example, if I set it to 95 in bethini, I go ingame, notice FOV is off, go to console and type in desired FOV and it feels much better and I don't get nausea from low FOV. Ini files are not set to read only.

[Rebel47]

Are you using MO, I haven't personally tried Bethini with MO so I don't know if it accesses and edits the right ini files, but if not you'll have to manually the ini files through MO

 

The above is just a theory that you can try out, at least until Double You weighs in with an opinion.

[magician16]

I don't use MO, I use Wrye Bash for Fallout 4, and in rare cases NMM for fomod mods.

[magician16]

I was thinking since using "fov 95" in console (or any other number) immediately reverts it, and using Bethini to change fov also doesn't do anything for me, I am thinking that Bethini does the same function whatever "fov 95" does.

 

However, if I write "fov 95 95", then the FOV sticks until I exit and relaunch the game. I am thinking that "fov 95 95" does additional changes which Bethini doesn't account for and this is why I get the same result from bethini as I do when I type "fov 95" instead of "fov 95 95". This is just an educated guess.

 

I have also reset my .ini files and made brand new ones and tried again with Bethini. No dice.

 

If somebody can confirm this for me I would be grateful. Simply set a FOV in Bethini, then go ingame, type "fov (desired number)" and see what happens. If the screen changes while in CC, bethini didn't apply settings. When you exit CC, the game should disregard the CC fov command you just typed in and revert to whatever the game set at launch, regardless of Bethini. Then again open the console and type "fov (desired number) (desired number)" so it looks like this as an example "fov 90 90" and see if it sticks after exiting CC.

 

CC = console command

Edited December 11, 2016 by magician16

[reddvilzz]

It would seem that you are using some kind of theme that is creating a second row of tabs that cuts off the settings. Maybe I can find a way to force my own theme so that doesn't happen.

Yes I'm using Ubuntu Themes. Not a biggie actually, I'll wait for your update. Thanks!

[DoubleYou]

FOV is somehow tied into the saved game, so the FOV INI tweak will not work on a save that started out with a different FOV. To get the correct FOV every time, you will have to start a new game. 

 

Or with Fallout 4 there is another trick you can try. Bethesda included a tweak that causes the game to launch specific console commands at startup. Simply add your FOV 95 tweak like this:

 

Fallout.ini

 

[General]

sStartingConsoleCommand=FOV 95

[DoubleYou]

@reddvilzz

@fantasma

 

I uploaded a test of a possible fix for you called BethINI Test in Miscellaneous. Please test and see if that fixes the issue.

[magician16]

FOV is somehow tied into the saved game, so the FOV INI tweak will not work on a save that started out with a different FOV. To get the correct FOV every time, you will have to start a new game. 

 

Or with Fallout 4 there is another trick you can try. Bethesda included a tweak that causes the game to launch specific console commands at startup. Simply add your FOV 95 tweak like this:

 

Fallout.ini

 

[General]

sStartingConsoleCommand=FOV 95

That seems like a bug, no? There is no reasonable reason for why Bethesda would do this. The fact that you can change FOV on the fly seems to indicate that this is one of those popular "Bethesda facepalm" moments :P

 

Thanks for the tip, I will try that out.

[magician16]

I haven't seen this mentioned but apparently you can only have one sStartingConsoleCommand tweak in your ini files. The first line under the category (i.e [general]) will take precedence apparently. I use a mod which needs sStartingConsoleCommand=prid and could not use sStartingConsoleCommand=fov 95 95

I got a popup saying that a mod missed a tweak in the ini files because my custom one took predesence. It suggested to change it so: sStartingConsoleCommand=prid;fov 95 95 which seems to work. You can apparently have multiple starting console commands, just put " ; " after each CC. This is very useful. Perhaps this is how bethini should handle FOV in Fallout 4? Thanks for the tool BTW DoubleYou.

[reddvilzz]

@reddvilzz

@fantasma

 

I uploaded a test of a possible fix for you called BethINI Test in Miscellaneous. Please test and see if that fixes the issue.

Thank you, I'll test it when I'm back home.

[magician16]

Here is some general feedback since I've been using Bethini for a while now. This is for Fallout 4 btw.

 

I think the gap between "high" and "ultra" is too big. For example, my PC can handle Fallout 4 on Ultra, if Godrays are set to Medium, shadow distance to High or Medium and a few other tweaks that really doesn't make much difference. When I choose ultra preset in Bethini, it sets all these values to ultra (well most of them) in the launcher (I just spent a while observing and checking what values Bethini sets the ini files and compared them and so on). If I choose "High" preset, it sets most of the option to medium/high that my PC can easily handle. I think most people are in a situation as me, their PC can handle Ultra as long as a few settings are set toned a bit, such as Godrays, Shadow Quality and Distance. I find that the AFx8 change in "High" preset unnecessary, decal quality going down to Medium, and that the shadow distance is still at "ultra" on high preset, this IMO should be exclusive to Ultra bethini preset and some of the view distance option to be closer to the ultra preset.

 

My suggestion would be this:

 

1) take the current Bethini Ultra and name it to something like "Ultra High". Then take that "Ultra High" and tweak a few values such as godray quality, shadow quality and distance and a few very high FPS hit tweaks to be less FPS tanking and name it to Ultra without touching the newly created "Ultra High". This would mean it would be like this; Low Preset, Medium Preset, High Preset, Ultra (toned down version of Ultra High that tones down very heavy FPS tanking tweaks) Preset and Ultra High Preset (formerly ultra preset)

 

2) Give the option to tweak values such as Godrays instead of it being "disable it or enable it". As example, I can play Ultra Preset as long as I tone down godrays quality, bethini only gives option to enable or disable, but a simple drop down menu could let you choose the quality of godray.

 

Additional suggestion is to add the option to enable/disable Weapon Debris feature in Bethini and choose quality. 

 

PS: I know I can select Bethini presets and then change stuff in the Launcher but I read somewhere by the author that this is not recommended and thus I base all of my feedback on this information. If I want to enable Weapon Debris or change Godrays quality after choosing a preset in Bethini, I would need to open the launcher (not recommended), or directly edit the ini files (which is not an option for non tech savy people, lol).

 

I am about to go to sleep and really tired, so I may have missed a few things or that all this could be non-sense. This is not an attack on the tool, just my personal thoughts and feedback and what I like to see. Let me know of any issues DoubleYou.

[DoubleYou]

Honestly, I have not spent as much time optimizing the Fallout 4 presets as I have for Skyrim. I had read somewhere that the Godrays were buggy if not set to ultra, but I didn't test that and took it at face value. Shadow distance I thought mostly irrelevant since everyone uses Shadow Boost. I will try to devote more time to optimizing the presets.

[magician16]

Thanks DoubleYou!