Jump to content
  • 0

ENB Graphics Enabled Can't load ANY save file


Question

Posted (edited)

I've looked up potential causes for this everywhere and I find bits and pieces of information but nothing for this specific issue. I'm not professional with ENB but I'm not new to it = )

 

(I don't know how to add "spoilers" or I'd make one)

 

When I try to load a save file with ENB Graphics enabled I instantly CTD (not even a piece of a load screen). Weird part for me.. I can start a new save game, play WITH ENB Graphics, have 55 to 60fps everywhere, smooth camera, no stutter, all over the map things seem to work wonderfully... but if I load a save file with ENB enabled... crash... I can save using the ENB, then turn enb off and load that save perfectly. I just can't load a save file with it. 

-Does this with near 400 mods installed. Does this with only the official DLC and Alternate Start installed.

-Windows 10

-ENB 305 (292 does this as well)

-Runtime June2010 installed 

-SkyrimPrefs.ini is correct

-Skyrim.ini has iPresentInteveral=1

 

I'm hopefully off to sleep at the moment but any feedback would be greatly appreciated...

 

[spoiler=ENBLocal.ini]
[PROXY]
EnableProxyLibrary=false
InitProxyFunctions=false
ProxyLibrary=other_d3d9.dll
 
[GLOBAL]
UsePatchSpeedhackWithoutGraphics=false
UseDefferedRendering=true
IgnoreCreationKit=true
 
[PERFORMANCE]
SpeedHack=true
EnableOcclusionCulling=true
 
[MEMORY]
ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=128
VideoMemorySizeMb=4064
EnableCompression=true
AutodetectVideoMemorySize=false
 
[THREADS]
DataSyncMode=0
PriorityMode=0
EnableUnsafeFixes=false
 
[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0
 
[WINDOW]
ForceBorderless=false
ForceBorderlessFullscreen=false
 
[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
ForceLodBias=false
LodBias=0.4
AddDisplaySuperSamplingResolutions=false
EnableVSync=true
VSyncSkipNumFrames=0
 
[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=59.0
 
[iNPUT]
//shift
KeyCombination=16
//f12
KeyUseEffect=123
//home
KeyFPSLimit=36
//num /       106
KeyShowFPS=106
//print screen
KeyScreenshot=44
//enter
KeyEditor=13
//f4
KeyFreeVRAM=115
//B
KeyBruteForce=66
 
[ADAPTIVEQUALITY]
Enable=false
Quality=1
DesiredFPS=30.0
 
[ANTIALIASING]
EnableEdgeAA=true
EnableTemporalAA=false
EnableSubPixelAA=true
 
[FIX]
FixGameBugs=true
FixParallaxBugs=true
FixParallaxTerrain=false
FixAliasedTextures=true
IgnoreInventory=true
FixTintGamma=true
RemoveBlur=false
FixSubSurfaceScattering=true
FixSkyReflection=true
FixCursorVisibility=true
FixLag=false
 
[LONGEXPOSURE]
EnableLongExposureMode=false
Time=1.0
BlendMax=0.0

 

Edit: Added spoiler tag to enblocal.ini - Nebulous112

 

[spoiler]text[/spoiler]
Edited by Nebulous112
Added spoiler tag

7 answers to this question

Recommended Posts

  • 0
Posted

Hi Gamer Poets,

 

I have relied heavily on your videos to set up my game, thank you so much. In view of the quality information you provide to the gaming community I’m going to guess that your game set up is spot on. The people here are the experts (not me) so I’m sure they will help you sort it out, but I will relate the following story, maybe it will be helpful.

 

Recently, on my usually utterly stable gaming rig I chased every possible CTD cause, reducing aggressive settings, reduce mod load, start new game, etc. Two weeks I’m fighting with it and finally I think I’ve solved everything and it CTD’s. I go to bed thinking it must be hardware and fearing it’s the GPU. The next morning my rig is dead, unbelievably my Seasonic SS 1250X Gold PSU has failed. I know the rail voltages had been perfect so I had eliminated it from consideration. Luckily I had a spare, and for the past two weeks no CTD’s or other issues.

 

Skyrim on Win 10 runs on a knife edge, it doesn’t take much to make it fail. The above experience taught me a lot about the inner workings of Win 10 and how differs from other OS’s. It also reminded me to not assume anything.

  • 0
Posted

Well, I cannot say that I have ever heard of that issue before. I assume this has not always been the case for you? Enblocal.ini looks fine. You can load the saves without ENB graphics, correct? You could post your INI files, but I doubt there would be anything there that would cause saved games to CTD. You use Crash Fixes?

  • 0
Posted

Thank you guys =) I appreciate the responses.

 

I just switched from windows 7 to 10 (i had some stutter issues that I couldn't figure out so I just did a clean install of everything due to lack of time to troubleshoot, and the stutter was gone.. I was guessing it had something to do with drivers.. but onward) however, I had windows 10 and skyrim working before with enb without issue.

 

I tried with shesons memory patch and then i tried with various combinations of crash fixes. Nothing helped.

 

Sheson and Joe both mentioned to test with the .fx files removed... that didn't work, however, that made me think to remove the enbseries folder (vivid weathers... which worked fine for me on both OS's before) and replace both it and everything else with just the files from enb dev (still having vivid weathers, the mod, installed) and now things are working. They aren't "working" because I'm not getting the ENB graphics that I want... but i can now load saves without an issue... it appears that something either in the enbseries folder from vivid weathers or from the enbseries.ini is conflicting in ways that I don't yet understand how. It's hard to think that it would be a memory issue with the game running smooth as can be while playing all over the map (a few fps "drop spots" but nothing less than 50fps). 

 

Well, now that its narrowed down this far I'll continue on = )

  • 0
Posted

SOLVED:

 

Sheson mentioned to try deleting the .fx files but to leave the enbeffect.fx file installed because he believed that ENB needed it... well on the Vivid Weathers page it states that you need to removed all old .fx files... however, when I install Vivid weathers it does not come with any .fx files of its own (to be placed in the skyrim directory folder)... i put the .fx files from the enb dev default archive into the skyrim directory.... save files not loading fixed... everything works... i sent manga a message

 

PS: Thank you Nebulous for showing me how to create spoilers = )

  • 0
Posted

Thank you = )

 

Man... I .... this.... i mean.....

a clean OS install (perhaps another one because I think I want windows 7 back lol), full redo of the load order installation, massive amounts of emails with various folks, tested turning on and off individual settings (all in the enblocal.ini and a good amount in the enbseries.ini) .... I needed an .fx file.... well... onward we go = )

  • 0
Posted

This is interesting.  I had also all of a sudden been having a very strange CTD issue  - MY THREAD - on Windows 10 which started happening for no real reason a few days ago after 4 months of trouble free modding on an unchanged system. My eventual solution after four days of tearing my hair out (see my avatar pic to appreciate how funny that last comment was), although not ideal, was to replace the 305 ENB files with those from 262 (only the core 3 for ENBoost/Crash Fixes) and that miraculously cured my CTDs on load save/enter Helgen Keep.  I am putting it down to an NVIDIA driver update or something I can't find now hooking the dll.  I was resigned to having to use 262 without an ENB (using VW so no old presets are compatible) but I am now wondering if I could get 305 working again by adding enbeffect.fx into the /Skyrim directory?  I'll try when  get home.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.