BurntLettuce Posted January 17, 2021 Posted January 17, 2021 Whenever I run FNIS to try and load some new animations I installed I get this error Unhandled USVFS proxy exception (line 110) access denied I have tried reinstalling FNIS and SKSE and I'm still getting the error.Looked up the error but I didn't get much in terms of info on what to do. Sorry if the answer is obvious or something I'm just really dumb.
HadToRegister Posted January 17, 2021 Posted January 17, 2021 Whenever I run FNIS to try and load some new animations I installed I get this error Unhandled USVFS proxy exception (line 110) access denied I have tried reinstalling FNIS and SKSE and I'm still getting the error.Looked up the error but I didn't get much in terms of info on what to do. Sorry if the answer is obvious or something I'm just really dumb. You must be using MO or MO2, judging by the mention of USVFS (virtual File System) you haven't placed FNIS in the correct folder or something like that, I don't use MO2 or MO, but AFAIK there are special requirements on where to place FNIS in order to use it with MO or MO2. You'll need to search for FNIS with MO or FNIS with MO2 in order to find an answer
BurntLettuce Posted January 17, 2021 Author Posted January 17, 2021 Whenever I run FNIS to try and load some new animations I installed I get this error Unhandled USVFS proxy exception (line 110) access denied I have tried reinstalling FNIS and SKSE and I'm still getting the error.Looked up the error but I didn't get much in terms of info on what to do. Sorry if the answer is obvious or something I'm just really dumb. You must be using MO or MO2, judging by the mention of USVFS (virtual File System) you haven't placed FNIS in the correct folder or something like that, I don't use MO2 or MO, but AFAIK there are special requirements on where to place FNIS in order to use it with MO or MO2. You'll need to search for FNIS with MO or FNIS with MO2 in order to find an answer as stated above I have already reinstalled FNIS, and I made sure that it was installed correctly.
HadToRegister Posted January 17, 2021 Posted January 17, 2021 Whenever I run FNIS to try and load some new animations I installed I get this error Unhandled USVFS proxy exception (line 110) access denied I have tried reinstalling FNIS and SKSE and I'm still getting the error.Looked up the error but I didn't get much in terms of info on what to do. Sorry if the answer is obvious or something I'm just really dumb. You must be using MO or MO2, judging by the mention of USVFS (virtual File System) you haven't placed FNIS in the correct folder or something like that, I don't use MO2 or MO, but AFAIK there are special requirements on where to place FNIS in order to use it with MO or MO2. You'll need to search for FNIS with MO or FNIS with MO2 in order to find an answer as stated above I have already reinstalled FNIS, and I made sure that it was installed correctly. Are you using MO or MO2, because from what I understand there are special steps to take when installing and using FNIS with MO, MO2
BurntLettuce Posted January 17, 2021 Author Posted January 17, 2021 Whenever I run FNIS to try and load some new animations I installed I get this error Unhandled USVFS proxy exception (line 110) access denied I have tried reinstalling FNIS and SKSE and I'm still getting the error.Looked up the error but I didn't get much in terms of info on what to do. Sorry if the answer is obvious or something I'm just really dumb. You must be using MO or MO2, judging by the mention of USVFS (virtual File System) you haven't placed FNIS in the correct folder or something like that, I don't use MO2 or MO, but AFAIK there are special requirements on where to place FNIS in order to use it with MO or MO2. You'll need to search for FNIS with MO or FNIS with MO2 in order to find an answer as stated above I have already reinstalled FNIS, and I made sure that it was installed correctly. Are you using MO or MO2, because from what I understand there are special steps to take when installing and using FNIS with MO, MO2MO2, I watched a tutorial on how to install FNIS for MO2 and followed it exactly, and the problem still persists.
BurntLettuce Posted January 17, 2021 Author Posted January 17, 2021 (edited) Unhandled USVFS proxy exception (line 111): Access is denied. new error, I think I might just do a clean install. Edit: it seems like Mod Organizer 2 is the problem. Edited January 17, 2021 by BurntLettuce
BurntLettuce Posted January 17, 2021 Author Posted January 17, 2021 Okay so I fixed it all I had to do was run MO2 as admin
Greed0083 Posted January 25, 2021 Posted January 25, 2021 (edited) I'm at a loss I've spent all day getting FNIS to work vie reinstalled it at least 5 times, I've made sure that all the mods I use are SE compatible, and even play around with the load order and which mods were active at the time of the FNIS update but I get the same warnings every time I use FNIS. and when I log onto Skyrim everyone is doing the infamous T pose. >>Warning: Generator not run from a legal (Steam) Skyrim installation directory. If you use SKSE, this can be fixed by starting Skyrim once through Steam.<<FNIS Behavior V7.6 1/24/2021 10:36:05 PMGenerator: Y:\Steam\steamapps\common\Skyrim Special Edition\Data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exeSkyrim SE 64bit: ??.??.?? - Skeleton(hkx) female: XPMS2HDT (126 bones) male: XPMS2HDT (126 bones)Patch: "GENDER Specific Animations" Patch: "SKELETON Arm Fix" Reading 0kal V?.? ... >>Warning: \character\behaviors\FNIS_DD_Behavior.hkx not Skyrim SE compatible<<Reading DD V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD2_Behavior.hkx not Skyrim SE compatible<<Reading DD2 V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD3_Behavior.hkx not Skyrim SE compatible<<Reading DD3 V4.1.0 ... >>Warning: \character\behaviors\FNIS_DDSL_Behavior.hkx not Skyrim SE compatible<<Reading DDSL V4.0.0 ... Reading FNISBase V7.6 ... Reading FNISCreatureVersion V7.0 ... Reading FNISSpells V5.0.1 ... Reading RydinAnimationPack V0.5 ... Reading SexLab V1.63 ... Reading SexLabAP V1.63 ... Reading SexLabAroused V2.9 ... Reading SexLabCreature V1.63 ... Reading XPMSE V7.2 ... Reading ZaZAnimationPack V7.00 ... All Anim Lists scanned. Generating Behavior Files....No GENDER directory maleNo GENDER directory femaleAlternate Animation mods: 5 sets: 47 total groups: 182 added file slots: 1410 alternate files: 1141 Create Creature Behaviors ...Reading SexLabCreature V1.63 ...Reading RydinAnimationPack V1.0 ... 3903 animations for 15 mods successfully included (character). 334 animations for 2 mods and 18 creatures successfully included.. 5 Warning(s). there is the results of my FNIS update every time. and yes before anyone asks I am using FNIS SE, or at least that's what FNIS says and the nexus page I downloaded it off of... Edited January 25, 2021 by Greed0083
HadToRegister Posted January 25, 2021 Posted January 25, 2021 I'm at a loss I've spent all day getting FNIS to work vie reinstalled it at least 5 times, I've made sure that all the mods I use are SE compatible, and even play around with the load order and which mods were active at the time of the FNIS update but I get the same warnings every time I use FNIS. and when I log onto Skyrim everyone is doing the infamous T pose. >>Warning: Generator not run from a legal (Steam) Skyrim installation directory. If you use SKSE, this can be fixed by starting Skyrim once through Steam.<<FNIS Behavior V7.6 1/24/2021 10:36:05 PMGenerator: Y:\Steam\steamapps\common\Skyrim Special Edition\Data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exeSkyrim SE 64bit: ??.??.?? - Skeleton(hkx) female: XPMS2HDT (126 bones) male: XPMS2HDT (126 bones)Patch: "GENDER Specific Animations" Patch: "SKELETON Arm Fix" Reading 0kal V?.? ... >>Warning: \character\behaviors\FNIS_DD_Behavior.hkx not Skyrim SE compatible<<Reading DD V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD2_Behavior.hkx not Skyrim SE compatible<<Reading DD2 V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD3_Behavior.hkx not Skyrim SE compatible<<Reading DD3 V4.1.0 ... >>Warning: \character\behaviors\FNIS_DDSL_Behavior.hkx not Skyrim SE compatible<<Reading DDSL V4.0.0 ... Reading FNISBase V7.6 ... Reading FNISCreatureVersion V7.0 ... Reading FNISSpells V5.0.1 ... Reading RydinAnimationPack V0.5 ... Reading SexLab V1.63 ... Reading SexLabAP V1.63 ... Reading SexLabAroused V2.9 ... Reading SexLabCreature V1.63 ... Reading XPMSE V7.2 ... Reading ZaZAnimationPack V7.00 ... All Anim Lists scanned. Generating Behavior Files....No GENDER directory maleNo GENDER directory femaleAlternate Animation mods: 5 sets: 47 total groups: 182 added file slots: 1410 alternate files: 1141 Create Creature Behaviors ...Reading SexLabCreature V1.63 ...Reading RydinAnimationPack V1.0 ... 3903 animations for 15 mods successfully included (character). 334 animations for 2 mods and 18 creatures successfully included.. 5 Warning(s). there is the results of my FNIS update every time. and yes before anyone asks I am using FNIS SE, or at least that's what FNIS says and the nexus page I downloaded it off of... You only need to run FNIS ONCE.Why do you keep running it? First question about the First eror...have you Started SKyrim ONCE through Steam as the first error says?
Algabar Posted January 25, 2021 Posted January 25, 2021 In addition: Reading 0kal V?.? ... >>Warning: \character\behaviors\FNIS_DD_Behavior.hkx not Skyrim SE compatible<<Reading DD V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD2_Behavior.hkx not Skyrim SE compatible<<Reading DD2 V4.0.0 ... >>Warning: \character\behaviors\FNIS_DD3_Behavior.hkx not Skyrim SE compatible<<Reading DD3 V4.1.0 ... >>Warning: \character\behaviors\FNIS_DDSL_Behavior.hkx not Skyrim SE compatible<< These are serious errors. These messages mean, that said files are probably still in "Oldrim" format. Animation files from Skyrim LE need to be converted for SE. "Oldrim" animations can't run in SE and can cause trouble like T-Pose and even CTDs. You can either search for a SE conversion - or convert the animations yourself. If you do a port, please be aware that the usual porting procedure also applies for mods using animations. On top, you have to convert your .hkx files to the new SE format.
Recommended Posts