What do you mean as "debug parameters"? I just added them to Fallout New Vegas and found that some are crosslinked with each other (two parameters for night/day will be divided from single, but don't remember now which one).
PS: also found some mistakes with parameters of config, when developed version for fallout nv...
This sounds like you found a bug in version for skyrim, when developing version for fallout:nv
So I thought, you might debug it.
Seems I misunderstood you.
ENBSeries wrote:What do you mean as "debug parameters"? I just added them to Fallout New Vegas and found that some are crosslinked with each other (two parameters for night/day will be divided from single, but don't remember now which one).
I believe you may be referring to AmbientLightingIntensityDay / Night. From my testing, they both affect Day for sure, not so sure if the same is true for Night but seems likely if they are indeed crosslinked.
Also there seems to be a threshold with their associated Curve parameter which limits the highest value that still has an effect. In other words, if AmbientLightingCurveDay is set beyond a certain value (not sure of the cap), increasing AmbientLightingIntensityDay has no effect beyond a specific value (again not sure of the exact value but not radically high).
Like I've mentioned before, it sure would be nice if someone included what the max/min of these values were as well. I know, more work.
CosmicBlue wrote:
PS: also found some mistakes with parameters of config, when developed version for fallout nv...
This sounds like you found a bug in version for skyrim, when developing version for fallout:nv
So I thought, you might debug it.
Seems I misunderstood you.
Did you? What exactly was changed? All we get is some half assed English muble jumble of this and that. Without a changelog we are flying blind here and it's starting to piss me off. I'm having issue's with this release that I didn't have with the last beta, and because I don't know what the fuck was changed I don't know how to adjust it or roll back if necessary. Hours of trial and error by us could be reduced to 15 minutes by the creator making a simple changelog.
Oh and BTW, you can thank CoT for figuring out how to minimize the clear water bug enb has been suffering from.
Sorry but this frustration has been building for months regarding this. Spend less time worrying about updating and more time documenting and you'd be amazed at the level of detailed feedback you would get allowing you to push forward instead of always backtracking.
Johnny5srv wrote:Did you? What exactly was changed? All we get is some half assed English muble jumble of this and that. Without a changelog we are flying blind here and it's starting to piss me off. I'm having issue's with this release that I didn't have with the last beta, and because I don't know what the fuck was changed I don't know how to adjust it or roll back if necessary. Hours of trial and error by us could be reduced to 15 minutes by the creator making a simple changelog.
Oh and BTW, you can thank CoT for figuring out how to minimize the clear water bug enb has been suffering from.
Sorry but this frustration has been building for months regarding this. Spend less time worrying about updating and more time documenting and you'd be amazed at the level of detailed feedback you would get allowing you to push forward instead of always backtracking.
8 august 2012
Updated 0.114 beta for TES Skyrim without version change. Fixed mistakes of configuration parameters.
There is a "changelog". It'S just not called "changelog".
I know it's hard without documentation, I've ask for some help/advises myself.
But now, after I figured it out, I say: no documentation needed, I'd rather want new features.
Johnny5srv wrote:Did you? What exactly was changed? All we get is some half assed English muble jumble of this and that. Without a changelog we are flying blind here and it's starting to piss me off. I'm having issue's with this release that I didn't have with the last beta, and because I don't know what the fuck was changed I don't know how to adjust it or roll back if necessary. Hours of trial and error by us could be reduced to 15 minutes by the creator making a simple changelog.
Oh and BTW, you can thank CoT for figuring out how to minimize the clear water bug enb has been suffering from.
Sorry but this frustration has been building for months regarding this. Spend less time worrying about updating and more time documenting and you'd be amazed at the level of detailed feedback you would get allowing you to push forward instead of always backtracking.
8 august 2012
Updated 0.114 beta for TES Skyrim without version change. Fixed mistakes of configuration parameters.
There is a "changelog". It'S just not called "changelog".
I know it's hard without documentation, I've ask for some help/advises myself.
But now, after I figured it out, I say: no documentation needed, I'd rather want new features.
I think Boris should hire an assistant to do these things. Like an intern perhaps... Last thing we need is another lazy game developer entering the marketplace. Boris, I love you (no homo), but you know first hand how frustrating working with those lazy developers work can be... Bugthesda?
Johnny5srv
I don't see any sence in changelog, it only required for game engines and developers who use it or for users who have some issue and waiting for it to be fixed (in this case i'm releasing fix silently, if possible). Yes i'm lazy and hate write description, but also i don't like to spend several hours to do this and then have headache and red eyes for several days. Experience also say that users even never open readme file, so why to bother with writing something to it?
Compare enbseries.ini of previous version and generated after running updated mod, then do changes to new parameters.
Boris, I love you (no homo), but you know first hand how frustrating working with those lazy developers work can be... Bugthesda?