Jump to content

Warnings on FNIS & Instant CTD on loading screen

abbbby

By abbbby,
in Skyrim Technical Support

Recommended Posts

Fifoo

Fifoo

Posted
Posted

I'm more accustomed to Use MO than NMM, so I don't know about how you installed BodySlide, never had a crash when installing it. But see if reinstalling the mod resolve the issue, it might be related to memory capacity, have you installed Crash Fixes and his requirement SKSE Plugin Preloader?

 

Then try using Crash Fixes option to use regular C malloc instead of the memory blocks:

 

Spoiler

How to use the memory allocator patch?
1. Open CrashFixPlugin.ini and find "UseOSAllocators=0"
2. Change it to "UseOSAllocators=1"
3. Download and install SKSE Plugin Preloader
4. Start game, if you get an error saying that memory patch could not be applied read the message for help, otherwise you're good to go.
(5.) Causes game to crash and you use ENB? Set ExpandSystemMemoryX64=false in enblocal.ini
(6.) Causes game to crash more frequently (especially with UNP RaceMenu sliders)? Try AlignHeapAllocate=1 in CrashFixPlugin.ini

 

Tips for additional stability:
(These are things I've observed and Not 100% fact!)

If you don't have some lines listed below in your INI it means they are set to default value.

Data/SKSE/SKSE.ini (not needed if UseOSAllocators=1 in CrashFixPlugin.ini):

  • Set DefaultHeapInitialAllocMB:Memory to 768. If you are using a lot of mods or higher uGrid than 5 then set 1024. Helps with CTD during save load, especially if you can load the save after qasmoke. Max value is 1280. If you are using ENB you may get CTD on startup with higher value than 768 and ExpandSystemMemoryX64 true in enblocal.ini!
  • Set ScrapHeapSizeMB:Memory to 256. Game can't use more than 256 of this and setting higher serves no purpose.

 

abbbby

abbbby

Posted
  • Author
Posted
9 hours ago, Fifoo said:

I'm more accustomed to Use MO than NMM, so I don't know about how you installed BodySlide, never had a crash when installing it. But see if reinstalling the mod resolve the issue, it might be related to memory capacity, have you installed Crash Fixes and his requirement SKSE Plugin Preloader?

 

Then try using Crash Fixes option to use regular C malloc instead of the memory blocks:

 

  Reveal hidden contents

How to use the memory allocator patch?
1. Open CrashFixPlugin.ini and find "UseOSAllocators=0"
2. Change it to "UseOSAllocators=1"
3. Download and install SKSE Plugin Preloader
4. Start game, if you get an error saying that memory patch could not be applied read the message for help, otherwise you're good to go.
(5.) Causes game to crash and you use ENB? Set ExpandSystemMemoryX64=false in enblocal.ini
(6.) Causes game to crash more frequently (especially with UNP RaceMenu sliders)? Try AlignHeapAllocate=1 in CrashFixPlugin.ini

 

Tips for additional stability:
(These are things I've observed and Not 100% fact!)

If you don't have some lines listed below in your INI it means they are set to default value.

Data/SKSE/SKSE.ini (not needed if UseOSAllocators=1 in CrashFixPlugin.ini):

  • Set DefaultHeapInitialAllocMB:Memory to 768. If you are using a lot of mods or higher uGrid than 5 then set 1024. Helps with CTD during save load, especially if you can load the save after qasmoke. Max value is 1280. If you are using ENB you may get CTD on startup with higher value than 768 and ExpandSystemMemoryX64 true in enblocal.ini!
  • Set ScrapHeapSizeMB:Memory to 256. Game can't use more than 256 of this and setting higher serves no purpose.

 

Tried, didn't go well. I was able to start a new game so I thought my saves were corrupted but nope, they're fine.

Fifoo

Fifoo

Posted
Posted
17 hours ago, abbbby said:

Edit* I can start a new game with no problem. BUT, if I exit to main menu or load a savegame (even if i save right after the execution scene) game just go poof!

 

I barely have 70 and i don't know why this things keep happening...it hates me.

Load Order:

  Reveal hidden contents

 0  0 Skyrim.esm
 1  1 Update.esm
 2  2 Dawnguard.esm
 3  3 HearthFires.esm
 4  4 Dragonborn.esm
 5  5 Unofficial Skyrim Legendary Edition Patch.esp
 6  6 RaceCompatibility.esm
 7  7 hdtHighHeel.esm
 8  8 SexLab.esm
 9  9 Schlongs of Skyrim - Core.esm
10  a SexLabAroused.esm
11  b CreatureFramework.esm
12  c ZaZAnimationPack.esm
13  d FNIS.esp
14  e The Ningheim.esp
15  f dD - Realistic Ragdoll Force - Realistic.esp
16 10 RaceMenu.esp
17 11 RaceMenuPlugin.esp
18 12 XPMSE.esp
19 13 SkyUI.esp
20 14 SLAnimLoader.esp
21 15 SexLabDefeat.esp
22 16 Fudou Myouou.esp
23 17 ImperialEliteGreatsword.esp
24 18 Schlongs of Skyrim.esp
25 19 SOS - Smurf Average Addon.esp
26 1a SLALAnimObj.esp
27 1b UIExtensions.esp
28 1c MoreNastyCritters.esp
29 1d SexLabNudeCreatures.esp
30 1e SexLabNudeCreaturesDB.esp
31 1f SexLabNudeCreaturesDG.esp
32 20 HentaiCreatures.esp
33 21 AR_Heroines.esp
34 22 AddItemMenu2.esp
35 23 AMatterOfTime.esp
36 24 KS Hairdo's.esp
37 25 SGEyebrows.esp
38 26 TMSG0Z.esp
39 27 TMSG.esp
40 28 sr_FillHerUp.esp
41 29 Facelight.esp
42 2a Eyes of Aber.esp
43 2b CL EDagger.esp
44 2c CL ESword.esp
45 2d CL EGreatsword.esp
46 2e DCR_Blade_Set_Reloaded_v1_0.esp
47 2f DaggerCraft.esp
48 30 kimono's witcher silver swords.esp
49 31 BS-TheHag_Overlays.esp
50 32 FalmerBikini.esp
51 33 CrainteVomir.esp
52 34 DragonBoneBikini.esp
53 35 Dwarvenbikini.esp
54 36 ISD_Longclaw.esp
55 37 TW3Weaponry.esp
56 38 Wolfbikini.esp
57 39 NeoDizzySet.esp
58 3a BladeofRebirth.esp
59 3b Bishu Osafune-ju Morikage.esp
60 3c Aradia Secretary.esp
61 3d XXGongzuorenyuanHH.esp
62 3e BladesBikini.esp
63 3f dD - Enhanced Blood Main.esp
64 40 dD-Dragonborn-Dawnguard-EBT Patch.esp
 

 

 

 Brows is missing in your Load Order, it's a Ningheim Race requirement. First deactivate 37 25 SGEyebrows.esp for not being overwrited when installing that one. Install Brows and load it before 14  e The Ningheim.esp. Then reactivate or reinstall 37 25 SGEyebrows.esp make what fit best but I can't say this will work as I never played with a different race then vanilla one, you will need to be cautious here. Sort your Load Order with LOOT.

 

When starting the game through the Vanilla Intro Sequence with a script heavy modded game they only overload your resource capacity and therefore can not initialize properly, leading to an inevitable game crash.

For starting correctly with a modded game you have two possibilities:

 

1. Classic Start:

Deactivate all your mods apart from SKSE and start your game through the vanilla Intro "Cart" sequence by following these steps:

 

Spoiler
  • At the sequence of character creation don't touch any trimmings except the sex of the character that you wish to play - leave all in default settings, save while naming it: test1.
  • Go trough the game sequence until your hands will be untied and let one of the protagonist (Hadvar) "Find what to equip you" or (Ralof) "Inspect Gunjar's corpse" finish their tirade without touching anything or open any menu.
  • Open the console and type: save test2. The save console command requires quotation marks around the name if includes spaces: save <save name>
  • Quit the game without going through the menus by typing in the console: qqq (may cause a crash).
  • Reboot your PC for having the system to launch with a pristine memory capacity load.
  • In NMM or MO, reactivate all your mods in the list order of appearance.
  • Load your last save by typing in console: load test2 and let all the scripted mods load without moving, touching or opening anything in your menus. The load console command requires quotation marks around the name if includes spaces: load <save name>.
  • Wait for all MCM menus to appear, it will take time according to the mods that need to be initialized. When finished type in the console: save test3 Quit the game by typing in the console: qqq.
  • Reboot your PC, reload your last backup, wait a few minutes and then configure your character with the showracemenu consol command and open the MCM SexLab menu to activate the mod because it is not yet installed, let them do scripts and then set up all your MCM mods menus settings.
  • When done, open the console and save your modded game: save basegame. Never delete the saves you made as they will be handy in case of problems without having to go through the whole sequence of introduction.
  • You're now good to go for your new adventure.

 

Just a few tips: when you start by following the Empire you have no heavy armor on the way, while following the Stormcloaks, you can pick on the first enemies encountered.

This is not the only advantage, Imperial armor is worth more than Stormcloaks, so in addition to getting heavy armor from the beginning of the game, you'll also get more money - from being new to pro-gamer, when we start a new character, we all need money. :classic_biggrin:

 

2. Alternate Start - Live Another Life:

This is the simplest and least time consuming method. Download and install Alternate Start - Live Another Life, put it at the end of your Load Order just before any Bashed Patch, this is necessary for the mod to work smoothly, the only exception is the SexLab Solution mod that need to be loaded after AS - LAL. Activate all your mods and do the following steps for starting your game:

 

Spoiler
  • Start a new game in the starting cell.
  • Wait for all MCM menus to appear, don't move and don't touch anything nor dare to open your in-game menus.
  • Open the console and type: save basestart
  • Quit the game with the console command: qqq
  • Reboot your PC, load your game and savegame, let all the scripts go and activate SexLab Framework, do your MCM settings, redo a new save named what you want and go for venture ...

And never delete save basestart because this will serve you as a workaround each time you play if your game crashes when loading saves with heavily scripted mods, as the script engine needs to be started in a certain way and a blank game just at the starting cell of AS - LAL does the trick. Once loaded, load your regular game file.

 

EDIT: syntax errors.

abbbby

abbbby

Posted
  • Author
Posted
1 hour ago, Fifoo said:

 Brows is missing in your Load Order, it's a Ningheim Race requirement. First deactivate 37 25 SGEyebrows.esp for not being overwrited when installing that one. Install Brows and load it before 14  e The Ningheim.esp. Then reactivate or reinstall 37 25 SGEyebrows.esp make what fit best but I can't say this will work as I never played with a different race then vanilla one, you will need to be cautious here. Sort your Load Order with LOOT.

 

When starting the game through the Vanilla Intro Sequence with a script heavy modded game they only overload your they only overload your resource capacity and therefore can not initialize properly, leading to an inevitable game crash.

For starting correctly with a modded game you have two possibilities:

 

1. Classic Start:

Deactivate all your mods apart from SKSE and start your game through the vanilla Intro "Cart" sequence by following these steps:

 

  Hide contents
  • At the sequence of character creation don't touch any trimmings except the sex of the character that you wish to play - leave all in default settings, save while naming it: test1.
  • Go trough the game sequence until your hands will be untied and let one of the protagonist (Hadvar) "Find what to equip you" or (Ralof) "Inspect Gunjar's corpse" finish their tirade without touching anything or open any menu.
  • Open the console and type: save test2. The save console command requires quotation marks around the name if includes spaces: save <save name>
  • Quit the game without going through the menus by typing in the console: qqq (may cause a crash).
  • Reboot your PC for having the system to launch with a pristine memory capacity load.
  • In NMM or MO, reactivate all your mods in the list order of appearance.
  • Load your last save by typing in console: load test2 and let all the scripted mods load without moving, touching or opening anything in your menus. The load console command requires quotation marks around the name if includes spaces: load <save name>.
  • Wait for all MCM menus to appear, it will take time according to the mods that need to be initialized. When finished type in the console: save test3 Quit the game by typing in the console: qqq.
  • Reboot your PC, reload your last backup, wait a few minutes and then configure your character with the showracemenu consol command and open the MCM SexLab menu to activate the mod because it is not yet installed, let them do scripts and then set up all your MCM mods menus settings.
  • When done, open the console and save your modded game: save basegame. Never delete the saves you made as they will be handy in case of problems without having to go through the whole sequence of introduction.
  • You're now good to go for your new adventure.

 

Just a few tips: when you start by following the Empire you have no heavy armor on the way, while following the Stormcloaks, you can pick on the first enemies encountered.

This is not the only advantage, Imperial armor is worth more than Stormcloaks, so in addition to getting heavy armor from the beginning of the game, you'll also get more money - from being new to pro-gamer, when we start a new character, we all need money. :classic_biggrin:

 

2. Alternate Start - Live Another Life:

This is the simplest and least time consuming method. Download and install Alternate Start - Live Another Life, put it at the end of your Load Order just before any Bashed Patch, this is necessary for the mod to work smoothly, the only exception is the SexLab Solution mod that need to be loaded after AS - LAL. Activate all your mods and do the following steps for starting your game:

 

  Hide contents
  • Start a new game in the starting cell.
  • Wait for all MCM menus to appear, don't move and don't touch anything nor dare to open your in-game menus.
  • Open the console and type: save basestart
  • Quit the game with the console command: qqq
  • Reboot your PC, load your game and savegame, let all the scripts go and activate SexLab Framework, do your MCM settings, redo a new save named what you want and go for venture ...

And never delete save basestart because this will serve you as a workaround each time you play your game crashes when loading saves with heavily scripted mods as the script engine needs to be started in a certain way and a blank game just at the starting cell of AS - LAL does the trick. Once loaded, load your regular game file.

 

 

I'll go for the second method as it seems less time-consuming. If it doesn't work, then I'll try the first one!

 

*By the way I noticed that sometimes my Skyrim.esm grays out (goes missing) and all the other mods turn orange which indicates that some of their requirements(skyrim.esm) is gone missing. So when that happens I just exit NMM and re-open it and the skyrim.esm is enabled again. 

Fifoo

Fifoo

Posted
Posted

Before that make a backup from your game ini files. Then just open up Skyrim and on the startup window, below options, check the data files if they are all validated there.

abbbby

abbbby

Posted
  • Author
Posted
8 hours ago, Fifoo said:

Before that make a backup from your game ini files. Then just open up Skyrim and on the startup window, below options, check the data files if they are all validated there.

Classic start almost worked except I get CTD when I enter Helgan Keep.

 

So the "classic start" seems to be more promising but personally, I don't think there's any much difference between disable&enable all mods and delete&re-install mods. Since I don't have many mods like a few days ago, it's really easier for me to just start all over again. I'm kinda unsure about sexlab related mods like Zaz, Defeated and MNC. I've been installing them in this order : Sexlab -> Funnybizness -> Defeated -> MNC -> Zaz. 

 

Edit* I've installed all mods except anything that is related to Sexlab. Also I decided NOT to use ENB since it causes CTD (I honestly used ENB to apply oil effect on my character body '_')

 

Edit** So far I've installed Sexlab and MNC. Things are going perfectly well!! I used NVIDIA Inspector to limit my fps ~64fps. But loading time is really long (about 5-6 times longer than normal loading screen time) I'm not exactly sure how to fix this. Will SafetyLoad help??

 

Edit*** Long loading screen issue fixed (it was a hiccup). I can't install funnybizness animation because it causes CTD "after" loading screen. Maybe because it contains too many animations??

Grey Cloud

Grey Cloud

Posted
Posted
8 hours ago, abbbby said:

*By the way I noticed that sometimes my Skyrim.esm grays out (goes missing) and all the other mods turn orange which indicates that some of their requirements(skyrim.esm) is gone missing. So when that happens I just exit NMM and re-open it and the skyrim.esm is enabled again. 

I get that from time to time. I don't worry about it.

Fifoo

Fifoo

Posted
Posted
10 hours ago, abbbby said:

*snip*

Apparently you don't care to take my suggestions and recommendations into account. You are the best candidate for crashes at the beginning of the game because already the introductory sequence is full of scripts and you still hope to be able to launch a modded game steadily? No serious modder will recommend you to start this sequence with - and in addition SexLab and all the following mods? All you will get is a massive overload of scripts who will be unable to do what they are intended for during your playthrough. None to say when you will be in need to update certain mod after that, it's not a cautious attitude. But as you seem to want to persist, free to you ...

 

10 hours ago, abbbby said:

I've been installing them in this order : Sexlab -> Funnybizness -> Defeated -> MNC -> Zaz.

Your install order is incorrect. Follow and also read additional notes given in the spoiler bellow, but before doing so edit the Skyrim.ini [Papyrus] section, this is recommended for a SexLab playthrough and never go over the given last digit unless your goal is to have an unstable game:

 

Spoiler

Make a backup of Skyrim.ini before making these tweaks:

 

[Papyrus]
fUpdateBudgetMS=1.6
fExtraTaskletBudgetMS=1.6
fPostLoadUpdateTimeMS=1000.0
bEnableLogging=0
bEnableTrace=0
bLoadDebugInformation=0
iMaxMemoryPageSize=8192
iMinMemoryPageSize=256
iMaxAllocatedMemoryBytes=153600

 

Recommended SexLab and required mods install order:

 

Spoiler

Correct Install Order:

 

  1. SKSE - 1.7.3 or newer
  2. SkyUI - v5.1
  3. UIExtensions - v1.2.0 - Needed for SexLabTools
  4. FNIS - v7.4 - Don't forget to download the "FNIS Creature Pack" - Notes and recommendations from the author: "Recent Changes - Release of FNIS (LE) as 32bit applications only (too much hazzle for many users to decide between FNIS 32/64 bit) - The optional FNIS 7.4 XXL Beta (20,000 animations) will run slower on PCs with little memory.
    It is also likely, that using mods with a total of more than 10000 animations will increase the likelyhood of load CTD. How much? I don't know. Use at your own risk.
    It is GENERALLY and STRONGLY recommended, that you DO NOT INSTALL any of Steam, Skyrim, FNIS in folders that are protected by Windows UAC (User Account Control). These are "C:/Program Files (x86)" or "C:/Program Files" (or their localized correspondents, e.g. "C:/Programme (x86)"). Use root folders like "D:\Games". This way you can avoid serious protection issues, especially when using Mod Managers."
  5. Skyrim SexLab - Sex Animation Framework v1.62 - Updated Jun 3rd 2016 v1.62
  6. SexLab Tools - v3.0 - Optional, but recommended - SexLab Tools is a simple mod that aim to give the player some tools to control a sexlab sex scene, mainly the pose & tags, using menus from the UIExtension mod.
  7. Sexlab Aroused Redux - December 05 2016 v28b - You only need it's bsa file to prevent the Creature Framework API reference not found error.
  8. More Nasty Critters: SLAL Edition - Updated v11.1D
  9. Hentai Creatures - Optional
  10. Creature Framework - v1.1.0-pre2
  11. JContainers - v3.3.0.RC.3
  12. SexLab Animation Loader: SLAL - v1.5 - If you want to build your own animation packs, you will also need:
  13. Python 3.x - Optional
  14. SexLab MatchMaker - Optional, but recommended - Updated 09/17/2014 Rev 7
  15. FunnyBizness (v25) SLAL Pack by Shashankie - v12.0 - Don't install FunnyBizness' Animation Resources as these are resources for Modders only - Install the FOMOD version with your Mod Manager - when you run the game, MCM Menu by the name of SL Anim Loader will appear. Just click enable all animations in that menu and then click register all animations. After that, those animations can be played by SexLab.
  16. SexLab Defeat - v5.3.5 - Disable the option Disable Starting Teleport from SexLab, it conflict somehow with Defeat and will slow down and break some feature of Defeat.
  17. Zaz Animation Pack - v8.0 [2017-11-15] - Don't install Zaz Animation Pack V7.0 [2017-05-16] it is outdated and have issues with some animations - Beware of the Skeleton versions you use:

    Highly Recommended - One of these

    XP32 Maximum Skeleton Extended - XPMSE 3.94+ by Groovtama - Use this if you are using HDT and NOT using the Milk Machine
    OR
    XP32 Maximum Skeleton Extended 1.93 Legacy Edition - Use this if you are NOT using HDT and ARE using the Milk Machine
    OR
    XP32 Maximum Skeleton -XPMS 1.96 by xp32

 

Important notes:

 

Beware of not reaching the 10.000 animations cap with the regular FNIS Behavior file. Use the FNIS XXL version when you want more animations to register correctly. FunnyBizness has 8.000 animations on its own asset, so watch this, but beware and read what Fore has noted.

After installing and activating all the SexLab related animation mods in your Mod Manager as per shown - and in that EXACT order, run LOOT to sort the plugins then run FNIS for generating the Output file.

Don't forget to activate SexLab Framework BEFORE configuring the other SexLab related mods, read the mod authors descriptions and recommendations.

 

10 hours ago, abbbby said:

Edit* I've installed all mods except anything that is related to Sexlab. Also I decided NOT to use ENB since it causes CTD (I honestly used ENB to apply oil effect on my character body '_')

Incorrect ENB Local.ini settings and/or inadapted hardware in correlation of the choosen ENB version. Incorrect Game ini's, etc ...

By disabling your ENB you also remove the possibility to have an implemented memory manager called "ENBoost" that enhances the efficiency of video memory management - your VRAM, resulting in increased performance and stabilization for your game - don't forget that Skyrim has a hard coded 3.1GB RAM limit, in addition to the increased quality provided by the post-processing engine.

Knowing that you can use ENBoost without installing an ENB.

 

10 hours ago, abbbby said:

~64fps

Why 64Fps? Is that the refresh rate of your monitor in a native resolution and at stock clock?

 

10 hours ago, abbbby said:

Will SafetyLoad help

Simply put: No. It will do worst instead: causing stability problems and obsolete.

The newest version of SKSE already comes with its own plugin.

abbbby

abbbby

Posted
  • Author
Posted

I forgot to run Wrye and build patch every time I add a mod. I wasn't familiar with Wrye so I kinda avoid to use it but I guess it was a pretty essential thing to be concerned about :tongue:

Archived

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

Go to topic listing

  • Recently Browsing   0 members

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