Jump to content

Recommended Posts

Posted (edited)
7 hours ago, NECESSARY3VIL said:

Anyone have the DoM5 voice pack? The mega link is deadzge https://mega.nz/file/sj1wACoA#WeI08zDBVqbQyNd9ZPLteGMfvN06_eWNq-itXRVprTY

 

I've already made a new voicepack since then. The links should be visible a few pages earlier, but I'll paste them here for you:

Female Generic: https://mega.nz/file/J6c22Jgb#JCXd0myAJ0Uqej0OlkKI0wDHnFZ2ZTJjqHfZYspKrmU
Female Unique: https://mega.nz/file/BmdnEZrJ#aO8lHp9DugqOF2HEBqAvrGSPgHXKBISXc7kmjjQFbGk
Male Generic: https://mega.nz/file/UjFU2YYT#3zWqgcdxO5kvinqybBP_1LUFoht3VJtc6gkmjIIoEYI
Male Unique: https://mega.nz/file/Z3NnALwZ#u8OQPD1rPmVJuC7wdrjgOQCI6js7wH62KapYJnXw5IQ


Also @TrollAutokill, you should probably update the link in the mod description, even if someone doesn't use the newest version, the new voicepack should cover most of the old voice lines (just with the folder name changed from .esp to .esm)

Edited by wower2345
Posted

I recently encountered a rather nasty bug on the newest version where a slave is stuck in a bugged "flee and cower" state. They look as if they're idle and waiting around but the MCM menu reports that they are actually running away. I can still have sex with them, open their inventory, and see their mood and stats but I cannot get them to follow me, pose for me, or masturbate and if I order them to carry weapons they keep replaying the equipping and unequipping animations over and over again.

This behavior is unique to DOM, there seems to be nothing wrong with the NPC itself. They can follow me through normal follower frameworks and PAH.

I've tried:
1. Disabling and enabling them
2. Killing and resurrecting them
3. Moving them to PAH and then back to DOM
4. Releasing them and then capturing them again.
5. Cleaning factions and cloning.

The last option seems to get stuck, and never actually successfully clone the NPC. I have also looked at the save itself with Resaver and found no visible issues.

I can of course go back to a save from back when they worked normally, I remember that it started happening right after I captured them. I didn't put on a leashing collar so they tried to run away but when I caught them and got the dialogue options for punishment they would just keep running away right after the punishment (without any notifications such as "X is trying to run away"). After a while, they stopped and I thought everything was okay but sadly that doesn't seem to be the case.

I would very much appreciate any sort of advice of perhaps some way of resetting them completely and purging them from DOM entirely.

Posted
2 hours ago, wower2345 said:

I recently encountered a rather nasty bug on the newest version where a slave is stuck in a bugged "flee and cower" state. They look as if they're idle and waiting around but the MCM menu reports that they are actually running away. I can still have sex with them, open their inventory, and see their mood and stats but I cannot get them to follow me, pose for me, or masturbate and if I order them to carry weapons they keep replaying the equipping and unequipping animations over and over again.

This behavior is unique to DOM, there seems to be nothing wrong with the NPC itself. They can follow me through normal follower frameworks and PAH.

I've tried:
1. Disabling and enabling them
2. Killing and resurrecting them
3. Moving them to PAH and then back to DOM
4. Releasing them and then capturing them again.
5. Cleaning factions and cloning.

The last option seems to get stuck, and never actually successfully clone the NPC. I have also looked at the save itself with Resaver and found no visible issues.

I can of course go back to a save from back when they worked normally, I remember that it started happening right after I captured them. I didn't put on a leashing collar so they tried to run away but when I caught them and got the dialogue options for punishment they would just keep running away right after the punishment (without any notifications such as "X is trying to run away"). After a while, they stopped and I thought everything was okay but sadly that doesn't seem to be the case.

I would very much appreciate any sort of advice of perhaps some way of resetting them completely and purging them from DOM entirely.

Did you try the reset from the MCM slave list or with the 'k' key?

 

Flee and cower is actually for freshly captured slaves and should only come once. After you notify them they have been enslaved, through dialogue, it should go away. I will make sure the wheel is not available in this state to avoid ending up in such a situation you're describing.

 

