Jump to content

ebaleytherogue

Members
  • Posts

    6
  • Joined

  • Last visited

Nexus Mods Profile

About ebaleytherogue

ebaleytherogue's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Thanks, all. Good stuff. I decided to address it via brute force. I uninstalled and reinstalled Vortex, and I'm starting with one of my Fallout 4 deployments to fix first. The mods are recognized, without their meta data, meaning they were all listed by name, with an ID number, but without the Version column populated, nor author, category, etc. That all makes sense. Example: So I ended up reinstalling each mod, from Nexus, allowing them to over-write the existing version. I could have simply dragged them, from the downloads folder, into the 'Drop Files' area, but I really wanted a) the 'Downloaded Time' value to equate to a true download time, and b) ensure I am getting the proper version installed. The latter is due to previously having multiple versions of the same mod due to multiple versions of FO4 on the PC. I'm to the point where I just want to finish my SIM Settlements 2 run-through and not bother with London until that is done, and thus I don't need different flavors of the same mod simultaneously. In addition, redownloading the game allows me to have the 'Open on Nexus Mods' option again, and thus also allow for automatic checking for mod updates for each mod. I keep launching the game and letting my save tell me what mods are still needed, and I back out and add them in. The act of reinstalling each mod is somewhere between a PITA and cathartic, depending on my current mood. @vortexposer, I laughed when you mentioned creating draft collections, because this idea occurred to me, about a month ago, and I thought, 'Christmas is coming up. I'll do that in January.'. {sigh} Coulda shoulda woulda! Once I'm all reinstalled I am going to do that. Thanks for the reminder!
  2. Vortex 1.13.3 (12/10/2024) Electron 28.2.0 Node 18.18.2 Chrome 120.0.6099.227 I did a boo-boo the other night, at 3AM, and renamed a folder or something. Now my Vortex configuration is yacked. The active profile still works but my other profiles will not load. I get the "Stuck? Check the log" message, and checking the log, there are no problems reported but the final lines say "reverting the last profile", and there I stay. I've attached a recent log showing the profile reverting back to its current state near the bottom of the file. All my games work (FO4 in various flavors, RDR2, Fallout New Vegas, Witcher 3) when I launch them via their mod-friendly launching techniques. I've played around with Vortex, manually changing the mod staging folder value, etc., but that has done no good to restore Vortex functionality. Since all the games' \data folders are fine, and their mods load just fine, I'd like to simply uninstall Vortex, reinstall it, and have it detect both the games themselves and all the mods within the data folders. I think this might be unlikely, since the already-installed mods' metadata might then be lost. I am aware of what the Mod Staging Folder and Downloads Folder each does, and how they relate to deployed mods. I am hoping there is a way for me to manually edit each profile to a) get Vortex to recognize all is well, and b) potentially repair/replace its folder management files. What would YOU do to get Vortex to recognize these games and their installed mods? Thanks for any advice! vortex.log.7z
  3. Thank you, lorg8472! I had the exact problem. Your post was the ONLY source on the webs that provided a solution for me. Once I read your post, I closed Steam, launched it with full admin authorities, and launched Creation Kit from within Steam. The base.zip downloaded and installed. After the several minutes that it took that to complete, CK then opened all its windows just fine. I appreciate you having taken the time to post your resolution, as it helped get me through to start modding after several days of my iRobot forehead bumping the wall.
  4. Update: I downloaded the two older depots listed elsewhere in this thread. I copied the downloaded depots to the Fallout 4 folder, replacing existing items. My folder is D:\SteamLibrary\steamapps\common\Fallout 4\ I ran CreationKit.exe from the FO4 folder. Creation Kit launched this time. I was able to grant it its admin rights, as the initial prompt asked. However, after this the 'Creation Kit' splash graphic remained ad infinitum. I let it go for two hours, and nothing happened. I started over, let it go for another hour, and nothing happened. In between all the following steps I force-closed the CreationKit: I renamed the .ini files, hoping new ones would generate, and tried again. The CreationKitPrefs.ini regenerated, but not the CreationKit.ini, and but the splash screen remained. I restored CreationKit.ini, kept the newly created prefs file, and again, same issue; the spash screen remained. I looked at the "xSE PluginPreloader.log", but I don't know enough to understand much of it, although the Framework init error seems like perhaps it could be in play...the fault...or not related...dunno. What do all y'all think? xSE PluginPreloader.log: [2024-12-05 20:36:55:336] Log opened [2024-12-05 20:36:55:464] Initializing framework [2024-12-05 20:36:55:492] <Framework> Module "kxf::NativeAPI::Private::InitializationModule" initialization failed [2024-12-05 20:36:55:530] Initializing framework: failed I have attached the complete log file, in a 7z archive, in case someone might be kind enough to take a look at it to assist me in getting my Creation Kit up and running. I know I am close...but I need someone to assist me in sticking the landing. Thanks! xSE PluginPreloader.7z
  5. Thank you for posting the initial question, and thanks to all those who contributed to the answer. I am in the same situation. Before I download the two, older depots, so I can start modding the non-updated FO4, I am curious how I should prevent The Creation Kit from auto-updating. Should I just add the kit's exe to my firewall blocking rules? Is there some other technique? I mean, I realize how to suppress updates, via Steam...until I accidentally LAUNCH IT FROM STEAM, but that's just an accident waiting to happen.
  6. I went to update Fallout London from v1.01 to v1.02 and noticed there was nothing readily available about how to do it specifically for my configuration, so I wrote a blog entry about it. Fallout 4 London Configuration with Update from v1.01 to v1.02 My configuration: Base Game: Fallout 4 "Upgraded" originally installed from Steam, then downgraded from Steam upon London's initial release Mod Manager: Vortex Enjoy!
×
×
  • Create New...