Jump to content

cooperbh

Supporter
  • Posts

    6
  • Joined

  • Last visited

Nexus Mods Profile

About cooperbh

cooperbh's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

1

Reputation

  1. That is indeed the case for me, but I have no recollection of ever navigating to that settings tab, nor can I think of a single reason why I would have changed that particular setting from the default, especially after reading the info popup. Oh, well. The toothpaste is out of the tube at this point.
  2. With all due respect, I hardly consider this issue "solved." In all the years I have been updating Vortex, never once did the app freeze up for 20+ minutes after restarting. Had I known this was expected behavior, I obviously would have never force quit. This lack of communication regarding a quite invasive update is the root of all the chaos that has followed. How can a Vortex user ever again trust that an update notification won't lead to a ransacked load order and ruined game saves? And the problems continue, I might add. Upon exiting the 1.9 version I rolled back to, I got a notification stating (not asking) that the newer version would be installed. I allowed Windows to proceed in order to see if I might have better luck on the second go round. Oddly enough, upon restart the app was functional in only a few minutes after clicking the prompt to deploy. However, since that initial session, the app now hangs indefinitely at startup once again. Even after giving it well over an hour on two separate occasions, it never enters an operational state. So, now I must re-rollback to the previous version just to see my modlist and assess the damage, making sure to have Windows cancel the auto-update that occurs every time I exit the app. Or I suppose I can wait for the next update and hope it renders the app functional again. Either way, I surely won't be playing my modded Skyrim anytime soon.
  3. See my posts in the thread linked below. Seems our issues are related.
  4. So, it appears those redundant mod notifications are a side effect of a much larger problem. Basically, either updating to 1.10 or reinstalling 1.9.12 reverted all my conflict overrides to default. This means the multitude of mesh and texture combinations I have been carefully mixing and matching over the course of years have been totally wiped out, and all of those countless hours of work have been for nothing. Just thinking about having to start again from scratch and all the issues it may cause with my current load order is overwhelming. I think at this point beginning from a fresh install of the game would be safer and less time consuming. Hope others somehow get a chance to read this before unknowingly subjecting their highly cultivated load orders to an unannounced beta test.
  5. Thanks for pointing me in the right direction. Rolled back to 1.9.12 and everything works just fine again. Edit: I did have to reinstall and reconfigure conflict rules for about a dozen mesh/texture mods, as their files had disappeared and thus they were being reported as redundant. Guess things could have been worse on an 800 mod install. Looks like I will just have to decline all update prompts from here on out.
  6. After updating, Vortex freezes during boot up and remains completely unresponsive until force closed through Task Manager. Attempting to reopen results in an error message saying the app can't connect to the meta database due to the process already running. Restarting my PC clears the error message, but Vortex just locks up again on subsequent attempts to open and the cycle continues. In short, I can no longer access Vortex and play my game. Is there any way to roll back to 1.9.12 outside of this now completely broken app?
×
×
  • Create New...