Jump to content

Can you please explain...


Triaxx2

Recommended Posts

To your software. That FalloutNV.esm should be the FIRST FILE in the load order. And should be checked, always. So that when I try and make a merged patch, I do not then have to open Fallout Mod Manager, reorder the plugins manually, and then enable the base game masterfile. Then make my patch, then enable it.

 

When your software breaks other software, something is wrong. Thank you for reading this.

Link to comment
Share on other sites

Wow, after reading your posts in other threads, it's become really apparent that you really have no idea what you're doing.
SERIOUSLY.

Have you tried clicking on the LOAD ORDER or MOD INDEX columns to get a properly sorted load order?

Why are you using FOMM while using Vortex?
I'm assuming you're talking about FALLOUT MOD MANAGER?
If so, which one, for which Fallout?
All you're doing is undoing what you changed in Vortex with FOMM, and undoing what you did in FOMM with Vortex.

Also, please tell me how you can make a Merged patch with FOMM?
You can make a merged patch with FO4Edit, FO3Edit, but not with FOMM, and if you can't tell the difference between the two, maybe you better watch some tutorials.

If you're using FO4Edit, or FO3Edit in conjunction with Vortex, then what you need to do is click on your PLUGINS tab in Vortex, and click on the LOAD ORDER column to see your load order properly sorted (Just like with WryeBash)
Then you need to click SORT NOW on the plugins tab of Vortex

Now, start FO4edit, or FO3Edit (nobody knows WHICH game you're trying to mod) (I'm REALLY hoping you meant FO4Edit/FO3Edit, and not Fallout Mod Manager) and your load order should show up correctly in FO3/FO4edit.

I seriously suggest you watch some youtube tutorials, because your posts show that you're not doing things correctly and blaming the software rather than "User Error"

The fact you say you're Reordering the plugins manually with FOMM, then going back to Vortex, means that you're fighting YOURSELF

Link to comment
Share on other sites

I am using FOMM in order to move Fallout NEW VEGAS MASTER FILE to the first position in the load order. Because Vortex organizes it to load TWELFTH in the list, and sets it to disabled. Which means when I open FALLOUT NEW VEGAS EDIT, it fails to launch because the load order is WRONG and cannot load the master before the other mods, because all the mods require FALLOUTNV.ESM as a master. So in order to make a merged patch without NEW VEGAS EDIT crashing on me, I have to manually order the load order.

 

I have set load order using Vortex in built tools, which I do like, other than there being no option to say: Ignore this conflict. Because Fallout New Vegas requires a vastly more intelligent piece of software to fix them because it's a UI mod.

 

I am not fighting myself. I am fighting the software which is not behaving allowing me to do what I need it to, forcing me to use another piece of software to complete the job.

Link to comment
Share on other sites

Have you tried 0.15.3 (on the testing channel)?

It should write the main esm to the plugins.txt which - for the record - is not technically necessary for compatibility with the game, it's just other third party tools (like xedit) that expect it.

Link to comment
Share on other sites

They still don't line up exactly and I'm not sure why. Hmm... Our mod indexes are different, but I'm not sure why it would make a difference.

 

https://imgur.com/a/lB0CblO

 

It's functioning now properly, but the mod index is incorrect. And now it's back to normal...

 

Ah. So it seems opening FNVEdit moves the Mod Index of FalloutNV.esm to 12. Resorting the order moves it back to 00. But only if Vortex is not running. If it's running it holds the correct index. Occurs with the latest version of FEdit (3.2.1)

Link to comment
Share on other sites

They still don't line up exactly and I'm not sure why. Hmm... Our mod indexes are different, but I'm not sure why it would make a difference.

 

https://imgur.com/a/lB0CblO

 

It's functioning now properly, but the mod index is incorrect. And now it's back to normal...

 

Ah. So it seems opening FNVEdit moves the Mod Index of FalloutNV.esm to 12. Resorting the order moves it back to 00. But only if Vortex is not running. If it's running it holds the correct index. Occurs with the latest version of FEdit (3.2.1)

 

 

That's what I meant by "fighting yourself"

 

I had that happen with WryeBash and Vortex, I had locked the load order with WryeBash, and closed it, then I opened Vortex, then opened WryeBash again and it caused the two to fight over the load order, Until I UNLOCKED the load order with WryeBash.

Now I can leave them both open (Like I used to do with NMM and Wryebash) and they get along.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...