Correct Enblocal Settings

[prizner]

So I was installing SkyRealism using the enb guide and I noticed the site https://www.iparadigm.org/pages/pnenb/ENBoost.html used for getting parameters for the memory section of enblocal no longer works. After some digging I found there were some formulas to come up with the needed information but as I am still unsure if I fully understand them I was wondering if anyone here could help? I have gtx 680 4GB and 12GB of ram with a i7 980x. Thanks!

[viper37]

I'm also on Windows 8.1 with a similar setup (780ti instead) and i have no issues with the Gui.Please ensure you have UsePatchSpeedhackWithoutGraphics=false and check your UAC settings. If it doesn't work try running the .exes in Windows 7 compatible mode.

I see the console, I just can't do anything with it.  No matter where I click, I get nothing, no menu is expanded, so I can't see what's under "memory" or anything else.

 

I'll try win7 compatible mode tonight.  It has never fixed anything for me in the past, but will try anyway. :)

Edited September 5, 2014 by viper37

[Nozzer66]

Which cursor are you pointing with? The one you want to use in the ENB console is the hourglass looking one.

[viper37]

@afonik

compatibility mode didn't work either for .264, disable display scaling on high DPI settings didn't work with either .262 or .264 (i mean, it has no effect).

 

 

@Nozzer66: I tried both cursors.  First the hourglass, then the other.  I tried changing:

ForceBorderless=trueForceBorderlessFullscreen=true 

to false for both, to no avail, it only made things worst.

 

 

Anyhow, I have upgraded to ENB 0.264, and whenever I try to have UsePatchSpeedhackWithoutGraphics=false instead of true, my game simply refuses to start.  I get a message from AMD Catalyst saying "Access to video hardware has been disabled for this application" and my loading screen is frozen, the mouse cursor is frozen in the center, pressing ENTER does not work to load a game, and I can't even see the usual menu to load, start a new game or quit.

 

Could be because I wasn't using any ENB mod (only ENBboost) and it now won't work without it, if I set the line to false.

 

I'll try tomorrow night to find & install one, see if it works that way, if I can get ENB to report how much memory it is using.  I just hope I won't taint my results.

Edited September 6, 2014 by viper37

[TechAngel85]

Set this DisableDriverMemoryManager=false to true and then UsePatchSpeedhackWithoutGraphics=false to true and see if that allows you to start the game.

[keithinhanoi]

I can't speak to the AMD Catalyst error issues you're having, but I made a quick video showing how to interact with the ENB GUI and where to find the Video Memory statistics.

 

https://www.youtube.com/watch?v=0LXIJ-Sc-FQ

Edited September 6, 2014 by keithinhanoi

[justjr]

Very usefull indeed!

[viper37]

Set this DisableDriverMemoryManager=false to true and then UsePatchSpeedhackWithoutGraphics=false to true and see if that allows you to start the game.

didn't work, and I wasn't the only one.  From ENbdev news:

 

 

AMD users have bugs with 0.264, so i put back 0.262 to downloads until this will be found and fixed.

[viper37]

I can't speak to the AMD Catalyst error issues you're having, but I made a quick video showing how to interact with the ENB GUI and where to find the Video Memory statistics.https://www.youtube.com/watch?v=0LXIJ-Sc-FQ

thanks for the vid.  I reverted back to 0.262, tried again, with Win7 compatibility, but it's not working for me.

I was doing things correctly, but clicking on a menu produces no results.  I can move the windows around, I can disable some, but clicking on highlighted 'profiler' simply flicks the screen, but the menu never opens.

 

I'll try some ENB preset mod to see if it changes my interactions with the ENB console.

 

 

 

 

Btw, My ful Enblocal.ini:

 

 

 

