![]() I also do not have that SSME mod, or anything similar, installed. It did not give any errors when running the installer and it is strange that the game could run fine without ENBoost and the "broken" DX11, but I am not complaining. ![]() I downloaded the DirectX file from here and ran it. I do remember reading on the ENB forums an issue for one user with Skyrim crashing at startup and they resolved it by re-installing DirectX 9.ĮNB does hook into DX9, even if only using ENBoost, so that's something to try. If not, then I only have one other suggestion at the moment. Just to double-check though - are you using SSME (the other implementation of the Sheson Memory patch fix) by chance? ![]() Apparently, AMD has done something in their drivers to use DX12 under win10 that seems to break the 0. I had been using the 0.279 fine, but like an idiot I updated the Win 10 video driver for my AMD. If running through the vanilla Skyrim launcher, without SKSE, then that rules out any influence of the Sheson Memory patch fix (because it's provided as part of SKSE if using the skse.ini settings), and you don't need Memory Blocks Log because it's only necessary to check on how the memory patch is working out in game. Out of desperation I tried stepping down on the ENB, I removed 0.279 and loaded 0.262 and Viola that worked. The enblocal.ini looks fine to me, and although reducing VideoMemorySizeMb would be a good idea, that value of 18432 won't cause Skyrim to crash.
0 Comments
Leave a Reply. |