prideslayer

That's normal behavior for arrays and why doc says to not do that in the tutorial. If you have an array like [0,1,2,3,4] and you're in a for or foreach loop on 2 and delete it, the next one is going to be 4 and 3 will be skipped. You can get around this with normal arrays (not maps or stringmaps) by counting downward instead of upward. I'm going to edit that post now because I didn't think of normal arrays like that, which won't work correctly even using ar_keys -- that works only with maps and stringmaps which are mainly what I use.

Wait, MY MCM? I wouldn't be writing an MCM for this -- that's up to whoever is using these insane vars. I can see it already.. NX_SetEVFl_Persist "has ever installed orgy" 1...

That will work also.

I mean it's "dangerous" because you could set some "sticky" cross-save value and then forget that you did, and have it impacting all the other saves unintentionally.

NVSE doesn't like it as it's more strict, so you have to resort to the old way of doing things.   int iRefref rRef; .... rRef contains some refset iRef to rRefif iRef >> 24 == 255; ref is dynamicendifI also don't remember if you can do the shift and compare in one line or not. If not:  int iRefint iShiftedref rRef; .... rRef contains some refset iRef to rReflet iShifted := iRef >> 24if iShifted == 255; ref is dynamicendifOr if you'd rather avoid the shift. int iRefref rRef; .... rRef contains some refset iRef to rRefif iRef >= 4278190080 ; this is 0xFF000000; ref is dynamicendif

Refs are just integers. Check if the value is >= 0xFF000000.

Nogore version? You're going to have to ask another German.

Well here's a good example of not following instructions. I said "nvse.log" You decided that meant "nvse_readme.txt" I'm starting to lose hope that this will ever work for you.

I mean attach it to your next message here. Upload it.

I just wanted to make sure that it says "launch nvse". That at least means NVSE is installed correctly, or probably is. Attach the nvse.log file in your game directory.

What's the top button on the right side of FOMM say?

Then why did you say "Try installing DirectX with the latest version from Microsoft"? The latest DirectX is version 12 and isn't going to help anyone with such a problem on bit.

You installed really old versions of both or you're not using the nvse launcher to start the game or... who knows. You're not following the directions somewhere along the way. Read them carefully.

NX V16 released. (ref.)NX_GetSkeletonPath - Returns the skeleton path for the actor reference. For example, returns "_male" for humans, "NVBigHorner" for big horners, etc. ----------------------- 1. Yes, just haven't had time to work on it lately. 2. Yes, sounds dangerous though!

No problem Hal, I'm annoyed by it too, just haven't been annoyed enough to fix it yet and nobody has asked. I'll try to get to it this weekend.

Sexout itself.

My point is you can't guarantee you're reaching that page instead of an imposter if your channel (network connection, browser, etc) is the thing you suspect of being compromised.

Install my FOMM found here in non-adult downloads. Not that old crap from nexus.

NMM sucks for this, unless it's fixed in newer ones (I am still 0.53.2) so using that rather than FOMM, it's a manual process. Click on an ESM and then make sure that anything listed on the right side as a "master" is higher up in the load order. You have many that look wrong at a glance, not just the sexout.esm.

You can use LOOT to sort it, or use FOMM instead which will tell you which ones are wrong (and color them, and prevent launching the game). Otherwise you need to read the instructions for the mods you've installed, but here's one free tip: sexout.esm needs to be before anything else that starts with 'sexout'.

That load order is so completely screwed up I'm surprised your only problem is with MCM. Put things in the right order first. Use FOMM or some other mod manager.

Really? I've never seen that be the case. Are you sure you didn't think this post was made in the skyrim section or something? There hasn't been a DX9 update in ages.

1. I don't really understand what you mean here, but you can't fuck animals or any non-humans -- they can only fuck you. We don't have any "person fucks dog/mutant/whatever" animations. It's possible whatever mod you're using to try to initiate sex is broken. 2. Earlier betas were causing pretty bad save bloat. If you load a game and then save it with the latest beta, future loads of that file should be much faster.

The upperbody that is included is the same one that has always been there (breezes). The erect version is also the same, except that AJ has weight painted it so that it will work properly with amras animation files -- note that this has nothing to do with amra's plugin/installer which will NOT work. It WILL work with the raw animations themselves, and also with Odessa's plugin for adding Amra's animations to sexout, which will be released when this beta is complete and all of that code is tested.

Using the same insecure channel that may already be compromised?