krlll Posted February 16 Posted February 16 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.
Holylokki Posted February 16 Posted February 16 All psychics are on vacation. Reinstall AAF in debug mode and check for errors.
krlll Posted February 16 Author Posted February 16 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.
Aelendil Posted February 16 Posted February 16 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.
krlll Posted February 16 Author Posted February 16 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.
dagobaking Posted February 17 Posted February 17 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.
dagobaking Posted February 17 Posted February 17 (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 February 17 by dagobaking
dagobaking Posted February 22 Posted February 22 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. 1
krlll Posted February 23 Author Posted February 23 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! 1
dagobaking Posted February 23 Posted February 23 1 hour ago, krlll said: It works, thank you. Good job! Right on! Thank you for reporting back after testing. Helps on my side.
dagobaking Posted February 24 Posted February 24 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).
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now