DonQuiWho Posted October 30, 2016 Posted October 30, 2016 update in green Effectively the new settings let you make it be half as much as before, since 65% chance versus 100% before is getting close to half, plus the damage amount can go down lower by 10%. Also note that the damage percent is a damage of remaining health, not total health. So if it's 40%, and lets assume you have no healing regen... the first bleeding would leave you at 60%, then the 2nd at 24. But with normal regen you never go below 50% health so essentially its only making things more dangerous while in combat. OK. Hadn't really twigged that, and it should be easy to check, assuming I can get Nocturnal to be nasty to me again And it might be worth noting that DA (and possibly Defeat? - I'm sure someone else will know OTTOTH) actually REDUCE health regeneration for an extended period, sometimes to zero (see -ve active effects in the magic menu), so if SLAV kicks in another punishment bleeding while that is so, the level to which the PC's health has been restored by that point may really be a lot less than you might think/expect Is that maybe worth another look at your end? DA can definitely cut health regeneration as part of the 'Near Death Experience', 100% slower with healing spells only 75% effective. And collar bleeding certainly can take you below 50% heath Another change which is in 2.81 (copied from change log)... Updated - Instead of Delayed Orgasm causing a forced dismount if you are mounted, Delayed Orgasm will not occur when you are mounted. Bleeding from punishing collars will still force dismount you if your health is low. Delayed Orgasm now has a chance of Exhilaration Dance You said getting dismounted was way too often, but I believe this was from delayed orgasm mostly, not the bleeding. FWIW, if 'Delayed Orgasm' should initiate any orgasmic animation on forced dismount, then I never saw one and remount could be carried out immediately, which maybe might imply that it was a health issue? Whatever, next time I'll count both! I tried this again, using the same save as a starting point, updated to 2.81. Test area was in the moorland area just west of Whiterun's city wall Using the new update's default settings, the PC got dismounted just as frequently, at points where the collar bleed message appeared. I reduced the punishment effects all to MCM minimum values and chance of Delayed orgarsm to Zero. The PC still was being dismounted on collar bleed & related message at about same intervals Leaving the horse, and just having the PC run around with those reduced settings though, did have one strange effect, in that the frequency of the collar bleed event seemed to reduce quite a bit. Pretty sure I wasn't imagining that, and the screenshot times seem to bear out the perception. But might just have been a fluke Feedback on this from anyone is appreciated. I can easily lower the chance minimum and damage minimums, but found it was fine when I tried a vampire which I suck at. I used the new default settings, not the min. With the Punitive Collar in particular, there needs to be incentive to report in or you could just go on wearing it forever. Hope those help you a bit further BTW, Halloween in Whiterun is priceless. Thanks vm
DonQuiWho Posted October 30, 2016 Posted October 30, 2016 Added this one as a separate issue, rather than muddle it into the others Just thought I'd mention that I get [EDIT] this same errorS in my logs every time '[Virgin}: Periodic Checks' appears.... [10/30/2016 - 11:46:54AM] [Virgin}: Periodic Checks[10/30/2016 - 11:46:54AM] Error: Cannot call IsSameLocation() on a None object, aborting function call ......followed by a bunch of, Virgin referenced, stacks. They vary, but I've added a couple of examples for reference. Might just be peculiar to my game, but thought you might be interested in case there's any sign that it's a more generic issue Hope this is of some use ================================ first appearance [10/30/2016 - 11:46:54AM] [Virgin}: Periodic Checks[10/30/2016 - 11:46:54AM] Error: Cannot call IsSameLocation() on a None object, aborting function callstack: [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507 [VirginStoryMain (F401848C)].virginmain.VirginSetHideousFrostResist() - "VirginMain.psc" Line 813 [item 3 in container (F408BA66)].VirginWristRestraintsScript.OnEquippedPost() - "VirginWristRestraintsScript.psc" Line 14 [item 3 in container (F408BA66)].VirginWristRestraintsScript.OnEquipped() - "zadEquipScript.psc" Line 138[10/30/2016 - 11:46:54AM] warning: Assigning None to a non-object variable named "::temp20"stack: [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507 [VirginStoryMain (F401848C)].virginmain.VirginSetHideousFrostResist() - "VirginMain.psc" Line 813 [item 3 in container (F408BA66)].VirginWristRestraintsScript.OnEquippedPost() - "VirginWristRestraintsScript.psc" Line 14 [item 3 in container (F408BA66)].VirginWristRestraintsScript.OnEquipped() - "zadEquipScript.psc" Line 138 ----------------------------- typical later appearances [10/30/2016 - 12:05:40PM] [Virgin}: Periodic Checks[10/30/2016 - 12:05:41PM] Error: Cannot check location against a None locationstack: [ (00018A56)].Location.HasCommonParent() - "<native>" Line ? [ (00018A56)].Location.IsSameLocation() - "Location.psc" Line 32 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507[10/30/2016 - 12:05:41PM] Error: Cannot call HasKeyword() on a None object, aborting function callstack: [ (00018A56)].Location.IsSameLocation() - "Location.psc" Line 34 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507[10/30/2016 - 12:05:41PM] warning: Assigning None to a non-object variable named "::temp2"stack: [ (00018A56)].Location.IsSameLocation() - "Location.psc" Line 34 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507[10/30/2016 - 12:05:41PM] Error: Cannot check location against a None locationstack: [ (00018A56)].Location.IsChild() - "<native>" Line ? [ (00018A56)].Location.IsSameLocation() - "Location.psc" Line 37 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 507[10/30/2016 - 12:05:41PM] Error: Cannot check location against a None locationstack: [ (0010D4BA)].Location.HasCommonParent() - "<native>" Line ? [ (0010D4BA)].Location.IsSameLocation() - "Location.psc" Line 32 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 513[10/30/2016 - 12:05:41PM] Error: Cannot call HasKeyword() on a None object, aborting function callstack: [ (0010D4BA)].Location.IsSameLocation() - "Location.psc" Line 34 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 513[10/30/2016 - 12:05:41PM] warning: Assigning None to a non-object variable named "::temp2"stack: [ (0010D4BA)].Location.IsSameLocation() - "Location.psc" Line 34 [VirginStoryMain (F401848C)].virginmain.OnUpdateGameTime() - "VirginMain.psc" Line 513
Bushi Neko Posted October 30, 2016 Posted October 30, 2016 lol! I took a bit of a break from Skyrim.. and come back to check on this.. wow.. your still at it! Excellent!!!! :-)
Guest Posted October 30, 2016 Posted October 30, 2016 Gotta say I really am enjoying the mod so far it reminded me I once created a colored texture of nocturnal just thought I would show here seems fitting.
VirginMarie Posted October 30, 2016 Author Posted October 30, 2016 Is the main quest considered complete after gaining the trust of 8 daedric? As of right now only 8 Daedric Princes have been completed. VirginMarie is looking into ways to expand but some Princes require a huge amount of work to make feasible. For example, Mephala's quest is not even able to be started until level 20, which not all players are necessarily going to get if they rely heavily on the love shout to progress through the mod. It would require figuring out how to "break" the quest start to ensure everyone can do it, which is not always easy. New Princes are added when there is a reliable way to ensure players can continue unimpeded. I would consider the main story to be complete when you've earned the 3rd word. In order to reach that point, you need to have done enough spits, and enough shrines. This involves both Nocturnal and Dibella side of things. Nocturne has no new dialogue after reporting in. How do I complete the objective to read tome in front of daedric princes as a virgin? Reading the Enchantment Tome in front of Sheogorath's Worship thing does nothing. Read the tome in front of the shrines of the Daedric Princes in Nocturnal's Sepulchre where you get rebirthed. Let us know if you have trouble with that. You need to be a virgin of course, which would take another rebirth ritual if you are not. Is the virgin anal soulgem related to a quest or only acquirable through MCM menu? The only devices at this time that require a quest to gain access to them are the Tales and Tallows devices from the 2.8 update. All others are only acquirable through MCM and being put into virgin training again. Whether or not any devices in the future have a quest requirement has not been decided as testing other ideas and requests for implementation have taken priority for now. Hope this answers your questions.
VirginMarie Posted October 30, 2016 Author Posted October 30, 2016 update in green Effectively the new settings let you make it be half as much as before, since 65% chance versus 100% before is getting close to half, plus the damage amount can go down lower by 10%. Also note that the damage percent is a damage of remaining health, not total health. So if it's 40%, and lets assume you have no healing regen... the first bleeding would leave you at 60%, then the 2nd at 24. But with normal regen you never go below 50% health so essentially its only making things more dangerous while in combat. OK. Hadn't really twigged that, and it should be easy to check, assuming I can get Nocturnal to be nasty to me again And it might be worth noting that DA (and possibly Defeat? - I'm sure someone else will know OTTOTH) actually REDUCE health regeneration for an extended period, sometimes to zero (see -ve active effects in the magic menu), so if SLAV kicks in another punishment bleeding while that is so, the level to which the PC's health has been restored by that point may really be a lot less than you might think/expect Is that maybe worth another look at your end? DA can definitely cut health regeneration as part of the 'Near Death Experience', 100% slower with healing spells only 75% effective. And collar bleeding certainly can take you below 50% heath Yes and this is intended. The part where I said wont go below 50% is in the first scenario below. There needs to be a disadvantage to nearly dying. There needs to be incentive to report in. I'd summarize it as follows to depict the intended: Player with normal health regen - Breast Torture Collar Player not in combat - health will rarely go below 50% due to the re-gen Provides more challenge when in combat. Train up your healing and don't die again Player with normal health regen - Punitive Collar Player not in combat - Initially, health will rarely go below 50% due to the re-gen. Over time it will and will become intolerable eventually such that you need to submit to Nocturnal Provides more challenge when in combat. Same progression over time Player with no health regen (example: vampire in daylight) - Breast Torture Collar Player not in combat - need to heal self or eventually die again - should be very manageable though Provides more challenge when in combat. Since needing to heal is normal, I found this did not feel much different using a vampire Player with normal no health regen - Punitive Collar - you get the idea I would just be repeating the above You have two settings: Chance to Bleed / Amount of Bleed So the question to users like you, with other mods in play, is... What settings are needed to achieve the above intentions? Something lower and if so to what amount? I can also think of a 3rd Setting that could be added... Bleeding occurs in combat (yes/no). Currently without it, you are stuck on yes. Is it in combat where it's too difficult? In order to answer those you really do need to have play tested a fair bit to get a proper feel of how it does work. And if you have this mod's DA turned off, you are also not getting the full picture since you'd not be getting the Breast Torture Collar. Another change which is in 2.81 (copied from change log)... Updated - Instead of Delayed Orgasm causing a forced dismount if you are mounted, Delayed Orgasm will not occur when you are mounted. Bleeding from punishing collars will still force dismount you if your health is low. Delayed Orgasm now has a chance of Exhilaration Dance You said getting dismounted was way too often, but I believe this was from delayed orgasm mostly, not the bleeding. FWIW, if 'Delayed Orgasm' should initiate any orgasmic animation on forced dismount, then I never saw one and remount could be carried out immediately, which maybe might imply that it was a health issue? Whatever, next time I'll count both! I tried this again, using the same save as a starting point, updated to 2.81. Test area was in the moorland area just west of Whiterun's city wall Using the new update's default settings, the PC got dismounted just as frequently, at points where the collar bleed message appeared. I reduced the punishment effects all to MCM minimum values and chance of Delayed orgarsm to Zero. The PC still was being dismounted on collar bleed & related message at about same intervals force-dismounted + No Delayed Orgasm occurring = you were dismounted due to bleeding In my testing this only occurs at low level (less than 5ish), or if you have no health regen... such as a vampire in daylight. What level are you at? An MCM setting I could add for this is "Bleeding while mounted (yes/no)". Does this seem needed? Leaving the horse, and just having the PC run around with those reduced settings though, did have one strange effect, in that the frequency of the collar bleed event seemed to reduce quite a bit. Pretty sure I wasn't imagining that, and the screenshot times seem to bear out the perception. But might just have been a fluke The setting "Chance of Bleeding" would give you that effect. It's the intended effect Chance of bleeding = each 15mins, do you bleed or not Feedback on this from anyone is appreciated. I can easily lower the chance minimum and damage minimums, but found it was fine when I tried a vampire which I suck at. I used the new default settings, not the min. With the Punitive Collar in particular, there needs to be incentive to report in or you could just go on wearing it forever. Hope those help you a bit further BTW, Halloween in Whiterun is priceless. Thanks vm Glad that grabbed your attention. There's some other things around like that. Good for screenshots which we need more submissions of Thanks for helping me to sort this out. More feedback appreciated but don't feel obligated to use up your time. To summarize, I may go ahead provide a lower minimum on the two settings for the next release. I'm not sure If I should also add the two additional settings described above.
VirginMarie Posted October 30, 2016 Author Posted October 30, 2016 Added this one as a separate issue, rather than muddle it into the others Just thought I'd mention that I get [EDIT] this same errorS in my logs every time '[Virgin}: Periodic Checks' appears.... [10/30/2016 - 11:46:54AM] [Virgin}: Periodic Checks [10/30/2016 - 11:46:54AM] Error: Cannot call IsSameLocation() on a None object, aborting function call ......followed by a bunch of, Virgin referenced, stacks. They vary, but I've added a couple of examples for reference. Might just be peculiar to my game, but thought you might be interested in case there's any sign that it's a more generic issue Hope this is of some use Yes I'm aware if this log message. It's been there since the very first version of this mod. It occurs when an NPC is on-route, looking for you, and then you've changed locations. The "tech" here is the same as the vanilla game courier, and the vanilla game courier can generate the same message. That's why I've not worried about it since it does not hurt anything. However now that I have more NPCs doing this (added 3 different ghosts in recent versions), the occurrences are greater so it's making much more mess in the log So it's on my list to see if I can't make Papyrus happy. lol! I took a bit of a break from Skyrim.. and come back to check on this.. wow.. your still at it! Excellent!!!! :-) Looking forward to seeing your Halloween pics. How about wearing a pumpkin gag on your waterfall loving machine? Gotta say I really am enjoying the mod so far it reminded me I once created a colored texture of nocturnal just thought I would show here seems fitting. Oh this is cool. What exactly did you do? I'm wondering if there's something here I could use in the mod.
DonQuiWho Posted October 30, 2016 Posted October 30, 2016 Added this one as a separate issue, rather than muddle it into the others Just thought I'd mention that I get [EDIT] this same errorS in my logs every time '[Virgin}: Periodic Checks' appears.... [10/30/2016 - 11:46:54AM] [Virgin}: Periodic Checks [10/30/2016 - 11:46:54AM] Error: Cannot call IsSameLocation() on a None object, aborting function call ......followed by a bunch of, Virgin referenced, stacks. They vary, but I've added a couple of examples for reference. Might just be peculiar to my game, but thought you might be interested in case there's any sign that it's a more generic issue Hope this is of some use Yes I'm aware if this log message. It's been there since the very first version of this mod. It occurs when an NPC is on-route, looking for you, and then you've changed locations. The "tech" here is the same as the vanilla game courier, and the vanilla game courier can generate the same message. That's why I've not worried about it since it does not hurt anything. However now that I have more NPCs doing this (added 3 different ghosts in recent versions), the occurrences are greater so it's making much more mess in the log So it's on my list to see if I can't make Papyrus happy. Good to know that the sky probably isn't going to fall down tomorrow I had wondered if it was Cassia or the like, desperately trying to find my PC Still, it has its plusses, as if she has to wait, the more eager she should be.....
DonQuiWho Posted October 30, 2016 Posted October 30, 2016 update in green Effectively the new settings let you make it be half as much as before, since 65% chance versus 100% before is getting close to half, plus the damage amount can go down lower by 10%. Also note that the damage percent is a damage of remaining health, not total health. So if it's 40%, and lets assume you have no healing regen... the first bleeding would leave you at 60%, then the 2nd at 24. But with normal regen you never go below 50% health so essentially its only making things more dangerous while in combat. OK. Hadn't really twigged that, and it should be easy to check, assuming I can get Nocturnal to be nasty to me again And it might be worth noting that DA (and possibly Defeat? - I'm sure someone else will know OTTOTH) actually REDUCE health regeneration for an extended period, sometimes to zero (see -ve active effects in the magic menu), so if SLAV kicks in another punishment bleeding while that is so, the level to which the PC's health has been restored by that point may really be a lot less than you might think/expect Is that maybe worth another look at your end? DA can definitely cut health regeneration as part of the 'Near Death Experience', 100% slower with healing spells only 75% effective. And collar bleeding certainly can take you below 50% heath Yes and this is intended. The part where I said wont go below 50% is in the first scenario below. There needs to be a disadvantage to nearly dying. There needs to be incentive to report in. I'd summarize it as follows to depict the intended: Player with normal health regen - Breast Torture Collar Player not in combat - health will rarely go below 50% due to the re-gen Provides more challenge when in combat. Train up your healing and don't die again Player with normal health regen - Punitive Collar Player not in combat - Initially, health will rarely go below 50% due to the re-gen. Over time it will and will become intolerable eventually such that you need to submit to Nocturnal Provides more challenge when in combat. Same progression over time Player with no health regen (example: vampire in daylight) - Breast Torture Collar Player not in combat - need to heal self or eventually die again - should be very manageable though Provides more challenge when in combat. Since needing to heal is normal, I found this did not feel much different using a vampire Player with normal no health regen - Punitive Collar - you get the idea I would just be repeating the above You have two settings: Chance to Bleed / Amount of Bleed So the question to users like you, with other mods in play, is... What settings are needed to achieve the above intentions? Something lower and if so to what amount? I can also think of a 3rd Setting that could be added... Bleeding occurs in combat (yes/no). Currently without it, you are stuck on yes. Is it in combat where it's too difficult? In order to answer those you really do need to have play tested a fair bit to get a proper feel of how it does work. And if you have this mod's DA turned off, you are also not getting the full picture since you'd not be getting the Breast Torture Collar. I see where you're coming from, and it does make a lot of sense in some circumstances, as well as for the style of gameplay that many may use, but an alternative take might be: - If you already well down on health when combat starts, having just had a massive zap from, say, the collar, a couple of hits can get you beaten almost instantly. - Although I haven't tested it too much with 2.8.1, the version prior to the increased minimums actually could get the PC to bleedout, and DA would kick in, on a collar zap that took place AFTER combat. You might have won, but , if severely wounded in the process, who needs enemies if your collar, as a sort of proxy for Nocturnal's spiteful sense of humour, can then still kill you? - And if you are down a dungeon, and you have already auto consumed all the health potions that you had, you're probably then looking for the proverbial gum tree, not to make life even more difficult, but just to save you.... There's no right answer to what limits should be set. Making them too varaible could make the mod much easier to play than you might like, and I certainly wouldn't want to have wasted my time either to craft something that every neep-heid (very apposite at Halloween ) could walk their way through effortlessly by setting every limit to zero. I've made the point. It's time others had a say as to what they think might be sensible, rather than letting me run all over it Another change which is in 2.81 (copied from change log)... Updated - Instead of Delayed Orgasm causing a forced dismount if you are mounted, Delayed Orgasm will not occur when you are mounted. Bleeding from punishing collars will still force dismount you if your health is low. Delayed Orgasm now has a chance of Exhilaration Dance You said getting dismounted was way too often, but I believe this was from delayed orgasm mostly, not the bleeding. FWIW, if 'Delayed Orgasm' should initiate any orgasmic animation on forced dismount, then I never saw one and remount could be carried out immediately, which maybe might imply that it was a health issue? Whatever, next time I'll count both! I tried this again, using the same save as a starting point, updated to 2.81. Test area was in the moorland area just west of Whiterun's city wall Using the new update's default settings, the PC got dismounted just as frequently, at points where the collar bleed message appeared. I reduced the punishment effects all to MCM minimum values and chance of Delayed orgarsm to Zero. The PC still was being dismounted on collar bleed & related message at about same intervals force-dismounted + No Delayed Orgasm occurring = you were dismounted due to bleeding In my testing this only occurs at low level (less than 5ish), or if you have no health regen... such as a vampire in daylight. What level are you at? An MCM setting I could add for this is "Bleeding while mounted (yes/no)". Does this seem needed? My PC is at level 50, so I guess I would have to say 'No' Leaving the horse, and just having the PC run around with those reduced settings though, did have one strange effect, in that the frequency of the collar bleed event seemed to reduce quite a bit. Pretty sure I wasn't imagining that, and the screenshot times seem to bear out the perception. But might just have been a fluke The setting "Chance of Bleeding" would give you that effect. It's the intended effect Chance of bleeding = each 15mins, do you bleed or not Yes, our heart and soul bleeds alright. It just seemed to be less often. Maybe the horseride bounces the collar up and down more? ...at which point, the Virgin wanders off, wondering which of us has the least grip on reality.. LOL Feedback on this from anyone is appreciated. I can easily lower the chance minimum and damage minimums, but found it was fine when I tried a vampire which I suck at. I used the new default settings, not the min. With the Punitive Collar in particular, there needs to be incentive to report in or you could just go on wearing it forever. Good for screenshots which we need more submissions of Thanks for helping me to sort this out. More feedback appreciated but don't feel obligated to use up your time. To summarize, I may go ahead provide a lower minimum on the two settings for the next release. I'm not sure If I should also add the two additional settings described above. Go on, folks, make sure you have your say too! And, very quickly, with no pretence of any finesse
VirginMarie Posted October 30, 2016 Author Posted October 30, 2016 20161029222614_1.jpg20161030211818_1.jpg20161030213132_1.jpg Thanks! I've posted two of them here. Not the Halloween pic section, but I do like these two pics a lot. One showing devices nicely, the other is a great punishment pic.
VirginMarie Posted October 30, 2016 Author Posted October 30, 2016 force-dismounted + No Delayed Orgasm occurring = you were dismounted due to bleeding In my testing this only occurs at low level (less than 5ish), or if you have no health regen... such as a vampire in daylight. What level are you at? An MCM setting I could add for this is "Bleeding while mounted (yes/no)". Does this seem needed? My PC is at level 50, so I guess I would have to say 'No' Thanks for helping me to sort this out. More feedback appreciated but don't feel obligated to use up your time. To summarize, I may go ahead provide a lower minimum on the two settings for the next release. I'm not sure If I should also add the two additional settings described above. Go on, folks, make sure you have your say too! And, very quickly, with no pretence of any finesse TESV 2016-10-30 15-43-09-44 cropped.jpg TESV 2016-10-30 12-31-55-16 cropped.jpg Your pics are now here. That's some funny stuff above (I mean in your reply, not the pics... the pics are spooooooky) Just one last question I have, then its enough info I think.... I'm starting to think maybe my testing needs to have included high level player scenarios. Could you tell me, what % of heath approximately, do you have, when you get dismounted due to bleeding? I mean what was it at right before you see the dismount? By the way the reason you are dismounted is not because Nocturnal is evil, its actually because death or bleedout while mounted results in an unstuckable stuck idle. So I had to do this... the skyrim engine gods made me.
DonQuiWho Posted October 30, 2016 Posted October 30, 2016 force-dismounted + No Delayed Orgasm occurring = you were dismounted due to bleeding In my testing this only occurs at low level (less than 5ish), or if you have no health regen... such as a vampire in daylight. What level are you at? An MCM setting I could add for this is "Bleeding while mounted (yes/no)". Does this seem needed? My PC is at level 50, so I guess I would have to say 'No' Thanks for helping me to sort this out. More feedback appreciated but don't feel obligated to use up your time. To summarize, I may go ahead provide a lower minimum on the two settings for the next release. I'm not sure If I should also add the two additional settings described above. Go on, folks, make sure you have your say too! And, very quickly, with no pretence of any finesse TESV 2016-10-30 15-43-09-44 cropped.jpg TESV 2016-10-30 12-31-55-16 cropped.jpg Your pics are now here. That's some funny stuff above (I mean in your reply, not the pics... the pics are spooooooky) Just one last question I have, then its enough info I think.... I'm starting to think maybe my testing needs to have included high level player scenarios. Could you tell me, what % of heath approximately, do you have, when you get dismounted due to bleeding? I mean what was it at right before you see the dismount? By the way the reason you are dismounted is not because Nocturnal is evil, its actually because death or bleedout while mounted results in an unstuckable stuck idle. So I had to do this... the skyrim engine gods made me. Do these help give some idea?
VirginMarie Posted October 31, 2016 Author Posted October 31, 2016 TESV 2016-10-30 11-52-05-51.jpgTESV 2016-10-30 11-52-25-41.jpgTESV 2016-10-30 11-53-30-51.jpgTESV 2016-10-30 11-53-44-32.jpgTESV 2016-10-30 11-54-13-34.jpgTESV 2016-10-30 11-54-25-49.jpgTESV 2016-10-30 11-55-39-82.jpgTESV 2016-10-30 11-55-48-61.jpg Do these help give some idea? Yes for sure. Working as intended. Basically you've been a really really bad girl. You managed to not report in, then be out there in the wilds long enough to reach the max of 90%. You should not expect to be able to ride a horse at all
DonQuiWho Posted October 31, 2016 Posted October 31, 2016 TESV 2016-10-30 11-52-05-51.jpgTESV 2016-10-30 11-52-25-41.jpgTESV 2016-10-30 11-53-30-51.jpgTESV 2016-10-30 11-53-44-32.jpgTESV 2016-10-30 11-54-13-34.jpgTESV 2016-10-30 11-54-25-49.jpgTESV 2016-10-30 11-55-39-82.jpgTESV 2016-10-30 11-55-48-61.jpg Do these help give some idea? Yes for sure. Working as intended. Basically you've been a really really bad girl. You managed to not report in, then be out there in the wilds long enough to reach the max of 90%. You should not expect to be able to ride a horse at all I really really should have closed down my PC ......LOL OK, I can see the merits of that So how about an alternative to messing about with all the settings etc? Just make the report back period a variable, ie 10/15/20/25/30 days, locked after each rebirth? That would make the game more manageable for those of us who eschew those pussy notions of Fast Travel and similar nonsense, by giving us a better timeframe in which to manage our main activities. If you play that way, and are also trying to make progress in the base game, at present it can take a day to get back to Nocturnal's secret entrances , some additional time while she torments your's, and a day back to where you left off whatever else you were doing, which might not be much different, but may be a long way away. A longer return interval would make the time out of the main game relatively smaller, and could be set by the player to suit their customised playstyle. I think that a similar change was made in Slaverun/Slaverun Reloaded(?) because the short report back time was driving people nuts And it has an upside for the mod author because, as Nocturnal's boon, for dispensing such benificence and accompanying indulgences, she could exact a heavier price, ie upping the level and nature of punishments levied on failure to comply with the extended times. Not by inflicting more bleeding collars and suchlike (No, please no!) but, for instance, after the bad girlie has suffered a painful rebirth, with no easy epidural option allowed, on her then being finally despatched from Sovngarde via the portal to the mortal world, you could deliver the miscreant straight into Prison Overhaul, where they would be welcomed by Inte with an open jail cell and a few days in the pillory, or maybe sent to SD+ to be owned for a while by a nastie, or to Simple Slavery and who knows what then, depending on what mods the player has installed, by using the existing hooks into those that are already potential outcomes from DA, Simple Slavery and the like. That would teach your PC to try to take advantage! Stories are alkl very well, but would that be something simple to do? Basic changes would appear to be a change to the variable report back time, a check on whether or not it's being used when dumped out of Sovngarde, (if people stay at 10 days, they should be spared the added trauma) and cribbing whatever code is used to recognise, and dump PCs into, those other mods. I'm sure Cassie and the others will still manage to port their way in, but can be told to go away, and messages about beautiful suicide jumping off spots and the like will still roll in over the ether, but they seem to just add to quests but don't require instant completion so hopefully wouldn't interfere. I'm sure it won't be THAT simple, but how's that for a suggestion? Or is it just a pipe dream? And is anybody else out there alive and got a voice? Or are you all wandering around the wilderness chewing logs between your teeth whilst ringing bells with your sphincter muscles? Wiggle your butts and indulge in some method ringing. I'm sure that Her Blastedness will understand what you're trying to tell her
mercplatypus Posted October 31, 2016 Posted October 31, 2016 TESV 2016-10-30 11-52-05-51.jpgTESV 2016-10-30 11-52-25-41.jpgTESV 2016-10-30 11-53-30-51.jpgTESV 2016-10-30 11-53-44-32.jpgTESV 2016-10-30 11-54-13-34.jpgTESV 2016-10-30 11-54-25-49.jpgTESV 2016-10-30 11-55-39-82.jpgTESV 2016-10-30 11-55-48-61.jpg Do these help give some idea? Yes for sure. Working as intended. Basically you've been a really really bad girl. You managed to not report in, then be out there in the wilds long enough to reach the max of 90%. You should not expect to be able to ride a horse at all I really really should have closed down my PC ......LOL OK, I can see the merits of that So how about an alternative to messing about with all the settings etc? Just make the report back period a variable, ie 10/15/20/25/30 days, locked after each rebirth? It is variable between 1-10 days set by the player. Are 10 days not enough, or were you unaware that you had up to 10 days? That would make the game more manageable for those of us who eschew those pussy notions of Fast Travel and similar nonsense, by giving us a better timeframe in which to manage our main activities. If you play that way, and are also trying to make progress in the base game, at present it can take a day to get back to Nocturnal's secret entrances , some additional time while she torments your's, and a day back to where you left off whatever else you were doing, which might not be much different, but may be a long way away. A longer return interval would make the time out of the main game relatively smaller, and could be set by the player to suit their customised playstyle. I think that a similar change was made in Slaverun/Slaverun Reloaded(?) because the short report back time was driving people nuts And it has an upside for the mod author because, as Nocturnal's boon, for dispensing such benificence and accompanying indulgences, she could exact a heavier price, ie upping the level and nature of punishments levied on failure to comply with the extended times. Not by inflicting more bleeding collars and suchlike (No, please no!) but, for instance, after the bad girlie has suffered a painful rebirth, with no easy epidural option allowed, on her then being finally despatched from Sovngarde via the portal to the mortal world, you could deliver the miscreant straight into Prison Overhaul, where they would be welcomed by Inte with an open jail cell and a few days in the pillory, or maybe sent to SD+ to be owned for a while by a nastie, or to Simple Slavery and who knows what then, depending on what mods the player has installed, by using the existing hooks into those that are already potential outcomes from DA, Simple Slavery and the like. I don't think this will happen for a long time, if ever. The main problem is design philosophy. Virgin is something that is meant to add to the base game, not to take you away from it. Making it play nicely alongside other mods is not so difficult to do. Making things like prison overhaul or SD+ a requirement goes directly against the design behind the mod. Besides, too many dependencies could destabilize Virgin very easily meaning we would be going over old news over and over again and never able to look for anything new. Plus you have another concern: if Nocturnal wants you to keep your virginity why on earth would she send you to be a sex slave, especially after rebirth? A brief punishment period that you can fast forward through has been the best middle ground thus far. If we have something that can be done t 10 minutes or less its worth looking at. That would teach your PC to try to take advantage! Stories are alkl very well, but would that be something simple to do? Basic changes would appear to be a change to the variable report back time, a check on whether or not it's being used when dumped out of Sovngarde, (if people stay at 10 days, they should be spared the added trauma) and cribbing whatever code is used to recognise, and dump PCs into, those other mods. I'm sure Cassie and the others will still manage to port their way in, but can be told to go away, and messages about beautiful suicide jumping off spots and the like will still roll in over the ether, but they seem to just add to quests but don't require instant completion so hopefully wouldn't interfere. I'm sure it won't be THAT simple, but how's that for a suggestion? Or is it just a pipe dream? In theory, not so difficult. Getting it to do so without major issues in practice is another story. It is much more stable, much smoother, and much easier to support when we avoid multiple masters like SD+ and incporporate directly into Virgin itself. A huge number of our current troubleshooting and workaround issues have nothing to do with Virgin but how it interacts with other mods. We include something like a tie in to SD+ the number of issues gets multiplied. For now, especially given all other requests out there, anything that cannot be put directly inside the mod is a very low priority. And is anybody else out there alive and got a voice? Or are you all wandering around the wilderness chewing logs between your teeth whilst ringing bells with your sphincter muscles? Wiggle your butts and indulge in some method ringing. I'm sure that Her Blastedness will understand what you're trying to tell her
pyrobladeich Posted October 31, 2016 Posted October 31, 2016 Is anyone else having an issue with the new Halloween version corrupting all 3 save types? I uninstalled it and I was able to save and load the save without CTD. I even tried it on a new game and it works for a wile then the saves start corrupting again. I thought it mite be too many scripted mods so I uninstalled some other heavily scripted mods and still no luck. I didn't have any issues until the Halloween version came out.
mercplatypus Posted October 31, 2016 Posted October 31, 2016 Is anyone else having an issue with the new Halloween version corrupting all 3 save types? I uninstalled it and I was able to save and load the save without CTD. I even tried it on a new game and it works for a wile then the saves start corrupting again. I thought it mite be too many scripted mods so I uninstalled some other heavily scripted mods and still no luck. I didn't have any issues until the Halloween version came out. I can definitively say that this is the first time some one has brought this to our attention. There's a few pieces of info we are going to need to be able to get to the bottom of why your saves are being corrupted. 1. Have you loaded a clean save first, then loading the save you want to access? This s a common workaround for the same issue in other mods that encounter this kind of problem. 2. How far along into the new game were you before you started having CTD issues? 3. Does this happen with the 2.81 update as well? 4. I'm assuming when you say all 3 save types you mean quicksave, manual save, and auto save. Is that correct? 5. What does your load order look like? 6. Do you have any papyrus logs that you can upload from when you had a crash?
VirginMarie Posted October 31, 2016 Author Posted October 31, 2016 Is anyone else having an issue with the new Halloween version corrupting all 3 save types? I uninstalled it and I was able to save and load the save without CTD. I even tried it on a new game and it works for a wile then the saves start corrupting again. I thought it mite be too many scripted mods so I uninstalled some other heavily scripted mods and still no luck. I didn't have any issues until the Halloween version came out. I can definitively say that this is the first time some one has brought this to our attention. There's a few pieces of info we are going to need to be able to get to the bottom of why your saves are being corrupted. 1. Have you loaded a clean save first, then loading the save you want to access? This s a common workaround for the same issue in other mods that encounter this kind of problem. 2. How far along into the new game were you before you started having CTD issues? 3. Does this happen with the 2.81 update as well? 4. I'm assuming when you say all 3 save types you mean quicksave, manual save, and auto save. Is that correct? 5. What does your load order look like? 6. Do you have any papyrus logs that you can upload from when you had a crash? Answers to mercplatypus questions will help a lot. I don't think it can be this mod directly causing it... far too many using to not have any other report of it. But we want to try and help. CTD is usually setup problems, and I'd start with load order, so... before even spending time on the questions, perhaps try using Loot to get the sort order if not already done. If you've not heard of Loot, it's an easy google. Then you'd need to try it with a new game again, to be sure, if it does not immediately fix with your last good save. If that does not fix, in addition to merc's questions above, can you tell us... What version are you using? What version did you upgrade from? When exactly does it CTD? It is right when you load the save? Did it CTD or misbehave in some way prior to that? You are saying the save is corrupted, but what are the symptoms that make you believe it's corrupted? CTD on load does not prove the save is corrupted Other than uninstalling being a fix, is there anything else that points to it being this mod? ( the requested papyrus log can help - Script load cannot be the source of CTD or corrupt save, only bad script, but more likely a setup issue) Was upgrading this mod the only change made. If no, what else changed? If you can get us a payrus log, the ideal log would be where you've started the game up, immediately loaded a save, followed by a CTD... grab the log for that alone. If you need to know how to get your papyrus log it's #12 in the FAQs.
VirginMarie Posted October 31, 2016 Author Posted October 31, 2016 Yes for sure. Working as intended. Basically you've been a really really bad girl. You managed to not report in, then be out there in the wilds long enough to reach the max of 90%. You should not expect to be able to ride a horse at all I really really should have closed down my PC ......LOL OK, I can see the merits of that So how about an alternative to messing about with all the settings etc? Just make the report back period a variable, ie 10/15/20/25/30 days, locked after each rebirth? It is variable between 1-10 days set by the player. Are 10 days not enough, or were you unaware that you had up to 10 days? MCM already has as Merc said "Days to report in" (max 10), and it has "Disable requirement to report in". Anything more than 10 days is essentially saying you don't want the feature so just turn it off for a while (it takes effect upon your next rebirth). But even if you just use that, I think people will benefit from the following... Here's what will likely go in the next release: Chance of Bleeding (currently allows from 65% to 100%) ... will be replaced with... Bleeding Chance Out of Combat (range 50% to 100) Bleeding Chance In Combat (range 50% to 100) Bleeding Chance when Mounted (range 0% to 100)
LordKeller Posted October 31, 2016 Posted October 31, 2016 I have Maria Eden installed, creating the gag issue.... with the pumpkin gag. Is there a new solution for this particular gag?
VirginMarie Posted October 31, 2016 Author Posted October 31, 2016 I have Maria Eden installed, creating the gag issue.... with the pumpkin gag. Is there a new solution for this particular gag? Once Tales & Tallows is complete, you can remove the gag. Until then... Option 1: disable Maria... ridiculous that Maria kills the intended devious device gag talk Option 2: cheat... use console to get Tallows device key Help "Virgin Tallows Devices Key" To see it's ID Player.Additem <ID>
DonQuiWho Posted October 31, 2016 Posted October 31, 2016 Yes for sure. Working as intended. Basically you've been a really really bad girl. You managed to not report in, then be out there in the wilds long enough to reach the max of 90%. You should not expect to be able to ride a horse at all I really really should have closed down my PC ......LOL OK, I can see the merits of that So how about an alternative to messing about with all the settings etc? Just make the report back period a variable, ie 10/15/20/25/30 days, locked after each rebirth? It is variable between 1-10 days set by the player. Are 10 days not enough, or were you unaware that you had up to 10 days? MCM already has as Merc said "Days to report in" (max 10), and it has "Disable requirement to report in". Anything more than 10 days is essentially saying you don't want the feature so just turn it off for a while (it takes effect upon your next rebirth). But even if you just use that, I think people will benefit from the following... Here's what will likely go in the next release: Chance of Bleeding (currently allows from 65% to 100%) ... will be replaced with... Bleeding Chance Out of Combat (range 50% to 100) Bleeding Chance In Combat (range 50% to 100) Bleeding Chance when Mounted (range 0% to 100) @ Her VirtualMaidenhood Thanks for getting back. Couple of things 1 - Minor point. Did you mean these two things to be the same? I would have hoped that the combat one would be less punitive Chance of Bleeding (currently allows from 65% to 100%) ... will be replaced with... Bleeding Chance Out of Combat (range 50% to 100) Bleeding Chance In Combat (range 50% to 100) Bleeding Chance when Mounted (range 0% to 100) 2 - I'm well aware that 10 days is available. My slider is hard right now. I scribbled something further upstream as to why only 10 days can be a problem when trying to play this mod alongside the base game. It takes too high a proportion of the 10 days, and reduces what can be done on other quests. And you can be imprisoned by Inte, enslaved by skyrimll, miles away from a suitable place from which to get back to Nocturnal, miss your alloeted timeslot and land up on your hands and knees trying to crawl back as her spiky necklaces try their utmost to drain your blood before you get there...well, you know what I mean! Personally, with a variable max, I'd have gone for 25/30 days that gives 20/25 days doing other things with 5 days grace to still get back in time, and therefore have a reasonable chance of meeting the deadline, in spite of every other combat/enslaving mod etc trying to stop me. 3 - Totally switching off the requirement to report back is something I'd rather avoid. First, it feels like cheating, just like fast travel and so on do. You've made the mod to be a challenge. I don't want to avoid that, but find that I might have no option if it has the potential to otherwise bring the game to a grinding halt at a point where so many things have been thrown in that they just become so overwhelming that the PC is just stuck Second, I'm actually totally sure exactly what switching off the 'report back' does, anyway. The MCM says that doing so will 'prevent progress'. Does that mean that all the mod's other side quests and so on just stop? Or can you carry on with them? It would be good to know for sure. Also, the intro text implies that punishments will still be meted out for loss of sanctity anyway. Or is th getting back to sort that actually additional to 'normal' reporting? I haven't totally sussed that out yet from the gameplay I've managed, and the chances of staying pure for 10 days anyway is next to nil. (On the upside, as there's no chance of finding 77 virgins in the whole of Skyrim, it possibly avoids other unpleasantnesses). So if that were so, what's the point of switching off reporting back? I'm not sure I know, and as It's not entirely clear, it would be useful to know I don't want to stop playing the mod at all. It's very good and has some great stuff. It just has a few strange side effects Able to help me with those queries, pls?
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