Search the Community

Is this something that I can ignore or should I make an attempt to resolve it?

I was going through LOOT and doing some cleaning, and I came across a peculiar message involving 'FacegenForKids.esp', which is part of the Simple Children mod. I have an image below of this odd warning and wanted to ask if this is something I should go through editing in USSEP or is this something to just ignore?

Talk on the Xedit Discord: There are rendering issues with version 4.0.3 of Xedit. These where not present in v4.0.2 and have been eliminated in version 4.0.3b anyone with those versions may need to verify the integrity of their files and reclean. Unfortunately, this would also require refixing navmesh if you haven't saved an uncleaned version of the DLCs

This topic is specifically for FNIS related issues when using Mod Organizer. -- EDIT: 17th April 2016. Due to @fore's "issues" with MO he has pulled all support and directed it here. Let it be stated that the "issues" he notes are due to user error and there is no inherent issue with FNIS running in MO. Further his claim that FNIS WILL NOT run through MO on Windows 10 machines is just wrong! DO NOT follow the advice he offers regarding using FNIS and MO. -- Setting up FNIS to run through MO Install it like any other mod through MO and make sure it is active (checkmarked) in the left pane mod list. Since you must launch FNIS through Mod Organizer in order for it to recognize your mods, add FNIS to the list of executables by doing the following: Click the gears icon . In the Title field, type FNIS. For the Binary field, browse to your FNIS installation (should be located in <ModOrganizer>/mods/Fores New Idles in Skyrim - FNIS/tools/GenerateFNIS_for_Users) and select the GenerateFNISforUsers.exe application. Click the Add button. This will add FNIS to your executables list. Click OK.Now each time you want to run FNIS, simply select it from the drop-down menu at top right and click Run. Running through MO Launch FNIS through MO In the Available Patches at the bottom of the window, check the boxes for all necessary patches in your setup. Click the [update FNIS Behavior] button and wait for a message to appear in the window stating "X animations for Y mods successfully included.". Click [Exit].After closing FNIS, there will be files in Overwrite (essentially a fake mod located at the bottom of the left pane if sorted by priority ascending) created by FNIS. Right-click Overwrite and select Create Mod, name it FNIS Output and click OK. This will create a new mod listing in the left pane for the FNIS generated files. You will then need to check it to enable it. Each subsequent time you update FNIS behavior, you must open Overwrite and drag the new files back to this mod. Common Errors Error 53 or 2012 "Could not find file <path to file>\1hm_behavior.hkx Ensure the animation sets you have installed are correctly placed in priority in the left-hand pane and FNIS is using the one you want. Open the Data tab in the right-hand pane and examine the filetree to see which animation is being used in the VFS. Navigate the filetree by expanding: data>meshes>actors>character>behaviors> and see which mod is providing the file. If the file name is displayed in red, the mouse tooltip will show which other mods are also providing this file. Move the correct mod to the correct location. Additional cause for Error 2012 A user(@patchling) had Spybot - Search & Destroy+AV 2.5 installed and was constantly getting JIT and 2012 errors, specifically the 0_master.xml was not found. The file was placed in the FNIS temporary_log folder ready for processing but before that could happen it was removed by said program. Opening the start menu > settings > live protection > mode > uncheck "Scan programs before they start" apparently stops that behaviour. ***** Error dialogue GenerateFNISForUsers.exe - This application could not be started. This application could not be started. Do you want to view information about this issue? Simply close the dialogue by pressing "No" and enable FNIS in the Left-hand pane. Correct FNIS installation and use explains this in the wiki. Why does the 6.2 Add-on not look correct in MO? What you need to remember here is MO is designed to handle 'mods' and what we are installing with FNIS, and its add-ons, are 'tools'. This means MO is looking for the correct folder structure for a 'mod' as seen by the game. The archive for the 6.2 add-on has as its top folder: "tools" and this is correct for FNIS, not the game. Simply 'set the data folder' so that the "tools" folder is now at the top of the tree and ignore the next dialogue that asks if you are sure.

Many, many reports are made about various issues with the functionality of MO that can be attributed to an overly zealous AV package, or some other software that operates on a file without your consent. Whenever you see errors about missing files, or support functions not working, or "failed to spawn '[program name]': failed to start process (Access is denied. [5])" check to see that your AV package hasn't been messing with those before you ask here.Functions that seem to stall or hang entirely are usually because your AV package is stopping the system from operating on those files/folders by either interrupting the copy process or removing the copied file afterward.The running of tools used inside MO, or called from it (e.g. FNIS), have been hindered by these AV packages. Even seemingly unrelated errors about files that contain no executable code can be traced to AV behaviour.For anyone using Windows 10 (or any successive iteration after this post) you will need to go to your settings and follow these steps:Open Settings, and click/tap on the Gaming icon.Click/tap on Game bar on the left side, and turn on (default) or off Record game clips, screenshots and broadcast using Game DVR.Unselect Show Game Bar when I play full screen games that Microsoft has verified. As a matter of course, one of the first things to check when you experience problems is your AV package. That is not to say these tools are broken or useless, though many are in fact next to useless, but rather the algorithms they use to determine "malicious" behaviour isn't clever enough to distinguish between what is and isn't "bad". Most AV packages have the ability to set aside certain programmes or folders from the process so that they can operate unhindered, whichever package you use it is strongly urged that you examine how to do so with MO. Another type of software that routinely causes havoc for MO is "in game overlay" software, from whichever company that provides: AMD, nVidia, Steam, etc. Adding another layer of code into the hooking process is playing with fire as MO will lose control of the process at some point in the execution and your game will likely crash, not load or otherwise fail to function properly. File backup software is also known to make file access errors with MO as the files that are being accessed, or tried to, are being actively checked by that sort of software. This will interfere with the 'hooking' code of MO. All the code used by MO is freely available on the GitHub so there is no chance of malicious code being introduced into it. You are of course encouraged to check for yourself if you so desire. Not specifically MO related but I have also made a brief guide for removing the more annoying software in Windows 10 that often gets in the way of MO. (Though most of it can be left if you desire.)