Darcaan2012 Posted December 31, 2017 Posted December 31, 2017 I've had some problems with the recent release of DDI 4.0. It conflicts in some areas with Zaz Animation Pack 8.0. Specifically, it overwrites the zbftestzone cell in such a way that if I try to teleport to it via console, I end up falling through an endless sky-blue cell.
Princessity Posted December 31, 2017 Posted December 31, 2017 5 minutes ago, Darcaan2012 said: I've had some problems with the recent release of DDI 4.0. It conflicts in some areas with Zaz Animation Pack 8.0. Specifically, it overwrites the zbftestzone cell in such a way that if I try to teleport to it via console, I end up falling through an endless sky-blue cell. Confirmed, we seem to have a cell with the same keyword but nothing in it. It must have been an override previously but turned into a duplicate record after we dropped the ZAP dependency. We'll fix it, thank you for the report. In the meantime, you can fix it simply by moving ZaZAnimationPack.esm before Devious Devices - Integration.esm in your load order.
Wibbiz Posted December 31, 2017 Posted December 31, 2017 1 hour ago, Princessity said: We have a "bubble hood"? Are you sure you're not using third party custom devices? I am using some third party devices, but the bug extends to typical DDx gags and hoods. Just that my character's head doesn't become invisible. Reminder: I am using Succubus Race, which uses horns. I moved the general DD hider to 61 for this reason, and played around with it a bit to try to solve this, to no avail. Back to default settings + hider on 61.
TurboNerd Posted December 31, 2017 Posted December 31, 2017 8 hours ago, LazyBoot said: There's a function called GetWornDeviceFuzzyMatch (or something similar) that will look at all the keywords on a worn device, and not just the main one the device identifies as. So you can feed that the mittens keyword, and it should return the mittens. 1 hour ago, Princessity said: Any given device only has ONE main keyword which the API uses to determine it's primary function for the purpose of device manipulation and it's usually associated with the slot occupied by the device. You can see exactly which keyword it is by looking up the inventory device's zad_DeviousDevice property. There's nothing obtuse about it, it's the only device keyword specified n the properties. Device detection (GetWornKeyword) can refer to any keyword equipped on the actor, but when it comes to manipulating a specific device, the API needs a specific point of reference As LazyBoot said, if you want to acquire a device by the keywords of the Rendered item itself (and not the Inventory device API keyword), you can use GetWornDeviceFuzzyMatch. Buuuuut it's only going to acquire the rendered device so its utility is limited. Thanks for the help. It clears up a few mysteries.
Princessity Posted December 31, 2017 Posted December 31, 2017 54 minutes ago, Wibbiz said: I am using some third party devices, but the bug extends to typical DDx gags and hoods. Just that my character's head doesn't become invisible. Reminder: I am using Succubus Race, which uses horns. I moved the general DD hider to 61 for this reason, and played around with it a bit to try to solve this, to no avail. Back to default settings + hider on 61. Do they show up on a vanilla race? Like Nord? And which slot do the horns occupy?
Wibbiz Posted December 31, 2017 Posted December 31, 2017 23 minutes ago, Princessity said: Do they show up on a vanilla race? Like Nord? And which slot do the horns occupy? Slot for horns: 60 so I must change the default, which is 60; I've been told 61 was probably the best bet I just tested, still invisible on Nords. I am getting the message: gag no food effect is on (paraphrasing here but yeah integration notices it's on) Also a few textures appear to be missing... I don't get it because I didn't mess with the original installation of V4
Princessity Posted December 31, 2017 Posted December 31, 2017 2 hours ago, Wibbiz said: Slot for horns: 60 so I must change the default, which is 60; I've been told 61 was probably the best bet I just tested, still invisible on Nords. I am getting the message: gag no food effect is on (paraphrasing here but yeah integration notices it's on) Also a few textures appear to be missing... I don't get it because I didn't mess with the original installation of V4 Then you must either be missing meshes (in which case please redownload and reinstall all DD modules) or you have some third party mod overriding those items. Try starting a new game with a minimal setup (DDa, DDi, DDx and their requirements only) and see if the issues persist.
Wibbiz Posted December 31, 2017 Posted December 31, 2017 I have reloaded and redownloaded multiple times Nothing is overwriting DDX in Mod Organizer
Princessity Posted December 31, 2017 Posted December 31, 2017 1 hour ago, Wibbiz said: I have reloaded and redownloaded multiple times Nothing is overwriting DDX in Mod Organizer MO won't show you overriden esp records. Please do try the minimal setup test just to be sure n_n I cannot reproduce your issue on my end so your local setup is most likely the culprit.
Wibbiz Posted December 31, 2017 Posted December 31, 2017 2 hours ago, Princessity said: MO won't show you overriden esp records. Please do try the minimal setup test just to be sure n_n I cannot reproduce your issue on my end so your local setup is most likely the culprit. I fixed all the little bugs with 3rd party mods thanks to your help! Gags also
BlastRadius Posted January 1, 2018 Posted January 1, 2018 On 12/24/2017 at 11:12 PM, Grognakk said: Hey, i was wondering what cum texture you were using for the screenshot? Its the one all the way on the right. Awesome mod by the way I was also curious about that
WaxenFigure Posted January 2, 2018 Posted January 2, 2018 On 12/28/2017 at 12:22 AM, HGLKingShadow said: um is this for new vegas, or what? im really confused, it says you need FNIS and xp32 but i wasn't aware those were compatible with new vegas... Since this is in the SKYRIM forums and not the Fallout New Vegas forums the answer is no, it is not for New Vegas. Welcome to Lovers Lab (LL) but please be sure of what forum you are in as LL supports many different games but they all have their own forums and mods.
Musje Posted January 2, 2018 Posted January 2, 2018 I had to reinstall Skyrim; I used the same of mods including DD 4, but now the yoke is broken. NPCs wear it but they don't seem to struggle anymore as they used to when wearing it. And as a player I can't equip the yoke at all anymore. When I try, I get a dialogue about UNequiping it, then for equiping it (put on, manipulate locks etc), then again for unequiping but nothing happens. The log shows this: Spoiler [01/02/2018 - 01:33:53PM] [Zad]: OnEquipped(test: Yoke (Iron)) [01/02/2018 - 01:33:57PM] [Zad]: OnUnequipped(test: Yoke (Iron)) [01/02/2018 - 01:33:57PM] [Zad]: Rendered device is missing. Sync'ing... [01/02/2018 - 01:33:57PM] [Zad]: SyncInventory(): Nothing needs to be done. [01/02/2018 - 01:33:57PM] [Zad]: Rendered device is still missing. done. I also get these in the log Spoiler [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyE on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ArmbinderIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyC on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ZapYokeBleedoutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyA on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS06 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD05 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD08 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyB on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD07 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDChastityBeltStruggle02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ZapArmbBleedoutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDChastityBeltStruggle01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD09 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD06 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD10 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property BleedOutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS05 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyD on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyC on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyB on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyA on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyE on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDBeltedSolo on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyD on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property I tried equiping other devices like armbinders, and those work fine. I also tried reinstalling DD4 manually (I don't fully trust NMM) but that didn't help. Any ideas? This is on a newly started game by the way
worik Posted January 2, 2018 Posted January 2, 2018 27 minutes ago, Musje said: II also get these in the log Hide contents [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyE on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ArmbinderIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyC on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ZapYokeBleedoutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyA on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS06 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD05 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD08 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyB on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD07 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDChastityBeltStruggle02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeIdle01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDH01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property ZapArmbBleedoutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS04 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD03 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDChastityBeltStruggle01 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD09 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD06 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPArmBZaD10 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property YokeHorny02 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property BleedOutIdle on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZaZAPCArmBZaDS05 on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyD on script zadlibs attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyC on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyB on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyA on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyE on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDBeltedSolo on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property [01/02/2018 - 01:33:41PM] warning: Property DDZazHornyD on script zadbq00 attached to zadQuest (1900F624) cannot be initialized because the script no longer contains that property I tried equiping other devices like armbinders, and those work fine. I also tried reinstalling DD4 manually (I don't fully trust NMM) but that didn't help. Any ideas? This is on a newly started game by the way I found the same ones in my log earlier today. New game, too.
LazyBoot Posted January 2, 2018 Posted January 2, 2018 Here's another mod to join SLIF on the known to break DD4 list: Devious Device Cutting (ImmerSlave-DeviceCut.esp). I had forgotten about this since I removed it when the DD4 beta added the feature, but it does overwrite scripts from DDi and therefore is incompatible with the latest DDi. Also it's kind of obsolete/redundant since DD4 added cutting as a mechanic anyway. 2
Psalam Posted January 2, 2018 Posted January 2, 2018 Since adding DDI4 (with a new game) I have had an exponential increase in the CTDs. I am going back to DDI3. I have attached the latest papyrus log if you think it might help. Papyrus.0.log
El_Duderino Posted January 2, 2018 Posted January 2, 2018 9 minutes ago, Psalam said: Since adding DDI4 (with a new game) I have had an exponential increase in the CTDs. I am going back to DDI3. I have attached the latest papyrus log if you think it might help. Papyrus.0.log That logs looks healthy to me, but I should add that I'm really not an expert in decyphering those logs. The few DD-related errors at the beginning have been reported to be harmless IIRC. The Creature Framework mod seems awfully busy in your log though, but then I don't have that mod myself and can't say if that's just some rather detailed logging it does or if it really eats up resources. If there are increased crashes, I'd say it points to some conflict with another mod. Maybe an older DD-related mod? DD itself shouldn't have grown more resource hungry from DD3 to DD4. Maybe also check your load order for the two known critical mod conflicts with DD4, SLIF and the only recently discovered Devious Device Cutting conflict (see the post directly above yours). I don't know if having these can cause crashes though, but they certainly will prevent DD4 from functioning properly. BTW, I've been running the beta and now release versions of DD4 in a pretty heavy 220+ mods load order (about twenty SL mods incl. CD, hydra slaves, DCL, plus heavy hitters like 3DNPC, Maids 2, 2nd Civil War, and others) -- without any issues besides some infrequent out of memory crashes after prolonged play times, and all that on a five years old dual core laptop. Based on that I'm fairly confident to say that it's likely spomething specific to your load order that's causing the crashes.
Veladarius Posted January 3, 2018 Posted January 3, 2018 3 hours ago, Psalam said: Since adding DDI4 (with a new game) I have had an exponential increase in the CTDs. I am going back to DDI3. I have attached the latest papyrus log if you think it might help. Papyrus.0.log Turn down how often Creature Framework runs and decrease the scan distance. By default it scans a 2 cell radius every 5 seconds and checks every actor (since animals are actors too). I found this to be unstable and going to 30 seconds and 1 cell made it much more stable.
netruss1964 Posted January 3, 2018 Posted January 3, 2018 17 minutes ago, Veladarius said: Turn down how often Creature Framework runs and decrease the scan distance. By default it scans a 2 cell radius every 5 seconds and checks every actor (since animals are actors too). I found this to be unstable and going to 30 seconds and 1 cell made it much more stable. Nice, I knew reading the forums would pay off. Thank you for this bit. I had turned up the timing but did not alter the distance. Thanks again! Happy new year!
c6222848 Posted January 3, 2018 Posted January 3, 2018 is it normal that i can open the item inventory now with the armbinder on? I'd prefer the older force-to-open first tab, is there a toggle for that?
Psalam Posted January 3, 2018 Posted January 3, 2018 19 hours ago, Veladarius said: Turn down how often Creature Framework runs and decrease the scan distance. By default it scans a 2 cell radius every 5 seconds and checks every actor (since animals are actors too). I found this to be unstable and going to 30 seconds and 1 cell made it much more stable. That did, at first, seem to improve performance but I still went only about 15 minutes before CTD. Here is the "after" changes log. Papyrus.0.log
Nazzzgul666 Posted January 3, 2018 Posted January 3, 2018 On 31.12.2017 at 9:02 PM, Wibbiz said: I fixed all the little bugs with 3rd party mods thanks to your help! Gags also I had/have the same problem you described earlier, some non-Bodyslide items not visible and even getting head invisible with hoods. Additionally aimations for yokes/armbinders didn't work. I've found a workaround, but not what caused these problems, happened even with pretty much minimum setup. Could you give me a hint how you've fixed it?
zenvois Posted January 3, 2018 Posted January 3, 2018 Would is be possible for a running list of unsupported mods with the new update? (if one has not been started already)
Wibbiz Posted January 3, 2018 Posted January 3, 2018 1 hour ago, Nazzzgul666 said: I had/have the same problem you described earlier, some non-Bodyslide items not visible and even getting head invisible with hoods. Additionally aimations for yokes/armbinders didn't work. I've found a workaround, but not what caused these problems, happened even with pretty much minimum setup. Could you give me a hint how you've fixed it? Complete reinstall after checking if minimal setup doesn't fix it. Do the minimal setup, keep additemmenu if you have it it's easier. (I'd been tinkering too much again trying to solve the issue) Re-do Bodyslide morphs unless you have them saved somewhere safe (or put them somewhere safe first) Get rid of your TestMeshX folder/mod you suggested I try. By this point, it might just mess with the mod. Also EquipItemFix is not a good thing to run. It should be called EquipItemBreak. Remove that if you run it! Check your right side of MO to see if the .esp is in.
Veladarius Posted January 4, 2018 Posted January 4, 2018 2 hours ago, Psalam said: That did, at first, seem to improve performance but I still went only about 15 minutes before CTD. Here is the "after" changes log. Papyrus.0.log These are the things I see in the last 2/3 of your log: - Creature Framework (at least half that part of the log is from that) - SOS (on occasion) - DD (typically when events are triggered) - UFO (on occasion) - Aroused (typical scan, default I believe is every 180 seconds or something like that) - FNIS Sexy Move (Idle being reset by DD after using something that uses a DD animation is removed) - Errors on Follower Dialogue Script (Skyrim script, may be caused by UFO) - Errors from Creature Framework (lower down in the log, instability may be starting as a few errors are starting to appear) - Sexlab Scene (no issues) - Slavetats (taking a LOT of entries within three seconds to decide what to do and do it, close to 2 dozen entries within that time period for 1 actor - excessive if you ask me) but only happens once. Overall, Creature Framework (CF) and FNIS resetting an actors idle are the majority of entries within 30 minutes. There are only a few errors overall just a lot of activity from the two mods mentioned. CF still has a lot of entries when it runs so you may want to make some more adjustments to it, maybe cut the scan distance to half of what you have now. With FNIS Sexy Move you may want to just set it to use just one animation set and not pick randomly. For 30 minutes of play it isn't an overly large log file and is fairly clean but CF is at least half of the log.
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