It’s not going to do anything for your crashing.
If you didn’t see that, you aren’t benefiting. Or are happy using RAM instead of VRAM for video things (which is slower, mind you) – and again, used more than 8 GB total for video stuff (that is, you would see: skyrim allocating up to (VRAM of your card or 4 GB, whichever is lower), and ENBoost allocating (all the rest of your VRAM and RAM up to 4 GB total).Have more than 8 GB of VRAM on your card, and used it all.It’ll be amusing to see if it comes out before or after SKSE64. Windows does a loooot of testing, as they must (remember they’re forcing us to download these patches whether they work or not!). This fix will take a long time to be widely available – probably not until next year.This generally decreased the total amount of memory available to hold things for both ENB and TESV to use, lessening the benefits from ENBoost (those benefits being less stuttering and smoother loading, potentially preventing missing texture bugs, particularly when using a high percent of your video card’s total VRAM). and ENBHost.exe could access up to 4 GB of memory (RAM and VRAM). If you were on Windows 8/10, TESV.exe could access up to 4 GB of VRAM (I think). ENBHost.exe could hold things that TESV.exe could use, freeing up VRAM and generally making the game run more smoothly.
What this means is … if you were on Windows 7 (where it worked correctly), TESV.exe could access all your VRAM, and ENBHost.exe could access up to 192 GB of memory (RAM and VRAM). We recently received news (via screenshots of a reddit private conversation) that Windows devs have confirmed a patch for the dx9 VRAM allocation bug in Windows 8/10 and that it will be in the next insider build.
0 kommentar(er)
