Kal

I'm also running ASIS and ReProccer, but SUM can't run AV for me. It just hangs partway through processing. I can run it fine standalone. Been the case since the previous update to AV. Interestingly(?) I've found that occasionally, AV won't run standalone either, but restarting my pc will clear that; there's no lingering processes that I can see in Task Manager, but something is obviously hanging around. This may seem like a silly question but have you followed this part of levi's faq? I was having issues getting AV to patch as well after the latest AV update (through SUM or via AV patcher) and asked him about it he checked it out and added the section to his readme. It should work for DSR if you're having problems, I'd try it at the very least the worst that would happen (didn't to me) is you would have to pick out the tesxtures to include for the variants all over again (and that doesn't take very long for me). Not a silly question at all! Yes, in fact I have, at Neo's suggestion a couple of days ago. It seemed to have worked at first, but subsequent runs started failing, and clearing the consistency files no longer seems to make any difference.

I'm also running ASIS and ReProccer, but SUM can't run AV for me. It just hangs partway through processing. I can run it fine standalone. Been the case since the previous update to AV. Interestingly(?) I've found that occasionally, AV won't run standalone either, but restarting my pc will clear that; there's no lingering processes that I can see in Task Manager, but something is obviously hanging around.

Subliminal Traps 2Â makes pressure plates and tripwires harder to see, much more realistic IMO. Includes versions specifically for RLO lighting. Just textures.

Hi FCqt :) Is there any chance you might still be going to do this? Â Between you, Vond and Neovalen (and a long weekend!) you've inspired me to get back up to speed with TES5Edit and start fixing these myself, but I'd appreciate the chance to compare notes (and verify I'm Doing It Right!)

As of now, I have never done it and not sure how to do it exactly. Like this: This logic can be followed to merge all your Compatibility Patches into a single .esp. It won't just be Cell records you copy, but the process is exactly the same, just deep copy every section you find when you expand each .esp. (hattip Vond)

Almost, but not quite. The first "condition" you are trying to drag in the image there is actually the entire "conditions" section. That box should be one further down - in both cases you are dragging a "Condition" record, not the "Conditions" . Otherwise, that's exactly right.

Yes - sorry about that, I realised that the problem was a different one and have edited my post accordingly, but obviously you've read the original and responded while I was editing. Sorry for any confusion :) You'll also hit a snag with the instruction for node 16776; there is a missing instruction to copy that node over during the creation of the VIS-RLO Patch, therefore VIS-RLO will not show up as you expect it to when you get to the same node in the VIS-RLO-SoS Patch. FCqt - obviously there are a few errors in this last set of changes, but more importantly - is it really necessary to create three patches? Could we not simply copy all the necessary overrides into a single patch (VIS-RLO-SoS Patch.esp)? I am hard up against the .esp limit so every file counts.

"VIS-RLO Patch.esp" does not even appear to be able to right-click on. I am lost.There is a missing instruction for that patch. You need to load the VIS-RLO Patch.esp in addition to the other files mentioned when you open TES5Edit for that patch. It should read:

Clearing the consistency files seems to have sorted it. Good call, thanks Neo :)Â

I can't get AV to run under SUM any more. It runs fine standalone, but under SUM, it grinds to a halt during processing of AV. Â I've tried increasing the memory allocation as far as I can (1,250mb) but it doesn't seem to make any difference. I really want to be using SUM because I've hit the active .esp limit, and the merged patch is an obvious way to reduce my .esp count! Any ideas?

It merges those files into the bashed patch, so if you already used that you'll even save six, not five. So yes, you can deactivate them after (WB will show a + icon for files that are deactivated but merged) Sent from my iPhone using Tapatalk 2 Is there any reason not to do this? I've often wondered why Neo chooses not to in baseline SR.

Very helpful, thank you!

Quite a nice little animation tweak if you like your archery killmoves: Archery - Spinning Arrows [video=youtube]https-~~-//www.youtube.com/watch?v=rJoPeV3-XYY

Can you explain a bit further Iroha? I've been sticking with the 1.6d xpms + cheskos quivers mod for now because I couldn't figure out this crash. I'm sure I'm not using anything more than you are, I'm using SR and a subset of the mods from your post (SkyRe etc) so the cause must be something we have in common. If you've fixed it I'd like to know the details please :)

It's not just FCqt - look a bit further back on the pre-release thread, several other people have mentioned this since the update to xp32.

Nothing to do with DLCs, I have them all and I get CTD's with females on the 1.7 skeletons. Interesting to see Neo isn't getting this himself though, I wonder why that is. I am using some extras on top of baseline SR - several things from Iroha's thread. Maybe the common factor is there? I can't imagine what might interract with the skeleton in such a fashion though.

Yes, same here, rolled back to 1.6d + Chesko Quivers which works fine.

This thread's title is just begging for hilarious misinterpretation.

I'm unable to find this record. Someone else mentioned this a few pages back, it looks like the mod might have had a silent update which cleaned this particular entry.

Still, I think it's probably easier to maintain (and to follow) when you only need to worry about the formID and the details of the edit. You could always include an instruction to set the relevant context so they still see the conflict that you're focusing on, it might be a good idea anyway as the colour might help prevent accidental mis-drags which can be catastrophic in TES5Edit! I know I got significantly faster when I switched to using the search box to select the formID instead of the tree, but I guess I only do it that way because I already know what I'm doing with TES5Edit, so I take your point :)

FormIDs are unique, when you go to a FormID via the search box it will show every loaded esm|p that contains it in the right hand window. The default context will be the earliest master for that FormID, most often this will be Skyrim.esm. In practice though, context doesn't matter: as long as you follow Neovalen's instructions and drag data from and to the correct .esp's columns, the result is the same regardless of which .esp you set as context. The benefit to selecting the relevant .esp as your context is that it makes it easier to spot the conflicting entries as they'll then typically show up in red. As Executor mentions, switching context is really easy once you've got the FormID open if you'd like to do that, but it isn't necessary to complete the edits as Neovalen has identified them for you already.

Alt Start / SoS patch and some general feedback: The change to "Cell">"Block 1">"Sub-Block 4" > "00016789" happens while you're still using the Alternate Start .esp as your context (as you are for the rest of the list), but if you try hunting the tree for that node starting from Alt Start, you won't find it, because that conflict is with RRR. Â So for that one change, to fit in with the style of the rest of the guide, you need to say, "Expand "Cell">"Block 1">"Sub-Block 4" under RealisticRoomRental.esp and select the "00016789" node." Â Maybe make it the last change so you don't have to switch context again! An alternative suggestion which may make life easier for anyone following the guide and possibly for you in writing it: when you're hunting down conflicts in the first place, obviously you will use the tree structure of the file to help locate them. But once you know the FormID of the node itself (e.g. in the example above, "00016789") you can just type that number into the top left field in TES5Edit (the FormID field) and it will take you right there. Â In this example, with the correct files loaded, you'd just type 16789 into that field and press enter. Voila, no need to mess around with pecking through the tree to find it, and no need for you to maintain that particular type of instruction (or any worry about which .esp's context you are in, as above) any more. Â Just a thought.

A guide like this for FNV would make me very happy indeed.

[accidental double post, sorry]