hogsmaws Posted February 4, 2019 Author Posted February 4, 2019 I am using CrashFix12 SKSE Plugin Preloader i uninstalled JK completely but now i can't even diagnose that issue with this ENB Boost hurdle I can't get over.
Grey Cloud Posted February 4, 2019 Posted February 4, 2019 1 hour ago, hogsmaws said: should I delete the ProxyLibrary=other_d3d9.dll Yes. 1 hour ago, hogsmaws said: I get this You weren't using an ENB were you? You should get something like this. Your text should be in red, that's normal for ENBoost (I'm using an ENB). Obviously the ENBseries version will be different but it should be pretty much the same content ending with your video card. The line in your screenshot should the first line. Double-check what you have done as you appear to have gone wrong somewhere. In the meantime don't be installng or uninstalling anything until we get this problem resolved.
hogsmaws Posted February 4, 2019 Author Posted February 4, 2019 oh when i said i get this = that screen came up after the logo with the enb info top left and then the red text screen and then black and then some music and then CTD. but this is only if i have this setting: [GLOBAL] UsePatchSpeedhackWithoutGraphics=true if i have that set to false then it just CTD right at that logo screen.
zniachtl Posted February 4, 2019 Posted February 4, 2019 If you use Skyrim on Windows 10, then this is wrong: [MEMORY]ExpandSystemMemoryX64=falseReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=128VideoMemorySizeMb=27106EnableCompression=falseAutodetectVideoMemorySize=false Windows 10 only has this - for Skyrim that is (not that other game that isn't Skyrim): VideoMemorySizeMb=4064 (that is exactly 4GB VRAM minus 32MB) (that goes for ANY dx9 game, not just Skyrim, on Win8, Win8.1 and of course Win10)
Grey Cloud Posted February 4, 2019 Posted February 4, 2019 17 minutes ago, hogsmaws said: GLOBAL] UsePatchSpeedhackWithoutGraphics=true That is the correct setting for ENBoost. You are only using the memory management part and not the grahics enhancer of an ENB preset. Let's start from the beginning. You are not using an ENB? You were not using an ENB before these problems? You have installed "d3d9.dll, enbhost.exe, and enblocal.ini into the base Skyrim directory (do NOT copy into the 'Data' directory!)". You ran the vramrest prog for DX9 and made any adjustments required by your OS? Don't change ini settings willy-nilly. Read (yes, the dreaded r-word) the STEP guide and follow its advice. I'm struggling here because LL keeps going dog-slow and it takes forever to load.
Grey Cloud Posted February 4, 2019 Posted February 4, 2019 9 minutes ago, zniachtl said: Windows 10 only has this - for Skyrim that is (not that other game that isn't Skyrim): VideoMemorySizeMb=4064 Source for this? 1. Video memory is more than just what your card has. (Unless W10 is different) 2. S.T.E.P recommends -35 for W10.
bandygirl1 Posted February 4, 2019 Posted February 4, 2019 I had the same problem Hogs, and it was instantly solved by following the first post in this thread https://forums.nexusmods.com/index.php?/topic/3089504-fix-for-skyrim-crashing-instantly-with-enb-on-windows-10/page-1 Hopefully it helps.
hogsmaws Posted February 4, 2019 Author Posted February 4, 2019 36 minutes ago, bandygirl1 said: I had the same problem Hogs, and it was instantly solved by following the first post in this thread https://forums.nexusmods.com/index.php?/topic/3089504-fix-for-skyrim-crashing-instantly-with-enb-on-windows-10/page-1 Hopefully it helps. OMG that fixed my getting past the logo & the going near towns issue! *crying* thanks to all who helped and thank you bandygirl1 *crying* I hope to never have to go thru this again. *weeping* ?
bandygirl1 Posted February 4, 2019 Posted February 4, 2019 57 minutes ago, hogsmaws said: OMG that fixed my getting past the logo & the going near towns issue! *crying* thanks to all who helped and thank you bandygirl1 *crying* I hope to never have to go thru this again. *weeping* ? Np hun. So glad I could help ;).
Grey Cloud Posted February 4, 2019 Posted February 4, 2019 Not to take anything away from bandygirl1 but Psalam gave the link back in post #20. You really should consider taking up reading.
bandygirl1 Posted February 5, 2019 Posted February 5, 2019 49 minutes ago, Grey Cloud said: Not to take anything away from bandygirl1 but Psalam gave the link back in post #20. You really should consider taking up reading. OMG, now I feel bad, cause I didn't see his post either. *embarrassed*
hogsmaws Posted February 5, 2019 Author Posted February 5, 2019 thank you Psalm! i gave you a thumbs up ??
zniachtl Posted February 6, 2019 Posted February 6, 2019 On 2/4/2019 at 9:08 PM, Grey Cloud said: Source for this? 1. Video memory is more than just what your card has. (Unless W10 is different) 2. S.T.E.P recommends -35 for W10. I have a 1060 with 6G - why would I use LESS physical VRAM (minus 2GB) if Microsoft hadn't killed dx9 support with introduction of Windows 8 Last dx9 VRAM uncapped Windows is Win7 Now it's completely different with that other game because that uses dx11, but when it comes to Skyrim, Oblivion, Fallout 3 & NV, and a ridiculously large amount of games then 4G is the cap for "total" VRAM, doesnt matter if you have 2x 8G in SLI or a single 2G card combined with 2G regular SystemRAM
Grey Cloud Posted February 6, 2019 Posted February 6, 2019 9 hours ago, zniachtl said: I have a 1060 with 6G - why would I use LESS physical VRAM (minus 2GB) if Microsoft hadn't killed dx9 support with introduction of Windows 8 Last dx9 VRAM uncapped Windows is Win7 Now it's completely different with that other game because that uses dx11, but when it comes to Skyrim, Oblivion, Fallout 3 & NV, and a ridiculously large amount of games then 4G is the cap for "total" VRAM, doesnt matter if you have 2x 8G in SLI or a single 2G card combined with 2G regular SystemRAM That's not a source, just your garbled opinion. And what the hell is this mysterious 'other game' you keep referring to?
sila Posted February 6, 2019 Posted February 6, 2019 On 2/4/2019 at 2:56 PM, zniachtl said: If you use Skyrim on Windows 10, then this is wrong: [MEMORY]ExpandSystemMemoryX64=falseReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=128VideoMemorySizeMb=27106EnableCompression=falseAutodetectVideoMemorySize=false Windows 10 only has this - for Skyrim that is (not that other game that isn't Skyrim): VideoMemorySizeMb=4064 (that is exactly 4GB VRAM minus 32MB) (that goes for ANY dx9 game, not just Skyrim, on Win8, Win8.1 and of course Win10) Actually the 4gb limit for dx9 games has been fixed for a while now. http://enbseries.enbdev.com/forum/viewtopic.php?f=17&t=5493 From the Step project: VideoMemorySizeMb This sets the total memory that will be used for the ENBoost dynamic memory allocation. All available VRAM, except for the amount set with ReservedMemorySizeMb, will be used first, and if VideoMemorySizeMb is set to a value higher than total VRAM of the user's videocard, then ENBoost will use system RAM, if necessary, by running instances of enbhost.exe. Download Boris's VRamSizeTest tool, run VRamSizeDX9.exe, and note the number it shows after "Video memory available." Then, if you are running Windows 7, subtract 170 from that number; if you are running Windows 8/8.1, use the number provided by the tool; and if you are running Windows 10, subtract 350 from that number. Use the result as the variable here. (Example 1: If VRamSizeDX9.exe shows 10240, and you're running Windows 7, you should subtract 170 to get 10070. Example 2: If VRamSizeDX9.exe shows 4064, and you're running Windows 8, you should use 4064. Example 3: If VRamSizeDX9.exe shows 11168, and you're running Windows 10, you should subtract 350 to get 10818.) For more information, please refer to this post. VideoMemorySizeMb=(see above instructions) Notice:Windows 8/8.1 users: Microsoft has, unintentionally, introduced a memory limit for DirectX 9 games/software. This limit is 4GBs (4096) and there is nothing which can be done to circumvent this limit. For users seeing the VRamSizeTest tool reporting 4064 or similar, this is not a mistake. This is actually the limit for the OS in use and the maximum value you can set the VideoMemorySizeMb to. This bug was fixed for Windows 10 in the 2017 Fall Creator's Update, but still affects Windows 8/8.1.
sila Posted February 6, 2019 Posted February 6, 2019 2 hours ago, Grey Cloud said: That's not a source, just your garbled opinion. And what the hell is this mysterious 'other game' you keep referring to? I am fairly sure he was referring to skyrim special edition.
Grey Cloud Posted February 6, 2019 Posted February 6, 2019 15 minutes ago, sila said: I am fairly sure he was referring to skyrim special edition. You have quoted from a source, the same one I linked to in post #16. This well respected source contradicts his opinion on more than one matter and as you pointed out, the W10 - 4GB issue has been resolved for a while now. ? I hope you didn't suffer any ill-effects due to naming the 'other game'. ?
sila Posted February 6, 2019 Posted February 6, 2019 10 minutes ago, Grey Cloud said: You have quoted from a source, the same one I linked to in post #16. This well respected source contradicts his opinion on more than one matter and as you pointed out, the W10 - 4GB issue has been resolved for a while now. ? I hope you didn't suffer any ill-effects due to naming the 'other game'. ? Yes, and I specified what the source was in my post. I was merely quoting the relevant part. Considering the guy was saying the game was limited to 4gb even after you posted the link, I doubt he bothered to look at it. And no, I am still alive and kicking after mentioning Skyrim special edition. Now if I had mentioned the creation cl..... OH GOD IT HURTS *dies*
zniachtl Posted February 6, 2019 Posted February 6, 2019 It is 4064 for me - Windows 10 .1607 .1703 (March 2017) was the first of the "Creators" I had already set my net to Metered by then to stop any and all automatic updates, a step I never regretted
sila Posted February 6, 2019 Posted February 6, 2019 1 hour ago, zniachtl said: It is 4064 for me - Windows 10 .1607 .1703 (March 2017) was the first of the "Creators" I had already set my net to Metered by then to stop any and all automatic updates, a step I never regretted If you refuse to get updates then.... I suppose you should be happy with the 4gb of vram then. http://prntscr.com/mhkaau
Recommended Posts
Archived
This topic is now archived and is closed to further replies.