TES Skyrim 0.192

[DigitalPrinceX]

Test 29 has no more brightness bugs. Tested with and without memory fix mode.

[ENBSeries]

Thank you!!! Don't run away, i'll check out everything again and post new test (guess for memory on AMD too).

[jones81]

Jopp Test 29 reached the finish line.
Memory fix for AMD would be fantastic

[ENBSeries]

Okay, looks clear. Now grab that test 29 and show me graph with memory fix enabled and disabled, if you AMD card owner (or NVidia if you have CTD even now).

[jones81]

So it looks to me.

[DigitalPrinceX]

My result



Test ran for 3 min. The big rise at end is where i kept lot of object in view. Did not crash, i just exited.

[CruNcher]

@Boris
you are right but it's not the system itself per se i tested carefully now, and im sure the crash for the older ENB versions is caused by a setting in my new enbseries.ini that the old ENB versions doesn't like for my System.

I didn't found out which one yet but i guess it's one of the hardware related parameters the default enbseries.ini of 119 for example doesn't crash but if i use my ini from 192 it crashes after tesv.exe start so on ENB initialization i tested with both Wrapper and Injector same result
And that it crashes on ENB initialization might be a indication that the crash could be caused by one of the hardware related parameters.

It doesn't seem to be one of the hardware related options that let previous versions crash with the new .ini

could it be

//

commenting as i use those in my enbseries.ini sometimes, though that was also in @ the time of 119 if i remember right and didn't caused any problems ?

or could it be the new options (to much to parse for the old enb versions ?)

or the added no space parts of these new functions

[RAIN]
Enable=true
EnableAntialiasing=true
EnableSupersampling=true
MotionStretch=0.5
MotionTransparency=0.0
[WEATHER]
EnableMultipleWeathers=false
[TIMEOFDAY]
Enable=false
DawnDuration=2.0
SunriseTime=7.5
DayTime=13.0
SunsetTime=18.5

my .ini 17,5 kb
default 119 .ini 5,61 kb
default 192 14,8 kb

also the default 192 ini doesn't crash so it could be also any option and it's value maybe, that will be hard to debug
i better try to create a clean new .ini based on the default, to make sure none of the commenting or maybe some strange formating however that found it's way in is causing the crash.

so maybe the old versions have a problem to parse these big files on initialization, or stumble over some functions ?

[KuroTenshi]

Thank you for everything Boris !!!

Memory fix works as supposed to be (for Nvidia at least). I had 1gb freed (1.7 max gb instead of 2.7gb max).
The only ways of improvements I see are an advanced precaching system (for example : artificially increase view distance for caching next elements but not display them until being at the real distance specified in config. Obviously, it has to be conditional, regarding consumed memory at the moment. Can decrease FPS but improve stability and limit stuttering) to prevent stuttering and a better support of AMD gpus.

For this moment it's already very good !!!

[ENBSeries]

jones81
DigitalPrinceX
Looks like AMD card don't want to use more than 1 gb my way. Give me some time, i'll post test or verdict, the problem is that any other memory fixing methods only decrease performance (stuttering).

CruNcher
I know that wrong parameters or syntax in config may produce crashes, but can't find what exactly.
Comments must be not in same line as parameter itself, then type of comment can be any, even withou // or ;.
Spaces do not affect anything. Important only is no spaces in value (may or may not work) or category name.

[jones81]

Yes but have only 1gb for tests not useful