TES Skyrim 0.139

[ENBSeries]

I'm using hotkeys when debugging the game, so can't miss issue which you have (but for special debug build of the mod, will do test in release version later). If GUI work when you can't press hotkey any more or it's not appear, effects do not work too? If so, then mod internal data deleted itself (let me know about this) and it's not functioning. Also try to delete additional configuration file and if this helps or not, let me know result. No changes made which may affect input directly, so this only two possible scenarios comparing to 0.136

[Phinix]

All versions (except 0.139) which use EInteriorFactor in shaders have a bug and it's affect only those modified shaders, which use this variable. I will not return to old versions and will not post them, old means obsolete, abandoned, no longer supported.

Not to be annoying, but I'm still a bit confused. Does this mean that the order of the variables in the lerp() for methods using EInteriorFactor simply need to be reversed in enbeffect.fx in order to get v0.139 working with these older shaders?

I shall test that theory...

EDIT: OK, so I inverted the order in my custom enbeffect.fx shaders for all uses of EInteriorFactor. For example, lerp( op1, op2, EInteriorFactor ) becomes lerp( op2, op1, EInteriorFactor ). However, this did not solve the problems I've been having in this version.

v0.138
v0.139
v0.139 inverted EInteriorFactor

So, I am just trying to understand why the appearance is so different between v0.138 and v0.139. I can't tell from your description that anything you changed should alter appearance so radically, so I am assuming there must be something configured wrong somewhere. But going by the release notes and inverting the EInteriorFactor variables didn't solve it, so I am at a roadblock.

If you say it is normal the appearance change so much in this release I will simply work on adapting my config to look like it did in the new system, but things are SO different I am still not sure if something is wrong and don't want particularly to dive into a complete remix unless I know for sure this is normal.

[excalibuurr]

What settings are affected by useoriginalobjectsprocessing?

[spyridon]

Instead of complaining about how different things look compared to older versions, why don't you just fix it yourself? We have an in-game GUI editor for this now. Just be sure to pause the game (I use the console command (~) so that I can still see the full result above the console window) then use SHIFT+ENTER to start tweaking the file to the way you like it.

Also, that looks like your SSAO is possibly set too strong, maybe tune it down a bit. Or it could be the ambient lighting, so turn it up / turn down the lightingcurve. Looks like the SSAO more than the Ambient lighting.

Because it's not a localized issue, and it's inconsistent based on location and time of day, other users in this post have similar issues, and Boris said he didn't do anything to change the look between versions, which gives the impression there is some form of bug or unintended change. But for some reason instead of getting support about these issues, I'm getting rude responses and being called lazy, when the developer said himself it should not look different, so I have no idea why these problems are happening.

Phinix is having the same exact issues, and doesnt understand why this is happening either. And neither of us are able to get decent support from the developer without insults.

Another example? I brought to Boris's attention that supported driver versions are not available anymore, for videocards that he says he supports (4xx series), and this is the response:

spyridon
I don't want to comment stupid things you said.

What about when Boris said in the Kalicola topic:

It's drivers issue, but i can't do anything at this moment to fix, if nvidia will do non beta drivers with this bug or it will continue to appear in several future driver updates, then seems walkaround must be done from my side

I brought to attention that the drivers are now non-beta, and he said himself he would do a workaround. To make it worse older driver versions aren't supported anymore, and won't work for most newer games, and all the older enbseries versions have been removed, so now there's a large amount of people out of luck either with serious visual problems or without support at all because their video cards are too new??

But apparently saying he was going to fix it if it was non beta, was a lie, and I'm called stupid because of it?

[chan]

I'm using hotkeys when debugging the game, so can't miss issue which you have (but for special debug build of the mod, will do test in release version later). If GUI work when you can't press hotkey any more or it's not appear, effects do not work too? If so, then mod internal data deleted itself (let me know about this) and it's not functioning. Also try to delete additional configuration file and if this helps or not, let me know result. No changes made which may affect input directly, so this only two possible scenarios comparing to 0.136

What I mean is, the Load button in GUI, and the hotkey, both work for a limited time.
They will reload the enbeffect.fx file, as well as the other files that are part of ENB.
Later, only the enbseries.ini file will update, no other ENB files will update (enbeffect.fx, enbeffectprepass, etc.)

[Mistappears]

chan I had exacltly same problem as you.
You need to let the game create new ini files for you, make sure you delete the render info file also. Wrote a much more detailed explination but apparentley the forum thinks I was trying to spam as I am a new user. Remember to make a back up though.

I am using driver 306.97.

[trustinall]

@spyridon a bunch of us are having problems lately and it can be frustrating, but please keep it civil, boris doesn't owe us anything, yet has always come through with a stable version sooner or later, so patience is the key here and not calling names

about 0.139 - i'm having some sort of "color adaption" whenever i tab in out of the game or enter and leave the save menu with this version, it's desaturarted for a few seconds then gets back to what i think is normal saturation - can anyone else confirm this?

also i can't access my old account anymore and had to make a new one, sorrey

[mindflux]

Exactly what trustinall said. Boris is the sole developer of ENB with limited resources, and since he's not a big-money company with vast testing processes, it's obviously impossible to test ENB with all possible system configurations. Since he's also not a psychic, there's no way he can know what causes any given issue with your specific system configuration. I don't want to sound rude, but you need to learn to help yourself, and to be honest, that's the name of the game in modding - if you can't handle it, better play the vanilla game.

I will look into the issues reported. As always, before reporting test with stock ENB files included in the redistributable - if you don't experience the issue, the problem is most likely in the custom enbeffect.fx code. And for the record, I'm using Nvidia driver version 310.70 with no issues whatsoever with stock ENB files.

[chan]

Trustinall, I saw that with 138, but not with 139.

chan I had exacltly same problem as you.
You need to let the game create new ini files for you, make sure you delete the render info file also. Wrote a much more detailed explination but apparentley the forum thinks I was trying to spam as I am a new user. Remember to make a back up though.

I am using driver 306.97.

Thank you for the tips. I will try this tomorrow.
What ini files are you referring to exactly? Those in the Documents directory?

[mindflux]

Yes, the files in My Games/Skyrim. Rename them first for reference, then start the launcher.