If the capture was notified and they are simply running away you should have the punishment dialogue coming up if you try to interact with them. Once again the wheel should be disabled in this case to avoid weird states.

 

I'll try to reproduce your problem, but it would help if you send me a list of their faction ranks. Also is the faulty slave unique or spawned?

 

 

Posted (edited)
13 hours ago, TrollAutokill said:

Did you try the reset from the MCM slave list or with the 'k' key?

 

Flee and cower is actually for freshly captured slaves and should only come once. After you notify them they have been enslaved, through dialogue, it should go away. I will make sure the wheel is not available in this state to avoid ending up in such a situation you're describing.

 

If the capture was notified and they are simply running away you should have the punishment dialogue coming up if you try to interact with them. Once again the wheel should be disabled in this case to avoid weird states.

 

I'll try to reproduce your problem, but it would help if you send me a list of their faction ranks. Also is the faulty slave unique or spawned?

 

 

I reset them in both ways.

I tried using both the wheel and dialogue (the dialogue was the same as for normal slaves). And yes, sorry, I wasn't aware what that state was, I thought that was the name of the state for when they are running away, the MCM reports them as in "FLEE_AND_COWER".

The slave is a unique character.

I'm very sorry, but by now I've decided to abandon that save. But before I did I made some inspections to the saves right before and after the bug first occurred (the one I checked before was a long time after that). There was a lot of stacks and frames detected by Resaver. Perhaps some script overload by DOM or another mod caused the capture to behave strangely?

If I ever run into this behavior again I'll be sure to collect more data. Apologies for not being able to be more helpful.

 

Edited by wower2345
Posted

Hi i thinks there is a little problem with animations, when i order to masturbate the slave stay in T pose like there isn't the animation, i have activated the animation log of OAR and say me the animation name but checking of the folder of DOM there isn't the animation that marks. Same thing with Kiss aniamtion on praise selection

Posted
1 hour ago, Rekop93 said:

Hi i thinks there is a little problem with animations, when i order to masturbate the slave stay in T pose like there isn't the animation, i have activated the animation log of OAR and say me the animation name but checking of the folder of DOM there isn't the animation that marks. Same thing with Kiss aniamtion on praise selection

All anim working or it's just DOM ? if it's just dome it's must be loaded after paradise hall and don't forgot Fnis and nemesis or pandora

 

and this mod

Posted

Can I add my voice to the choir to remove zaz dependancy ? It is not compatible with Sexlab P+ from what I understand and SLP+ is kinda vital nowadays due to the sheer speed of it :)

 

And unrelated but I've been using DOM in my playthroughs for a long time now and I just want to say this is an extremely nice and vital mod! Thanks a lot for your time and efforts !

Posted (edited)
21 hours ago, TrollAutokill said:

Did you try the reset from the MCM slave list or with the 'k' key?

 

Flee and cower is actually for freshly captured slaves and should only come once. After you notify them they have been enslaved, through dialogue, it should go away. I will make sure the wheel is not available in this state to avoid ending up in such a situation you're describing.

 

If the capture was notified and they are simply running away you should have the punishment dialogue coming up if you try to interact with them. Once again the wheel should be disabled in this case to avoid weird states.

 

I'll try to reproduce your problem, but it would help if you send me a list of their faction ranks. Also is the faulty slave unique or spawned?

 

 

Ok, I think I solved the issue. This actually doesn't seem to be related to DOM itself but rather to Sexlab p+. Specifically, around the time I captured that first bugged slave, I had updated p+to a newer version (2.11.5.0 -> 2.11.8.0). It would seem that something introduced between these two versions broke the interaction between Sexlab and DOM.

The trigger is a sex scene, the slave gets bugged after playing one on that older version of p+. The "flee and cower" part is seemingly just a result of the bug, not a cause. I've tested it quite a bit with a new save now.

I updated to a newer version (2.11.8.0 -> 2.13.3), re-initialized p+ in-game, and tried to capture a new slave for testing. That one seems to work correctly, without any issues.

