Also, it doesn't cause any problems adding FOSE after already adding mods. It's only there for anyone, with programming skills, who's interested in tinkering with the utility. A good utility to use is BOSS for Fallout, which will automatically sort many of your mods for you.Īs for the source folder of FOSE, it's not necessary to use that. Are you using something like FOMM in order to sort your mods or are you just dumping them in the Data folder and using the game's activator to select them? Load order is important in this game, and having mods load up in the wrong order can cause problems. In a crash like you're describing, the usual culprit is a mod that relies on some other mod that doesn't exist in your load order, or one that is loading afterwards. The problem is no doubt being caused by a mod that is now being activated after FOSE starts up. Louise fortin Posts: 3327 Joined: Wed 4:51 amįOSE won't cause a game crash when it's used. The mods I'm running are those under the F03 Wanderer Edition and the Unified HUD. Then I cut the "src" folder from the Fose download folder, and placed it in the Fallout directory. dll files and the Fose_loader from the folder and placed them in the Fallout Directory. Originally, the Fose folder was in the directory, so I cut all the.
When I installed FOSE, I extracted it to my Fallout 3 directory in Program Files (x86). However, while Fallout startup went swimmingly prior to FOSE (Fose-requiring mods and all), now start-up results in a black screen and a crash, and this is when using FOSE loader or Fallout 3 launcher. I then saw a post that said that installing mods prior to FOSE causes problems, so I went back and deactivated all the mods, finished installing FOSE, and re-activated/re-installed the mods.
As I began modding (using the Nexus Modder) I saw that a number of mods required FOSE, so I went and downloaded that while the Nexus Modder was working. Hiya! Getting back into Fallout 3 again, now that I have it for PC, and I wanted to mod it.
0 kommentar(er)
