OBody NG Troubleshooting Guide - Frequent Issues

Let me preface this by saying that as of version 4.0.0, OBody NG is in a very stable state - in other words, it's a mod practically free of bugs. There are still some very minor bugs that will always be fixed in each update, but nothing that makes the mod stop working as it should altogether. If you can't get this mod to work at all, it is always user error. No exceptions.

If you still can't fix the problems listed with the solutions provided. you are doing something else horribly wrong. I can't tell what. Go through the installation guide again, and take it easy.

Remember that you when have an issue, always try on a New Game. I'm not saying that you must start a New Game - it's that if it works on a New Game, there is something wrong with your save.

1) When I press O, nothing happens or the game freezes!

This is always the case when one or more of the below items happens.

1) You did not install the latest version of UIExtensions, a requirement clearly listed in the Requirements list of OBody NG.
Solution: Install UIExtensions. Duh.

2) UIExtensions is installed but the UIExtensions.esp plugin is disabled.
Solution: Enable UIExtensions.esp on the plugin panel of your mod manager. Sometimes, when you install a mod, both MO2 and Vortex forget to enable the actual plugin of the mod.

3) You have the wrong version of PapyrusUtil installed, or it's being overwritten by another mod.
Solution: Check and install the correct version of PapyrusUtil for your Skyrim version.
- For Skyrim version 1.5.97 (SE), get version 3.9.
- For Skyrim version 1.6.353 (AE), get version 4.3 under "Old Files".
- For Skyrim version 1.6.640 (AE), get version 4.4.
- For Skyrim from GOG, get PapyrusUtil GOG.

If you are now 100% sure you have the correct version of PapyrusUtil for your Skyrim version, check if it's being overwritten by some other mod in your mod manager. A popular mod that overwrites PapyrusUtil is a mod called Campfire. If you have Campfire, you must let PapyrusUtil load AFTER Campfire. In Vortex, simply set the rule to load after Campfire. In MO2, put PapyrusUtil at the bottom of your load order (highest priority number).

Sexlab and Sexlab mods might also overwrite PapyrusUtil. There are plenty of mods out there in the wild doing this. So always check PapyrusUtil overwrites!

4) The key is most likely not 'O'. Sometimes, OBody NG might assign a different key for unknown reasons. This can also happen if you have a different keyboard layout than standard.
Solution: Open the OBody NG MCM menu and check which key is assigned to the preset menu. Reassign it to whatever you like.

2) The MCM is not appearing!

This is always the case when one or more of the below items happens.

1) You have not given enough time for the MCM to register in the first place.
Solution: MCMs are great, but they are damn slow. Go ingame and let the game run unpaused for up to 5 minutes. After that, check if the OBody NG MCM now appears.

2) You are using OBody NG Settings Loader but not did not install MCM Helper, or got the wrong version.
Solution: Check and install the correct version of MCM Helper for your Skyrim version.
- For Skyrim version 1.5.97 (SE), get version 1.3.0 under "Old Files".
- For Skyrim version 1.6.353 (AE), get version 1.3.2 under "Old Files".
- For Skyrim version 1.6.640 (AE), get version 1.4.0
- For Skyrim from GOG, also get version 1.4.0.

3) I went through this and the MCM is still not loading.
Solution: MCMs are stubborn bitches sometimes. When all else fails, this mod has been proven to work 100% of the time: MCM Kicker SE. Another mod that always helps as well is Papyrus Tweaks NG.

3) Sometimes, I get a random CTD while playing or in very specific areas of the game.

First off, get Crash Logger SSE AE VR, and make the game crash so you can actually check a crash log.

Read the description of the Crash Logger mod page linked above. It has all the instructions about where you can find the crash logs.

Now, check if OBody and Racemenu are actually in the crash log in the Probable Call Stack section (you will see references to skee64.dll and OBody.dll).

If they don't appear there, OBody and Racemenu are not at fault. Your problem lies elsewhere, unrelated to these mods.

If they do appear there, then there are two possible reasons:

1. At the top of the crash log, it says: Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0xrandomNumberHere skee64.dll+001EAB4
The skee64.dll+001EAB4 is a crash that happens for unknown reasons on Racemenu's side. INI Tweaks for Racemenu helps alleviate this problem. Otherwise, there isn't much more you can do about it. Please note that after you install that ini file, you must open it and apply the changes necessary for OBody NG to work detailed in the OBody NG Installation Guide. You have been warned.

Crashes with the 001EAB4 code should be very rare and not happen often, and only happen after you have played the game for many hours straight. This means that when you reload the game again, you most likely won't see the crash again for quite some time.

2. If the skee64.dll crash code is different from the one above, then it's a crash that happens for unknown reasons when Racemenu applies the morphs. This crash should be random and extremely rare. If you're getting it frequently or in a specific area of the game, turn off Performance Mode from the OBody NG MCM to help alleviate this issue. You may turn it on again after playing for some time - you most likely won't get the crash again, at least for a long time.

Please understand there isn't much I can do regarding these problems. The crash happens when OBody asks Racemenu to do the morphing, so the problem is technically on Racemenu's side.

If you think your problem is different from what is described here, please let me know in the comments section of the mod page.


4) When I assign a preset to the NPC, the body is not changing!

Update to version 4.2.0 or greater, and make sure the option "Force immediate preset application" in the OBody NG MCM is turned on. You're welcome.

Still not working? It means you didn't build all the outfits properly with Zeroed Sliders in Bodyslide with the Build Morphs checkbox ticked.

If the body does not change only when nude, check item number 5) below.

----------------------------------------

