framework Advanced Animation Framework

[Holylokki]

6 hours ago, judge007 said:

I am on OG (1.10.163, downgraded) and all other mods work correctly.

Yes, it doesn't work on OG. The papyrus log contains many errors indicating on new functions.

[judge007]

54 minutes ago, Holylokki said:

Yes, it doesn't work on OG. The papyrus log contains many errors indicating on new functions.

It only comes with two versions of .dll's , one is for OG. The FOMOD even allows to select between latest version and OG.

How do you come to that conclusion?

 

[Holylokki]

34 minutes ago, judge007 said:

How do you come to that conclusion?

Strange question. Tested it. Found a problem. Found the cause. Rolled back to v1.5.5.

[jaam]

54 minutes ago, Holylokki said:

Strange question. Tested it. Found a problem. Found the cause. Rolled back to v1.5.5.

Did you check if the F4SE folder and DLL were deployed ? When I installed my version, the FOMOD did not deploy the DLLs, I had to extract them myself.

And there is also a syntax error in the FOMOD for the sources.

[judge007]

1 hour ago, jaam said:

Did you check if the F4SE folder and DLL were deployed ? When I installed my version, the FOMOD did not deploy the DLLs, I had to extract them myself.

And there is also a syntax error in the FOMOD for the sources.

My installation of 1.7.0 deployed the correct .dlls. In the correct folders.

No error messages and the debug log contained no clues.

Ran it without debug, same.

On the Discord, it stated it was designed for Old-Gen and the latest Bethesda bugfest.

It installed with the fomod functioning to all appearances correctly.

The Fomod's menu structure indicated it would work for Old-Gen or the latest FO4 version.

Since I don't have the latest version, I obviously selected Old-Gen setup.

 

If the AAF team state it would work for Old-Gen and it did not, I reported here with my results, expecting a response from @dagobaking or at least an AAF team member.

Instead I get a response from a respected mod author whose own work is still in Beta.

 

I really did not come here to be baffled with bullsh1t.

[dagobaking]

My apologies. 1.7.0 had some issues.

 

The FOMOD was missing a file. That has been fixed. So, NG (211) should work fine with it. But, OG (163) is missing some functions.

 

Working on a fix for the 163 issue. Will post asap.

 

12 hours ago, judge007 said:

If the AAF team state it would work for Old-Gen and it did not, I reported here with my results, expecting a response from @dagobaking or at least an AAF team member.

Instead I get a response from a respected mod author whose own work is still in Beta.

 

I really did not come here to be baffled with bullsh1t.

 

Don't disrespect mod authors just trying to pitch in with help.

[hy303]

I'm using AAF_V1-7-0-1 with Fallout 4 version 1.11.221.

Playing certain animations causes a CTD (crash to the desktop).

I haven't yet identified which animation is causing the problem.

It worked without issues with Fallout 4 version 1.11.191 and AAF version 1.5.5.

If anyone has any information, please let me know.

[judge007]

38 minutes ago, dagobaking said:

My apologies. 1.7.0 had some issues.

 

The FOMOD was missing a file. That has been fixed. So, NG (211) should work fine with it. But, OG (163) is missing some functions.

 

Working on a fix for the 163 issue. Will post asap.

 

 

Don't disrespect mod authors just trying to pitch in with help.

Thanks.

 

That wasn't help, that was weird.

[dagobaking]

5 minutes ago, judge007 said:

Thanks.

 

That wasn't help, that was weird.

 

Interestingly, I think you've judged poorly.

---
 

 

# AAF 1.7.1 (2026-06-13)
Fixes animations not playing on game version 1.10.163 (Old-Gen). Next-Gen (1.11.221) is unaffected and unchanged.

## Fixed
- On 1.10.163, scenes would start but actors stood frozen with no idle playing. The 1.7.0 Old-Gen plugin never registered the `AAF:AAF_DLLNative` Papyrus functions that position, rotate, and animate scene actors (`SetActorPosition`, `SetRefAngle`, `ActorStopInteractingQuick`, `PlayMultipleIdles`, `PlayIdle`, `StopCurrentIdle`, `PlayerUpdateEquipment`), so every call failed as an unbound native. The Old-Gen plugin now registers and implements all of them, matching the Next-Gen build. Only `aaf_1_10_163.dll` changes in this release.

