justsomeguy333333333 Posted March 31, 2025 Posted March 31, 2025 (edited) 20 hours ago, Min said: Are you on 2.0.2+? 2.0.2 fixed an issue that could cause CTD's. There are no other known stability issues at present. Im on Version 1.0.5.2 Updating kills my save. Edited March 31, 2025 by justsomeguy333333333
Min Posted March 31, 2025 Author Posted March 31, 2025 1 hour ago, justsomeguy333333333 said: Im on Version 1.0.5.2 Updating kills my save. Are you sure you have all of the requirements (Namely, https://www.nexusmods.com/skyrimspecialedition/mods/77779 )? I had a couple users on the discord report that updating versions (Even pre-2.0.0 , such as 1.0.5 -> 1.2.3) would break their saves. They were missing some of the requirements. In any case - I'll add a warning that "2.0.0+ may require a new save for some users, but that upgrading works for most. Back up your save before updating".
Min Posted March 31, 2025 Author Posted March 31, 2025 (edited) 4 hours ago, jc321 said: The older issue of game freeze I was experiencing stopped quite a while ago but have noticed some CTD's since around 2.0.0 but no save corruptions myself as yet. No idea of the cause other than my loose theories of too many NPC's potentially talking (currently have 7 followers though NFF) .. No big deal as I just need to save more. What I have noticed .. and this may be more prevalent due to the better diagnosis tools .. is that sometimes one of the NPC's won't talk but when I have a look at the event log they clearly have (this is all within sound range of my character so not a distance thing) .. -- What I'm wondering is - I use a cheap/free LLM for the majority of my NPC's and then use something like Sonnet for my main interaction NPC's Could it be that one NPC is responding and the cheap LLM is taking so long to respond that's it's focused on that NPC (be in in STT or TTS) that my other NPC has already responded .. but I just never get the TTS element coming through. Upload a copy of your crashlog, and I will be able to tell you if it's chim / minai (And, if it's the same issue that's fixed in 2.0.2). Too many NPC's talking at once wouldn't cause savegame instability. I have contributed a bunch of stability fixes to CHIM itself that may resolve your CTD's. Think the new version will likely release later today, or tomorrow. Try that out, and see if it resolves your issues. AIAgent.log also contains a lot of useful diagnostic information for trying to figure things like this out. Edited March 31, 2025 by Min
jc321 Posted March 31, 2025 Posted March 31, 2025 13 minutes ago, Min said: AIAgent.log also contains a lot of useful diagnostic information for trying to figure things like this out. This is the last crash I had. crash-2025-03-29-18-55-58.log I don't have the corresponding AIAgent.log but I've attached a later one if that helps unearth anything. AIAgent.log
Min Posted March 31, 2025 Author Posted March 31, 2025 (edited) 1 hour ago, jc321 said: This is the last crash I had. crash-2025-03-29-18-55-58.log I don't have the corresponding AIAgent.log but I've attached a later one if that helps unearth anything. AIAgent.log 606.67 kB · 0 downloads I don't see any evidence that this is related to CHIM or MinAI. The crash is occurring within Skyrim itself (Not CHIM's DLL), and I don't see any strings / data that would make me suspect that MinAI is at fault. It's most likely something else with your save / setup. Possibly related to lighting. There was also a lot regarding hydra slavegirls / device processing in your registers. Edited March 31, 2025 by Min
jc321 Posted March 31, 2025 Posted March 31, 2025 1 hour ago, Min said: It's most likely something else with your save / setup. Possibly related to lighting. There was also a lot regarding hydra slavegirls / device processing in your registers. OK, thanks for checking.. I have been playing with Natural & Atmosperic Tamriel (NAT) which equips a torch on player/NPC's at night (very good in VR BTW!) , may that's related but don't recall it causing any problems previously. 1
Pandacius Posted March 31, 2025 Posted March 31, 2025 I have a bug/error to report. After downloading the latest version 2.02. My character will not stop talking at all, which eventually overwhelms the server/LLM so that player entered prompts don't register. Checking the server logs on CHIM, I see it spamming store item commands like at the rate of 1-3 times per second *** minai_storeitem_batch|188542046711400|75164224|Sigurd@final@0001397E@Skyrim.esm@Iron Dagger@41@00@1~000209A5@Skyrim.esm@Boots@26@00@1~000209A6@Skyrim.esm@Clothes@26@00@1~0000000F@Skyrim.esm@gold@32@00@6~0000000A@Skyrim.esm@Lockpick@32@00@1~00100E29@Skyrim.esm@Ring of Minor Wielding@26@00@1~0006F993@Skyrim.esm@Firewood@32@00@3 *** These storeitem commands would take 99% or all prompts. Is there some way to fix this?
Min Posted March 31, 2025 Author Posted March 31, 2025 (edited) 2 hours ago, Pandacius said: I have a bug/error to report. After downloading the latest version 2.02. My character will not stop talking at all, which eventually overwhelms the server/LLM so that player entered prompts don't register. Checking the server logs on CHIM, I see it spamming store item commands like at the rate of 1-3 times per second *** minai_storeitem_batch|188542046711400|75164224|Sigurd@final@0001397E@Skyrim.esm@Iron Dagger@41@00@1~000209A5@Skyrim.esm@Boots@26@00@1~000209A6@Skyrim.esm@Clothes@26@00@1~0000000F@Skyrim.esm@gold@32@00@6~0000000A@Skyrim.esm@Lockpick@32@00@1~00100E29@Skyrim.esm@Ring of Minor Wielding@26@00@1~0006F993@Skyrim.esm@Firewood@32@00@3 *** These storeitem commands would take 99% or all prompts. Is there some way to fix this? Install the updated MinAI server plugin. It processes these requests, they aren't intended to be sent to the LLM. When I publish a new release here, you need to update both the skyrim side (The game mod) and the server side (Through the updater in the minai web config). Edited March 31, 2025 by Min
ashleytaylor Posted April 1, 2025 Posted April 1, 2025 (edited) On 3/31/2025 at 2:21 PM, Min said: Are you sure the save wasn't damaged before you upgraded to 2.0.2? There have been no reports of this issue since I published that release on the discord. The issue was with strings that were too large being generated (While serializing the inventory). This was resulting in unstable saves that occurred while the inventory sync was occurring. Also: Your issue (Papyrus block being truncated) is different than the issue others were reporting. That's not a known issue, and no one else has reported that. Need more information to know if it's related. How to reproduce it, papyrus logs of you reproducing it, etc. If I had to guess, I suspect that your update failed for some reason, and the scripts suspended. That could result in the symptoms you're describing. Impossible to diagnose without more information though. See if you can load a save before this happened, and then share a copy of your papyrus log. Thank you for your speedy response. The save file could have already been damaged, I tried to upgrade to 2.0.2 again, with the latest save (downgraded to 1.2.3 before and cleaned with FallrimTools) the issue is no long present, however, with the save file I used before downgrading, 2.0.2 caused the problem almost every time I made a save (See logs below). So I came to the conclusion that people may have to use an old save before a certain version or clean their save in order to upgrade to 2.0.2. Thank you again for your time and effort! Update: It reoccurred after several successful saves on 2.0.4, but I've already turned off Papyrus logging. I'll share the logs when I get time to try again. Spoiler [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] XPMSE MainQuest Initialization failed. If you are starting a new game, the game might not initialized fully and this warning is normal. If this message is persistent in your log and XPMSE does not function properly, you should check the requirements for XPMSE. XPMSE will try initialization again in 5 seconds. [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:07PM] [minai (Info)]: SAPIENCE: Removing Briehl from AI [03/31/2025 - 10:47:07PM] [CHIM] CHIM_NPC Briehl Remove [03/31/2025 - 10:47:07PM] [minai (Info)]: OnAIActorChange(Briehl): Remove [03/31/2025 - 10:47:07PM] [minai (Info)]: Setting Crime context for actor: [03/31/2025 - 10:47:07PM] [minai (Info)]: Found 4 active bounties for context [03/31/2025 - 10:47:08PM] [minai (Info)]: PersistInventory - Actor: Aria using batch size: 40 [03/31/2025 - 10:47:10PM] VM is freezing... [03/31/2025 - 10:47:10PM] VM is frozen [03/31/2025 - 10:47:11PM] Saving game... [03/31/2025 - 10:47:11PM] Error: Failed to write element 102 on array 0x3B9BA080 to save game [03/31/2025 - 10:47:11PM] Error: Failed to write array 0x3B9BA080 to save game [03/31/2025 - 10:47:11PM] Error: Unable to write arrays to save game [03/31/2025 - 10:47:11PM] Errors occurred while saving the Papyrus save game data [03/31/2025 - 10:47:11PM] VM is thawing... Edited April 1, 2025 by ashleytaylor
toly656 Posted April 1, 2025 Posted April 1, 2025 (edited) no matter what I do if I trigger a sexlab scene through minAI, the game crashes. even if I decline the scene and then just touch the NPC the game crashes everything else works flawlessly, npcs talk to eachother, sapience gets applied all the nine yards (heck I even struggled to find none prudish NPCs to trigger the scene in the first place) but for some reason when the sexlab commands get sent through minAI the game starts breaking edit: I have also tested my current setup without minAI present and this issue does not exist but with minAI present and initiating the scenes using matchmaker the game still crashes I also grabbed a crash log seems like sexlab is being sent a null refrence when minAI is present in the load order, even if the one calling the scene is matchmaker Unhandled exception "EXCEPTION_BREAKPOINT" at 0x7FFA97894961 SexLabUtil.dll+0064961 int3 Exception Flags: 0x00000000 Number of Parameters: 1 Exception Information Parameters: Parameter[0]: 0x000000000000 Edited April 1, 2025 by toly656
jerixho555 Posted April 1, 2025 Posted April 1, 2025 I'm using SOS, not TNG. Any reason every female NPC is calling my dick a tiny pathetic Nord cock? It's hiliarious but also jarring
Min Posted April 1, 2025 Author Posted April 1, 2025 20 hours ago, ashleytaylor said: Thank you for your speedy response. The save file could have already been damaged, I tried to upgrade to 2.0.2 again, with the latest save (downgraded to 1.2.3 before and cleaned with FallrimTools) the issue is no long present, however, with the save file I used before downgrading, 2.0.2 caused the problem almost every time I made a save (See logs below). So I came to the conclusion that people may have to use an old save before a certain version or clean their save in order to upgrade to 2.0.2. Thank you again for your time and effort! Update: It reoccurred after several successful saves on 2.0.4, but I've already turned off Papyrus logging. I'll share the logs when I get time to try again. Reveal hidden contents [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] XPMSE MainQuest Initialization failed. If you are starting a new game, the game might not initialized fully and this warning is normal. If this message is persistent in your log and XPMSE does not function properly, you should check the requirements for XPMSE. XPMSE will try initialization again in 5 seconds. [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:06PM] [minai (Info)]: Re-enabling sapience (leaving stealth mode) [03/31/2025 - 10:47:07PM] [minai (Info)]: SAPIENCE: Removing Briehl from AI [03/31/2025 - 10:47:07PM] [CHIM] CHIM_NPC Briehl Remove [03/31/2025 - 10:47:07PM] [minai (Info)]: OnAIActorChange(Briehl): Remove [03/31/2025 - 10:47:07PM] [minai (Info)]: Setting Crime context for actor: [03/31/2025 - 10:47:07PM] [minai (Info)]: Found 4 active bounties for context [03/31/2025 - 10:47:08PM] [minai (Info)]: PersistInventory - Actor: Aria using batch size: 40 [03/31/2025 - 10:47:10PM] VM is freezing... [03/31/2025 - 10:47:10PM] VM is frozen [03/31/2025 - 10:47:11PM] Saving game... [03/31/2025 - 10:47:11PM] Error: Failed to write element 102 on array 0x3B9BA080 to save game [03/31/2025 - 10:47:11PM] Error: Failed to write array 0x3B9BA080 to save game [03/31/2025 - 10:47:11PM] Error: Unable to write arrays to save game [03/31/2025 - 10:47:11PM] Errors occurred while saving the Papyrus save game data [03/31/2025 - 10:47:11PM] VM is thawing... See if you can reproduce on a fresh save. No one else has reported this particular problem, and there's probably at least 500 hours of playtime spread across my testers since 2.0.2. 5 hours ago, toly656 said: no matter what I do if I trigger a sexlab scene through minAI, the game crashes. even if I decline the scene and then just touch the NPC the game crashes everything else works flawlessly, npcs talk to eachother, sapience gets applied all the nine yards (heck I even struggled to find none prudish NPCs to trigger the scene in the first place) but for some reason when the sexlab commands get sent through minAI the game starts breaking edit: I have also tested my current setup without minAI present and this issue does not exist but with minAI present and initiating the scenes using matchmaker the game still crashes I also grabbed a crash log seems like sexlab is being sent a null refrence when minAI is present in the load order, even if the one calling the scene is matchmaker Unhandled exception "EXCEPTION_BREAKPOINT" at 0x7FFA97894961 SexLabUtil.dll+0064961 int3 Exception Flags: 0x00000000 Number of Parameters: 1 Exception Information Parameters: Parameter[0]: 0x000000000000 What version of Sexlab? Upload a copy of your Papyrus.0.log, and the full crashlog. Seems as if we're triggering a crash in SexlabUtil.dll, not in minai/chim itself. 44 minutes ago, jerixho555 said: I'm using SOS, not TNG. Any reason every female NPC is calling my dick a tiny pathetic Nord cock? It's hiliarious but also jarring @stnfnk ^^ That is hilarious. You can turn off the "Physical Description" context builder to turn this off.
TheArtOfLove Posted April 1, 2025 Posted April 1, 2025 @Min Thanks for the update! Can you tell me which file contains the text for this action? I tried to find it, but I couldn't 39 => array ( 'role' => 'user', 'content' => ' Rsyn found 1 Casual Dongtan Dress - Cotton in a Senna\'s Outfit', ),
justsomeguy333333333 Posted April 1, 2025 Posted April 1, 2025 On 3/31/2025 at 4:56 PM, Min said: Are you sure you have all of the requirements (Namely, https://www.nexusmods.com/skyrimspecialedition/mods/77779 )? I had a couple users on the discord report that updating versions (Even pre-2.0.0 , such as 1.0.5 -> 1.2.3) would break their saves. They were missing some of the requirements. In any case - I'll add a warning that "2.0.0+ may require a new save for some users, but that upgrading works for most. Back up your save before updating". All requirements met, but it could also be one of my 1800+ mods beefing with MinAI. Regardless, Thanks for the support!
stnfnk Posted April 2, 2025 Posted April 2, 2025 3 hours ago, jerixho555 said: I'm using SOS, not TNG. Any reason every female NPC is calling my dick a tiny pathetic Nord cock? It's hiliarious but also jarring Do you have a dummy file for TheNewGentleman.esp? Delete it.
ThaConquer Posted April 2, 2025 Posted April 2, 2025 Fantastic work with this mod! Also, for people who want a cheap but intelligent, uncensored and fast LLM, I have been very happy with Mistral Nemo so far. I recommend testing it out.
toly656 Posted April 2, 2025 Posted April 2, 2025 6 hours ago, Min said: See if you can reproduce on a fresh save. No one else has reported this particular problem, and there's probably at least 500 hours of playtime spread across my testers since 2.0.2. What version of Sexlab? Upload a copy of your Papyrus.0.log, and the full crashlog. Seems as if we're triggering a crash in SexlabUtil.dll, not in minai/chim itself. @stnfnk ^^ That is hilarious. You can turn off the "Physical Description" context builder to turn this off. sexlab v163 I would love to give you the papyrus logs, but after hours of trying it's refused to pump any out (yes I've turned them on in the respective INIs, yes I've tried bethINI) if I manage to get any more useful logs I'll hand them over
jerixho555 Posted April 2, 2025 Posted April 2, 2025 5 hours ago, stnfnk said: Do you have a dummy file for TheNewGentleman.esp? Delete it. No, not nothing for TNG in my plugins. I thought that would be it too. Have the SOSRaceMenu from XP32, SOS PhysicsManager, and VectorPlexus Regular and Light.
stnfnk Posted April 2, 2025 Posted April 2, 2025 4 hours ago, jerixho555 said: No, not nothing for TNG in my plugins. I thought that would be it too. Have the SOSRaceMenu from XP32, SOS PhysicsManager, and VectorPlexus Regular and Light. If there is no TheNewGentleman.esp then a lot of that stuff just gets bypassed and the game never sees it. If you had the TNG esp before and removed it, you might still have tng_size column in your CHIM database. You can go in and drop the column or reset your whole database to clear it (big red button).
toly656 Posted April 2, 2025 Posted April 2, 2025 (edited) 19 hours ago, Min said: See if you can reproduce on a fresh save. No one else has reported this particular problem, and there's probably at least 500 hours of playtime spread across my testers since 2.0.2. What version of Sexlab? Upload a copy of your Papyrus.0.log, and the full crashlog. Seems as if we're triggering a crash in SexlabUtil.dll, not in minai/chim itself. @stnfnk ^^ That is hilarious. You can turn off the "Physical Description" context builder to turn this off. OK I narrowed the issue down to an animation pack the behaved without minAI but not with it. so nothing to worry about on your end if I might give some feedback, devious followers will talk about nothing other than your debt, even if it's minor, maybe add some kind of minimum were the devious follower gets told about the debt, only when it's significant enough to be worth a deal? like 1000 gold or probably reading the config of the devious followers thing to see how much gold a deal will pay off (which is a multiplier of daily debt) also the devious follower AI has no way of taking your money from you and paying that debt Edited April 2, 2025 by toly656
ashleytaylor Posted April 3, 2025 Posted April 3, 2025 On 4/2/2025 at 5:30 AM, Min said: See if you can reproduce on a fresh save. No one else has reported this particular problem, and there's probably at least 500 hours of playtime spread across my testers since 2.0.2. I've tried to purge MinAI with ReSaver on my latest working save, played for 1.5 hours and no more corrupt save so far. I must say I really appreciate all you've done, I've noticed a problem with followers during this playthrough, seems that CHIM disables interactions with followers when AI is speaking, but now it is not re-enabled automatically unless I speak to them again with the AI key, then I found a new version of CHIM on Nexus and the first line of the changelogs mentioned that Min fixed the bug. Wow. 1
ashleytaylor Posted April 3, 2025 Posted April 3, 2025 On 4/2/2025 at 12:18 PM, toly656 said: sexlab v163 I would love to give you the papyrus logs, but after hours of trying it's refused to pump any out (yes I've turned them on in the respective INIs, yes I've tried bethINI) if I manage to get any more useful logs I'll hand them over There's another INI file named SkyrimCustom.ini.
Min Posted April 3, 2025 Author Posted April 3, 2025 (edited) 4 hours ago, ashleytaylor said: I've tried to purge MinAI with ReSaver on my latest working save, played for 1.5 hours and no more corrupt save so far. I must say I really appreciate all you've done, I've noticed a problem with followers during this playthrough, seems that CHIM disables interactions with followers when AI is speaking, but now it is not re-enabled automatically unless I speak to them again with the AI key, then I found a new version of CHIM on Nexus and the first line of the changelogs mentioned that Min fixed the bug. Wow. Thanks! Yeah, I've fixed probably at least 100 different unique ways that CHIM can CTD, freeze, deadlock, or otherwise bug out the game. 1.1.1.3 should be pretty stable. I'm continuing to fix issues as I come across them. CHIM had some *gnarly* issues before I started working on it.. The most egregious of these was that it was spawning thousands of threads per minute with no lifecycle management before 1.1.1... Some of those threads would deadlock (Other bugs that I've also fixed), and the threads would just live forever and leak resources. This is what was causing the freezes that Nolvus users were reporting. I spent a fair bit of time debugging and fixing that. I refactored the core of how the DLL schedules and executes work to fix this. Not a small change, but comprehensively fixes the problem. You can check out what it's doing by looking at AIAgent.log (Status dumped every 1 minute, looks like this) : [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:374] [ThreadPool] Pool Status: Uptime=4m, Queued=5648, Completed=5642, TimedOut=0, Errors=0, Cancelled=1, QueueSize=0, ActiveThreads=48 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:380] [ThreadPool] Task Type Statistics: [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:381] Type | Queued | Completed | TimedOut | Errors | Cancelled | Avg Time(ms) | Max Time(ms) [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:383] --------------------------+----------+-----------+----------+--------+----------+--------------+------------ [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] SetDrivenByAIA | 1 | 1 | 0 | 0 | 0 | 24 | 24 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPLog | 1758 | 1754 | 0 | 0 | 0 | 232 | 1135 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPStream | 1 | 1 | 0 | 0 | 1 | 14263 | 14263 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:413] Cancellation distribution by key for 'HTTPStream': [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:415] Chloe: 1 cancellations [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] VoiceRecord | 2 | 1 | 0 | 0 | 0 | 6 | 6 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] ProcessActor | 2 | 2 | 0 | 0 | 0 | 7598 | 9457 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPLogWithActor | 1 | 1 | 0 | 0 | 0 | 6728 | 6728 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:422] [ThreadPool] Thread Details: [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:423] ThreadID | Uptime(m) | Tasks Done | TimeOuts | Errors | Last Task(s) | Status | Longest Task | Current Task [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:425] -----------+-----------+------------+-----------+--------+-------------+---------+---------------------------+--------------------------------------------------- [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 63220 | 4 | 36 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 50756 | 4 | 36 | 0 | 0 | 2 | Idle | 818ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 39500 | 4 | 36 | 0 | 0 | 2 | Idle | 706ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 56944 | 4 | 38 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 63152 | 4 | 30 | 0 | 0 | 2 | Idle | 817ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 17920 | 4 | 38 | 0 | 0 | 2 | Idle | 717ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 31412 | 4 | 0 | 0 | 0 | 240 | Working | 0ms | ManagerMainQueue [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 34572 | 4 | 41 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 24028 | 4 | 38 | 0 | 0 | 2 | Idle | 717ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 55436 | 4 | 36 | 0 | 0 | 0 | Working | 918ms HTTPLog | HTTPLog (setconf|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 34940 | 4 | 38 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 29880 | 4 | 35 | 0 | 0 | 1 | Idle | 6728ms HTTPLogWithActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 63328 | 4 | 36 | 0 | 0 | 0 | Working | 812ms HTTPLog | HTTPLog (infonpc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 55524 | 4 | 39 | 0 | 0 | 2 | Idle | 804ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 48164 | 4 | 38 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 46332 | 4 | 38 | 0 | 0 | 2 | Idle | 1135ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 4136 | 4 | 40 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 42164 | 4 | 40 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 39964 | 4 | 34 | 0 | 0 | 2 | Idle | 919ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 53840 | 4 | 35 | 0 | 0 | 2 | Idle | 14263ms HTTPStream | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 30980 | 4 | 37 | 0 | 0 | 2 | Idle | 814ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 38176 | 4 | 40 | 0 | 0 | 2 | Idle | 919ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54508 | 4 | 31 | 0 | 0 | 2 | Idle | 9457ms ProcessActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54444 | 4 | 33 | 0 | 0 | 2 | Idle | 924ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 53328 | 4 | 41 | 0 | 0 | 2 | Idle | 815ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 37508 | 4 | 40 | 0 | 0 | 2 | Idle | 806ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 52944 | 4 | 33 | 0 | 0 | 2 | Idle | 713ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 49328 | 4 | 43 | 0 | 0 | 2 | Idle | 608ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 64232 | 4 | 39 | 0 | 0 | 2 | Idle | 815ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 34508 | 4 | 33 | 0 | 0 | 2 | Idle | 812ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 58000 | 4 | 32 | 0 | 0 | 1 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 46816 | 4 | 37 | 0 | 0 | 2 | Idle | 810ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 59320 | 4 | 36 | 0 | 0 | 2 | Idle | 1132ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 45092 | 4 | 41 | 0 | 0 | 2 | Idle | 715ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 17032 | 4 | 37 | 0 | 0 | 0 | Working | 917ms HTTPLog | HTTPLog (infoloc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 51936 | 4 | 38 | 0 | 0 | 0 | Working | 708ms HTTPLog | HTTPLog (infonpc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 14992 | 4 | 41 | 0 | 0 | 2 | Idle | 811ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 64144 | 4 | 37 | 0 | 0 | 2 | Idle | 814ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 51592 | 4 | 41 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 41180 | 4 | 40 | 0 | 0 | 1 | Idle | 715ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 59820 | 4 | 40 | 0 | 0 | 2 | Idle | 707ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54636 | 4 | 38 | 0 | 0 | 2 | Idle | 5740ms ProcessActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 50652 | 4 | 33 | 0 | 0 | 2 | Idle | 1134ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54920 | 4 | 46 | 0 | 0 | 2 | Idle | 607ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 788 | 4 | 36 | 0 | 0 | 0 | Working | 915ms HTTPLog | VoiceRecord [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 61464 | 4 | 36 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 48052 | 4 | 37 | 0 | 0 | 2 | Idle | 803ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 29848 | 4 | 42 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none Edited April 3, 2025 by Min 2
Talesien Posted April 3, 2025 Posted April 3, 2025 (edited) 4 hours ago, Min said: Thanks! Yeah, I've fixed probably at least 100 different unique ways that CHIM can CTD, freeze, deadlock, or otherwise bug out the game. 1.1.1.3 should be pretty stable. I'm continuing to fix issues as I come across them. CHIM had some *gnarly* issues before I started working on it.. The most egregious of these was that it was spawning thousands of threads per minute with no lifecycle management before 1.1.1... Some of those threads would deadlock (Other bugs that I've also fixed), and the threads would just live forever and leak resources. This is what was causing the freezes that Nolvus users were reporting. I spent a fair bit of time debugging and fixing that. I refactored the core of how the DLL schedules and executes work to fix this. Not a small change, but comprehensively fixes the problem. You can check out what it's doing by looking at AIAgent.log (Status dumped every 1 minute, looks like this) : [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:374] [ThreadPool] Pool Status: Uptime=4m, Queued=5648, Completed=5642, TimedOut=0, Errors=0, Cancelled=1, QueueSize=0, ActiveThreads=48 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:380] [ThreadPool] Task Type Statistics: [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:381] Type | Queued | Completed | TimedOut | Errors | Cancelled | Avg Time(ms) | Max Time(ms) [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:383] --------------------------+----------+-----------+----------+--------+----------+--------------+------------ [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] SetDrivenByAIA | 1 | 1 | 0 | 0 | 0 | 24 | 24 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPLog | 1758 | 1754 | 0 | 0 | 0 | 232 | 1135 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPStream | 1 | 1 | 0 | 0 | 1 | 14263 | 14263 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:413] Cancellation distribution by key for 'HTTPStream': [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:415] Chloe: 1 cancellations [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] VoiceRecord | 2 | 1 | 0 | 0 | 0 | 6 | 6 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] ProcessActor | 2 | 2 | 0 | 0 | 0 | 7598 | 9457 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:392] HTTPLogWithActor | 1 | 1 | 0 | 0 | 0 | 6728 | 6728 [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:422] [ThreadPool] Thread Details: [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:423] ThreadID | Uptime(m) | Tasks Done | TimeOuts | Errors | Last Task(s) | Status | Longest Task | Current Task [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:425] -----------+-----------+------------+-----------+--------+-------------+---------+---------------------------+--------------------------------------------------- [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 63220 | 4 | 36 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 50756 | 4 | 36 | 0 | 0 | 2 | Idle | 818ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 39500 | 4 | 36 | 0 | 0 | 2 | Idle | 706ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 56944 | 4 | 38 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 63152 | 4 | 30 | 0 | 0 | 2 | Idle | 817ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 17920 | 4 | 38 | 0 | 0 | 2 | Idle | 717ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 31412 | 4 | 0 | 0 | 0 | 240 | Working | 0ms | ManagerMainQueue [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 34572 | 4 | 41 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 24028 | 4 | 38 | 0 | 0 | 2 | Idle | 717ms HTTPLog | none [2025-04-02 22:48:58.886] [log] [info] [ThreadPool.h:445] 55436 | 4 | 36 | 0 | 0 | 0 | Working | 918ms HTTPLog | HTTPLog (setconf|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 34940 | 4 | 38 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 29880 | 4 | 35 | 0 | 0 | 1 | Idle | 6728ms HTTPLogWithActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 63328 | 4 | 36 | 0 | 0 | 0 | Working | 812ms HTTPLog | HTTPLog (infonpc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 55524 | 4 | 39 | 0 | 0 | 2 | Idle | 804ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 48164 | 4 | 38 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 46332 | 4 | 38 | 0 | 0 | 2 | Idle | 1135ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 4136 | 4 | 40 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 42164 | 4 | 40 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 39964 | 4 | 34 | 0 | 0 | 2 | Idle | 919ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 53840 | 4 | 35 | 0 | 0 | 2 | Idle | 14263ms HTTPStream | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 30980 | 4 | 37 | 0 | 0 | 2 | Idle | 814ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 38176 | 4 | 40 | 0 | 0 | 2 | Idle | 919ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54508 | 4 | 31 | 0 | 0 | 2 | Idle | 9457ms ProcessActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54444 | 4 | 33 | 0 | 0 | 2 | Idle | 924ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 53328 | 4 | 41 | 0 | 0 | 2 | Idle | 815ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 37508 | 4 | 40 | 0 | 0 | 2 | Idle | 806ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 52944 | 4 | 33 | 0 | 0 | 2 | Idle | 713ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 49328 | 4 | 43 | 0 | 0 | 2 | Idle | 608ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 64232 | 4 | 39 | 0 | 0 | 2 | Idle | 815ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 34508 | 4 | 33 | 0 | 0 | 2 | Idle | 812ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 58000 | 4 | 32 | 0 | 0 | 1 | Idle | 816ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 46816 | 4 | 37 | 0 | 0 | 2 | Idle | 810ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 59320 | 4 | 36 | 0 | 0 | 2 | Idle | 1132ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 45092 | 4 | 41 | 0 | 0 | 2 | Idle | 715ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 17032 | 4 | 37 | 0 | 0 | 0 | Working | 917ms HTTPLog | HTTPLog (infoloc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 51936 | 4 | 38 | 0 | 0 | 0 | Working | 708ms HTTPLog | HTTPLog (infonpc|4732) [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 14992 | 4 | 41 | 0 | 0 | 2 | Idle | 811ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 64144 | 4 | 37 | 0 | 0 | 2 | Idle | 814ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 51592 | 4 | 41 | 0 | 0 | 2 | Idle | 1133ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 41180 | 4 | 40 | 0 | 0 | 1 | Idle | 715ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 59820 | 4 | 40 | 0 | 0 | 2 | Idle | 707ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54636 | 4 | 38 | 0 | 0 | 2 | Idle | 5740ms ProcessActor | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 50652 | 4 | 33 | 0 | 0 | 2 | Idle | 1134ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 54920 | 4 | 46 | 0 | 0 | 2 | Idle | 607ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 788 | 4 | 36 | 0 | 0 | 0 | Working | 915ms HTTPLog | VoiceRecord [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 61464 | 4 | 36 | 0 | 0 | 2 | Idle | 716ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 48052 | 4 | 37 | 0 | 0 | 2 | Idle | 803ms HTTPLog | none [2025-04-02 22:48:58.887] [log] [info] [ThreadPool.h:445] 29848 | 4 | 42 | 0 | 0 | 2 | Idle | 816ms HTTPLog | none So, it seems Chim was also responsible for that bug that often prevented me from initiating a dialogue with an NPC's? I sorta suspected Chim, but the intermittent nature of the bug made it hard to fully prove it. Since 1.113 I've not seen that again (fingers crossed). Well, at least not in this extreme form that could block an NPC seemingly forever. It seems the dialogue option still vanishes from a NPC if he is currently waiting for the LLM. At least it looks that way, as the dialogue option reliably returns once the NPC said his line. Edited April 3, 2025 by Talesien
Min Posted April 4, 2025 Author Posted April 4, 2025 1 hour ago, Talesien said: So, it seems Chim was also responsible for that bug that often prevented me from initiating a dialogue with an NPC's? I sorta suspected Chim, but the intermittent nature of the bug made it hard to fully prove it. Since 1.113 I've not seen that again (fingers crossed). Well, at least not in this extreme form that could block an NPC seemingly forever. It seems the dialogue option still vanishes from a NPC if he is currently waiting for the LLM. At least it looks that way, as the dialogue option reliably returns once the NPC said his line. Yeah, CHIM does that intentionally while talking to an actor. The bug was that it wasn't being restored under some circumstances. I fixed that and made it considerably more reliable in restoring that. If you have an actor stuck in that state still, just prompting the AI to respond will fix it (Though, I don't think you'll encounter this anymore as of 1.1.1.3)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now