TES Skyrim 0.166

[ENBSeries]

RLY? v149:


Исправления нет и быть не может, таковы модели и движок игры, объяснять не вижу смысла.

[MOTOSXORPIO]

Sorry Boris. I'll leave well enough alone. Thanks for your efforts.

[Dinkledorf]

@Boris - read your post on the main page regarding weather change triggers allowing for different configs per weather and how that would lead to a rather large number of potential configurations. You could use the weather classification (of which there are 4) coupled with time of day (again 4, but am not sure you have access to time of day i.e. Dawn, Day, Sunset, Night) which still leads to 16 combinations, lol. Or just night and day per classification which leads to 8. Personally, I think it would be sufficient to combine the classifications as :

1. Pleasant and Cloudy = Pleasant
2. Rainy and Snow = Storm

And couple the above with Night and Day. This yields 4 configs which should be better manageable, maybe. Note there is also a "None" classification which is used but not sure where, I think its used for Emittance for some Lights and other Objects and not as actual weather.

Question, how are you thinking of phasing in a config? Does the engine provide you with data regarding its own weather transition and percentage of mix so that the configs can be interpolated over a period of time and thus not be a sudden transition?

A config system such as one above would require to be applicable in ENBSERIES.INI, would the values be available in ENBEFFECT.FX as well? If you only use the classification mentioned above, there would only need to be one more variable exposed to enbeffect, I believe.

[ENBSeries]

Game engine have weather transition info which i can use to interpolate own variables.
Don't know about enbeffect.fx, how blend it between several files, may be new variables will be added. Interpolation of enbseries.ini is simple task, i'm planning to make many copies of it in some folder, each copy is id of weather f.e.
Weather type like snowy, cloudy, rainy, sunny is not enough. Their exact id types is what i'd like to use. Time of the day also available and i thought long time ago about sunset and sunrize separation, but it's not simple, because of short period of time when they occur.
Seems i'm moving to things which nobody need, so after few days i'll give up.

[Dinkledorf]

I certainly wouldn't say nobody needs these ideas Boris, I believe they have a lot of value. I am especially interested in the Sunrise/Sunset separation. As to their duration, not difficult to increase by modifying Climate. I have changed this already for my setup to increase the length of day by a number of hours as well as increasing the duration of both Sunrise and Sunset, a couple of sliders in Climate.

There are currently about 40 weathers in Skyrim (hundreds if one uses CoT) which would could lead to somewhat of a nightmare for managing configurations. Certainly flexible as hell but not sure its manageable. How about another file that allows grouping of weathers under a specific label and then have a config for each label? Something like that would allow it to be as granular as one wants it to be. By default, Weather ID is used unless grouped under a different label.

Something like:

Weather1 = 0010A240, 0000081A, 0010A244
Weather2 = 000C821E
etc.

On another note, if time of day is available, can this be used to govern Night/Day instead of sky brightness? Its tough to get a really bright horizon at Sunrise/Sunset without throwing Night/Day values out the window. The current settings could be replaced with the hours that define start and end of day, for example:

[NIGHTDAY]
TimeStartSunrise=5:00
TimeStartDay=8:00
TimeStartSunset=17:00
TimeStartNight=20:00

Lol, just shooting for the moon here.

[ENBSeries]

With weather it's a nice idea, much better than many files for each weather.
The time is problematic anyway, i don't know how to switch between sky based day/night detector and time dependent. Incompability with old presets? New parameter to use real game time which is off by default? And where parameters for each part of the day, in enbseries.ini, but part of them unused (sunset,sunrize)?

[tapioks]

I just want to chime in and say I think these are very good and useful ideas. I understand the concerns about having too many variables. For me the biggest concerns for weather are just clean/nice vs rainy/snowy; if by default all the weather vanilla weater types could be grouped like this it would be amazing. True time-based day/night cycles would be amazing. Separate settings for sunrise and sunset as suggested earlier in this thread sounds great too

[Dinkledorf]

With weather it's a nice idea, much better than many files for each weather.
The time is problematic anyway, i don't know how to switch between sky based day/night detector and time dependent. Incompability with old presets? New parameter to use real game time which is off by default? And where parameters for each part of the day, in enbseries.ini, but part of them unused (sunset,sunrize)?

Ha, yep this would definitely break old config unless another switch was added to determine which day/night method is chosen and then, of course it would double the number of those settings although half would always be unused.

Not sure what you mean by "not knowing how to switch between time and sky based". There is a caveat with the time based method unless weather is also considered. Mid-day on a sunny day is not the same as mid-day on a stormy day in terms of lighting.

If you go with the weather idea, then it seems to me that there is no need for day/night lighting settings in the current enbseries at all since they should all be in the individual weather configs (with the possible exception of Interior based settings).

Hmm, no matter how this is sliced, seems to break current configs. You could have a master switch in ENBSERIES for either weather or non-weather based config, keep current day/night lighting values in enbseries that are active only if non-weather is selected, otherwise use associated weather configs? Its complicated but does provide compatibility.

I doubt I am being clear at all, its late. :mrgreen:

[valks666]

Why is it such a big issue if a new version is not compatible with older configs, can't they just use an older enb?

~Cheers

[ENBSeries]

It's the matter of performance and new effects, which can be created with helper mod.