[PROXY]EnableProxyLibrary=falseInitProxyFunctions=trueProxyLibrary=other_d3d9.dll[GLOBAL]UsePatchSpeedhackWithoutGraphics=falseUseDefferedRendering=falseIgnoreCreationKit=trueForceFakeVideocard=false[PERFORMANCE]SpeedHack=trueEnableOcclusionCulling=true[MULTIHEAD]ForceVideoAdapterIndex=falseVideoAdapterIndex=0[MEMORY]ExpandSystemMemoryX64=trueReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=768VideoMemorySizeMb=EnableCompression=trueAutodetectVideoMemorySize=true[WINDOW]ForceBorderless=trueForceBorderlessFullscreen=true[ENGINE]ForceAnisotropicFiltering=falseMaxAnisotropy=16ForceLodBias=falseLodBias=0.0AddDisplaySuperSamplingResolutions=falseEnableVSync=trueVSyncSkipNumFrames=0[LIMITER]WaitBusyRenderer=falseEnableFPSLimit=falseFPSLimit=10.0[iNPUT]//shiftKeyCombination=16//f12KeyUseEffect=123//homeKeyFPSLimit=36//num / 106KeyShowFPS=106//print screenKeyScreenshot=44//enterKeyEditor=13//f4KeyFreeVRAM=115[ADAPTIVEQUALITY]Enable=falseQuality=1DesiredFPS=20.0[ANTIALIASING]EnableEdgeAA=falseEnableTemporalAA=falseEnableSubPixelAA=falseEnableTransparencyAA=false[FIX]FixGameBugs=trueFixParallaxBugs=trueFixAliasedTextures=trueIgnoreInventory=trueFixSsaoHairTransparency=trueFixTintGamma=trueRemoveBlur=falseFixSubSurfaceScattering=trueFixSkyReflection=trueFixCursorVisibility=true

 

[phazer11]

Added the enblocal stuff to a spoiler. Man I wish it were easier for new users to add spoilers. It's

[spoiler] Text Here [/spoiler]

by the way.

[viper37]

Sorry, I never think of using this tag.

[afonik]

Are you using Skyrim Performance Monitor? If it is the case then ENB will work but not the console.

[viper37]

Are you using Skyrim Performance Monitor? If it is the case then ENB will work but not the console.

Ah, yes, I am.  I don't think I thought of trying without Skyrim Performance monitor.

[viper37]

Ok, so first, I disabled my RAMdrive.  I have some computer problems (it enters sleep, does not seem to wake up, possibly due to an electrical problem).

 

Then I tried launching Skyrim from MO as usual (not using Skyrim Performance Monitor), I had no success.  Tried without using SKSE, no success.

 

Now, I found a workaround.  Clicking the profiler menu and hitting enter, I noticed some flicker, and some quickly fading numbers.  So, now, I keep enter pressed and I can see the numbers flickering and being visible just long enough to kinda guess what is behind.

 

And now after alt-tabbing a few times, it seems I can see clearly... The trick seems to keep pressing ENTER, alt+tab when I can see something, go back, the menu is expanded.

So here is what I've got, in order of appearance, top to bottom:

 

 

Under the menu 'profiler'

Available video memory: 2539

Mod video memory usage: 0

Total video memory: 4064

 

Under the menu MEMORY, I have:

ReservedMemorysizeMB: 768

VideomemorysizeMB: 4064

 

 

 

 

 

Hope that helps.

As for Keithinhanoi comment on CTDs when I runout of memory, this seems to happen when I leave other memory intensive software running in the background.
Shutting everything off, as I usually do results in no crashes at all during gameplay.

[keithinhanoi]

And now after alt-tabbing a few times, it seems I can see clearly... The trick seems to keep pressing ENTER, alt+tab when I can see something, go back, the menu is expanded.So here is what I've got, in order of appearance, top to bottom:

Under the menu 'profiler'Available video memory: 2539Mod video memory usage: 0Total video memory: 4064 Under the menu MEMORY, I have:ReservedMemorysizeMB: 768VideomemorysizeMB: 4064 

  Hope that helps.As for Keithinhanoi comment on CTDs when I runout of memory, this seems to happen when I leave other memory intensive software running in the background.Shutting everything off, as I usually do results in no crashes at all during gameplay.

Wow, I'm sorry that it was such a pain to view those ENB memory values - but it is still quite useful to see what ENB has alloted. It seems that in your case at least, ENB has calculated the "right" amount of memory - just a little under 4GB, which matches the amount of VRAM on your R9 290x. Perhaps Boris has changed things under the hood recently so that the AutodetectVideoMemorySize feature works better.

 

When I'm not so slammed with work, I'll test AutodetectVideoMemorySize out on my new setup, and report back here.

[viper37]

Cool.  Eventually, maybe we'll arrive at some kind of generalized guidelines for everyone :)