TechAngel85

Nexus has a new position open (Community management and development lead) that is available for any member of the community who has been a member of Nexus for at least one year. Salary: 18,000 Euro ~27,600 USD If I wasn't already making more, I'd consider applying. I can think of several members here that would be good for the job.

I wonder if the author forgot to remake the normals after his changes because that would result in what kryptopyr is saying. Personally, I am in agreeance with EssArrBee on this one unless a less busty/more vanilla version can be made. You can see the horrible stretching in the shots crime_syndicate made. @Crime_syndicate I take it you are familiar with 3ds?

All users should be able to add a normal tag to the thread. The prefix tag (yellow tag) can only be added by Staff. Adding the normal tag will allow the mod to show up when the threads are filtered for testing. Then if we decide it's worth testing, a staff member will add the official prefix tag to it. If not, we'll remove the normal tag and the mod will be removed from the testing filter.

ENB will affect the look if the author relies on SSS for the fur in any way.

That's a good question for Z, but I will say that no user with

Are you trying to install an ENB Prest or just ENBoost? I'm not set up with ENB right now due to STEP testing and whatnot, or I'd test this out. What I can say this that bFullScreen in my personal profile is set to 1 while it was running in window mode. I personally think that ENB simply overrides that parameter in the INI so there's no need to mess with it. I'd be interested to hear if anyone has different results.

Looks like the same thing you get with the fire mesh and objects with transparency in them. If you look through the transparent part of the fire mesh, objects with transparency in them tend to revert back to a non-transparent state. This appears to be the same thing, just with the "glow mesh" from the staff. As far as I know, this is an engine limitation with transparencies and can't be fixed.

64bit users should only use that formula if they have at least 8GB of system RAM; else, they should use the same formula as a 32bit user in most cases. Z came through and "optimized" the guides and seemed to have missed that little bit of info. I'll update the mod page.

If anything, I'd say silverware only. Everything else, I prefer what we currently have.

I would vote, yes.

Serious looks over-saturated to me.

All Extended users should have the mod installed.

I've always had Realistic Force installed, but have the ESP moved up to Optionals as per the instructions. I'm assuming that is what you incorporated. The actual mod should still be installed by all users.

Well that one change is required by XPMS apparently. I've posted on the Nexus forum asking for some clarity between the two versions.

No Spinning Death Animations was just updated again. I don't know which version is included in the Patches. https://www.nexusmods.com/skyrim/mods/17214/

I can see where it wouldn't be needed for Core as there aren't any Core mods that rely on it. Ragdolls and DSR are the only two mods that it should be installed for in Extended. Ragdolls is actually a requirement for XPMS. I really see no reason not to install it for Core as many animation mods down the road in the Guide or in Packs might require it. More of a preventive thing than anything. In fact, we might want to check into Groovtama's XPMS Extended version as it supports far more things and doesn't seem to require any specific body mod that I can tell from the Nexus page. Though, the Nexus page could use some cleaning up and clarity.

Possibly. I don't see why XPMS couldn't be Core. It's a skeletal fix over vanilla, imho.

I just tested the females. I tested it allowing BSW to overwrite CQLA and there was no arrow length issue nor was there any floating issue with the quivers. This was using a female nord and the small body build possible. I also tested without CQLA and saw no arrows clipping into the hands. I would like to know other user's experience without CQLA to find out if we even still need that mod. If we go with BSW, then I think we can drop CQLA.

It's a minimal effect, but if you want it to be tested add the "testing" tag and we'll get to it.

I agree as well from those shots. I've said it several time but CaBaL's landscape textures just appear to have a blur applied to all of them. STEP is much better.

Yeah, I figured we'd roll any patched needed into the STEP patch. I'll ask about rolling out a Beta of the STEP Patch for testers. Unless the conflicts are game-breaking, it might not be a big deal though.

I'll probably look more into this thing today and see what the STEP option for the FOMOD will need. I'm officially on vacation for a bit so I'll have more time than usual to work on some things. Priority was finishing up some FOMOD work I was doing for Krypto, which I finished yesterday so I'm a fairly free agent at the moment.

Follow directions using HearthfireChimneys.

Moved it back to Interface.

I added some basic info to the the ForceBorderless parameter. I might hit up keithinhanoi for a more detail explanation on those two parameters. As far as having to set bFull screen=0, I don't think I've done this and I run in Windowed mode. The only experience is that the game seems to have to "re-render" the game scene when you Alt-Tab back into it. This could be because I, myself, have it set up incorrectly. As for EnableUnsafeMemoryHacks, there isn't much more to say on the subject than what is in the description. If you want finer details, I'd suggest asking over on the ENB Dev threads.