Mig35 Posted August 9, 2019 Share Posted August 9, 2019 (edited) Can somebody help me with the right ini settings for the enb local. I had some stuttering in the game ? For now I switched of "UsePatchSpeedhackWithoutGraphics" so I could play further but without ENB. There was no stuttering anymore so logically assumed the problem was in the ENB. I did some tweaking based on a guide from nexus/youtube but then my game crashed on the menu screen. I think it should be possible however to adjust the Enblocal in such a way I can get rid of the stuttering and use ENB. (I had been using an ENB before with lots of mods and this installation does not differ that much from the one before. Maybe I overlooked/forgot something) ENB: Vividian ENB with purity and lots of graphic mods (list will follow if needed)ENB 0.389 (Before I used ENB 0.279 might this make any difference?) GPU: geforce gtx 960 2gb vram12gb ram My enblocal.ini settings [PROXY]EnableProxyLibrary=falseInitProxyFunctions=trueProxyLibrary=[GLOBAL]UsePatchSpeedhackWithoutGraphics=trueUseDefferedRendering=trueIgnoreCreationKit=true[PERFORMANCE]SpeedHack=trueEnableOcclusionCulling=true[MEMORY]ExpandSystemMemoryX64=trueReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=512VideoMemorySizeMb=1920EnableCompression=falseAutodetectVideoMemorySize=false[THREADS]DataSyncMode=0PriorityMode=0EnableUnsafeFixes=false[MULTIHEAD]ForceVideoAdapterIndex=falseVideoAdapterIndex=0[WINDOW]ForceBorderless=falseForceBorderlessFullscreen=false[ENGINE]ForceAnisotropicFiltering=trueMaxAnisotropy=16ForceLodBias=falseLodBias=0.0EnableVSync=falseAddDisplaySuperSamplingResolutions=falseVSyncSkipNumFrames=0[LIMITER]WaitBusyRenderer=trueEnableFPSLimit=falseFPSLimit=60.0[iNPUT]KeyCombination=16KeyUseEffect=123KeyFPSLimit=36KeyShowFPS=106KeyScreenshot=44KeyEditor=13KeyFreeVRAM=115KeyBruteForce=66KeyDepthOfField=118[ADAPTIVEQUALITY]Enable=trueQuality=0DesiredFPS=20.0[ANTIALIASING]EnableEdgeAA=trueEnableSubPixelAA=falseEnableTemporalAA=false[FIX]FixGameBugs=falseFixParallaxBugs=trueFixParallaxTerrain=trueFixAliasedTextures=trueIgnoreInventory=trueFixTintGamma=falseRemoveBlur=falseFixSubSurfaceScattering=trueFixSkyReflection=trueFixCursorVisibility=trueFixLag=false[LONGEXPOSURE]EnableLongExposureMode=falseTime=1.0BlendMax=0.0 SKSE memory patch (ini) is present as well. Who knows what to do? Edited August 9, 2019 by Mig35 Link to comment Share on other sites More sharing options...
saurusmaximus Posted August 10, 2019 Share Posted August 10, 2019 Do you have the memory edits set with SKSE? If not, you should because that will help. Set ExpandSystemMemoryX64=falseSet ReservedMemorySizeMb=256For VideoMemorySizeMb=use the memory tool on the ENB website to find this setting. Link to comment Share on other sites More sharing options...
Mig35 Posted August 12, 2019 Author Share Posted August 12, 2019 (Without ENB the game looks stunning already. I am just a spoiled (old) kid :P) Do you mean by: memory edits, adjusting this one in the memory patch? (SKSE.ini) DefaultHeapInitialAllocMB=768 It seems that I have 26944 mb available....?? Have no clue on how that is calculated. It was the DirectX 11 calcutation. I have DirectX 12 (should i downgrade?) @Saurusmaximus: As we speak, I just configured the enblocal based on your specs. Filled in the 26944mb. The stuttering is gone already. Still anything needed to do with the SKSE.ini? Link to comment Share on other sites More sharing options...
poncington Posted August 13, 2019 Share Posted August 13, 2019 i use this and everything works pretty wellhttps://wiki.step-project.com/Guide:ENBlocal_INIi believe you use the dx9 calculation and subtract 350 if using windows 10. from the link above Download Boris's VRamSizeTest tool, run VRamSizeDX9.exe, and note the number it shows after "Video memory available." Then, if you are running Windows 7, subtract 170 from that number; if you are running Windows 8/8.1, use the number provided by the tool; and if you are running Windows 10, subtract 350 from that number. Use the result as the variable here. (Example 1: If VRamSizeDX9.exe shows 10240, and you're running Windows 7, you should subtract 170 to get 10070. Example 2: If VRamSizeDX9.exe shows 4064, and you're running Windows 8, you should use 4064. Example 3: If VRamSizeDX9.exe shows 11168, and you're running Windows 10, you should subtract 350 to get 10818.) For more information, please refer to this post. Link to comment Share on other sites More sharing options...
Mig35 Posted August 13, 2019 Author Share Posted August 13, 2019 @poncington: this is exactly what I did. Only used the DX11 calculation and filled in the found number. It never ran so smooth ever and I do not experience any problems. Although I read somewhere there is a limit and that is top. If you fill in a higher number, that has no use. I think I simply leave things the way they are now. Still: I wonder if it makes any more difference if I change this on from the SKSE.ini into a higher number: DefaultHeapInitialAllocMB=768 On the other hand: If it ain't broke, don't fix it. Link to comment Share on other sites More sharing options...
saurusmaximus Posted August 13, 2019 Share Posted August 13, 2019 Download Boris's VRamSizeTest tool, run VRamSizeDX9.exe, and note the number it shows after "Video memory available." Then, if you are running Windows 7, subtract 170 from that number; if you are running Windows 8/8.1, use the number provided by the tool; and if you are running Windows 10, subtract 350 from that number. Use the result as the variable here. (Example 1: If VRamSizeDX9.exe shows 10240, and you're running Windows 7, you should subtract 170 to get 10070. Example 2: If VRamSizeDX9.exe shows 4064, and you're running Windows 8, you should use 4064. Example 3: If VRamSizeDX9.exe shows 11168, and you're running Windows 10, you should subtract 350 to get 10818.)This is no longer true. One of the updates to Windows 10 got rid of the DX9 memory cap. @poncington: this is exactly what I did. Only used the DX11 calculation and filled in the found number. It never ran so smooth ever and I do not experience any problems. Although I read somewhere there is a limit and that is top. If you fill in a higher number, that has no use. I think I simply leave things the way they are now. Still: I wonder if it makes any more difference if I change this on from the SKSE.ini into a higher number: DefaultHeapInitialAllocMB=768 On the other hand: If it ain't broke, don't fix it.If your game is running smooth, there is no reason to increase the SKSE value. As for the VideoMemorySizeMb in your enblocal.ini, I believe the max value is approx 14000 (don't have the exact figure handy); setting it higher won't help anything, though I don't think it hurts either. Link to comment Share on other sites More sharing options...
Mig35 Posted August 13, 2019 Author Share Posted August 13, 2019 Nonetheless: there was and is a lot of confusion still about the VideoMemorySizeMB. http://enbseries.enbdev.com/forum/viewtopic.php?f=28&t=4614&hilit=VideoMemorySizeMb+limit https://steamcommunity.com/app/72850/discussions/0/41973821380180612/ https://www.reddit.com/r/FalloutMods/comments/3tzbkh/enboost_how_to_determine_the_correct_vram_setting/ These are only three examples. It seems in my case: with 2gb physical vram and 12gb ram, a lot of extra mb's seem to be possible from the harddrive. The available VideoMemorySizeMB seem to be a whooping: 27232 mb....(?)The assumed max of 10240 shows up in a lot of articles. Seen no smoke coming out of my machine so far.... Link to comment Share on other sites More sharing options...
Grospolina Posted August 16, 2019 Share Posted August 16, 2019 @poncington: this is exactly what I did. Only used the DX11 calculation and filled in the found number.That's wrong then. Use the DirectX9 version, since Skyrim Classic is a DirectX 9 application and doesn't support DirectX 11. The two tools can report different numbers. Skyrim SE supports DX11, but ENB for it doesn't have this option. Link to comment Share on other sites More sharing options...
Deleted79169328User Posted June 17, 2020 Share Posted June 17, 2020 I'm using the latest version and I don't even see any of these options in the enblocal file. Was there a change or am I missing something? This is all that shows up. Trying to improve my FPS and my memory usage but I don't even have the option for the latter. [PROXY]EnableProxyLibrary=falseInitProxyFunctions=trueProxyLibrary= [PERFORMANCE]SpeedHack=trueShaderCache=true [ENGINE]ForceVSync=trueVSyncSkipNumFrames=0 [LIMITER]EnableFPSLimit=trueFPSLimit=61.0 [iNPUT]KeyCombination=16KeyUseEffect=123KeyFPSLimit=36KeyShowFPS=106KeyScreenshot=44KeyEditor=13KeyDof=118 [ANTIALIASING]EnableEdgeAA=false [DITHERING]EnablePrepass=falseEnablePostpass=trueAmountPrepass=1.0AmountPostpass=1.0 [FIX]FixReflectionTrees=trueDisableFakeLights=trueFixReflectionThirdPerson=trueFixBlackHair=trueIgnoreInventory=trueDisableGameDOF=false[FILE]ScreenshotFormat=0[GUI]HighResolutionScaling=true Link to comment Share on other sites More sharing options...
Mig35 Posted June 27, 2020 Author Share Posted June 27, 2020 Dhampir! Maybe it might be a good idea to put your question in a separate topic. The last posts before yours are from 2019 and I did not notice your post either.I have switched to Skyrim SE and I am not using ENB anymore. I do not have a solution right now but i recommend to take some time to investigate this: https://wiki.step-project.com/Main_Page Link to comment Share on other sites More sharing options...
Recommended Posts