Guest Posted October 23, 2017 Posted October 23, 2017 You can increase vram size by adding gpus and ram. If you mean how to set end to use more vram open enblocal and change the value to what you want Cmd->dxdiag-> check vram, set in enb vram-2gb the equation listed in enblocal says it's "VRAM + RAM - 2048", does that mean add up total vram and TOTAL RAM??? then minus 2048? i got 16 gigs ram lmao so should i just set it as 10240 cuz 8000+16000-2048=21952, which is already way exceeding 10240... Of Course you should
prinyo Posted October 23, 2017 Author Posted October 23, 2017 There is a lot of confusion around all this, so here is a screenshot I just made. Following the STEP recommendations I downloaded the memory tools and after the Windows update the video memory for DX9 is no longer shown as 4GB. But it is still not the same as DX11: DX9 - 12 192 DX11 - 25 120 As you can see I have 16GB system RAM and a GPU with 4GB video memory. I have no idea how the number for DX11 is been calculated, but the control panel of my GPU agrees with the value for DX9 - it says "Total available graphics memory" - 12 247. And it seems it is been calculated as 4GB from the GPU + "Shared system memory". So if I did the calculation for VideoMemorySizeMb by adding the system and GPU RAM then I would get 16 + 4 = 20GB which would be a wrong value (according to all tutorials and guides). Instead (as I'm running Win 10) the correct value for VideoMemorySizeMb on my system is 12192, as shown by the VRamSizeTest tool for DX9. And as the author of ENB himself states on that page: "For DX9 version of ENBoost better to not set video memory size available above detected size by this tool."
Guest Posted October 23, 2017 Posted October 23, 2017 For the lowbrainers out there which don't even know about dx9 nor 11 there's a ini setting called autodetectvideomemorysize, you set it to true and don't need to worry about stuff you don't understand. Of course you shouldn't set it to more as the sizetest shows because you should subtract 2gb
prinyo Posted October 23, 2017 Author Posted October 23, 2017 For the lowbrainers out there which don't even know about dx9 nor 11 there's a ini setting called autodetectvideomemorysize, you set it to true and don't need to worry about stuff you don't understand. Of course you shouldn't set it to more as the sizetest shows because you should subtract 2gb So 16 + 4 - 2 = 12? Or what exactly are you talking about? Xaqq was asking about the formula "VRAM + RAM - 2048", which is obviously wrong at this time. There is a tool that tells you the value you need. Doesn't get easier than that.
Guest Posted October 24, 2017 Posted October 24, 2017 For the lowbrainers out there which don't even know about dx9 nor 11 there's a ini setting called autodetectvideomemorysize, you set it to true and don't need to worry about stuff you don't understand. Of course you shouldn't set it to more as the sizetest shows because you should subtract 2gb So 16 + 4 - 2 = 12? Or what exactly are you talking about? Xaqq was asking about the formula "VRAM + RAM - 2048", which is obviously wrong at this time. There is a tool that tells you the value you need. Doesn't get easier than that. Vram of gpu+system ram-2gb is total right
prinyo Posted October 24, 2017 Author Posted October 24, 2017 Vram of gpu+system ram-2gb is total right Ok, I will need to choose if I believe you or STEP and the ENB author as the difference in the value is quite big :-) 18GB vs 12GB I guess the 2GB offset comes from some time ago, it seems the confusion is around the "Shared system memory" - the part of the system RAM that can be used for graphics. Or something like this. Anyway, I have provided relevant links and a screenshot, people are free to do as they wish.
Guest Posted October 24, 2017 Posted October 24, 2017 Why not just use Windows 7 and avoid the issue altogether? Been using 7 since the beta ISOs and never had such dumb problems. Windows 7 stops getting updated in 2020, that's three years. And I'll still probably use it, most stable and secure OS Microsoft has released/
Guest Posted October 24, 2017 Posted October 24, 2017 Why not just use Windows 7 and avoid the issue altogether? Been using 7 since the beta ISOs and never had such dumb problems. Windows 7 stops getting updated in 2020, that's three years. And I'll still probably use it, most stable and secure OS Microsoft has released/ Dx12, Hardware, uefi, USB 3.0, m2 ssd and High Resolution Gaming. But you're totaly right if you say win7 is the best msoft ever made.
yatol Posted October 24, 2017 Posted October 24, 2017 I guess the 2GB offset comes from some time ago it's removing 1 gb for windows and 1gb for skyrim.exe (or something like that) should be fine for most won't be for the ones that have a few 100 mb esp, try war mods that put hundreds of npc, load the game with antivirus/mo that don't close itself on game load/something to film the game/whatever enbhost use 3 gb there's 1.5 gb to load you gave 6 gb to enbhost 3+1.5 < 6 no need to unload unused textures the first 200 mb are load, then 500, then 700, then 950, then ctd because there wasn't 6gb available for enbhost.exe crashing because there's too much to load for skyrim.exe was replaced by crashing because you try to use more ram than what you have
Shizof Posted October 24, 2017 Posted October 24, 2017 Vram of gpu+system ram-2gb is total right Ok, I will need to choose if I believe you or STEP and the ENB author as the difference in the value is quite big :-) 18GB vs 12GB I guess the 2GB offset comes from some time ago, it seems the confusion is around the "Shared system memory" - the part of the system RAM that can be used for graphics. Or something like this. Anyway, I have provided relevant links and a screenshot, people are free to do as they wish. That calculation method is outdated. You need to use whatever vramsizedx9.exe gives - 350 So if vramsizedx9.exe gives you 18000, you should use 18000-350 = 17650 that's it. Check out below link for proof from Boris himself: http://enbseries.enbdev.com/forum/viewtopic.php?f=28&t=4614&p=65336&hilit=VideoMemorySizeMb+limit#p65336
prinyo Posted October 24, 2017 Author Posted October 24, 2017 Check out below link for proof from Boris himself: http://enbseries.enbdev.com/forum/viewtopic.php?f=28&t=4614&p=65336&hilit=VideoMemorySizeMb+limit#p65336 Thanks for that link. Here is a quote from that thread: "Do not use any math, it's outdated. When mod reports in statistics available video memory and VRamSizeTest tool for dx9 - these are the only valid values. Old computations where based on old drivers for users with 4-8gb of ram. How much video memory required for OS itself still matters, mod ignore them in fullscreen mode, so much safer to subtract them from reported by the mod and VRamSizeTest." This confirms my suspicion that it was specific to a situation in the past since it seems the shared RAM is usually half of the total system RAM. I haven't seen a full explanation on how ENB Boost actually works. From what I understand Skyrim keeps it's graphics data (meshes, textures...) both in the VRAM and RAM. It uses exactly half less memory with ENB Boost running - I assume this is because in my setup there is need for only one instance of enbhost. So in therms of system RAM consumption the enb "moves" some of the assets of the game from the memory pool of the game to enbhost and then "streams" them to the game as needed. However it can't do that for the graphics memory so the game would still need to comply with the available graphics memory on it's own. Before the update on Win10 that was always 4GB. So even if the game would not crash because of exceeding the system RAM limit, it would be still limited to 4GB and would struggle to free memory if it is near the limit. This is now gone and the game has on average RAM/2 + VRAM to use and it is running more smoothly. This is what I have gathered from different explanations I have read online, if something is wrong I would appreciate a correction. Added: This understanding of the situation seems is confirmed by the experience shared in the post by krakken that follow below.
prinyo Posted October 24, 2017 Author Posted October 24, 2017 Why not just use Windows 7 and avoid the issue altogether? Been using 7 since the beta ISOs and never had such dumb problems. Windows 7 stops getting updated in 2020, that's three years. And I'll still probably use it, most stable and secure OS Microsoft has released/ Because for the past 2 years that has been the only free option when buying a new PC. Downgrades from 8 and 10 to 7 require paying for the OS. I for example went for 10 after been asked 140 euro to downgrade to 7 when I got a PC running the abomination known as 8.
Guest Posted October 24, 2017 Posted October 24, 2017 Just wanted to chime in with some anecdotal data. I recently ran into "black body diamonds/triangles" on my player characters skin after adding some additional outfits to my game. After some quick research I figured it might have to do with me brushing up against the VRAM limit for DirectX 9 when using Skyrim on Windows 10 with my GTX 1060 6GB. I was curious if applying the Fall Creators Update would do anything, so I tried it and changed my enblocal.ini to the new values boris tool for DirectX 9 reported. It seem to have worked like a charm. Consistently got that same graphical glitch when loading a specific save before installing the Windows update, but it hasn't happened so far after upgrading.
Guest Posted October 24, 2017 Posted October 24, 2017 Why not just use Windows 7 and avoid the issue altogether? Been using 7 since the beta ISOs and never had such dumb problems. Windows 7 stops getting updated in 2020, that's three years. And I'll still probably use it, most stable and secure OS Microsoft has released/ Dx12, Hardware, uefi, USB 3.0, m2 ssd and High Resolution Gaming. But you're totaly right if you say win7 is the best msoft ever made. dx12 = dx10 uefi - crap usb 3.0 - works on win 7 high res gaming - also works Win10 = WinMe aka Mistake Edition I hate Windows 10 with a burning passion. You have to activate it just to change colors. Updates break everything. You need specific hardware to use Face Unlock. The call it secure, but really they just lock things down and the user can't change them. I have to use Group Policy Editor to disable Windows Defender! Cortana is an annoying whore and the Action Center is just as bad. It comes preloaded with bloatware (Skype, Candy Crush, etc) and they didn't include prepackaged drivers for USB3! What in the goddamn! Windows 8.1 Pro includes drivers for USB3... DirextX 12 is being ported to 8 and 7 by some Russians last I heard. USB 3.0/3.1 works fine on my rig. High res gaming? I have a 1070 and game at a little over 2K. Windows 10 was the biggest mistake since Windows ME. Hell, even Windows 8 is better than 10. UEFI makes everything worse, Legacy mode is <3. I have all systems that need W10 booting in legacy mode. Why not just use Windows 7 and avoid the issue altogether? Been using 7 since the beta ISOs and never had such dumb problems. Windows 7 stops getting updated in 2020, that's three years. And I'll still probably use it, most stable and secure OS Microsoft has released/ Because for the past 2 years that has been the only free option when buying a new PC. Downgrades from 8 and 10 to 7 require paying for the OS. I for example went for 10 after been asked 140 euro to downgrade to 7 when I got a PC running the abomination known as 8. Paying for Windows 7? Lmao, use Windows Loader by Daz, KMS Pico, Activator by R@1N, they don't even change files, they just emulate a KMS server and make the OS think it's activated. That isn't even illegal. Cracking windows with a fake key is, but every ISO has its own key so there's no reason to have one with a KMS server emulator. You can even buy legit copies off Amazon for like $10 and come as a CD. Rip the ISO with ISO Magic or whatever and install it to a USB. Or just grab the ISO from M$FT's website with a key from the Net and then use a KMS emu. Tons of people who run Windows in a VM use KMS emus.
27X Posted October 24, 2017 Posted October 24, 2017 There is a lot of confusion around all this, so here is a screenshot I just made. Following the STEP recommendations I downloaded the memory tools and after the Windows update the video memory for DX9 is no longer shown as 4GB. But it is still not the same as DX11: ram.jpg DX9 - 12 192 DX11 - 25 120 As you can see I have 16GB system RAM and a GPU with 4GB video memory. I have no idea how the number for DX11 is been calculated, but the control panel of my GPU agrees with the value for DX9 - it says "Total available graphics memory" - 12 247. And it seems it is been calculated as 4GB from the GPU + "Shared system memory". So if I did the calculation for VideoMemorySizeMb by adding the system and GPU RAM then I would get 16 + 4 = 20GB which would be a wrong value (according to all tutorials and guides). Instead (as I'm running Win 10) the correct value for VideoMemorySizeMb on my system is 12192, as shown by the VRamSizeTest tool for DX9. And as the author of ENB himself states on that page: "For DX9 version of ENBoost better to not set video memory size available above detected size by this tool." The author also states to always set expand64 to true, which generally does nothing on systems only using enb and actively harm any setup using memory reallocation (ANY setup using ANY memory reallocation), so best and repeated testing would be your navigation point, not Mr. Vorontsov, who's own rig is almost 6 years old and has had little replacement parts, and thus no testing on other parts aside from those few people he trusts, which is a far far shorter list than you'd surmise from reading the forums. You also have to account for windows antiquated need to mirror vram in ram, which they have yet to remove.
nufndash Posted November 2, 2017 Posted November 2, 2017 Just wanted to chime in with some anecdotal data. I recently ran into "black body diamonds/triangles" on my player characters skin after adding some additional outfits to my game. After some quick research I figured it might have to do with me brushing up against the VRAM limit for DirectX 9 when using Skyrim on Windows 10 with my GTX 1060 6GB. I was curious if applying the Fall Creators Update would do anything, so I tried it and changed my enblocal.ini to the new values boris tool for DirectX 9 reported. It seem to have worked like a charm. Consistently got that same graphical glitch when loading a specific save before installing the Windows update, but it hasn't happened so far after upgrading. I decided to do the update also, but it started 4 hours ago and still hasn't finished, did your update take a looooong time also? I have never had a update take this long so I am afraid I did something wrong, but after waiting 4 hours already, I'm afraid to do anything that might set me back to 0.
jimmywon34 Posted November 8, 2017 Posted November 8, 2017 is there any legit media creation tool floating around of windows 7, I have an old iso of it with the product key I had from awhile back, but I'd have to find it plus i'm not sure what tools I need to install it correctly from an iso file and get it onto a usb to boot from.
pinky6225 Posted December 3, 2017 Posted December 3, 2017 DX9 fix has been pushed out to regular win10 users now, getting 16224 returned on the test instead of 4064
johntrine Posted December 3, 2017 Posted December 3, 2017 1st. does it work well? 2nd is the win 10 exclusive?
nb097 Posted December 3, 2017 Posted December 3, 2017 1 hour ago, johntrine said: 1st. does it work well? 2nd is the win 10 exclusive? Works great for me. No issues seen so far. Not sure I follow on "is it exclusive?". If you mean, is it only for certain versions, I don't think so, but I could be completely wrong.
johntrine Posted December 3, 2017 Posted December 3, 2017 2 hours ago, nb097 said: Not sure I follow on "is it exclusive?". If you mean, is it only for certain versions, I don't think so, but I could be completely wrong. you know. like how a few softwares and updates are ONLY available for windows 10 cos microsoft's being an asshole edit- checked it out and sure enough. it's only for win 8 and 10. on the other hand, don't know if the memory problem was something ONLY in windoes 8 and 10 or all of them. soooo ya.
pinky6225 Posted December 4, 2017 Posted December 4, 2017 On 03/12/2017 at 1:15 PM, johntrine said: 1st. does it work well? 2nd is the win 10 exclusive? Not noticed a difference tbh Its standard win10 (i.e. dont need to have opted in to anything to get it) so it should have come like other updates, the bug only existed in win10's handling of directx9 to my knowledge for it to be fixed
zupra Posted December 4, 2017 Posted December 4, 2017 On 24.10.2017 at 11:07 PM, krakken said: Just wanted to chime in with some anecdotal data. I recently ran into "black body diamonds/triangles" on my player characters skin Same happened to me and the reason was that i had disabled expandsystemmemoryx64.
jimmywon34 Posted December 9, 2017 Posted December 9, 2017 On 12/4/2017 at 1:01 PM, zupra said: Same happened to me and the reason was that i had disabled expandsystemmemoryx64. doesn't setting that to true cause crashes for you? It has for me in the past, I've read on several guides that it conflicts with memory patch fixes such as crash fixes, SSME or SKSE memory patch
guk Posted December 9, 2017 Posted December 9, 2017 Been testing a bit, seems to run like a charm. Using Snapdragon Prime ENB with uGrids 7, i could run around testing stuff for half an hour. Then changed speedmult to 1000 and ran/flew around in circles across half the map for like 10 minutes, still no CTD. Before the memory fix, the game would just get random framerate drops (especially when looking at the town center in Riverwood, or the farms south of Whiterun) and eventually CTD when you run around too much. Also the issues where landscape doesn't switch from LOD to the actual textures seems to be fixed. There actually was one CTD on load, though on a savegame where i had removed around 100 mods and tested some settings to fix the mouse lag. On 3.12.2017 at 6:17 PM, johntrine said: you know. like how a few softwares and updates are ONLY available for windows 10 cos microsoft's being an asshole edit- checked it out and sure enough. it's only for win 8 and 10. on the other hand, don't know if the memory problem was something ONLY in windoes 8 and 10 or all of them. soooo ya. Well the bug fixed in this update was only there in Windows 10, and ONLY for DX9 applications. Also keep in mind that DX9 is a standard from 15 years ago, so the vast majority of old games never had issues on Win10 since games couldn't use 4GB anyways.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.