Jump to content

yonkiman

Citizen
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by yonkiman

  1. I'm using MO2 for the first time, and (as with MO1), every mod I download from Nexus has an incorrect (or if I'm lucky, missing) Category entry. There's some discussion about this here that resulted in a Managing Categories entry on the Mod Organizer Guide. However I've read it a few times and still haven't figured out how to map things properly, so I just manually change the category of each mod as I add them. So my (probably naive) question is: Why doesn't MO (1 or 2) automatically work with Nexus Categories? It seems like ~95% of the mods people use with MO come from Nexus, so why does every single MO user need to edit the mapping or manually change each mod's category after downloading. Not complaining - just genuinely curious.
  2. Thanks - I'll try Free Commander. Where is the best place to report MO2 bugs? Here? Never mind - found it on github.
  3. Ah...in the end it was obvious (as it usually is). When I started modding, falloutcustom.ini and custom.ini were empty. At some point something (probably bethINI) added the [fonts] yp both of them, and that was overwriting my changes to the usual INIs. Working now.
  4. Can't get the Darnified fonts to appear. I've installed Darnified v04, made the font changes to fallout.ini and falloutprefs.ini, reinstalled Danified, verified the fonts are in the Darnified filetree, but it's not showing up. Could easily be something besides MO2, but I never had any difficulty with MO1 so I thought I'd ask. While troubleshooting, I did realize I had a basic misunderstanding about exactly how MO (1 or 2) operates. I thought that when you launched something (a game, LOOT, FNVEdit, etc.) from within MO, the contents of the game directories (particularly Data) would change to show all the mods, ini files, etc. enabled in that MO profile. But if I start LOOT from within MO, nothing seems to have changed in my game directory when I look at it with Explorer. (I was trying to check to make sure the game was launching with the correct .ini files.) Is there a way for me to see the MO-populated directories the way LOOT sees the directories?
  5. That did the trick - thanks for the super-fast response.
  6. Used to use MO1, now starting a new New Vegas runthrough with v2.1.3. In MO1 I could select 2 (or more?) plugins in the Plugins window, right click, choose "Lock Load Order" and they would stay locked in that order (along with a visual confirmation - can't remember exactly what that looked like). MO2 has the same "Lock Load Order" option, but when I try to lock 2 files together I get no visual indication that the files are locked, and after I run LOOT it's clear that they were NOT locked together. Am I doing something wrong or is this just not implemented yet?
  7. 1. Thanks. Was also looking for a recommendation of what "best practices" would be - uninstall mod but keep original archive in downloads in case some of the merged mods get updated? 2. Thanks!
  8. Good lord what an awesome guide! Thanks!!! Two suggestions for the next rev: 1) For the merge fix examples like this one, it's not clear if it's OK to delete the original mods that have been merged (I think it is), so it would be great if you spelled that out along with a recommendation of what to do with the mods. 2) I had 100% success with this guide (I playtested as I went along to try to catch any problems early) until I got to Running FNVLODGen. I followed the instructions to the letter, but when I went to run the game, I got a huge blank pink screen of death. To get a playable installation back, first I undid all the FNVLODGen changes (that didn't help), then I flailed wildly, then I stumbled up someone saying a pink screen could have something to do with Archive Invalidation. I went into MO and turned Archive Invalidation off, launched the game, and it worked perfectly. I quit, turned Archive Invalidation back on in MO, and it ran perfectly well again, and has been working ever since. So you might want to mention Archive Invalidation as a potential fix if FNVLODGen goes south. I haven't had the guts to try it again (will backup my FNV and Mod Organizer directories before I do). Thanks again!
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.