Jump to content

blove

Premium Member
  • Posts

    1296
  • Joined

  • Last visited

Nexus Mods Profile

About blove

Profile Fields

  • Country
    None

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

blove's Achievements

Mentor

Mentor (12/14)

  • First Post
  • Collaborator
  • Posting Machine
  • Conversation Starter
  • Week One Done

Recent Badges

0

Reputation

  1. Precise Aim might work for your sensitivity request. I have never used it with iron sights, though.
  2. I cleared my FO3 install, downloaded MO2, set it up with NXM, downloaded both archives, installed them, sorted the plugins, and ran the game with FOOK2 active. Delete and redownload or maybe go to MO2 File>Install Mod>yourfile and see if that works. MO2 was an unexpectedly pleasant experience. The mod does not seem to be packaged incorrectly. Does Vortex require mods to be repackaged differently? The issue with old FOMM and 32bit NMM was that they could not extract the 2GB+ FOOK2 Main BSA. 64bit NMM (and FOMM Fork?) did not have the same problem. EDIT: Uninstalled MO2, downloaded Vortex, set it up with NXM, downloaded both archives, and installed them. Found an issue where Vortex treats both archives as the same version of the same main file. Only one can win unless you make one archive a different instance. Any mod with multiple main files (presumably with the same version) will have the issue since updating is done by version. Enabled the plugins, sorted the plugins, and tried to run the game. Found another issue where Vortex was loading fose_loader.exe when I had already used the anniversary patcher. Have to make fallout3.exe the primary or have fallout script extender the primary and change the target to fallout3.exe. Ran the game with FOOK2 active.
  3. Merged patch last. The weapons are probably not in the supermutantweaponslist or the supermutants were not given the correct ammo in the leveled lists for the weapons.
  4. Like a tiny black hole is sucking them all together? Double check that you do not have any crazy position values, especially Z.
  5. GECK does not like to save a plugin as a master to a plugin. You can false flag the ESP as an ESM with FO3Edit.
  6. I tried a perk heavy run once. The problem I ran in to is that it takes a level up to trigger the perk selection screen in Fallout 3. So those mods will add experience to advance your level then remove it once the perk is selected. If you have any mod that relies on player level to trigger something, such as the Lawbringer quest, you may have problems if the conditions for that something will not handle the level reverting.
  7. A troll. How droll. I really loved your postings about how great LOOT is and how everyone should be using it. But from where I sit, it looks like you should be devoting all of your considerable posting time to updating that questionable LOOT masterlist.
  8. Downloaded and read some of this thread before installing, thankfully. No tried and true drag and drop quick and simple what you see is what you get manual load ordering? Wow. Gotta love this place.
  9. Are you using a custom race? Have you tried Custom Race Endings Broken Steel OverRide by Laffie?
  10. GECK is not saving those plugins as masters to your plugin. Either false flag those would be master plugins as ESMs and make your changes in GECK or...using FNVEdit copy that existing container you want to use out as an override to a new file and then continue using FNVEdit to populate that container in its new file.
  11. You might try moving all of your old saves out of your Saves folder (something like C:\Users\<username>\Documents\My Games\Fallout 3\Saves) and starting a new game to see if the issue persists.
×
×
  • Create New...