STEP guide missing misinformation on moding ENBlocal.ini

[Gethal]

Hello,

 

I am following the latest STEP guide and I just downloaded ENBoost.

I am tweaking the ENBlocal.ini file as instructed and there is a warning at the bottom that says:

 

Warning: Do not change the settings in the [THREADS] section! These are for special case use only. You are 99% not likely one of those special cases! The section should remain as follows:

[THREADS]
DataSyncMode=0
PriorityMode=0
EnableUnsafeFixes=false

 

The warning assumes that my ini says that but when I open it for the first time all it has under [THREADS] is

 

DataSyncMode=1
PriorityMode=0

 

I have not touched and will not touch it but I just wanted to let you know. This is from the latest version of ENBoost (v0.305)

Should I leave it like that?

[DoubleYou]

Change it to 0. Don't know why it says to not change it when it definitely must be changed.

[TechAngel85]

What the hell, Boris?! Why is DataSyncMode defaulted to 1? I'll notify him that it should be changed. Values should reflect what is in the note. I had no idea it was defaulted to being 1.

 

EDIT:

I've posted a message to him to see if he'll change it.

[TechAngel85]

I've updated the warning text to be more specific.

[Gethal]

Should I add the line:

 

EnableUnsafeFixes=false

 

?

[Tinnota]

When I download ENB v0.305 and extract the enblocal.ini file from the WrapperVersion folder, it tells me DataSyncMode=0.

[Kesta]

As long as you have EnableUnsafeFixes=false, DataSyncMode and PriorityMode are ignored anyway.

EnableUnsafeFixes is set to false by default. If not written in the enblocal.ini at game-start, it'll be considered false and added as such to the enblocal.ini under [Thread] like you'd expect.


So long story short : Nothing to worry about, everything is properly disabled with the default file.

Edited April 13, 2016 by Kesta

[TechAngel85]

When I download ENB v0.305 and extract the enblocal.ini file from the WrapperVersion folder, it tells me DataSyncMode=0.

Correct. When I checked before messaging Boris, it was indeed set to 1. I messaged him and he's set it to 0 now saying this:

 

Okay. But DataSyncMode=1 is better in general, 0 - disables fix. It's all about messing with skyrimprefs.ini and cpu/os combo.

 

 

As long as you have EnableUnsafeFixes=false, DataSyncMode and PriorityMode are ignored anyway.

 

EnableUnsafeFixes is set to false by default. If not written in the enblocal.ini at game-start, it'll be considered false and added as such to the enblocal.ini under [Thread] like you'd expect.

 

 

So long story short : Nothing to worry about, everything is properly disabled with the default file.

With the given quote from Boris, are you sure about that statement?

[Kesta]

 

With the given quote from Boris, are you sure about that statement?

Can you link the "given quote" you're talking about ?

I'm just relying on programming logic and general observation of how the whole enbseries work (i.e. for everything else but a single exception it follow the programming logic I'm relying upon) :

For everything, you have an on/off toggle. When toggle is off, the whole feature is disabled, when the toggle is on, parameters are used to configure this feature.

Edited April 13, 2016 by Kesta

[TechAngel85]

Start and following quote: https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4891&start=150#p71078

 

Topic mostly about THREADS section: https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4880

[DoubleYou]

Hmm interesting that he would say that 1 is better in general, considering the number of cases we have had lately where it caused issues.

 

And the EnableUnsafeFixes setting is for some other fixes that cause issues with other things, notably the map, when enabled and is separate from the other settings. See the various news posts on his site for details.

[TechAngel85]

I knew that. Was just letting Kesta figure it out on his own. Haha!

 

He only says 1 is better because it fixes one or two places he found that the game crashes 100% of the time. If users run into that, they can turn it on for that part of the game and then turn it back off after.

[DoubleYou]

Did he say what those two places were?

[TechAngel85]

Did he say what those two places were?

It's Boris...so no. ::

[Hackfield]

Actually, EnableUnsafeFixes is not related to DataSyncMode nor PriorityMode. 

The [Thread] section was introduced in the very first release of v303, then he added those fixes enabled by default in a ghost version (v303 from feb 22th), but due to some bugs reports, Boris removed it (all without changin versions).

 

Added

https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4880&start=20#p69961

 

Removed

https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4880&start=20#p69966

 

Then I requested (complained) to add it again (he have it removed because some users had problems scrolling the worldmap, but I didn't and that fix improved the stuttering a lot), so he added it again in v304 as a toggeable parameter

 

Added back

https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4887#p69991

 

 

Edit: note to self, read the entire thread before posting

Edited April 15, 2016 by Hackfield