framework Advanced Animation Framework

[nitemares]

next batch in (in no particular order, because its 1:30am, I'm drinking and smoking and lost my place.. yes i know i listed some up top..but well... yea...)

 

Atomic lust 2.6.1 

Savage cabbages animation pack v1.172

fo4 leito voicefix 1.1

Fo4 animations by leito v2.0a

 

Things are going good so far...

 

[nitemares]

next group...

 

aaf patch for leito and crazy v3.2

XML unlocked human anims september 

Crazy animations 3-11-17

Mutated Lust

 

All are a go... 

 

However, I am noticing a large increase in load times... first batch finished in like 4 seconds... this batch took 30 seconds.. (but that is the total list of the last 3 posts... so its to be expected.. makes me wonder if its an overload issue?) 

 

Will continue to reinstall the XMLS until an error is found or they are all installed. 

[dagobaking]

hm. if each mod put their XML files into the new "master XML" format it would speed up load times.

[NoJoker]

I suspect it's either One Patch or Animation Addon and Fixes, gonna test later when I got home

[nitemares]

next group

 

AJ various XMLs 2.2 <aaf>

AAF Bondage animations 1.00

(not sure if the following contain XMlLS...)

Release BondDevAnim V1.00

release BadEnd v1.05

release 50shades v1.05

 

And, no issues... Moving on

[nitemares]

next batch...

 

(sorry for all the spam.. but using this to keep track of what I have re-installed as I enable them in hopes of finding the file, and knowing what grp its in exactly to zero in on it... If a mod wants to clean up the spam above, I am not against it) 

 

AAF compatibility patches v3.0

Animationsaddons and fixes 4.7

aaf modder resource v1.0

AAF the one patch to rule them all 1.1.1

 

And... 

 

no issue. that is pretty much all the XMLs mods that I directly know... so I have no idea. Going to slowly install the more AAF intensive mods to see if they have any XML files in them that might be the issue....

 

 

 

[NoJoker]

Hold on, did you test these on existing save or a new save? Is there a possibility that it may have something to do with the backup doppelganger change? So far people having trouble including me are using 113 on an existing save.

 

Gonna test with a new save now, hold up.

 

EDIT: Nevermind, new save still doesn't work, it has to be something with AAF addons, gonna test more.

[mashup47]

1 hour ago, nitemares said:

first batch of XMLs enabled with no issues:

Farelle anim mod 0.1.2

aaf kinky animation themes v190116.0

bp70FO4 sexanimations 2.2 

AAF basic animations themes v190116.0

AAF Vanilla Sex Animation themes v190116.0

 

And AAF still loading fine.

 

Moving on...

You really only Need One Theme's mod installed?  As the kinky Animations theme's contains the same XML's as the Vanilla themes, And the Basic Theme pack is used for Pose mods. Also noticed your using "The one patch to rule them all" I thought we were using "The One Patch To Bang Them All" ????

[arbiter7x]

 

1 hour ago, nitemares said:

first batch of XMLs enabled with no issues:

Farelle anim mod 0.1.2

aaf kinky animation themes v190116.0

bp70FO4 sexanimations 2.2 

AAF basic animations themes v190116.0

AAF Vanilla Sex Animation themes v190116.0

 

And AAF still loading fine.

 

Moving on...

 

Im having the same problem here with AAF loading 60% and getting stuck at "positioning", except in my case it's the combined theme mod (kinky/vanilla/creatures) that's causing it. Installing it in the mod manager with any animation pack will get it stuck at positioning, with or without the One Patch installed. I have no other AAF add-on installed. I'll try to do a manual install of its components and see which specific xml in there is causing this.

 

Edit: I tried installing the Basic and the standalone Vanilla theme from Nexus and AAF does load. 

 

In your case, may I ask how were the themes installed? 

[arbiter7x]

20 minutes ago, arbiter7x said:

 

 

Im having the same problem here with AAF loading 60% and getting stuck at "positioning", except in my case it's the combined theme mod (kinky/vanilla/creatures) that's causing it. Installing it in the mod manager with any animation pack will get it stuck at positioning, with or without the One Patch installed. I have no other AAF add-on installed. I'll try to do a manual install of its components and see which specific xml in there is causing this.

 

Edit: I tried installing the Basic and the standalone Vanilla theme from Nexus and AAF does load. 

 

In your case, may I ask how were the themes installed? 

Ok I figured it out, at least for my case. I disabled the patch for Devious Devices (that prevents them from being unequipped by AAF) in the AAF Themes installer and now everything works. Not sure if it works for you guys

[nitemares]

So.. yea,

 

All mods reinstalled... and AAF is loading on a new game... and my old save is (seemingly) running again and AAF loaded there too...

 

the ONLY mod I did not re-enable was a couple of face presets I don't use.. and Animated Fannies (didn't even realize I still had that after a body upgrade!) 

 

