27X

Using NMM for "injection" mods is not a particularly good idea.   MO actually isn't that great either owing to some issues with virtualization.   For stuff like FNIS, SKSE and BS, the first two should be raw installed to and maintained via in Data, with any plugins you have (SMP/HDT/Tints) managed through discreet MO "plugins". BS should be in an MO folder, but unchecked and only opened when you need to boob the boobs, with any updates being applied as raw overwrites.   Can't really recommend NMM.

  Brilliant. Been working on a khajiit/Ka Po' Tun based martial arts mod, this will help immensely.

see above post.   also this: http://www.loverslab.com/files/file/2373-sos-addon-pubic-hair-for-females/

  Oh look this topic again.   Never mind that the AI in the game just now got fixed, never mind that the best method for globally flagging npcs without exploding papyrus has just been established like 9 months ago, never mind that Cabal is just about to update Book of Secrets, never mind that FO4 modding will be much tighter controlled by Beth and won't be viable for months after launch other than generic replacer mods, never mind that 0S's framework can be applied to combat and magic dules and all kinds of state-machine type stuff to make interactive cutscenes or choose your-own-adventure mini battles/duels/bard slap fight, never mind that there's been seven huge ass landmass/quest mods made within the last four months, never mind that a perk overhaul that doesn't completely break java and Skyrim has been released and works exactly as advertised, right out of the box, never mind that Fore is presenting a framework to expand the WORST area of the game into something current gen and compelling without having to pay for an absurdly marked up license, never mind all that shit, cause you know it's over guys, it's all done and will never come back.  

>http://www.youtube.com/watch?v=7EgWWuWJ7pw

  This is the biggest issue right here, because we've already seen what Intel has done when AMD no longer proved to be viable threat, as sure as shit nVidia will do the same, because fabbing and making GPUs is fucking expensive, and AMD respinning their GCU business back into a discreet division is not a good sign, because it means they're probably shopping it around behind closed doors.   AMD currently has 26% presence in the dedicated consumer GPU market, and instead of the Fury being a leapfrog that everyone expected it to be, it was just a slightly under parity release with a much better price point, and nVidia will have both a smaller process and up to 32gig capacity on HBM 2nd gen next go round.

Sound/voice/esm/[male/female]/dialogUEGE_*******.fuz and several dialoguegeneric_******.fuz files as well, you're going to have to sort through those to separate breathing, grunts and shouts.

I'm using 279 and I don't have any issue like that UNLESS, I've also loaded SMP.   SMP is incompatible with ANY ENB that alters imagespace values, aka pretty much any ENB that uses Matso's or Prod80's code/set up.   .279 + K:   also, every enb is at Boris' site so I have no idea what "archive deleted" means, unless you were somehow obnoxious enough to get yourself banned from enbdev, which would take a huge amount of assery considering how apathetic boris is.

Pretty awesome.

  http://www.tomshardware.com/reviews/amd-radeon-r9-fury-x,4196-8.html   http://www.anandtech.com/show/9390/the-amd-radeon-r9-fury-x-review/25   the 295 hits even higher when fully pegged, which provided list of said games will do, also said charts were conducted with 3K and 2K screenspaces respectively and most certainly without 8K/4K in a 4K screenspace textures hogging the ram, which Skyrim can certainly accomodate.     I've owned both the fractal and the Haf X, the Haf X has literally double the airflow capacity by means of using the recommended size and spin rate of fans.   There is certainly someone who doesn't know what they're talking about and has been routinely criticized for such, and it isn't me.   As an aside it's pretty interesting that you consider yourself versed in non-downsampled 8K/4K gaming without having ever actually done it.

Except this isn't enough of an incentive to add more scripts and anims I'm never going to use, which is why the suggestion exists in the first place.   I'm not going to order a full course meal just to get a drink of water.     Which is is more inline with being workable.  

  Two titans is 12 gigs until such time as DX12 drivers reach full maturity for asynchronous storage , by which time both AMD and nVidia will have new flagships.

You want the extra s, for future proofness.

Most is an extremely relative term, and I have no use for it.

That doesn't change my premise at all.

how about a nonzaz version.

  Just do the process in reverse if you don't have the correct nodes: open 0.nif and copy/paste.   Don't forget to add the nistring in the new parent, and don't forget to check your xmls to make sure they have the right names and the right bounding constraints for the mesh objects.   Also make sure to sure you add _0 and _1 nifs SEPARATELY or you won't have difference in your weights.

what order are the following installed in   Racemenu 3 XPMSE Realistic Ragdolls UUNP + bits

UUNP has DG weights, but as btn would be the first to point out, there's an asston of added stuff on there, hence the issues cell alluded to.   Personally I would lose the belly weighting and deformation or put it to a specific branch.

How old is your skeleton

  The only way noodles arms goes away for Skyrim bodies is if a deformable section is "welded" over the joint itself to stretch, essentially the same as what was done to add vaginas to the standardized bodies, and good luck in getting not look like a bat wing in flight on arm-over-head animations and poses.   DG is about as close as you're going to get with the normal mesh and polycount.

  The same way you'd add it to any other head, you need to unpack the citrus bsa first is the only additional step. Then add the appropriate NiStrings afterward.

Would be kind of hard to do seeing they're deleted, seeing as SMP and any ENB that alters imagespaces don't get along at all, so I went back to PE.   The thread that shows you what to do is here:   http://www.loverslab.com/topic/44803-hdt-smp-ks-pony-hair/   Ledo's very helpful xmls are here:   http://www.loverslab.com/topic/45034-prepacked-hdt-sm-hdt-skinned-mesh-physics-with-modding-guide/page-13   Ledo's premade xmls are also in the same thread

Remove the mempatch. If your SKSE ini and enboost are set up correctly, it's not needed anyway.