AAF Violate

[venacavareis]

19 minutes ago, EgoBallistic said:

 

Strange.  What version of AAF are you using?

Now AAF_Violate_1.45 FOMOD.

Bug AAF_Violate_1.50 FOMOD.

 

AAF version: AAF Beta 106-31304-106b-1575369689 (For version Fallout 1.10.138 is old)

[EgoBallistic]

57 minutes ago, venacavareis said:

AAF version: AAF Beta 106-31304-106b-1575369689 (For version Fallout 1.10.138 is old)

 

Ah, that is very old.

 

The stripping function in the new version of AAF Violate uses an AAF function that appeared in Beta 121.  You may be able to prevent the crash by disabling "Strip victims before violation" in the Global Options MCM page.

[JB.]

56 minutes ago, venacavareis said:

Now AAF_Violate_1.45 FOMOD.

Bug AAF_Violate_1.50 FOMOD.

 

AAF version: AAF Beta 106-31304-106b-1575369689 (For version Fallout 1.10.138 is old)

Many of the problems of the users is due to the fact that people do not read or have an interest in looking for the solution using the forum tools (such as the search engine).

 

MAIN PAGE: 
 

Quote

Note: The AAF Violate requires the latest version of Fallout 4. If you are running an older version of Fallout 4 you can use Fallout 4 Plugin Version Check Patcher to enable it to load AAF Violate.

 

 

You should update everything and you will have no problems.

[EgoBallistic]

12 minutes ago, JBpy said:

You should update everything and you will have no problems.

 

True that.  Nonetheless, because I'm such a nice guy, I put a check in the next version of Violate so that the strip function won't crash the game if AAF is older than Beta 121.

[venacavareis]

10 minutes ago, JBpy said:

Many of the problems of the users is due to the fact that people do not read or have an interest in looking for the solution using the forum tools (such as the search engine).

 

MAIN PAGE: 
 

You should update everything and you will have no problems.

Yes I have read and re-read it several times. And i use setup guide for install.
I use the Fallout 4 Plugin Version Check Patcher. If I install the latest version 
of AAF the game closes before the fallout 4 home menu screen. So I am still in the old version of AAF. 
Well I managed to play again, this is good enough ?

[jae2222]

My character keep dying after violation. I really don't know what cause this problem. Any helps?

[JB.]

2 hours ago, jae2222 said:

My character keep dying after violation. I really don't know what cause this problem. Any helps?

That happened to me often until I remembered that in Sex Attributes now you lose a little life when you reach 100% vaginal / anal / oral abuse. That means that, during a rape, you can die. ?

 

What I did was adjust the levels on the Sex Attributes MCM (and try not to fuck too much ...).

[soup_time]

how can i get my weapons back after i have been taken captive and escaped? (with the raider pet plugin/addon)

[mishovur]

6 hours ago, EgoBallistic said:

 

True that.  Nonetheless, because I'm such a nice guy, I put a check in the next version of Violate so that the strip function won't crash the game if AAF is older than Beta 121.

I am using AAF Beta 161.1-31304-161-1b-1610914138.7z

 

The problem with newer then 1.45 Violate for me is - that the characters are 'kinda dressed' during the AAF animation. Not always, from time to time. But 1.45 works flawlessly, so also I download and check newer versions I don't use them, because the 'redressing glitch' is annoying. 

[izzyknows]

7 hours ago, soup_time said:

how can i get my weapons back after i have been taken captive and escaped? (with the raider pet plugin/addon)

Kill or pickpocket the raider that collared you.

[jae2222]

14 hours ago, JBpy said:

That happened to me often until I remembered that in Sex Attributes now you lose a little life when you reach 100% vaginal / anal / oral abuse. That means that, during a rape, you can die. ?

 

What I did was adjust the levels on the Sex Attributes MCM (and try not to fuck too much ...).

Damn, you genius! Thanks to your advice, I turned off "Fuck to death" in Sex Attributes. And problem solved. 

[EgoBallistic]

16 hours ago, mishovur said:

I am using AAF Beta 161.1-31304-161-1b-1610914138.7z

 

The problem with newer then 1.45 Violate for me is - that the characters are 'kinda dressed' during the AAF animation. Not always, from time to time. But 1.45 works flawlessly, so also I download and check newer versions I don't use them, because the 'redressing glitch' is annoying. 

 

