DimDimdum Posted June 29, 2018 Posted June 29, 2018 All right, my mind has been steadily disintegrating over the past 2 days. So up to yesterday FNIS and LOOT have been working fine, then they decided to bug out. Now whenever I try to run FNIS it gives me this: ERROR(2012): Could not generate: defaultfemale.hkx defaultmale.hkx weapequip.hkx staggerbehavior.hkx sprintbehavior.hkx shout_behavior.hkx mt_behavior.hkx magicmountedbehavior.hkx magicbehavior.hkx magic_readied_direction_behavior.hkx 1hm_locomotion.hkx 1hm_behavior.hkx 0_master.hkx and LOOT does not detect mod plugins, only Skyrim.esm, Update.esm etc. Im pretty sure this is a permission problem-yesterday I disabled then re-enabled admin for FNIS and LOOT and then they worked fine, but then today they decided not to work again. I've tried disabling and enabling admin (but it didn't work this time), added both of them to my AV's exclusions, reinstalled FNIS, LOOT and MO2, moved my MO2's install from C root to desktop, running usfvs.exe, no dice.
Pinute Posted June 29, 2018 Posted June 29, 2018 7 hours ago, DimDimdum said: All right, my mind has been steadily disintegrating over the past 2 days. So up to yesterday FNIS and LOOT have been working fine, then they decided to bug out. Now whenever I try to run FNIS it gives me this: ERROR(2012): Could not generate: defaultfemale.hkx defaultmale.hkx weapequip.hkx staggerbehavior.hkx sprintbehavior.hkx shout_behavior.hkx mt_behavior.hkx magicmountedbehavior.hkx magicbehavior.hkx magic_readied_direction_behavior.hkx 1hm_locomotion.hkx 1hm_behavior.hkx 0_master.hkx and LOOT does not detect mod plugins, only Skyrim.esm, Update.esm etc. Im pretty sure this is a permission problem-yesterday I disabled then re-enabled admin for FNIS and LOOT and then they worked fine, but then today they decided not to work again. I've tried disabling and enabling admin (but it didn't work this time), added both of them to my AV's exclusions, reinstalled FNIS, LOOT and MO2, moved my MO2's install from C root to desktop, running usfvs.exe, no dice. silly question, but you are running loot from inside MO2?
rosedesavane Posted September 20, 2018 Posted September 20, 2018 I've the same issue, i solve this as bellow: 1. I reinstall loot comletely : remove it from where it's installed and remove the folder loot under app data 2. desinstall wreye bash 3. desinstall sseedit 4. remove skyrim.ini ( don't forget to make a copie) 5. Reinstall loot under c:\steam\....\common 6.reinstall Wreye bash under c:\ steam\...\common 3.reinstall sseedit under c:\steam\...\common 4. reinstall fnis behavior manually (take care to file rediriction in fnis.ini0 and rename it to fnis ini : see how to in NMM fnis ) 5. delete all executable in MO2 ( optional run ccsetup for cleaning register...run uninstaller for delete temporaly files) 6. Rebuild new executable in MO2 7. Make MO2 and generate fnis for users run as administrator. 8. run skyrim se via MO 2 with launcher (not skse loader ) and close it after have see option , ...quit Execute loot , WB, Essedit, and fnis under MO2 9. don't forget to clean your save with appropriate tools this have solve my issue (hope help you)
Yinkle Posted September 20, 2018 Posted September 20, 2018 Can you remember any significant changes you made to your system before this started happening? New programs? CCleaner regedits? Could be a miriad of things... The first thing that comes to mind is are you running MO2 as admin? If not then do!
fore Posted September 21, 2018 Posted September 21, 2018 There are 2 main reasons for this general 2012 error showing a list of hkx files: A problem with a (cheap) AV that has falsely flagged hkxcmd A problem with your access rights. For example caused by UAC, or when COPYING files from UAC protected folders. Often can be dealt with by running MO with admin rights.
rosedesavane Posted October 3, 2018 Posted October 3, 2018 you will find under this link a well made video that explains how to properly install fnis under MO2. I think it could solve the problem of error 2012. Regards
rosedesavane Posted October 9, 2018 Posted October 9, 2018 After some research I concluded that this issue comes from the application loot. When loot can't read in the MO2 folder\mods it accesses directely to the default folder where skyrim is installed . To fix it go to ? \ ... \ ....\ AppData \ Local \ LOOT (in my case ? \ Users \ admin \ AppData \ Local \ LOOT) and erase the folder loot or cut it and paste it elsewhere for reuse when needed. restart the loot as usual.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.