FNIS XXL Not working

[Exzerno]

So when I installed FNIS XXL because I have too many animations when loading normal FNIS, I get this error code posted in the image. 
However, if I use normal FNIS, it all works fine if I don't go over the animation limit.

I already tried reinstalling everything and the animations that go with FNIS and still "Error(5): Not Found" 

[lisander68]

2 hours ago, Exzerno said:

So when I installed FNIS XXL because I have too many animations when loading normal FNIS, I get this error code posted in the image. 
However, if I use normal FNIS, it all works fine if I don't go over the animation limit.

I already tried reinstalling everything and the animations that go with FNIS and still "Error(5): Not Found" 

you must also tick GENDER Specific Animations

[Just Don't]

Error 5 is covered in the very description of FNIS. Try doing what it's instructed there.

[Exzerno]

On 8/17/2023 at 3:15 AM, lisander68 said:

you must also tick GENDER Specific Animations

 

On 8/17/2023 at 11:50 AM, Just Don't said:

Error 5 is covered in the very description of FNIS. Try doing what it's instructed there.

Ticked Gender Specific animations, didn't work. 

Followed Error 5 on the FNIS description, to even the point of moving all my mods and game to my SSD instead of my program files (x86) as it stated it caused issues, didn't work. 

 

[Just Don't]

Error 5 and most errors like file or file path not found or unable to be accessed are permission related. Having your programs outside of Program Files and such is the bare minimum. On top of that you could have an antivirus or similar software preventing FNIS or your mod manager from accessing the files. So make sure you set an exclusion for FNIS/your game and mods folders and try again. Running FNIS as admin isn't the recommended way IMO, but it's also a workaround suggested by the description itself.

[Exzerno]

1 hour ago, Just Don't said:

Error 5 and most errors like file or file path not found or unable to be accessed are permission related. Having your programs outside of Program Files and such is the bare minimum. On top of that you could have an antivirus or similar software preventing FNIS or your mod manager from accessing the files. So make sure you set an exclusion for FNIS/your game and mods folders and try again. Running FNIS as admin isn't the recommended way IMO, but it's also a workaround suggested by the description itself.

I have nothing that should prevent it, it works fine if I use normal FNIS, just animation count is too high so I resorted to XXL and that's where I run into the issue, I even went and disabled windows security and even added FNIS and my mods into a set exclusion, still the same error.

[lisander68]

3 hours ago, Exzerno said:

I have nothing that should prevent it, it works fine if I use normal FNIS, just animation count is too high so I resorted to XXL and that's where I run into the issue, I even went and disabled windows security and even added FNIS and my mods into a set exclusion, still the same error.

I have the same game version as you and also FNIS, but I noticed one detail. While my FNIS identifies Skyrim as AE, yours only recognises it as Skyrim SE

Spoiler

Try reinstalling it

[Exzerno]

Hmmm maybe, though it's still reading Skyrim SE 64Bit and it's located in my special edition folder because it's been installed before AE, though it's just the name of the folder. 
reinstalled Skyrim, FNIS, and SKSE, and still this error with XXL. 

[coolfreaky]

i notice in your screenshot that your path is using the yen ( symbole ) instead of slash !

are you using Asian version of fnis ? or installed it in Asian ?

 

[Exzerno]

On 8/20/2023 at 11:09 AM, coolfreaky said:

i notice in your screenshot that your path is using the yen ( symbole ) instead of slash !

are you using Asian version of fnis ? or installed it in Asian ?

 

That is because my system locale was in Japanese, but I changed it back to english .... and didn't work. 

But however, I was gonna send a screenshot and when I pressed "Update FNIS Behavior" it started working!

So that must of been the issue, because of the system locale.