DarkladyLexy Posted January 12, 2018 Posted January 12, 2018 I have not had as many crashes since I installed Crash fixes the only i have crash was when I was doing something silly like try to do too much crafting in a sort amount of time.
InstantKor Posted January 12, 2018 Posted January 12, 2018 OH really, now thats interesting. Now I have to ask how many hours is a play session generally? As when I was playing all day yesterday which was 12 hours (was having a ton of fun) the game had a CTD 2 or 3 times but that crash fix error didnt occur during that play session.
memnochs Posted January 12, 2018 Posted January 12, 2018 (edited) @InstantKor: custommemoryblock helps to avoid this problem and is still needed even with an updated windows 10. The purposes of this feature is to counteract memory fragmentation which prevent skyrim to allocate memory. So it should enabled most of the time especially because windows and other apps love to fragment your memory ^^. Sadly, even with a software dedicated to this, it is impossible to avoid this problem totally. Quote from the troubleshoot section of my guide to set it properly:Game says message box "running out of memory" and crashes and ReduceSystemMemoryUsage=true :Edit CrashFixPlugin.ini and set CustomMemoryBlock=1 Take a look at crash fixes in-game report by opening skyrim console (with ²) In CrashFixplugin.ini, increase or decrease CustomMemoryBlockTotalSizeMb until highest memory block usage's value is around 85% - 90% I can play 4 hours to my game with no crashes ;) I can rarely play longer so I can't tell you how it is stable after that. My mod list is based on SRLE extended with a lot of mod not added to it. (to be simple my load order is really heavy).Skyrim is a strange beast because one of my friend only use USLEEP, crash fixes, bug fixes, skyui and an enb preset and he's got a CTD every 3 hours. It seems very system depending (OS, hardware and third party software). @berndaroy: the removed cap from windows 10 only concerns enb setting "VideoMemorySizeMb" which can be increased upper to 4064, now. Nothing relative to crash fixes ;) Edited January 12, 2018 by memnochs 1
DarkladyLexy Posted January 12, 2018 Posted January 12, 2018 for me I am lucky if I can get 2 or 3 hours in of actual playing.
berndaroy Posted January 12, 2018 Posted January 12, 2018 (edited) @berndaroy: the removed cap from windows 10 only concerns enb setting "VideoMemorySizeMb" which can be increased upper to 4064, now. Nothing relative to crash fixes ;)Ok thanks Menoch...yah thats why win 8.1 is still capped to 4064..i get myself confused with these settings, so to be clear Videomemory is the maximum amount of vram on graphics card that the game can use dependant on your win version i.e win 8.1 4064; win7/10 can use more than this plus ram. Custommemory is the two portioned blocks of memory allocated in ENB, the game uses, first one (lower) before drawing on the other and these can be fragmented by apps etc. Have i got this right? I have found that whilst playing i get slight warning signs...when running after a period of play, i start getting stuttering, small brief sections of or micro pauses. At this point i save, exit, back up saves, restore last save ,start up and good for another period of play...between 3/5 hours Edited January 12, 2018 by berndaroy
Lordx1 Posted January 13, 2018 Posted January 13, 2018 it is getting there It is more stable than oldrim??
TheLoneStar19 Posted January 13, 2018 Posted January 13, 2018 At Arthmoor's Villages now, when installing Darkwater Crossing it says not to install Darkwater Crossing.bslDarkwater Crossing.txt I saw that BSL isn't their, should I just install as normal? Sorry if this is a silly question I'm a type of person that always has to make sure everything Is right xD
DarkladyLexy Posted January 13, 2018 Posted January 13, 2018 It is more stable than oldrim??I can't say still in the testing trying things out phase. At Arthmoor's Villages now, when installing Darkwater Crossing it says not to install Darkwater Crossing.bslDarkwater Crossing.txt I saw that BSL isn't their, should I just install as normal? Sorry if this is a silly question I'm a type of person that always has to make sure everything Is right xDyes just install as normal probably Arthmoor remove that file from an update and i missed it. 1
bekcicandrej Posted January 13, 2018 Posted January 13, 2018 (edited) Just a fyi, that I found out because spluff was going wonky. You can load total commander 32bit in MO and see how your data dir looks like.I found some readme folders that I missed for example Edited January 13, 2018 by bekcicandrej
mavanaic Posted January 13, 2018 Posted January 13, 2018 (edited) It is more stable than oldrim??Much more stable...I'm using in parallel something close to this guide + a lot of extra mods (like 800 plugins each)...Although Oldrim it's still prettier, SE with the new enb is getting there...As for stability-wise..the difference is that after a half of hour of Oldrim (with a perfect CR file) I got a crash ...in SSE..very rare I got crashes, even that my CR is based on a Smashed Patch only, I even was able to play the entire Bruma qustline without a single crash with my SSE build up to 150 gig...so I decided to port everything from my Oldrim build...basically what is in this guide can be run in SSE ..except some SKSE plugins that I love from OLDRIM like the Search Plugin, Face to Face conversation, Immersive Camera/Enhanced Camera(not in this guide), or disable quicksave...I managed to make Racemenu, even CACO, will port CCOR..although Ars Metallica is already ported for SSE and doing a fine job... Edited January 13, 2018 by mavanaic
DarkladyLexy Posted January 13, 2018 Posted January 13, 2018 https://forum.step-project.com/topic/13092-lexys-legacy-of-the-dragonborn-special-edition/ 1
godescalcus Posted January 13, 2018 Posted January 13, 2018 MoreHUD and SKYUI are not detecting SKSE, yet the game window shows it's running SKSE version 1.7.0.48 (or something similar) and if I type "getskseversion" in the console I also get the expected output... I've tried reinstalling SKSE, rebuilt the ini files, no deal.,,
godescalcus Posted January 13, 2018 Posted January 13, 2018 Much more stable...I'd like to know what patches or fixes you're using... I'm also running a WIP SSE build but with barely anything other than weathers, lighting and landscape I still get occasional instant CTD's which I suspect are caused by memory full. And yes, oldrim is still prettier... I don't understand it and it puzzles me, why the heck do they make a more advanced engine that produces crappy results. There's a ton of great weather and ENB mods now that produce amazing vivid image, but I ABHOR TAA with all my guts. It blurs everything completely, especially faces. So I run the game without TAA and use NVIDIA FXAA instead, not nearly perfect but more bearable. Then after a while I just go back to plain old Skyrim...
godescalcus Posted January 13, 2018 Posted January 13, 2018 (edited) MoreHUD and SKYUI are not detecting SKSE, yet the game window shows it's running SKSE version 1.7.0.48 (or something similar) and if I type "getskseversion" in the console I also get the expected output... I've tried reinstalling SKSE, rebuilt the ini files, no deal.,,Updating... I've been at this for two hours. Completely vanillified and reinstalled the game, the problem persists. I did restart windows in the mean time, for whatever good it serves. Tried to unblock dlls but none appears to be blocked. Damn, I've always managed to get this working without any problem! Could it be a conflict with skse64 that I have installed in my SSE folder? Could the script calls from the skse plugins be getting messed up by an OS level conflict? Edited January 13, 2018 by godescalcus
godescalcus Posted January 13, 2018 Posted January 13, 2018 Updating... I've been at this for two hours. Completely vanillified and reinstalled the game, the problem persists. I did restart windows in the mean time, for whatever good it serves. Tried to unblock dlls but none appears to be blocked. Damn, I've always managed to get this working without any problem! Could it be a conflict with skse64 that I have installed in my SSE folder? Could the script calls from the skse plugins be getting messed up by an OS level conflict?Finally over. Turn out this "oldrim with WB specialist" committed an idiot's mistake - trying to outsmart the instructions I created an installer with an SKSE folder in it and created the SKSE.ini inside that folder. My idea was to add the SKSE scripts in there too so they could be replaced by WB if by any chance another mod replaced them and was subsequently deleted. My error was that I placed the scripts folder inside the SKSE folder in the installer. DUUUUUH Moved the scripts to the installer's root folder, where they belong. Corrected and everything working. There goes one afternoon.
Recommended Posts