GenioMaestro Posted March 5, 2019 Posted March 5, 2019 25 minutes ago, sila said: @GenioMaestro So I was going through the ini files, it seems I never changed the "VideoMemorySizeMb=" value in enblocal.ini when I redid my mods on my new pc. I suppose that would be a likely culprit? It was on the default of 4096 which I think was the old limit for 32bit programs. That can NOT cause CTD. Simply limit the ENB usable memory to 4096 but not more. If you not have enougth Vram and ENB not have enougth RAM you simply get purple textures or textures in lower resolution or have bad game performance. https://www.loverslab.com/topic/117542-stuttering/?do=findComment&comment=2537976 Read that post and the nexts.
sila Posted March 5, 2019 Posted March 5, 2019 Spoiler 36 minutes ago, GenioMaestro said: That can NOT cause CTD. Simply limit the ENB usable memory to 4096 but not more. If you not have enougth Vram and ENB not have enougth RAM you simply get purple textures or textures in lower resolution or have bad game performance. https://www.loverslab.com/topic/117542-stuttering/?do=findComment&comment=2537976 Read that post and the nexts. Well I guess that is not it either then. I use HDT so I cannot use the OsAlocators=1 if that is going to cause problems. I suppose I can try rebuilding the .ini files, though I have not changed anything in them other than what crash fixes mentions. Anyway, I am going to continue trying this tomorrow probably. I will pm you later if you don't mind, I don't really want to keep going on someone else's thread here.
GenioMaestro Posted March 5, 2019 Posted March 5, 2019 8 minutes ago, sila said: Reveal hidden contents Well I guess that is not it either then. I use HDT so I cannot use the OsAlocators=1 if that is going to cause problems. I guess I can try rebuilding the .ini files, though I have not changed anything in them other than what crash fixes mentions. You can use OsAlocators because only give SOME problems in HDT and not disable completely the HDT. I use OsAlocators and probably is the only way for have a stable game with a minimun of CTD that can allow you play 4 consecutive hours or more. But of course, all the good things have a bad part. https://www.loverslab.com/topic/115340-hair-physics-stops-working-for-no-cause-or-change-to-any-files/?do=findComment&comment=2500674 https://www.loverslab.com/topic/111977-updated-title-and-description-crash-fixes-problem-with-hdt-wigsearrings/?do=findComment&comment=2445269 https://www.loverslab.com/topic/111977-updated-title-and-description-crash-fixes-problem-with-hdt-wigsearrings/?do=findComment&comment=2446839 Read that two post and learn the capacity of OsAlocators against SKSE Memory Path and the problems that you can have in HDT when you use OsAlocators. You can select have a perfect HDT with CTD or you can select lost some HDT functionalities and have a stable game near free of CTD.
GenioMaestro Posted March 10, 2019 Posted March 10, 2019 On 3/5/2019 at 1:31 AM, sila said: Well I guess that is not it either then. I use HDT so I cannot use the OsAlocators=1 if that is going to cause problems. Seems that the HDT Problems have solution and is use HDT MemPatch. Go to the post, read it, download the second HDT MemPatch and configure it following the instructions. https://www.loverslab.com/topic/118138-sexy-idle-hdt-doesnt-work/?do=findComment&comment=2548840
Kapootable Posted March 12, 2019 Author Posted March 12, 2019 On 3/10/2019 at 7:52 PM, GenioMaestro said: Seems that the HDT Problems have solution and is use HDT MemPatch. Go to the post, read it, download the second HDT MemPatch and configure it following the instructions. https://www.loverslab.com/topic/118138-sexy-idle-hdt-doesnt-work/?do=findComment&comment=2548840 So basically crash fix set up like this if using the mempatch? UseOSAllocators=0AlignHeapAllocate=0
GenioMaestro Posted March 12, 2019 Posted March 12, 2019 1 hour ago, Kapootable said: So basically crash fix set up like this if using the mempatch? UseOSAllocators=0AlignHeapAllocate=0 I making test and collecting performance data and seems that the HDTMemPatch solve the a lot of strange HDT problems. For one side, when i put OsAlocators=0 i can get CTD in less than one hour. But when i add HDTMemPatch i can play more than 2 hours whitout CDT. That mean the HDTMemPatch correct some problems in the memory asigment of HDT and allow play the game more time before get a CTD by memory out. For other side, when i put OsAlocators=1 i no have CTD but my chains not works. But when i add HDTMemPatch the chains works perfect for hours whitout CDT. That mean the HDTMemPatch correct some problems in HDT and allow play with chains and others HDT Elements whitout any problem. Of course, as i reported before, use OsAlocators=1 is much more efficient than the SKSE Memory Manager and i have better framerate, less ussage resources, less Vram ussage, less access to hard disk... I recomend every player install SKSE Pluging Preloader for enable the use of OsAlocators in CrashFix.ini and test the performace of the game. If that give some problems in HDT add HDTMemPatch for solve it. Aditionally, you must have AlignHeapAllocate=1 when have OsAlocators=1 because is the only way for solve the CTD caused by RaceMenu when change the sliders: UseOSAllocators=1 and crashing when touching sliders in character creation or otherwise.Set AlignHeapAllocate=1 in CrashFixPlugin.ini, downside is increased load time and increased memory usage. For me, the performance of the game is better with OsAlocators=1 and i have AlignHeapAllocate=1 because i not whant any CTD in my game. If i not put AlignHeapAllocate=1 i must close the game, change the parameters and open the game again for use RaceMenu and i see that stupid.
Kapootable Posted March 13, 2019 Author Posted March 13, 2019 On 3/12/2019 at 8:30 PM, GenioMaestro said: I making test and collecting performance data and seems that the HDTMemPatch solve the a lot of strange HDT problems. For one side, when i put OsAlocators=0 i can get CTD in less than one hour. But when i add HDTMemPatch i can play more than 2 hours whitout CDT. That mean the HDTMemPatch correct some problems in the memory asigment of HDT and allow play the game more time before get a CTD by memory out. For other side, when i put OsAlocators=1 i no have CTD but my chains not works. But when i add HDTMemPatch the chains works perfect for hours whitout CDT. That mean the HDTMemPatch correct some problems in HDT and allow play with chains and others HDT Elements whitout any problem. Of course, as i reported before, use OsAlocators=1 is much more efficient than the SKSE Memory Manager and i have better framerate, less ussage resources, less Vram ussage, less access to hard disk... I recomend every player install SKSE Pluging Preloader for enable the use of OsAlocators in CrashFix.ini and test the performace of the game. If that give some problems in HDT add HDTMemPatch for solve it. Aditionally, you must have AlignHeapAllocate=1 when have OsAlocators=1 because is the only way for solve the CTD caused by RaceMenu when change the sliders: UseOSAllocators=1 and crashing when touching sliders in character creation or otherwise.Set AlignHeapAllocate=1 in CrashFixPlugin.ini, downside is increased load time and increased memory usage. For me, the performance of the game is better with OsAlocators=1 and i have AlignHeapAllocate=1 because i not whant any CTD in my game. If i not put AlignHeapAllocate=1 i must close the game, change the parameters and open the game again for use RaceMenu and i see that stupid. Read your previous posts, said useosallocators made the hdt chains in the devious devices disappearing. Like wise on mine. Sick of re-equipping every single time it happened. Refering to https://www.loverslab.com/topic/86382-hdtskinnedmeshphysics-explainedlatest-binarys/ 1.1 - hdtMemPatch[Exception]AutoSaveGame = false //-- Try save game when CTD happenMiniDumpWithFullMemory = false //-- Save the minidump file(.dmp) with the hole memory Skyrim usedReportToWindows = false //-- Deliver the error to werr so developer can use their debugger to find out what happen[Memory]RecordFormHeapAllocateFailed = true //-- If memory allocate failed, it will write to the log fileFormHeapAllocateFromLargerSpace = trueFixInfiniteLoad = true //-- just does what SafetyLoad do in a more compatible wayReplaceDefaultHavokHeap = true //-- allocate memory for havok by _aligned_malloc,may fix some CTD while loadingdoNotReleaseHavokResource = true[Optimize]FasterLoading = true //-- fast texture loading, may result in purple texturesUseShaderCache = false //-- enables shader cache, will dump cache files to the overwrite folder[Camera]fix3rdPersonCameraScale = true Under the memory configs, basically what crash fixes do? Not too sure. I tried fiddling with useallocators & alignheapallocate to 1 along with the mempatch, gave me a bsod. So i tried turning useallocators & alignheapallocate to 0, with satisfying results. Though u mentioned crashing on racemenu sliders, u may need the ShowRaceMenu Precache Killer https://www.nexusmods.com/skyrim/mods/33526
GenioMaestro Posted March 14, 2019 Posted March 14, 2019 21 hours ago, Kapootable said: Under the memory configs, basically what crash fixes do? Not too sure. I tried fiddling with useallocators & alignheapallocate to 1 along with the mempatch, gave me a bsod. So i tried turning useallocators & alignheapallocate to 0, with satisfying results. Though u mentioned crashing on racemenu sliders, u may need the ShowRaceMenu Precache Killer https://www.nexusmods.com/skyrim/mods/33526 These are diferent tools for solve diferent problems. ShowRaceMenu Precache Killer is designed for solve a CTD in RaceMenu caused when you have a lot of hairs. alignheapallocate is need ONLY when you have OsAlocators 1 and you move sliders in RaceMenu I not know WHY you have BSOD. Is very strange. I not remember any BSOD with Skyrim. Normally, the BSOD are caused by defective hardware, problems in drivers, operating system... but is strange get it ONLY when activate one option in a game. Maybe you have a specific mix of utils that are colliding and maybe for that you have the BSOD. Remove SSME is you have it. Is a OLD tool and the funcionality of SSME is included into SKSE. You NEED the SKSE Memory Patch, that is only a INI file but is strictly necesary because SKSE not include it. Enable OsAlocators is not strictly necesary. Is recomended and give more stability to the game but, normally, you can play from 2 to 4 hours with OsAlocators = 0 depending of your exact configuration.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.