Thanks for this, but I'm curious - How is this different from the patches provided on the original mod's page itself? I's under Optional files, link here.
This patch does not have High Poly NPC Overhaul 2.0 as a master. It only has the resources and High Poly Head as masters. You may want to add that in your next update.
Hey. Thanks for the update. Was wondering if the patch will work for CRF v 3.1.9 (the latest one before AE update). I haven't upgraded to AE and since CRF requires USSEP as master which requires AE, hence the question.
I am wondering the same thing. Many of us have not updated to SSE 1.6xx yet. I am still on SSE 1.5.xx and have CRF v3.1.9, too. Fortunately, its getting easier to know what goes with what. Obviously, things will stabilize eventually.
Thanks for maintaining your patch!
EDIT: This suggests that if one has not updated CRF to 3.1.11 yet, then one should stay on the older version of this patch for now. Is that correct?
i still have the latest ussep (before AE which is master) and CRF 3.1.11 works with that ussep. in my case i lost my CRF 3.1.9 version and i made the patch with the latest version.
idk what to do anymore. If I install either this patch or the individual patches from the original mod, Hulda finally has a high poly head but NPCs like Saadia get a neck seam no matter what load order I do. Removing this patch removes the neck seam but some NPCs have no high poly head. Anyone else have a similar problem?
I'm assuming this combined patch replaces the 3 patches provided by the mod author (AIO, CRF, AIO + CRF) without adding, removing or changing anything substantive? Thanks for your efforts.
Give Feedback
21 comments
HIGH POLY NPC OVERHAUL 2.0 PATCH FOR IMPROVED BANDITS at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)
This patch does not have High Poly NPC Overhaul 2.0 as a master. It only has the resources and High Poly Head as masters. You may want to add that in your next update.
Thanks for maintaining your patch!
EDIT: This suggests that if one has not updated CRF to 3.1.11 yet, then one should stay on the older version of this patch for now. Is that correct?
in my case i lost my CRF 3.1.9 version and i made the patch with the latest version.