If the new undressing code in 1.50 doesn't work well for you, you can turn it off in Global Options.  Then it lets AAF handle that.

[maddadicusrex]

13 minutes ago, EgoBallistic said:

 

If the new undressing code in 1.50 doesn't work well for you, you can turn it off in Global Options.  Then it lets AAF handle that.

I hope you are doing stuff to relieve stress! The simple non issues are only going to multiply with a generation that reads nothing, comprehends nothing, needs an app just to remember to pee, and generally believes all mods work as they demand, out of the box, and totally not their problem if it does not! IMHO! WE DO NOT WANT YOU TO LEAVE US AGAIN. 

[mishovur]

7 hours ago, maddadicusrex said:

I hope you are doing stuff to relieve stress! The simple non issues are only going to multiply with a generation that reads nothing, comprehends nothing, needs an app just to remember to pee, and generally believes all mods work as they demand, out of the box, and totally not their problem if it does not! IMHO! WE DO NOT WANT YOU TO LEAVE US AGAIN. 

 

Mate, It's not about the generation , it's about ease of use. In fact I believe I'm one of the eldest people on this forum.

And as to tinkering with the systems my main OS is Debian, sometimes I also use SuSE (old habits, started with 4.x around 98-98)

So trust me, when I tell you - I'm NOT from 'that generation'. 

 

The mod works perfectly in the 1.45. No glitches, no problems at all.

Starting with 1.46 - the character starting to get redressed during the animation (by redressing I refer to a 'phantom copies' of the clothing not the ACTUAL clothing it wears)

Meaning there is some conflict between Violate 1.46+ and 'No strip manager'. and since the later haven't been modified in years it means something changed in the code of Violate since version 1.45.

 

Please note, I'm not trying to complain, I'm trying to explain what happening.  I have tried the latest version as well, 1.50, where you have an option to make the mod or AAF itself to handle undressing/redressing, the result was the same with both setting (let Violate handle it, or AAF, it works the same). The first round of animation works properly, on a second one character get redressed in a 'phantom' copies of the gear (let's say the default skin for some item is grey, one crafts it at the proper station to make it black, the gear that will suddenly appear during animation will be grey, also was painted black)

 

This happens on the second round of animations with the Violate 1.46-1.50 regardless of the settings (in 1.5 I mean).

Everything else is static. The only mod that is being changed is Violate. 

 

So. Where exactly am I stupid?

 

[maddadicusrex]

7 minutes ago, mishovur said:

 

Mate, It's not about the generation , it's about ease of use. In fact I believe I'm one of the eldest people on this forum.

And as to tinkering with the systems my main OS is Debian, sometimes I also use SuSE (old habits, started with 4.x around 98-98)

So trust me, when I tell you - I'm NOT from 'that generation'. 

 

The mod works perfectly in the 1.45. No glitches, no problems at all.

Starting with 1.46 - the character starting to get redressed during the animation (by redressing I refer to a 'phantom copies' of the clothing not the ACTUAL clothing it wears)

Meaning there is some conflict between Violate 1.46+ and 'No strip manager'. and since the later haven't been modified in years it means something changed in the code of Violate since version 1.45.

 

Please note, I'm not trying to complain, I'm trying to explain what happening.  I have tried the latest version as well, 1.50, where you have an option to make the mod or AAF itself to handle undressing/redressing, the result was the same with both setting (let Violate handle it, or AAF, it works the same). The first round of animation works properly, on a second one character get redressed in a 'phantom' copies of the gear (let's say the default skin for some item is grey, one crafts it at the proper station to make it black, the gear that will suddenly appear during animation will be grey, also was painted black)

 

This happens on the second round of animations with the Violate 1.46-1.50 regardless of the settings (in 1.5 I mean).

Everything else is static. The only mod that is being changed is Violate. 

 

So. Where exactly am I stupid?

 

You are not. I am 67, so no spring chicken. I am lucky to have a bunch of pc geek kids on a forum I frequent that bail me out. The redressing is usually an AAF issue. I go into the AAF settings and change the duration of animation and redress to a longer period. Sometimes the problem is with the animations themselves. Often the modder or a given patch will extend the animations well beyond what AAF limits. I always set my animations at 60 sec. no matter what mod might give me that duration option. Have not had the redress issue in a while. But I use AAF 147 because the newer versions cause grief with some of my favorite animations for BP70. I sometimes wait a bit for any updates to see if the bugs work themselves out. Not really sure there is much difference between Violate 1.45 or the newer ones. Only EGO would know for sure. Sorry to lump you into the I want generation. Be well..

[mishovur]

1 hour ago, maddadicusrex said:

You are not. I am 67, so no spring chicken. I am lucky to have a bunch of pc geek kids on a forum I frequent that bail me out. The redressing is usually an AAF issue. I go into the AAF settings and change the duration of animation and redress to a longer period. Sometimes the problem is with the animations themselves. Often the modder or a given patch will extend the animations well beyond what AAF limits. I always set my animations at 60 sec. no matter what mod might give me that duration option. Have not had the redress issue in a while. But I use AAF 147 because the newer versions cause grief with some of my favorite animations for BP70. I sometimes wait a bit for any updates to see if the bugs work themselves out. Not really sure there is much difference between Violate 1.45 or the newer ones. Only EGO would know for sure. Sorry to lump you into the I want generation. Be well..

 

Oh, god, another old-timer :))

