Jump to content

Have all the required ments, but SL not working


Recommended Posts

Posted

I have the latest SKSE, FNIS 5.1.1 and the FNIS creatures 5.1, and SkyUI 4.1. When I load into a saved game in Skyrim, I get a message stating that by FNIS is out of date and that SL will not work. I have tried reinstalling FNIS and SL, and the error still pops up. The menu will load and let me configure the settings as if it works, but when I tried to download a mod to see if if it did, the mod didn't work properly. Attached as a picture is what I believe to be the relevant debug data, per the pinned post. I have to attach it as a picture because the forum system thought some of the text in the debug code was a link, and I'm not allowed to post those, so I apologize for the confusion.

post-533943-0-09655200-1408079590_thumb.jpg

post-533943-0-21903400-1408079927_thumb.png

Posted

did you run generatefnisforusers.exe

you have to run that to generate the behavior files for it to work. you also have to check the correct patches for it.
ec87108914f4eb7c03d7c6bb759147123510e7ef

Posted

You haven't installed FNIS right and are thus missing the FNIS.psc and/or FNIS.pex scripts. Nothing else to it.

 

Reinstall the latest fnis, and READ the fnis output when you run the tool and fix an errors it's yelling at you about.  

Posted

You haven't installed FNIS right and are thus missing the FNIS.psc and/or FNIS.pex scripts. Nothing else to it.

 

Reinstall the latest fnis, and READ the fnis output when you run the tool and fix an errors it's yelling at you about.  

 

I think he has FNIS installed, but not run. It's missing FNISVersionGenerated.pex, the one which is created when the generation was successful.

Posted

 

You haven't installed FNIS right and are thus missing the FNIS.psc and/or FNIS.pex scripts. Nothing else to it.

 

Reinstall the latest fnis, and READ the fnis output when you run the tool and fix an errors it's yelling at you about.  

 

I think he has FNIS installed, but not run. It's missing FNISVersionGenerated.pex, the one which is created when the generation was successful.

 

 

The last few people I've seen having this problem yelling about how they've installed and run the latest FNIS, we're having it because they were running the tool, but blatantly ignoring the errors about them having the PCEA patch ticked but not installed, which seems to make it skip the scripts copying over. It'd be nice if FNIS highlighted this error more so people stopped ignoring it, or FNIS instead of hard failing at this point, soft failed and just skipped over the PCEA stuff if not installed.

Posted

 

 

You haven't installed FNIS right and are thus missing the FNIS.psc and/or FNIS.pex scripts. Nothing else to it.

 

Reinstall the latest fnis, and READ the fnis output when you run the tool and fix an errors it's yelling at you about.  

 

I think he has FNIS installed, but not run. It's missing FNISVersionGenerated.pex, the one which is created when the generation was successful.

 

 

The last few people I've seen having this problem yelling about how they've installed and run the latest FNIS, we're having it because they were running the tool, but blatantly ignoring the errors about them having the PCEA patch ticked but not installed, which seems to make it skip the scripts copying over. It'd be nice if FNIS highlighted this error more so people stopped ignoring it, or FNIS instead of hard failing at this point, soft failed and just skipped over the PCEA stuff if not installed.

 

 

Only problem being with MO NMM and BAIN, unless FNIS can FIND PCEA/SL/insert animation thingy here, it's not guaranteed to be a binary fix.

 

FNIS doesn't play well with segregated, off data and/or virtual directory setups at all, and Fore doesn't seem particularly enthusiastic about fixing it.

 

I ended up having to write batch file to temporarily "install" (and then delete) already installed shit in MO directly in the base data folder for FNIS to finally f*(&(*@W$ recognize it and account for it during runtime, and installing FNIS through the MO executable tool literally did nothing. The issue is just as much fore's as it is users' ignorance.

 

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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