So maybe that was it??

 

The only thing I noticed after I took a quick second to go through the animations was that many of the leito pack would not function for me. and I am pretty sure they worked before. So maybe I deleted instead of disabled a mod patch or something?

 

long story short, disabling all the animation packs and then re-enabling them after AAF loads seems to do the trick if it doesn't work right off the bat..

 

 

 

 

[NoJoker]

CONFIRMED IT'S ROGG'S DD MANAGER OR NO STRIP MANAGER

[nitemares]

49 minutes ago, mashup47 said:

You really only Need One Theme's mod installed?  As the kinky Animations theme's contains the same XML's as the Vanilla themes, And the Basic Theme pack is used for Pose mods. Also noticed your using "The one patch to rule them all" I thought we were using "The One Patch To Bang Them All" ????

I am no modding expert  , I just grab various animation packs that catch my interest, and since i have been modding FO$ since, well, the day I got it... stuff gets left behind... (ESP if its not causing an issue) 

 

AS for The OPTRTM VS OPTBTM, from my understanding (and I am probably wrong) the difference between the two are basically gay animations. Not something that I am after, so I grabbed the other one to help free up tags for animations somewhat. 

[nitemares]

7 minutes ago, NoJoker said:

CONFIRMED IT'S ROGG'S DD MANAGER OR NO STRIP MANAGER

you sure? 

I have that mod, I never changed it (meaning its been active this whole time) and my AAF install wouldn't load until mucked around with the XML files in uninstalling them...

 

In any case, if that's all it going to take... cudos!

 

[NoJoker]

HOLD UP a second, need some more testing!

[nitemares]

1 hour ago, NoJoker said:

Hold on, did you test these on existing save or a new save? Is there a possibility that it may have something to do with the backup doppelganger change? So far people having trouble including me are using 113 on an existing save.

 

Gonna test with a new save now, hold up.

 

EDIT: Nevermind, new save still doesn't work, it has to be something with AAF addons, gonna test more.

Technically.. 

