Fallout 4 Support

[rmm200]

Fallout 4 launches in 3 days.

Even though there are no mods available - I would like to get started the right way - which means running under Mod Manager.

Any tips for running this new Fallout under the latest Mod Manager - or are the paths and executables hard coded?

 

Any schedule for official support?

---

 

 

Lets keep this topic specific to FO4. General MO2 discussion can be found here: https://forum.step-project.com/topic/9377-mod-organizer-2-discussion-and-feedback/

[EssArrBee]

No one has the game yet. You gotta wait for the mod managers to be updated for the game.

[GSDFan]

Also the game requires a 64 bit OS and at the moment MO can't launch 64 bit executables.

[Guest]

So you could say MO currently has no MO for Fallout 4?

 

 

  Reveal hidden contents

Is that terrible enough for you?!

 

[Neovalen]

  On 11/7/2015 at 4:28 AM, SparrowPrince said:

So you could say MO currently has no MO for Fallout 4?

 

 

  Reveal hidden contents

Is that terrible enough for you?!

 

There is no MOFO4 you! (I win on the terrible front)

 

At least until Tannin upgrades MO to 64-bit, which I think he has in his "long term" plans.

[DirtyWeasel]

I'll just chime in here, but considering the horsepower of the above posters I'm sure I'm out of my depth. 

 

I would love to be able to use MO straight from the start of FO4, but given the current limitations mentioned above, it is unlikely.  Now... does Tannin have some big announcement upcoming?

My heart would love to say, "YES, PLEASE!" But, my brain tells me that just like the guys at Silverlock.org, he has to wait to see the game files/structure fully before work can begin.

 

So for the time being, we'll have to "make do" with NMM.

Edited November 7, 2015 by DirtyWeasel

[TechAngel85]

Tannin, as I understand it, has been working on making MO 64-bit compatible. There is a lot of work he can do to simply convert the program to 64-bit architecture and then when the game releases and he has it, he can do the game-specific work to add the game to MO. How much of the pre-work he's done? Who knows!? I've been waiting for quite a while just for the next update that will fix an issue in the FOMOD installer. Seems like things are slow, but who knows. He's hasn't released much about his plans in a good while.

[rmm200]

The ability to launch a 64 bit executable looks like the first hurdle, and the one I would expect to come first.

 

If anyone needs testers / reviewers, etc. - keep us in mind.

There is an awful lot of programming experience floating around out here.

[EssArrBee]

  On 11/7/2015 at 9:09 PM, rmm200 said:

The ability to launch a 64 bit executable looks like the first hurdle, and the one I would expect to come first.

 

If anyone needs testers / reviewers, etc. - keep us in mind.

There is an awful lot of programming experience floating around out here.

MO is open source so you can check it out on github. https://github.com/TanninOne

[rmm200]

  On 11/9/2015 at 2:20 AM, EssArrBee said:

MO is open source so you can check it out on github. https://github.com/TanninOne

Well I can download it and look at it.

For the life of me, I can't even see why ModOrganizer would have to change to launch a 64 bit executable, or be a 64 bit application itself.

It is not like it is being linked with the target. ShellExec (for launching) does not care about the architecture.

[GrantSP]

  On 11/9/2015 at 3:16 AM, rmm200 said:

Well I can download it and look at it.

For the life of me, I can't even see why ModOrganizer would have to change to launch a 64 bit executable, or be a 64 bit application itself.

It is not like it is being linked with the target. ShellExec (for launching) does not care about the architecture.

It's no so much the "launching" being the issue, more of the "hooking" of the executables to see the VFS. They have to be tricked in to seeing paths and files in different locations than what they really are, that's the tricky bit.

[Nozzer66]

There's no way in the world I'd be using NMM for anything. Except to point and snicker at, anyway...

 

I'll stay Vanilla till Tannin gets this up. :D

 

And yes this is the real Nozzer66 after a self-enforced hiatus.

Edited November 9, 2015 by Nozzer66

[rmm200]

  On 11/9/2015 at 3:19 AM, GrantSP said:

It's no so much the "launching" being the issue, more of the "hooking" of the executables to see the VFS. They have to be tricked in to seeing paths and files in different locations than what they really are, that's the tricky bit.

Thanks - that helps. Makes a lot more sense now. Makes it a lot less likely that I could do anything useful too.

[DoubleYou]

Maybe Fallout 4 will be made in such a way that you don't need a mod manager. Just drop the files in a mods folder and forget about it.

 

Except I doubt Bethesda would be that kind.

[Guest]

  On 11/7/2015 at 4:43 AM, Neovalen said:

There is no MOFO4 you! (I win on the terrible front)

 

At least until Tannin upgrades MO to 64-bit, which I think he has in his "long term" plans.

That's damn good!

  Reveal hidden contents

Don't out-stage me again, it's all I have left to make people cringe! You feel me punk?!

 

 

  On 11/9/2015 at 7:53 AM, DoubleYou said:

Maybe Fallout 4 will be made in such a way that you don't need a mod manager. Just drop the files in a mods folder and forget about it.

 

Except I doubt Bethesda would be that kind.

I can't tell if this is great sarcasm or great stupidity. Either way it's a 10 from me!

Edited November 9, 2015 by Guest

[GrantSP]

This question was posed on the GitHub issues page and @Tannin has provided his take on it.