Jump to content


Photo

Mod Organizer 2 Discussion and Feedback


  • Please log in to reply
233 replies to this topic

#1 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 10:53 AM

Mod Organizer 2 is now in alpha, which is the 64-bit version of MO featuring support for Fallout 4. Testers are welcome and encouraged!

 

Download the Alpha here: https://github.com/T...anizer/releases

 

This is not a bug report topic! Please report bugs to the GitHub issue tracker.

Thought I'd start this thread for the discussion of MO2 instead of filling the Fallout Support topic with unrelated posts.



#2 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 11:03 AM

This is interesting: https://github.com/T...izer/issues/365

 

MO is no longer managing BSAs as it has in the past and does currently. What does this mean for BSA management and MO now? I was never on top of this topic before so I'm uncertain what this means exactly.



#3 DoubleYou

DoubleYou

    Wiki Stepper

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,466 posts

Posted 24 November 2015 - 11:12 AM

It essentially means we will have to go back to extracting mod archives.

#4 Kesta

Kesta

    Thane

  • Mod Authors
  • PipPipPipPipPipPip
  • 471 posts

Posted 24 November 2015 - 11:22 AM

It essentially means we will have to go back to extracting mod archives.

Bad news for modaholic with small HDD :/

 

Looking forward to Tannin's reply on this, I'd like to know if the feature have been removed for technical issue or by design.


  • 1

#5 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 11:47 AM

I take it this means that we will no longer be able to see conflicts within BSAs. That is a real bummer as that was one of the nicer features of MO. We might have to go back to managing STEP like we did with WB....extracting everything. ::(:



#6 Octopuss

Octopuss

    Swears by everything

  • Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1,625 posts

Posted 24 November 2015 - 12:05 PM

I'd like to see the reasoning behind this.


  • 1

#7 EssArrBee

EssArrBee

    Incompatibilism Manager

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 7,721 posts

Posted 24 November 2015 - 12:46 PM

STEP can just keep MO 1.3.11. What doesn't it do that we need?

FO4 doesn't even have BSAs to mess with. It's a new type of archive that may behave weirdly.

#8 Greg

Greg

    High King

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,437 posts

Posted 24 November 2015 - 12:53 PM

The lack of BSA management is a real setback, but I'm hoping this can eventually be resolved.

 

Has anyone been able to get the INI editor to work with Skyrim? When I open the INI Editor, I get a blank dialog so I have to edit the INIs with an external editor.

 

I also get "Object reference not set to an instance of an object" error when installing SkyUI 5.1, so i had to repackage it without the fomod folder.



#9 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 01:05 PM

If, rather when, we get into a "STEP: FO4 Guide", it would be nice to simply have support for one version of MO rather than doing multiple. That and the current version will likely end up in the grave over time as MO2 grows.

 

I've reported the INI Editor issue already.



#10 Neovalen

Neovalen

    Talos

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 5,643 posts

Posted 24 November 2015 - 01:10 PM

I've noted using this for Fallout 4 only thus far that the data tab doesn't appear to auto-refresh. I had to manually select refresh after activating all my mods. Might just be a visual issue though.


  • 0

#11 Tannin

Tannin

    Commander

  • Mod Authors
  • PipPipPipPip
  • 342 posts

Posted 24 November 2015 - 01:38 PM

The feature has been removed because it required a lot of complex game-specific and error-prone code inside the hooking lib and caused ton of confusion, bug reports and hatred from other modders.

It made the whole PMOP business necessary which way too many people didn't understand.

The bsa management was supposed to make things more intuitive by giving assets the "expected" order, but in practice it made everything more complicated.

With MO2 my primary focus is Fallout 4 where I don't want to repeat the same mistake and non-gamebryo games where it's unnecessary.

 

If you need this functionality for step then you should stick with MO1.


  • 0

#12 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 01:47 PM

Thanks for the information. It's not necessarily needed for STEP. It just made things easier. We're adaptable. I'll be monitoring progress and testing this as issues are fixed. Currently, I can't do much more testing for actual STEP until some things are fixed. Particularly, the FOMOD installer is messed up. I can easily work around that and other issues, but I'm attempting complete our Guide from the average user prospective. For now, I'm doing it with MO1.

 

Keep up the good work. I'm excited to see the new possibilities this version could bring.


I forgot to ask, does this mean that conflicts within archives will no longer show in the Conflicts tab?



#13 Tannin

Tannin

    Commander

  • Mod Authors
  • PipPipPipPip
  • 342 posts

Posted 24 November 2015 - 01:53 PM

Conflict display is still possible, I haven't implemented support for ba2 yet however.


  • 0

#14 Octopuss

Octopuss

    Swears by everything

  • Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1,625 posts

Posted 24 November 2015 - 01:54 PM

So just to make sure: with the new MO I will no longer be able to load BSAs in the same order as mods in the left panel?


  • 0

#15 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,861 posts

Posted 24 November 2015 - 02:10 PM

So just to make sure: with the new MO I will no longer be able to load BSAs in the same order as mods in the left panel?

Tannin can confirm, but I think that is correct. It's going back to more of WB style where BSA are loaded in the same order as their ESPs. I'm also assuming this means that we won't be able to disable "empty plugins" that their sole function is to extract the BSAs. Lots of nice functionality could be missing with this change, but it will align MO better with how they're meant to be managed. Arthmoor will be happy. Haha!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users