It was a "new" (made for this batch of testing) save that I was using. Mainly because my "game" save was corrupted from the mod disables (wouldn't load) 

 

However, after I re-enabled the XMLs and the Mods, my "Game" save is again working, and AAF 113beta loads in.. 

   (However, we will see how long that lasts... Bethseda games.. mods... stability!??! HAHAHAHAH!!!   ) 

[NoJoker]

@dagobaking After some testing, I finally found out why.

 

Any mod, any, if it includes XXXXXX_protectedEquipmentData.xml will stall AAF 113 at 60%.

 

Real Handcuffs + Themes (DD protection) + Rogg No Strip Manager

 

These 3 mods I have all have protectedEquipmentData.xml, delete those protectedEquipmentData.xml, AAF works again

 

EDIT:  Yep, CONFIRMED 100%, I enabled all AAF mods, but removed ALL protectedEquipmentData.xml, AAF 113 works again.

 

 

[EgoBallistic]

I had the same issue.  Based on the above comments, and knowing that equipment handling has changed, I moved all of my EquipmentSetData XML out of my AAF folder.  Sure enough that got it to load.  I will now move them back in one at a time and see if I can narrow it down.

 

This is why people reported that the DD compatibility from Themes, and Rogg's No-Strip Manager, were causing the problem.  They both include EquipmentData XML.

[NoJoker]

1 minute ago, EgoBallistic said:

I had the same issue.  Based on the above comments, and knowing that equipment handling has changed, I moved all of my EquipmentSetData XML out of my AAF folder.  Sure enough that got it to load.  I will now move them back in one at a time and see if I can narrow it down.

 

This is why people reported that the DD compatibility from Themes, and Rogg's No-Strip Manager, were causing the problem.  They both include EquipmentData XML.

I think equipmentSetData XML is fine, they are still in my folder, however, protectedEquipmentData is definitely the issue, I only removed protectedEquipmentData.XML, and it works again. Other XMLs are left untouched.

[EgoBallistic]

21 minutes ago, NoJoker said:

EDIT:  Yep, CONFIRMED 100%, I enabled all AAF mods, but removed ALL protectedEquipmentData.xml, AAF 113 works again.

Yep, confirmed here also.  I have protectedEquipmentData.xml from Raider Pet, Real Handcuffs, Rogg No Strip, and Themes, and if any of those protectedEquipmentData files are loaded 113 locks up at 60%.  If I remove all of them AAF loads and works.  The mod themselves are fine, it's just the protectedEquipmentData causing the issue.

 

4 minutes ago, NoJoker said:

I think equipmentSetData XML is fine, they are still in my folder, however, protectedEquipmentData is definitely the issue, I only removed protectedEquipmentData.XML, and it works again. Other XMLs are left untouched.

Agreed.  All of my other equipmentSet files work fine.  Sorry, I didn't see your earlier post when I posted that, and I guess I was a few minutes behind you

[Guest]

19 minutes ago, NoJoker said:

@dagobaking  Après quelques tests, j'ai finalement trouvé pourquoi.

 

Tout mod, tout, s'il comprend XXXXXX_protectedEquipmentData.xml, bloquera AAF 113 à 60%.

 

Real Menottes + Thèmes (protection DD) + Rogg No Strip Manager

 

Ces 3 mods que j'ai tous ont protectedEquipmentData.xml, supprimez ces protectedEquipmentData.xml, AAF fonctionne à nouveau

 

EDIT:  Oui, CONFIRMÉ à 100%, j'ai activé tous les mods AAF, mais supprimé TOUS protectedEquipmentData.xml, AAF 113 fonctionne à nouveau.

 

 

I confirm that by removing 2 xml files:

AAF_protectedEquipmentData.xml and RealHandcuffs_protectedEquipmentData.xml

now aaf works fine !

 

thank you to everyone who had the patience to test

[nitemares]

I too can confirm that I do not have any * ProtectedEquipmentData.xml"s in my AAF folder... 

 

(Not sure why, As I have realhandcuffs and Rog's DD manager installed, and never disabled Rog's DD manager... but I do not have any ProtectedEquipmentXMLs)

[nitemares]

On a separate note:

 

How do I disable Debugging mode now?

I thought it was just a simple ESP file to enable and disable (which I have done) to turn Debug mode on and off... 

but I am still in debug mode after disabling the AAF_Debug_On.ESP 

 

Please remind me to not roll my face over my keyboard when I am tired and try the obvious first

[mashup47]

13 minutes ago, nitemares said:

On a separate note:

 

How do I disable Debugging mode now?

I thought it was just a simple ESP file to enable and disable (which I have done) to turn Debug mode on and off... 

but I am still in debug mode after disabling the AAF_Debug_On.ESP 

////Fallout/Data/AAF/ AAF Settings.ini open "AAF settings.ini" with note pad and Change Debug Value to False 

[nitemares]

3 minutes ago, mashup47 said:

////Fallout/Data/AAF/ AAF Settings.ini open "AAF settings.ini" with note pad and Change Debug Value to False 

Wassn't the issue  

(I did check that first  )

 

I actually installed AAF in debug mode for testing... and forgot I did that... a simple reinstall to normal mode was all that was needed