JustinBailey87 Posted June 26 Posted June 26 There's this stupid-ass crash log analyzer that gives me this one piece of useless advice: "Please increase the log level for hdtsmp64 (if you have not done so yet) and check its content." and I'm like WELL HOW IN THE NAME OF ALL f*#@ DO I DO THAT YOU f*#@ING ASSHOLE?!!!!!!!!!!!!!!!!!!!! Do any of you guys know?!
scorrp10 Posted June 27 Posted June 27 Asking in a nice, calm manner generally works better.  If I go to FSMP page, there is not much in the description.  But it has like 6 articles on the Articles tab.  One of those is about configs.xml modifying. Checking it, it mentions configs.xml in Data\SKSE\Plugins\hdtSkinnedMeshConfigs.  If I go and check that file, logLevel is the first setting in there. P.S. even without checking FSMP page - if in Vortex, I click the dropdown for Faster HDT-SMP mod, and choose 'Open in File Manager' to access its staging folder, it literally contains a total of three 'payload' files: SKSE\Plugins\hdtSMP64.dll SKSE\Plugins\hdtSMP64.pdb SKSE\Plugins\hdtSkinnedMeshConfigs\configs.xml Shouldn't take a rocket science degree to figure out which one is the configuration.  1
JustinBailey87 Posted June 28 Author Posted June 28 On 6/27/2025 at 8:11 AM, scorrp10 said: Asking in a nice, calm manner generally works better.  If I go to FSMP page, there is not much in the description.  But it has like 6 articles on the Articles tab.  One of those is about configs.xml modifying. Checking it, it mentions configs.xml in Data\SKSE\Plugins\hdtSkinnedMeshConfigs.  If I go and check that file, logLevel is the first setting in there. P.S. even without checking FSMP page - if in Vortex, I click the dropdown for Faster HDT-SMP mod, and choose 'Open in File Manager' to access its staging folder, it literally contains a total of three 'payload' files: SKSE\Plugins\hdtSMP64.dll SKSE\Plugins\hdtSMP64.pdb SKSE\Plugins\hdtSkinnedMeshConfigs\configs.xml Shouldn't take a rocket science degree to figure out which one is the configuration.  Unfortunately raising the log level did not solve the issue. I still have every single save after the one that I made right after I killed cicero ctd when I try to load them. Below is the latest from the useless crash log analyzer if you can get more out of it than I did, which I highly doubt. f*#@ the f*#@ing saveload manager and whoever programmed it, and the creators of hdt-smp and its useless npc patch! (So much for the latter being supposedly able to work with the older 2.2.1. What a crock of s#*!. f*#@ the asshole who claimed that too.) CLA SSE - Sephs Skyrim Experimental Crash Log Analyzer (1.2.0) / 2023.09.10 --------------------------------------------------------------------------- If you are asking others for assistance / help, ALWAYS provide the crashlog as well! ##################################################################################### Crashlog Tool:     CrashLoggerSSE v1-15-0-0 Oct 12 2024 11:33:37 Game Version:    1.6.1170 Script Extender:  1.6.1170 ################################################################################ RAM ################################################################################ RAM Total:  12.92 GB RAM Used:  7.91 GB RAM Free:  5.01 GB Analysis RAM (all good):     It is absolute unlikely that the crash was due to RAM.  ################################################################################ Mod Count: ################################################################################   Light: 96  Regular: 134  Total: 230 ################################################################################ Header indicators: ################################################################################ Memory:     0x7FF86CCCF88B    count: (2) File:      VCRUNTIME140.dll    count: (3) Address:     000F88B      count: (2) Assembler:    rep movsb  count: (1) [ 0] 0x7FF86CCCF88B  VCRUNTIME140.dll+000F88B -//- count: (1) VCRUNTIME140.dll         0x7FF86CCC0000 -//- count: (1)  ################################################################################ Solutions ################################################################################ SkyrimSE.exe: count: (50)   This file on its own is not the cause, however, we'll do further parsing...   Could not find any known issues related to SkyrimSE.exe.   SkyrimSE.exe _might_ be listed for the sole reason of... you're playing this game!! -------------------------------------------------------------------------------- hdtSMP64.dll: count: (7)   If this appears often, it might indicate a bad config (rare).   However, it might also just indicate that there were NPCs around that were wearing hdt/SMP enabled clothing...   Please increase the log level for hdtsmp64 (if you have not done so yet) and check its content.   Make sure to have Faster HDT-SMP that suits your Skyrim Version:   - https://www.nexusmods.com/skyrimspecialedition/mods/57339   Also make sure you have these installed:   - SMP NPC fix: https://www.nexusmods.com/skyrimspecialedition/mods/91616   You are using FSMP version: 1.6.1170   Please ensure that this is compatible with your SKSE version: 1.6.1170   Possible FOMOD settings for installation   You might want to try different AVX options, because eventhough supported, they might cause shutter/'lag' in populated areas...   CPU:     avx:  True     avx2:  True     avx512:  False -------------------------------------------------------------------------------- BGSSaveLoadManager: count: (3)   Once you've managed to load the last working save, try this:  player.kill   This has to be confirmed to be working (guess, I'll be told when its not). ################################################################################ Success Statistic: (this has been detected/handled, does not mean it's the cause) ################################################################################ Issues Found:  3 Issues Solved:  3 ################################################################################ DEBUG State: ################################################################################ Culprit list content: (just a list) SkyrimSE.exe, hdtSMP64.dll, BGSSaveLoadManager, ################################################################################ Random 'Fallback' Checks ################################################################################ How to read these results? - They are simple keywords that may appear when you have a lot of issues. - They do NOT have to mean anything. - Only if the "regular" results / solutions do not help, they might provide an indication to the reason for this crash. [RSP+E90 ] 0x7FF842670D65   (void* -> CustomSkills.dll+0010D65  mov rdi, [rax+0xE8] | D:\source\repos\SkyrimSE\CustomSkills\external\CommonLibSSE\include\REL\Relocation.h:855 REL::ID::address (mangled: ?address@ID@REL@@QEBA_KXZ) C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\xmemory:974 REL::ID::address (mangled: ?address@ID@REL@@QEBA_KXZ)) -//- count: (1) RBP 0xF2BC59E7C8    (BGSLoadGameBuffer*) -//- count: (1) [RSP+528 ] 0x20A3651B900   (BGSSaveLoadManager*) -//- count: (1) [RSP+B60 ] 0x20A3651B900   (BGSSaveLoadManager*) -//- count: (1) [RSP+FD0 ] 0x20A3651B900   (BGSSaveLoadManager*) -//- count: (1) VoltekLib.MemoryManager.dll    0x7FF87B1F0000 -//- count: (1) Â
Recommended Posts