Vanilla Skyrim loads data that should go into VRAM, but not regular system RAM, into both. Whether this is an issue because of Microsoft or something else. Originally posted by Candid:To make an example of this, currently ENB which allows you to use past the 32-bit allocation of memory for Skyrim (as it is a 32-bit game) reportedly doesn't work on Windows 10 OS's, but used to on the previous Window operating systems. What this means, I don't really know, but it could entail some problems for older mods whose authors have stopped working on. And to further add some cynicism here, supposedly old mods will need to be run through a newer version of CK in order to work correctly. Of course, to sound less like I'm kissing ass, there will probably still be a ♥♥♥♥♥♥ of bugs that will only be corrected through mods. Which is good news because Skyrim remastered is confirmed to be 64-bit, run on DX-11, which means it will support newer and more modern hardware. To make an example of this, currently ENB which allows you to use past the 32-bit allocation of memory for Skyrim (as it is a 32-bit game) reportedly doesn't work on Windows 10 OS's, but used to on the previous Window operating systems. Not to say ENB doesn't make your game look amazing or isn't coded very well, but it was done only because the developer (Boris) is considered somewhat of a mad genius who could do this despite limited access to the game unlike say a developer from Bethesda. Which means all the new graphical shaders will be much more optimized than ENB. I'm no developer for games so I'm probably talking out my ass here, but the people in Bethesda have access to developmental tools for the game that the modding community probably doesn't. Hell yes, all those mods for graphics come with a cost on performance.

Bethesda skyrim remastered mods