I'm having an issue with newer (not sure which version) Wrye Bash and Mod Organizer vs the ASIS Patch. When I start up Wrye Bash to rebuild the bashed patch, it disables automatically the ASIS Patch also in the process. Once the bashed patch is rebuilt the bashed patch is reactivated by Wrye bash, but the ASIS Patch is not... and when i go back to Mod Organizer and manually reactivates the ASIS Patch it doesn't work. Somehow regardless of what I do unless I just delete the ASIS Patch entirely and rebuild it from scratch it is automatically deactivated, even if I make sure that the tick is active and quit Mod Organizer, if I start up Skyrim it tells me I have missing files, and when I start up Mod Organizer again the ASIS patch is disabled. As of now I have found no means of reenabling the damn patch and making sure MO does not automagically deactivate it for no good reason except deleting and rebuilding it, but it seems being deactivated in Wrye Bash somehow bakes that into my load order. Note that there are no conflicts in the ASIS patch and no real reason for it to need a rebuild, and that this never happened when Wrye Bash did not deactivate ASIS patches on rebuilding patch.
Question
Sacremas
I'm having an issue with newer (not sure which version) Wrye Bash and Mod Organizer vs the ASIS Patch. When I start up Wrye Bash to rebuild the bashed patch, it disables automatically the ASIS Patch also in the process. Once the bashed patch is rebuilt the bashed patch is reactivated by Wrye bash, but the ASIS Patch is not... and when i go back to Mod Organizer and manually reactivates the ASIS Patch it doesn't work. Somehow regardless of what I do unless I just delete the ASIS Patch entirely and rebuild it from scratch it is automatically deactivated, even if I make sure that the tick is active and quit Mod Organizer, if I start up Skyrim it tells me I have missing files, and when I start up Mod Organizer again the ASIS patch is disabled. As of now I have found no means of reenabling the damn patch and making sure MO does not automagically deactivate it for no good reason except deleting and rebuilding it, but it seems being deactivated in Wrye Bash somehow bakes that into my load order. Note that there are no conflicts in the ASIS patch and no real reason for it to need a rebuild, and that this never happened when Wrye Bash did not deactivate ASIS patches on rebuilding patch.
(Crossposted on the Nexus Wrye Bash forum.)
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now