Please report back your findings.Īs wolverine said already the only working way (that I am aware of) is simply creating a fake New Vegas directory placing inside the default_ini' date=' the new vegas.exe, the new vegas launcher.exe and a Data folder containing the new vegas.esm and then change the settings in FOMM to point at that directory. Install the mods with NMM, then use the NMM importer to import them into MO. I haven't tested the NMM importer of MO RC8 myself at this point but I'm pretty confident it is pretty stable know. After that it was tested again for 1.5 days and Tannin again used that feedback to make improvements. I know of someone who torture tested the importer for 2 days, Tannin used the feedback to improve the importer.
You install the mods and then copy the contents back to MO. This can indeed be cumbersome.Īt this point there should be a another solution. Solutions so far have been FOMM or NMM, you can set them up in such a way that they point to a fake Fallout New Vegas (FONV) install. In the current situation with MO when installing those kind of mods with the fomod installer plugin (both internal and externall) the installer plugin can't find those xml files. The fundamental concept of MO (Mod Organizer) is mod isolation. Mods like darnified UI, MCM, Unified Hud needs to see the XXX_menu.xml files installed by other mods to work properly.
