Mekii Posted August 4, 2009 Share Posted August 4, 2009 Hello! I have a question The last FOSE version is compatible with 1.6, If I install the 1.7 patch FOSE and all mods that use FOSE will not work?. I have not installed yet the 1.7 pacth and Mothership Zeta because I am scare that many of the mods I have installed do not work Thanks!! I've heard that it screws FOSE, but I've also heard it doesn't. So I'm in same boat as you on that point. Link to comment Share on other sites More sharing options...
Luthais1337 Posted August 4, 2009 Share Posted August 4, 2009 with the new fose beta version it works perfect. Link to comment Share on other sites More sharing options...
Monolithic0117 Posted August 4, 2009 Share Posted August 4, 2009 with the new fose beta version it works perfect. Indeed. FOSE Beta 1.9 added support for patch 1.7. Link to comment Share on other sites More sharing options...
M4ttlock Posted August 5, 2009 Share Posted August 5, 2009 Alll DLC's + 1.7patch + FOSE1.9 + FO3edit/Masterupdate + FOMM + s***ton of mods = epic winrar ^_______^ Link to comment Share on other sites More sharing options...
xaechireon Posted August 5, 2009 Share Posted August 5, 2009 Since this is the last DLC they're making, this is also probably the last patch they're releasing, which also means this is the last third-party compatibility issue we will ever worry about. Whoopees. Link to comment Share on other sites More sharing options...
Chemix Posted August 6, 2009 Share Posted August 6, 2009 I've heard many times to place the Pitt before Operation Anchorage, but beyond that, and using FO3EDIT Master Update, 1.7 is fine. Load Order should look something like Fallout 3.esm(if you have it)> Destruction mod whatever.esm (only one is an ESM file)The Pitt.esmOperation Anchorage.esmBroken Steel.esmPoint Lookout.esmZeta.esm at the beginning, just generally keep all files labeled .esm (not .esp flagged as ESM) at the beginning. Oh and 1.6 didn't fix the .esp bug or the persistence requirement, you still need FO3Edit to run things proper. Link to comment Share on other sites More sharing options...
evilneko Posted August 6, 2009 Share Posted August 6, 2009 FOMM loads ESM before ESP automatically, no matter their position in the list. ;) Link to comment Share on other sites More sharing options...
M4ttlock Posted August 6, 2009 Share Posted August 6, 2009 From my testing i load the DLC's in this fashion: Fallout3.esmBroken steel.esmOperation Anchorage.esmThe Pitt.esmPoint Lookout.esmZeta.esm i've had no issues so far. basically im loading them in the order they were released sans BS as it is more related to the core game ^_^ Link to comment Share on other sites More sharing options...
Chemix Posted August 7, 2009 Share Posted August 7, 2009 whatever works for ya, I just stuck them the way I did to avoid conflicts; my game still crashes every couple of hours of play, and I can expect that from piling over a hundred mods onto some outdated beta .net framework from 2005. I've some times run into issues, like putting Fallout 3 last (weird mistake) and crashing the game on start up, so I'd say, put your ESMs in some kind of order. Link to comment Share on other sites More sharing options...
Recommended Posts