[dagobaking]

8 minutes ago, hy303 said:

I'm using AAF_V1-7-0-1 with Fallout 4 version 1.11.221.

Playing certain animations causes a CTD (crash to the desktop).

I haven't yet identified which animation is causing the problem.

It worked without issues with Fallout 4 version 1.11.191 and AAF version 1.5.5.

If anyone has any information, please let me know.

 

Please let me know if you can find more specific information about this.

[jaam]

22 minutes ago, judge007 said:

Thanks.

 

That wasn't help, that was weird.

That was not weird that was my experience.

[judge007]

17 minutes ago, jaam said:

That was not weird that was my experience.

Sorry, that comment wasn't aimed at you, HolyLokki in fact.

 

I submitted a report for the AAF team with my experience with the new version, and he was trying to tell me what I already reported.

I wasn't looking for troubleshooting, and even stated I had reverted back to 1.5.5.

What he was trying to accomplish, I have no idea, but you got the brunt of it. I apologize to you, but not to Holylokki.

[reconphil]

7 hours ago, dagobaking said:

 

Interestingly, I think you've judged poorly.

---
 

 

# AAF 1.7.1 (2026-06-13)
Fixes animations not playing on game version 1.10.163 (Old-Gen). Next-Gen (1.11.221) is unaffected and unchanged.

## Fixed
- On 1.10.163, scenes would start but actors stood frozen with no idle playing. The 1.7.0 Old-Gen plugin never registered the `AAF:AAF_DLLNative` Papyrus functions that position, rotate, and animate scene actors (`SetActorPosition`, `SetRefAngle`, `ActorStopInteractingQuick`, `PlayMultipleIdles`, `PlayIdle`, `StopCurrentIdle`, `PlayerUpdateEquipment`), so every call failed as an unbound native. The Old-Gen plugin now registers and implements all of them, matching the Next-Gen build. Only `aaf_1_10_163.dll` changes in this release.

I tried to download AAF 1.7.1 (more than once) but, Windows Defender blocks it.  When I checked into it it says there is a "Trojan:Win32/MalUri.A!cl" in the file.  this is the first time I have encountered this problem with a Discord download.  I just thought I would make you aware of it.  Has anyone else had this issue?

[dagobaking]

3 hours ago, reconphil said:

I tried to download AAF 1.7.1 (more than once) but, Windows Defender blocks it.  When I checked into it it says there is a "Trojan:Win32/MalUri.A!cl" in the file.  this is the first time I have encountered this problem with a Discord download.  I just thought I would make you aware of it.  Has anyone else had this issue?

 

We did some exhaustive checks and this appears to be a false positive. But, I will also double-check.

[reconphil]

3 hours ago, dagobaking said:

 

We did some exhaustive checks and this appears to be a false positive. But, I will also double-check.

Thank you.

[hy303]

16 hours ago, dagobaking said:

 

この件に関して、より詳しい情報が見つかったら教えてください。

This issue occurs in Fallout 4 version 1.11.221, AAF_V1_7-1.
The crash occurs during the Super Mutant animation in Mutated Lust 1.4.
All other functions work correctly.
 

[dagobaking]

2 hours ago, hy303 said:

This issue occurs in Fallout 4 version 1.11.221, AAF_V1_7-1.
The crash occurs during the Super Mutant animation in Mutated Lust 1.4.
All other functions work correctly.
 

 

I believe this bug has been fixed. About to release a test version with the solution. But, someone will have to test this particular scenario.

[judge007]

@dagobaking @jaam Using AAF 1.7.1, loaded without issue, not running debug.

 

I'm on Old-Gen, and running Commonwealth Slavers so I went to downtown Boston to test out Supermutant animations.

Found some, surrendered via Violate and made sure to test out Mutated Lust animations, no crashes.

 

One question - is the source download for 1.7.0 suitable for 1.7.1?