prideslayer

Wheeeeee manythreads GO.

No you should use the normal interface. You're saying it's the right 'way round in the call? That's not what the log I saw before said/says, but this one says they're in the right order. So.. dafuck is goin' on n' stuff. I'll dig.

EDIT:

Oh just FYI we do not actually have any animations at all for normal mirelurks -- only mirelurk kings. Different skeletons and all.

Ah beat to the punch. It appears actora/actorb are swapped in the call for mirelurk, not sure if it's happening anywhere else. Tomm, let me know if they're actually the right way 'round and sexout is somehow screwing up or what.

Thanks for tracking it down to Submit. I'll see if anyone is actively working on that, it's easy enough to fix there; just swap actora/actorb (or male/female if it's using the extremely old interface) arguments to the call.

Mod Explorer is only for Skyrim? I was just guessing that it would work with anything NMM is managing, I only use it for Skyrim though.

You installed something else, maybe manually, I don't know. I can guarantee it's not sexout, because I test sexout's default install with no other body mods loaded nearly every day, installed via FOMM. It works. The hands don't flash weird colors. You have some kind of texture conflict with something else you've installed.

If you don't know what it is, you're the only one that can figure it out. None of us can magically guess what you did wrong. Deactivate all your mods in both NMM and FOMM, verify your steam cache to reset all the files in the data dir, and then start over. Only use ONE mod manager per game this time, and use it for *everything*. No mixing mod managers. No manual installs. No future problems.

2.10.93Beta8 in OP

Changes:

- 801-804 half-fixed.

- A new option to run/runfull calls to pick a random animation by matching flags.

801-804 are properly showing the prop now, but SOME mesh is still missing, as I'm still seeing the big missing mess exclamation mark when running them. I haven't dug in to figure out just what's missing now.

fnSexoutActRun and fnSexoutActRunFull now understand the animation registry flags, so mods that want to filter by sex position "type" or any of the other flags in the registry can do so easily. SexoutNGDoPlayerVaginal has been modified to make use of this as a sort of demo, and now only picks "doggy" flagged anims -- which in sexout parlance means "doggy style."

The old call was this:

call fnSexoutActRunFull ar_Map "actorA"::0 "actorB"::playerRef "isVaginal"::1

let arFilter := ar_List "doggy"call fnSexoutActRunFull ar_Map "actorA"::0 "actorB"::playerRef "isVaginal"::1 "flags"::arFilterlet arFilter := ar_Null

I've left beta7 up as well, intentionally. This flags honoring thing was a bit of a mess to code and may have introduced nvse cosave leaks. So just in case it has, people can go back to beta7 if needed.

If you install SexoutNG with the default options, then both males and females fully get naked duing sex scenes. Males will be in their underwear when naked but not having sex.

If that isn't working, it means you've either told sexout to not use its bodysuit, or you installed some other body mod that's overriding the bodies.

The lesson here is that you should install one mod at a time and test them. When you install a dozen or a hundred of them all at once before testing any of them, figuring out what is causing your problems becomes a lot of work -- more work than it would have been to test them one at a time in the first place.

Yeah I'm seeing the same thing on those two packprof, thanks.

Also, to whoever it was that reported 203 is messed up -- it's not, on my end. It should be the 'pushup' blowjob and looks fine here.

OK, 801-804 are fixed locally, my dupe removal also removed those since there were two (or more) of each one, so the pipe/wrench/bottle/baton anims will be fixed next beta. 5001 and 5401 are both horribly misaligned for me. I haven't tested yet, but I think something may have went wrong with all the 3p animations -- would be helpful if others could confirm.

Odessa's testing seems pretty thorough, but I still just sv_destruct or ar_null the arguments anyway; the engine seems to make copies for the arguments rather than passing the original values in, so I haven't seen it do any harm, and it's easy to just copy/paste the list of vars from the top of the script to the bottom to catch them all.

I do also, and arrays get set to ar_null as well.

Assuming you've already handled any "same frame" issues (don't add the item in the same frame you equip it or remove another item -- usually does work, sometimes does not) are you sure the previous item in that slot wasn't set with the nounequip flag? Was there possibly a script running that reequipped the old item?

Ok. Well let me know if it continues growing at a seemingly abnormal rate. It's normal for it to grow as more NPCs are morphed for the first time, same with the CSV -- or make a save clean of bodymorph and resume testing.

I can purge the deads and all that in a future version, won't be too difficult. However, can you answer the question about if you made a clean save or not? I'm not as concerned with the load times as I am with the possibility that data in the cosave is still leaking.

I really thought they were for some reason, and I'm the last person that would mistype the eff-ell in NX as eff-one. Oh well.

Well according to the NX file, there are only 72 actors with morphs applied. I'm digging into the cosave now, there's definitely some leaked data in here from bodymorph but unless this save was made clean of bodymorph I can't tell if it's "old" leaks that no longer exist, or if it's still leaking.

The bodymorph fixes cannot recover old leaked data, they can just prevent future leaks.

There is a similar program that works with NMM called "Mod Explorer for NMM". It's not as nice to use as the FOMM one but it does basically the same thing. You should not continue to mix and match mod managers, they are not strictly compatible when used that way.

There's a link in the first post of the SexoutNG thread that tells you how to fix the mods that are causing this problem. Weapon mods or not doesn't matter. Anything that adds or modifies animations (morphs and poses are also animations) can cause it, sexy or not.

Yes. Do what I told you to do above, it's hardly "weeding through." Less than 10 mouse clicks. If that's too much to do, then just uninstall everything, because problem solving doesn't get easier.

Generally no. Sexout packs most of its resources in BSAs so you can install things that override it without conflicts you have to ask/guess about in the mod manager. Any loose files in the data dir will always override what is in the Sexout BSAs no matter what order they are installed in.

The game crashing before starting means you have some other plugin active that depends on sexout, and you haven't uninstalled THAT. If you use my FOMM version (here on LL in non-adult downloads) to launch the game, it will refuse to do so and tell you which plugin is causing the problem.

Sexout isn't doing what you think it is. The breezes it installs is THE breezes, without modification. Installing both of them at the same time is pointless but can't harm anything, as there's no difference between the two.

You've installed some other mod that overwrote the texture(s), something with it's own male textures. If you're using FOMM, the built in file manager can be used for you to find out exactly which mods have installed a particular file (like the texture dds), and which one of them is active as well.

Pregnancy is one of those things that you'll likely still want custom meshes for, however this can give Hal the capability to adjust steps between the meshes -- so maybe there won't have to be so many different ones for each outfit. Just using this to show pregnancy is possible, but it doesn't look very good when the belly starts to get large from a slim starting point.

I don't know if you're serious or if that's sarcasm.. or if it's fixed in yet another NVSE release.. or if I'm on drugs. So...... yeah.

Yeah for some reason the NX functions are like the only case sensitive thing in the game.. well except for other NVSE plugin functions I guess. I should at least make lowercase aliases for all of them.

Better yet: Uninstall that and install my version of FOMM, from the non-adult downloads area. If you ARE using my version.. why the heck does that say GeMM, mine installs to FOMM, not GeMM -- and that readme doesn't exist.