Of course, the problem might be more complicated, with multiple more causes, that I haven't fully tested yet.

But all in all, it's probably not a DOM bug but rather something caused by p+ that broke DOM indirectly.



I'll have to look into it a bit more, it should be related to p+ but the newest version may not be the exact solution I thought it to be.

Edited by wower2345
Posted
16 minutes ago, wower2345 said:

Ok, I think I solved the issue. This actually doesn't seem to be related to DOM itself but rather to Sexlab p+. Specifically, around the time I captured that first bugged slave, I had updated p+to a newer version (2.11.5.0 -> 2.11.8.0). It would seem that something introduced between these two versions broke the interaction between Sexlab and DOM.

The trigger is a sex scene, the slave gets bugged after playing one on that older version of p+. The "flee and cower" part is seemingly just a result of the bug, not a cause. I've tested it quite a bit with a new save now.

I updated to a newer version (2.11.8.0 -> 2.13.3), re-initialized p+ in-game, and tried to capture a new slave for testing. That one seems to work correctly, without any issues.

Of course, the problem might be more complicated, with multiple more causes, that I haven't fully tested yet.

But all in all, it's probably not a DOM bug but rather something caused by p+ that broke DOM indirectly.

I never managed to get SL p+ to work with PAHE nor DOM.

Posted (edited)
56 minutes ago, TrollAutokill said:

I never managed to get SL p+ to work with PAHE nor DOM.

Well, some of the older versions of p+ had an annoying bug that caused an error message every time a DOM animation was supposed to be played but if I recall correctly this should be fixed by now.

The new version works fine for me right now.

 

Ok, nevermind I take it back, this seems a little more complicated than I thought, I'll have to look into it a bit more.

edit: As for my current findings, this seems to be something introduced between DOM 7.1.4 and 7.1.6

Edited by wower2345
Posted
3 hours ago, Mort-Vivant said:

hey, I have the problem of npc unresponsive at the end of each animation, somebody knows how to get rid of this issue ?

 

I think it's caused by my load order, I tried to organized it according to advices found here but I doubt that's right

 

What do you think ? Any advices ?

 

 

Thanks

DOM should be last in both. The rule is: most recent install and load last.

 

If your actors are unresponsive with the 'E' key not appearing, just hit them with the whip and you'll have a 0.5 second window to interract. Choose follow me and they should be responsive again.

 

 

Posted
1 minute ago, Mort-Vivant said:

thanks for the answer

I put it in order but still have the same issue every time at end of the animation (i have the E khey)

i don't know what's causing it, certainly another mod... i'll look into it further tomorrow, now i just want to play ^^

So what DOM version? What kind of animation? What do you call unresponsive?

Posted
On 12/14/2024 at 7:36 AM, FallenSully said:

Ok to expound on my previous issue that I just noticed it seems whenever I have sex with a slave (consensual or not) its registered twice in the diary, once as the original instance and again like they were raped for no reason although its not logged when checking their status through the wheel it does seem to effect moods as one got angry over it.

Yeah its not a problem with Vortex or any other mod. Just AE

Posted

