Dorabella Posted April 20 Posted April 20 (edited) I'm having a problem I've never encountered before. When I launch Sexlab with Falmer/Riekling, I get a CTD. For now, the issue only occurs with the creatures listed crash-2026-04-20-21-47-35.log First off, I should mention that I installed the experimental version of CF (4.0), which I found right here on LL. Could that be the cause? Before contacting the appropriate channel to report the issue, I’d rather ask No reports detects installation errors Edited May 18 by Dorabella Change title
traison Posted April 20 Posted April 20 This crash was indirectly caused by CBPC. It calls RefreshNode, which is an inlined function, passing an NiAVObject. This argument is null pointer checked. It then calls UpdateWorldData on this node, which I assume is a call into SkyrimSE.exe; somewhere in there it runs into a null pointer and crashes. The problematic node is attached to form id 0x7 reference id 0x14 "Melissa". If this experiemental version of CF contains CBPC components, then yes it could be the cause.
VeraDra Posted April 22 Posted April 22 CF is most likely just a red herring, as it doesn't have any dependancy on cbpc. We would expect CBPC to show up in the crash log as an animation is trying to play, especially since it appears to be loading some falmer-specific ABC configs. Which makes me think something with your ABC configs for Falmer/Riekling is broken, and is causing cbpc to load garbage data. Maybe something with HDT, but I'd suspect something HDT related to show up in the logs.
traison Posted April 22 Posted April 22 6 hours ago, VeraDra said: We would expect CBPC to show up in the crash log as an animation is trying to play, especially since it appears to be loading some falmer-specific ABC configs. Configs only load when the game starts or when the user issues the cbpc reload console command. SMP might be loading some* configs on demand, but CBPC does not. I've poked around in the CBPC source code for a few years, and I've not had this crash before nor do I recall fixing anything related to this. If I had to guess right now what caused this crash, it's either a skeleton thing, a race condition or a conflict with another dll. * Namely those assigned in SMP hints in meshes. 6 hours ago, VeraDra said: Maybe something with HDT, but I'd suspect something HDT related to show up in the logs. Disabling SMP is still a good test in this situation; for the same reason that disabling any other dll is also a good idea.
Dorabella Posted April 22 Author Posted April 22 I restored the previous version of CF (likely overwriting of the skeleton) After inspecting the creatures' NIF files, I noticed that they don't match the SMP XML files. Now that I've installed the creatures in CBPC, I'll run a few tests to see if the problem has been resolved 10 hours ago, traison said: and I've not had this crash before nor do I recall fixing anything related to this. Me neither it happened recently, and I didn't think much of it. Now, though, it really seems like something's wrong.
Dorabella Posted April 28 Author Posted April 28 On 4/21/2026 at 1:28 AM, traison said: This crash was indirectly caused by CBPC. As suggested, assuming the direct cause was CBPC, and since I didn't know which file was causing the problem, I uninstalled and reinstalled CBPC, and it seems the issue has been resolved I forgot to back up my files, so now the bouncing boobs aren't working anymore. What do I need to fix? In which file? Everything else works
traison Posted April 28 Posted April 28 11 minutes ago, Dorabella said: ...the bouncing boobs aren't working anymore. What do I need to fix? In which file? First decide which system you want to use to control the tits, then worry about where the files are. There's a paper in my signature for finding physics presets. It might be useful here.
Dorabella Posted April 28 Author Posted April 28 In the meantime, I've tweaked the various files and fixed the problem with the rock-hard boobs ( This time, I'm going to back up myself 😋) Before I consider the issue with the creatures resolved, I’ll run a few more tests, but for now, it seems to be fixed
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