Deleted14423759User Posted December 31, 2015 Share Posted December 31, 2015 Hey, I have 16gb RAM 2gb VRAM on a Windows 10 OS. What is the ideal amount to add to the enblocal.ini file? I'm reading all over the place and there seems to be a different answer for everything. Link to comment Share on other sites More sharing options...
IsharaMeradin Posted January 1, 2016 Share Posted January 1, 2016 STEP's guide to setting up ENBoost mentions (and provides link) a tool that you can use which will give you the value that you should use. Their instructions further state that specific operating systems should subtract an additional amount from the tool's result. Link to comment Share on other sites More sharing options...
Novem99 Posted January 1, 2016 Share Posted January 1, 2016 16384 (16GB RAM) + 2048 (2GB VRAM) - 2048 = 16384 So in your case it would be 16384 BUT!!! this value maxes out at 10240. So set it to 10240. Link to comment Share on other sites More sharing options...
blattgeist Posted January 1, 2016 Share Posted January 1, 2016 (edited) Quote from STEP: "Boris normally recommends setting VideoMemorySizeMb to be equal or a little under your actual amount of VRAM." Quote from STEP: "64-bit systems with >8 GB of system RAM should set this equal to (Total Available Graphics Memory- [170 (for Win7) or 350 (for Win8+)]." Means, simple take your GPU memory and subtract 170 or 350, depending on your operating system. For a 2GB GPU with Windows 10 that would be 2048-350=1698MB. Edited January 1, 2016 by blattgeist Link to comment Share on other sites More sharing options...
Deleted14423759User Posted January 1, 2016 Author Share Posted January 1, 2016 (edited) okay, that's where i'm confused. do I subtract 350 from my 'dedicated video memory' (2048) or..do I subtract 350 from my 'total avalible graphics memory (10192) which do I put: 1698 or 9842? Edit: I've read that it's done differently (subtract 350 from total graphics memory not video memory) if one has 8gb of RAM or greater and there's 16gb in my case. Edited January 1, 2016 by Guest Link to comment Share on other sites More sharing options...
bcofer Posted January 3, 2016 Share Posted January 3, 2016 I have been following this thread with great interest. I also have a 2 gb VRAM and 16 gb RAM and can play on either WIN 10 or WIN 7. In my case, though, I'm nursing along a GTX 660 so just trying to use ENBoost. As illustrated both in this thread and the internet at large, different people have put a great deal of thought and testing into the question and have come up with greatly different answers. For example, using the tool linked above, I'm told 4032 for DX9 and 29056 for DX11. I thought Skyrim was a DX9 game, but the skyrim directory (before skyrim/data) includes a DX10 folder. Also watched dptheslothking's video here on Nexus, and got yet another number. As noted above, I have both WIN 7 and 10 on different hard drives. Using 7 so I can make a restore point a day. Skyim game freezes, no keys do anything, hard reboot. I used to say I spent more time playing out mods than playing Skyrim. Now I spend more time scanning big-ass hard drives than I do trying out mods. Link to comment Share on other sites More sharing options...
Deleted14423759User Posted January 3, 2016 Author Share Posted January 3, 2016 (edited) For anyone with 8GB of RAM or greater, I'm pretty sure the official number to put in the VideoMemorySizeMb is your 'total available graphics memory' minus 350 (for Windows 8 or 10) or minus 170 (Windows 7) Correct me if I'm wrong, please. That's why I made this topic. Edit: Check out this video on Youtube that I got the information from. it's in-depth configuration of that enblocal.ini. It's revised and pretty recent. http://www.youtube.com/watch?v=zYqFihHMD4w&feature=iv&src_vid=9VNuwJecWZI&annotation_id=annotation_2872088939 Edited January 3, 2016 by Guest Link to comment Share on other sites More sharing options...
Adarcer Posted January 3, 2016 Share Posted January 3, 2016 (edited) Use the number the dx9 version of the tool gives you and for win 7 -170 for win 8-10 -350The other formulas are wrong and will cause problems later onDo not set this any higher than this or your enbhost will be starved to perform its extra memory features. Edited January 3, 2016 by Adarcer Link to comment Share on other sites More sharing options...
ParsaFaramarzi Posted December 11, 2016 Share Posted December 11, 2016 Use the number the dx9 version of the tool gives you and for win 7 -170 for win 8-10 -350The other formulas are wrong and will cause problems later onDo not set this any higher than this or your enbhost will be starved to perform its extra memory features.but the step enboost page said:VideoMemorySizeMb=<integer in MB>Users should download and run Boris's VRamSizeTest tool. Run the VRamSizeDX9.exe. Windows 7 users subtract 170 from the value provided and use that value. Windows 8/10 users use the value provided. so if we are a win10 user we shouldnt actually subtract it from 350 and use the exact amount :confused: Link to comment Share on other sites More sharing options...
twiztedmongoloid Posted December 11, 2016 Share Posted December 11, 2016 Use the number the dx9 version of the tool gives you and for win 7 -170 for win 8-10 -350The other formulas are wrong and will cause problems later onDo not set this any higher than this or your enbhost will be starved to perform its extra memory features.but the step enboost page said:VideoMemorySizeMb=<integer in MB>Users should download and run Boris's VRamSizeTest tool. Run the VRamSizeDX9.exe. Windows 7 users subtract 170 from the value provided and use that value. Windows 8/10 users use the value provided. so if we are a win10 user we shouldnt actually subtract it from 350 and use the exact amount :confused: Why revive an ancient thread? Too answer your question tho according to the people at STEP you should use the value provided if you have windows 8 or 10. 4064 is the maximum. At one time it was suggested to do 4064-350=3714 I used to do that but was told otherwise on the STEP forums. Link to comment Share on other sites More sharing options...
Recommended Posts