Getting a new issue where sometimes after a sex scene the wheel options for for rape and sex disappear permanently (K and re initiating doesn't fix it) and rape doesn't finish the punishment (only says start then doesnt do the punishing message, doesn't clear the reason etc). Uninstalled P+ and tried a new game. Same issue. Latest DoM version.

Posted (edited)
3 hours ago, Mysticlaus said:

Getting a new issue where sometimes after a sex scene the wheel options for for rape and sex disappear permanently (K and re initiating doesn't fix it) and rape doesn't finish the punishment (only says start then doesnt do the punishing message, doesn't clear the reason etc). Uninstalled P+ and tried a new game. Same issue. Latest DoM version.

Are you using SLSO? This can only happen if Sexlab didn't end correctly. P+ and SLSO have different events to end the scene. P+ is not compatible with DOM. SLSO needs to be tested further.

 

I will add the clear Sexlab factions in the reset slave function.

Edited by TrollAutokill
Posted
14 hours ago, TrollAutokill said:

Are you using SLSO? This can only happen if Sexlab didn't end correctly. P+ and SLSO have different events to end the scene. P+ is not compatible with DOM. SLSO needs to be tested further.

 

I will add the clear Sexlab factions in the reset slave function.

Nevermind figured out the issue. I forgot P+ added it's own SLAL thing so I didn't actually have SLAL installed. Reinstalling it seems to have fixed the issue. As for the factions. Any way to do this manually or will I have to wait for an update?

Posted
48 minutes ago, Mysticlaus said:

Nevermind figured out the issue. I forgot P+ added it's own SLAL thing so I didn't actually have SLAL installed. Reinstalling it seems to have fixed the issue. As for the factions. Any way to do this manually or will I have to wait for an update?

You can check the factions with More Informative Console. Then clean the factions with the console.

Posted (edited)
1 hour ago, PerhapsNotTripleH said:

Curious if it's possible to save slaves for DOM or PAHE between playthroughs or some other kind of mechanism? It's so sad when i start a new game...

You can save them in a JSON file and read them back later. You'll need to enslave them again in the new game. Then read the JSON right after capture. For uniques it's rather straightforward but for spawned characters it might be a bit harder as you need to rename them manually first.

 

Also it's missing the diary but all of the abuse is there. Including the diary in the JSON file is on my to-do list.

Edited by TrollAutokill
Posted (edited)

Version 7.1.7 is out. Still a beta version and to be used with new games or games started with DOM 7.1+

 

New in version 7.1.7:

  • DOMAYGAS is in for DOM standalone.

  • Number of kinks extended from 6 to 8.

  • Punishing a freshly captured slave for "no reason" gives a boost instead of a malus.

  • Ordering a masturbating slave to masturbate in same position calls masturbate harder.

  • Added training status change to diary entries if there was no change of mood.

  • Corrected diary reporting sex twice and wrongly reporting some punishments.

  • Diary memories are now saved to json file and read.

  • Most wheel menus and hotkeys are deactivated on freshly captured and fleeing slaves.

  • Bludgeon was relocated on the Riverwood trader counter. A recipe is available to make one from torch, leather strips and deathbells.

  • Slavers can be recruited for free from defeated enemies. Press the 'E' key and choose 'Recruit (DOM)'. Enemies with high honesty might refuse.

  • Corrected travel to camp for slavers. Changing camp location during travel will also change the travel to goal.

  • Slavers can now use all type of punishment weapons with keyword zbfWeaponPunishment.

  • Corrected name generator for fresh slaves always leading to male gender. Corrected name generator DOM path.

  • Corrected armor/weapons being unequipped at capture.

  • Corrected dress/undress with Sexlab.

 

EDIT: FOMOD XML file was corrected.

Edited by TrollAutokill
Posted (edited)
8 hours ago, PerhapsNotTripleH said:

Curious if it's possible to save slaves for DOM or PAHE between playthroughs or some other kind of mechanism? It's so sad when i start a new game...

If you're into playtesting you can try version 7.1.7.  But it won't work with old saves while it's in beta.

Edited by TrollAutokill
Posted (edited)

I still can't make player diary work, it's so frustrating. I open it, it closes to update and never re-open.  Thought a new game would help with updates and all that, but there must be some incompatibility going on.

Edited by Durante
Posted
8 minutes ago, Durante said:

I still can't make player diary work, it's so frustrating. I open it, it closes to update and never re-open.  Thought a new game would help with updates and all that, but there must be some incompatibility going on.

So the slaves diaries are working?

Posted (edited)
1 minute ago, TrollAutokill said:

So the slaves diaries are working?

 

It's a new game I haven't captured anyone yet :sweat_smile: but the player diary found in breezehome pretty much did the same like in previous save game, it opens empty, closes, updates, and that's it, can't interact with it. 


To be fair, on previous save game I had the same issue with a diary mod that lets you write text into it, so there might be some incompatibility going on.

Edited by Durante
Posted (edited)

image.jpeg.023261085661aff8e707a2f8c4e181fe.jpeg

 

Also I got this error in MO2 for 7.1.7, there seems to be issue with the mod packaging

Edited by Durante

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...