Jump to content

Recommended Posts

Posted

AAF v1.5.0 gets stuck at 11%. No log is created so I don't know what the error is. The only thing I've changed is AAF. When I go back to AAF v1.1.5, everything works fine.

 

Edited for additional info:

 

Current Mod list: f4se, mcm,  AAF

 

 Papyrus log snippet:

 scanning plugin directory E:\Steam\steamapps\common\Fallout 4\Data\F4SE\Plugins\
checking plugin AAF_1_11_191.DLL
plugin AAF_1_11_191.DLL (00000000  00000000) no version data 0 (handle 0)
checking plugin LL_FourPlay_1_11_191.DLL
preinit complete
using custom control map: E:\Steam\steamapps\common\Fallout 4\Data\F4SE\CustomControlMap.txt
loading plugin "LL_fourPlay"
registering plugin listener for F4SE at 1 of 3
plugin LL_FourPlay_1_11_191.DLL (00000001 LL_fourPlay 0000003B) loaded correctly (handle 1)

 

Papyrus log does not say that AAF_1_11_191.DLL has loaded correctly.

Posted
10 minutes ago, Holylokki said:

All psychics are on vacation.

Reinstall AAF in debug mode and check for errors.

I did that. Nothing is printed to the screen.

Posted

I get that aswell even with only the themes no and n other mods that use the framework installed, so something is blocking it. Weird thing is 1.1.5 runs it just fine.

Posted
39 minutes ago, Aelendil said:

I get that aswell even with only the themes no and n other mods that use the framework installed, so something is blocking it. Weird thing is 1.1.5 runs it just fine.

All I have installed is f4se, MCM and AAF and it still gets stuck at 11%. Like you, v1.1.5 works fine.

Posted

There is a lot that is new in 1.5.0. So, will have to get more info. I added additional logging in a future version and will look further into this. More info you can give the better.

Posted (edited)
Quote

 

As for their root cause — the DLL showing "no version data" suggests either:
  - They're missing xmlutility.dll in Data/
  - The DLL is corrupted or from a mismatched build
  - A permissions/antivirus issue preventing the DLL from loading properly

  This is a user installation issue, not an AAF bug

 

 

Edited by dagobaking
Posted
On 2/16/2026 at 1:22 PM, krlll said:

AAF v1.5.0 gets stuck at 11%. No log is created so I don't know what the error is. The only thing I've changed is AAF. When I go back to AAF v1.1.5, everything works fine.

 

Edited for additional info:

 

Current Mod list: f4se, mcm,  AAF

 

 Papyrus log snippet:

 scanning plugin directory E:\Steam\steamapps\common\Fallout 4\Data\F4SE\Plugins\
checking plugin AAF_1_11_191.DLL
plugin AAF_1_11_191.DLL (00000000  00000000) no version data 0 (handle 0)
checking plugin LL_FourPlay_1_11_191.DLL
preinit complete
using custom control map: E:\Steam\steamapps\common\Fallout 4\Data\F4SE\CustomControlMap.txt
loading plugin "LL_fourPlay"
registering plugin listener for F4SE at 1 of 3
plugin LL_FourPlay_1_11_191.DLL (00000001 LL_fourPlay 0000003B) loaded correctly (handle 1)

 

Papyrus log does not say that AAF_1_11_191.DLL has loaded correctly.

 

It turns out that F4SE changed the way that versions are declared. So, I had to adjust for that with the 191 version.

 

A new test release was just posted that should fix this 11% issue.

Posted
1 hour ago, dagobaking said:

 

It turns out that F4SE changed the way that versions are declared. So, I had to adjust for that with the 191 version.

 

A new test release was just posted that should fix this 11% issue.

It works, thank you. Good job!

Posted

thank you

 

fyi - there are some XML files in packs out there that were saved with a BOM header (usually windows text editors add this). those are not loading correctly. a quick fix is to just re-save those files with encoding without BOM (ie. UTF-8 instead of UTF-8-BOM).

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...