Uh, you don't want to update OBody NG to a newer version? You really should. Anyway, here goes the old explanation then:

This is a memorisation issue with SSE Engine Fixes and Racemenu once you hit a certain number of mods (around 40 is the reported threshold, but please note the exact number can vary wildly. It's not recommended to try to get rid of mods to try to solve this issue). The preset and weight changes will only apply if the actor redresses, if you change cells or if you save the game, exit the game and reload the game.

To fix this, set MemoryManager and ScaleformAllocator to false in the SSE Engine Fixes configuration found in SKSE > Plugins > EngineFixes.toml, wherever you installed SSE Engine Fixes to. NOTE HOWEVER that turning those two off might cause random CTDs while playing in load orders with many mods.

If you get CTDs after setting those two options to false, set them back to true. You'll have to live with presets not applying right away after selecting them until either SSE Engine Fixes or Racemenu fix this issue. It is NOT a problem with OBody.

Note that you can turn those settings in SSE Engine Fixes on and off as many times as you want. It won't harm your save in any way.

Another thing that helps fix this problem is not running any other apps on your PC while playing Skyrim. Restarting your PC also helps. Free up that RAM, Skyrim is a RAM hungry game after all, especially when modded!

This problem also exists in Autobody, and is well documented in both Racemenu's and Autobody's Github repositories. If you don't believe me, check the Github issues below, which are still open (i.e. not fixed):

https://github.com/napmouse/autoBodyAE/issues/13
https://github.com/expired6978/SKSE64Plugins/issues/51


5) The bodies change when clothed, but look the same nude!

This usually happens when you are using an NPC replacer which ships with its own body meshes. The most popular NPC replacer that does is Bijin NPCs. Note that many others do this as well! It's not exclusive to Bijin.

The solution to this is changing the replacer in SSEEdit to point to your default female body mesh, or try to find a De-Standalone version of the replacer here on Nexus. Bijin has one, which you can find by clicking here.

If all else fails, look into using a different NPC replacer.


6) When I change my character's weight in Racemenu, the weight does not change at all.

This is somewhat related to the problem above. For the weight change to reflect on your character, do the following steps:

1. Change the character's weight in Racemenu to the desired value
2. Save changes to exit Racemenu
3. Open the OBody menu
4. Give the character a different preset
5. Open the OBody menu again
6. Give the character the preset you actually want

The weight should now be properly updated.


7) I blacklisted an outfit from ORefit, but the boobs and nipples still look weird.

This is also due to the problem described above. If you change to the blacklisted outfit, remove it, and apply it again, the boobs should look normal now. Alternatively, if you apply the outfit and the boobs look weird, you can save the game, exit and restart Skyrim. When you load the save again, the boobs will look as expected.

As I said in the previous question, this is not a bug with OBody. It's a memory issue related to Racemenu/SSE Engine Fixes and possibly how Skyrim's engine itself handles memorization.

If after this the boobs STILL look weird, then you most likely have an outfit part equipped in a slot that is turning on ORefit (slot 32 or 46 or 56). Unequip that outfit part or also add it to the blacklist list in the JSON configuration file!


8) The presets ingame don't look the same as in the Bodyslide preview!

This happens when you've built the nude body or outfits with a preset that is not Zeroed Sliders.

Rebuild everything with Zeroed Sliders.


9) Most outfits are fine, but some look weird or change the body's proportions.

I've been investigating this issue for some time, and it seems like this is a problem with the outfits themselves. Unfortunately there is currently no workaround for this issue.

10) The preset menu appears, but the list is empty.

Assuming everything is installed correctly, this is a bug with Racemenu and also with the non deterministic way that Windows loads files. In short, if this happens to you, there's nothing you can do.

In rare cases, it might mean that you have a corrupt bodyslide preset, or a preset with special characters in its name and filename (such as kanji, cyrilic, etc). Rename those presets to have only standard characters.

11) Some presets are not appearing.

OBody NG filters out clothed presets by default. Yeah, those which have "Bra", "Outfit", "Clothed", and similar words in their name. There's no way to change this behaviour.

If you really want them, simply change the preset's name to remove those keywords.

12) I get clipping with some combinations of outfits and presets.

Some outfits are badly ported/converted and are prone to clipping.

Some presets go way overboard on the slider values, and clip with outfits.

ORefit may exacerbate both of these problems. Try turning off ORefit to see if it alleviates the issue.

The best solution, though, is usually to get rid of problematic presets.


13) SMP collisions are not correct for body and hair.

I could never tell why CBBE 3BA SMP Collision objects and SMP hair that you build in Bodyslide don't morph properly in OBody NG. It could be a problem with the SMP collision objects themselves in those mods, but a solution has not been found as of now.

What I usually advise people is to build SMP collision objects with your favourite preset or with a preset that is a good middle ground between all of your presets, instead of the usual Zeroed Sliders. This will ensure the most accurate collisions.


14) The NPCs have purple or blue bodies/textures!

This is not a problem with OBody NG. OBody does NOT touch textures. It only morphs body meshes.

If you are getting purple/blue body textures, it means you installed OPubes but you forgot to install one of its pube overlay packs.

In this case, you should upgrade to OPubes NG and follow the installation instructions there. OPubes NG is an improved and updated version of OPubes, with more features, many bug fixes, and with proper and clearer installation instructions. It is also specifically made to leverage the new features of the OBody NG API, providing better compatibility.

Purple/blue body textures can also mean you installed RBT and/or RSV, and did not install them properly. Once more, it's not a problem with OBody NG.

Don't come here complaining that OBody NG is giving you purple/blue bodies, because it is most certainly an installation error on your end from other mod.