TES Skyrim 0.193

[charlievoviii]

charlievoviii
What? So VandersApp only don't have issue? Hmm, i just added news to the site and posted message to author of Skyrim Performance Monitor.

yep, can't use it with SPM OSD which is when you checked "Attempt support for custom D3D9.DLL". It works if you uncheck that which you won't get the OSD from SPM but still get the monitor data from the software like the screenshot. I wouldn't doubt that VandersApp have it unchecked. Also noticing lots of micro stutters.

ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=true

[ENBSeries]

VadersApp
If on screen display was ever visible properly with enbseries or other d3d9 mods?

[CruNcher]

CruNcher
Show me content of your enbinjector.ini file

[LIBRARY]
LibraryName=enbseries.dll

[TARGETPROCESS]
ProcessName0=tesv.exe
ProcessName1=
ProcessName2=
ProcessName3=
ProcessName4=
ProcessName5=
ProcessName6=
ProcessName7=
ProcessName8=
ProcessName9=
ProcessName10=
ProcessName11=
ProcessName12=
ProcessName13=
ProcessName14=
ProcessName15=


@Xilandro

Could you test it too your system and mine are not very far away from each other

[charlievoviii]

SPM work perfectly for me up until enb v188, anything after v188 = CTD

[Behelit]

Test 37

Skyrim + SPM with ""Attempt support for custom D3D9.DLL" ON

Settings:
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false

Crash

[Drallen]

Test 37 works with SPM (support for experimental dll option CHECKED) with the following options:

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=false
DisableDriverMemoryManager=true

Of course, I'm getting >3.1Gb crashes, but it works

[charlievoviii]

Test 37 works with SPM (support for experimental dll option CHECKED) with the following options:

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=false
DisableDriverMemoryManager=true

Of course, I'm getting >3.1Gb crashes, but it works

So the game fully loaded and you saw the SPM OSD showing the ram reaching over 3.1 gig before it crash ?

also the reason you reach such a high RAM usage cause you have ReduceSystemMemoryUsage on FALSE

[ENBSeries]

CruNcher
I don't know. The code of injector creates threads for each process from enbconvertor.ini and separately waiting those processes,so in your case it's just one thread + main thread in sleep state. When injected, waiting thread enter sleep state and stay in it each 0.1 sec with interruption only to check if process is not running any more. If code cost cpu, this means that functions of checking process is running are in times slower than on amd cpu or Sleep(time) function from WinAPI not work properly. Both cases are wrong and hard to believe. Just unload injector after job done, i don't have solution.

charlievoviii
Try attached version, but it's 188 actually modified, so backup enbseries.ini first. Is it have OSD visible?

[ENBSeries]

Arrr crap, forgot again

EDIT: file deleted

[ENBSeries]

And this is another test of crashes with performance monitor, is it work?

EDIT: file deleted