use FPS limit in the enblocal.ini instead to set your FPS limit.

_________________
W10*I7 6700K*MSI Z170A MPower Gaming Titanium*2x Titan X Pascal*32GB 3600mhz DDR4* 3x 512GB Samsung Pro SSD*ASUS ROG Swift PG348Q

New test: disable ENB, run Skyrim with SPM.

Results: FPS and stuttering improved (or back to acceptable levels) - 2 CTDs: 1 when changing locations, 1 which looks like >3.1Gb limit crash. Also, Skyrim Performance Monitor on-screen display is still dim and pixelated!

Analysis: Clearly, ENB is not the problem. Maybe not driver/hardware problems either. I think there is something in skyrim.ini / skyrimprefs.ini that is conflicting both ENB and SPM. That would be my fault - I have been tweaking both of them wildly in hopes of stopping >3.1Gb CTDs (I have too many). ENB v0.193 resolves the >3.1Gb crashes but costs performance.

Question: Are there any ini settings that should or should not be used with ENB? Or any ENB ini settings that were changed between 21/7 v0.193 and test36 (these may have fixed whatever was wrong with my inis before)?

_________________
Intel 3570k - 8GB RAM - Gigabyte AMD Radeon HD 7950 3GB GDDR5 - Win 7 x64
Skyrim 1.9.32.0 - no DLC - modded with S.T.E.P.

lol your test make no sense. So you tested without ENB and got better performance and less stutter ? DUHHH

As for skyrim.ini and skyrimprefs.ini tweaks, it takes a lot of time. It took me weeks to get everything perfect and balance between visual and performance. Same goes for enbseries.ini settings.

One way to test if it's your skyrim.ini and skyrimprefs.ini issue causing your CTD, copy them to a different location. Open the skyrim launcher and redo your settings inside the launcher. After run the game. If it stills CTD, than might want to check your load order, papyrus log for scripts error, or your mods for incompatibility.

_________________
W10*I7 6700K*MSI Z170A MPower Gaming Titanium*2x Titan X Pascal*32GB 3600mhz DDR4* 3x 512GB Samsung Pro SSD*ASUS ROG Swift PG348Q

CruNcher
Injector is harmless, you just don't know how to use it. When it injected mod in to the game, it can be unloaded, because no longer in use. I can't disable it or exit from it, because more than one process can run at single time or after each other.

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

Drallen
Nothing changed for test 36 in ini setting. And version which is on site is much better for AMD cards than 36, same stuttering, but less memory usage, the only cost is crash because of incompatibility with memory monitor.

EDIT: can you run the game without patch at all? Or it's the case when everything toggled on to get crash at any cost?

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

ok so injector.exe detects tesv.exe start hooks enbseries.dll into it's win32 process and then injector.exe gets destroyed from enbseries.dll is not possible ?

_________________

Hi all
First thank you for all your work Boris
and all comunity.

so Im not an expert but I see you want some tester for the new code and i will be happy to help you if i can.
i have an amd card perhaps , so if i can help with this hardwre i will be .
with the 192 release the memory usage=true work well but hit my fps -20
I will test the 0.193 this night ...

CruNcher

Hard to understand for me. If you mean unload itself when injected - impossible, because skyrimlauncher.exe (at least) also must be injected. You need manually exit from injector after game started. Huh, i have an idea, but not 100% sure. May be send message from the mod after several seconds when it's started and running effects?

HighPitchedMcFly
Thanks

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

No, it's bad idea to exit automatically from injector, found several conditions when such behavior is wrong.

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

Ok @ least you thought about it now if you see problems in your architecture with this approach that's another thing, i guess i will test too what these conditions would be
Because im really lazy to always close enbinjector.exe so i let it run and get angry about it's cpu usage in the background letting my CPU Fan speed up Intels Speedstep and Fan Controll System is very proactive on such things

i mean i know your statepoint about it since several posts now though still i find it not a thing to overlook





i find this still a lot for a simple injection pooling, and Intel agrees with it, especially the kernel usage is massive, i mean you even beat firefox in its background consumption
i surely wouldn't be proud about this 1st place, the cpu cycles run upwards like crazy, and that surprises me im used to very good efficient windows code from russian devs over the past, and your enb is that too but that enbinjector idle behavior is still crazy to me

Im also not sure how one of the Kernel 3rd Party security layers should interfere here and might causing this overload nothing impossible of course.

_________________