Nice to know I'm not the only one with grandkids on this forum

 

But back to the topic, it is possible that the problem is indeed in AAF settings. I will try when I'll get back to the game to set shorter animation duration, I believe it is set to 90 second.

 

[izzyknows]

3 hours ago, mishovur said:

 

Oh, god, another old-timer :))

Nice to know I'm not the only one with grandkids on this forum

 

But back to the topic, it is possible that the problem is indeed in AAF settings. I will try when I'll get back to the game to set shorter animation duration, I believe it is set to 90 second.

 

Grandkids.. teaching them pranks to play on their parents and getting the phone call later "WTF Dad!!"... priceless.

 

The redress bug is AAF. It happens with any mod calling animations. Or sometimes while switching animations.

[EgoBallistic]

3 hours ago, mishovur said:

Please note, I'm not trying to complain, I'm trying to explain what happening.  I have tried the latest version as well, 1.50, where you have an option to make the mod or AAF itself to handle undressing/redressing, the result was the same with both setting (let Violate handle it, or AAF, it works the same). The first round of animation works properly, on a second one character get redressed in a 'phantom' copies of the gear (let's say the default skin for some item is grey, one crafts it at the proper station to make it black, the gear that will suddenly appear during animation will be grey, also was painted black)

 

This happens on the second round of animations with the Violate 1.46-1.50 regardless of the settings (in 1.5 I mean).

Everything else is static. The only mod that is being changed is Violate. 

 

That is definitely an AAF issue.  In a nutshell, AAF keeps track of each actor's equipped armor to speed up unequipping/re-equipping in animations.  There is a bug in recent versions of AAF where if your equipment changes between animations, AAF will get out of synch and try to re-equip the equipment you no longer have. 

 

This bug can be triggered by playing an AAF animation that undresses and redresses you, then getting violated with robbery enabled.  The robbery takes all your clothes and armor away.  Then when the next animation ends, AAF tries to reapply the old equipment set.  But, you no longer have that equipment in your inventory, so the game gives you generic versions instead.

 

This bug is fixed in the current development build of AAF but not in the 161 public release.

 

Violate's code did not change between 1.45/1.46/1.47 in any way that affects undressing/redressing.  So I really am not sure why you would see this bug in one version more than another.  1.50 introduced the built-in stripping, which is really intended to prevent AAF from re-dressing you during or after the violation.  If you turn off the built-in stripping, the code path becomes exactly the same as it was in 1.45/1.46/1.47.

[mishovur]

1 hour ago, EgoBallistic said:

 

That is definitely an AAF issue.  In a nutshell, AAF keeps track of each actor's equipped armor to speed up unequipping/re-equipping in animations.  There is a bug in recent versions of AAF where if your equipment changes between animations, AAF will get out of synch and try to re-equip the equipment you no longer have. 

 

This bug can be triggered by playing an AAF animation that undresses and redresses you, then getting violated with robbery enabled.  The robbery takes all your clothes and armor away.  Then when the next animation ends, AAF tries to reapply the old equipment set.  But, you no longer have that equipment in your inventory, so the game gives you generic versions instead.

 

This bug is fixed in the current development build of AAF but not in the 161 public release.

 

Violate's code did not change between 1.45/1.46/1.47 in any way that affects undressing/redressing.  So I really am not sure why you would see this bug in one version more than another.  1.50 introduced the built-in stripping, which is really intended to prevent AAF from re-dressing you during or after the violation.  If you turn off the built-in stripping, the code path becomes exactly the same as it was in 1.45/1.46/1.47.

 

Don't know what to say, mate

 

I just now, for a test, without changing anything else switched to 1.46, 1.47, 1.50

In all this cases I'm getting the redressing bug after the first animation

I turned 'robbery' option off completely. 

For sure I do have the gear in the inventory. I double checked.

 

With 1.45 it works flawlessly, no issues whatsoever. I can repeat it any amount of times, no bugs at all.

 

As soon as I switch to a newer version (starting with 1.46) - voila, after the first round of animation the character is redressed into 'copies' of my gear (but not the actual gear my character was wearing)

 

It's not a fluke it's a 100% repeatable thing. 

The rest of my setup stays the same, I'm only switching between Violate versions :)))

 

Again, mate, please don't think I'm complaining, because I'm NOT.

The issue is not bothering me at all, I'm just using 1.45, and again it works flawlessly.

All I'm saying - It's the reason I'm keeping an older version.

 

And many thanks to you for creating the mod in the first place!

[VonHelton]

As the resident "bugg magnet", if there's a bugg to find, I'll find it, somehow, some way. Well, I currently have no buggs. NOT ONE. Not sure what to tell ya. Maybe corrupt files?

 

[EgoBallistic]

9 hours ago, mishovur said:

As soon as I switch to a newer version (starting with 1.46) - voila, after the first round of animation the character is redressed into 'copies' of my gear (but not the actual gear my character was wearing)

 

That's really odd.  I tried the same thing - reverted to AAF 161 and Violate 1.45, disabled robberies and restraints, and the correct equipment was always re-equipped.  I then updated to 1.47 and 1.50 and each time it worked as expected.  The only way I can get the AAF redress problem to happen is if I get robbed and cause the equipmentset to go out of synch.

 

Just to be nitpicky: did you redo your MCM settings after each time you updated the mod?  Violate comes with a default settings file, so your MCM settings get reset each time you update the mod.  And since robbery is enabled by default, that could be a way to reintroduce the problem.

[mishovur]

3 hours ago, EgoBallistic said:

 

That's really odd.  I tried the same thing - reverted to AAF 161 and Violate 1.45, disabled robberies and restraints, and the correct equipment was always re-equipped.  I then updated to 1.47 and 1.50 and each time it worked as expected.  The only way I can get the AAF redress problem to happen is if I get robbed and cause the equipmentset to go out of synch.

 

Just to be nitpicky: did you redo your MCM settings after each time you updated the mod?  Violate comes with a default settings file, so your MCM settings get reset each time you update the mod.  And since robbery is enabled by default, that could be a way to reintroduce the problem.

 

Yes, of course, later today I can make you screenshots to prove it. And again, probably something really weird going on with my installation. But I have no reason to be pulling your leg, I mean - I'm not making it up :))

[vaultbait]

On 4/26/2021 at 4:58 AM, EgoBallistic said:

This bug is fixed in the current development build of AAF but not in the 161 public release.

 

Agreed, it broke in 156 and was finally solved in 163. I haven't seen it happen again with the indicated fixed version of AAF.

 

https://bitbucket.org/dagobaking/aaf-framework/wiki/Main/CHANGELOG.md

[mishovur]

8 hours ago, vaultbait said:

 

Agreed, it broke in 156 and was finally solved in 163. I haven't seen it happen again with the indicated fixed version of AAF.

 

https://bitbucket.org/dagobaking/aaf-framework/wiki/Main/CHANGELOG.md

Ok, so rather then upgrading Violate now I'll wait till new AAF will be released, problem solved

[vaultbait]

6 hours ago, mishovur said:

Ok, so rather then upgrading Violate now I'll wait till new AAF will be released, problem solved

 

Or you could use the undressing feature of the most recent Violate version. If AAF doesn't see any clothing to strip, then it shouldn't try to put any back on you after the animations finish.