Jump to content


Photo

Cannot install FOMODs in FNV Mod Organizer 1.3.3


  • Please log in to reply
6 replies to this topic

#1 wario44

wario44

    Watcher

  • Citizen
  • 4 posts

Posted 27 March 2015 - 10:46 PM

I have no idea what changed but suddenly I cannot instal FOMODs in Mod Organizer.  It goes straight to the manual install as if it was a normal archive instead of having the .fomod extension.  I installed version 1.3.3 of MO over 1.2.18 in hopes it would be fixed but no luck.

 

System Specs

 

Load Order

 

Please help me :(


  • 0

#2 EssArrBee

EssArrBee

    Incompatibilism Manager

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 7,461 posts

Posted 27 March 2015 - 10:47 PM

What mod?


  • 0

#3 wario44

wario44

    Watcher

  • Citizen
  • 4 posts

Posted 27 March 2015 - 10:50 PM

Shiloh Desert Succubus Body Mesh Pack.

https://www.nexusmod...as/mods/38093/?


  • 0

#4 EssArrBee

EssArrBee

    Incompatibilism Manager

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 7,461 posts

Posted 27 March 2015 - 11:09 PM

Don't extract the .fomod from the archive. It should default to the external installer and work fine that way. Using the .fomod will throw it for a loop.


  • 0

#5 wario44

wario44

    Watcher

  • Citizen
  • 4 posts

Posted 28 March 2015 - 06:57 AM

nope that didn't work.  still opens as a normal mod.


  • 0

#6 EssArrBee

EssArrBee

    Incompatibilism Manager

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 7,461 posts

Posted 28 March 2015 - 01:56 PM

You needs to see if the external and internal installer are active. Go to the settings and look under the plugins tab.
  • 0

#7 GrantSP

GrantSP

    The antipodean

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPip
  • 4,302 posts

Posted 28 March 2015 - 06:12 PM

@wario44

If you are seeing that file open as a manual install then there is something amiss with your MO installation. No matter which setting you have for your plugins, internal or external fomod installer, that file always shows in my MO 1.3.3 install with its fomod scripted install.

 

Can I assume you updated to 1.3.3 over an existing 1.2.18?

If that is true you may need to do a bit of cleaning. There could be some remants of the previous install conflicting, though @Tannin did make the new installer clean out that stuff first.

 

At any rate, grab the latest MO full install archive, not the installer, and open it in your archive manager.

Open an explorer window with the MO installation.

Delete every folder and file that exists in the MO install AND in the MO archive. This is to ensure no leftovers from a previous install.

 

The files/folders that you should be removing are:

NCC
platforms
dlls
plugins
loot
stylesheets
tutorials
translations
license
nxmhandler.exe
helper.exe
hook.dll
ModOrganizer.exe
uibase.dll
msvcr120.dll
msvcp120.dll
python27.zip
python27.dll
 
Everything else is either a setting you have made or the downloads, mods, profiles folders with your files in them.
 
Copy all the contents of the MO Full install archive and the result will be a pristine 1.3.3 MO install with all your settings and mods intact.
 
Try that mod installation again and if still doesn't work could you post all the relevant details into a bug report in the Bug Genie.

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users