FOOK2 - crash upon entering Moriarty's Saloon

[DarkStar88]

Title about says it all. I've pretty well isolated the problem to Fook2 by deactivating all other mods and DLC packs in FOMM.

 

What happens is every time I try to enter through either door of Moriarty's Saloon, I get a crash. For some reason it doesn't happen if I use the cheat that lets you fly/walk anywhere...could this indicate some kind of bad ground mesh? My FO3 modding is very novice.

 

More information gladly made available on request. PLEASE help me solve this...it's the only problem I have with Fook2 and it's very annoying as you almost have to enter to even continue the main storyline. I can get around that by catching the man on break just outside the Saloon, but it's still frustrating.

[HavocPL]

Maybe this is problem with corupted save?To fix this kill yourself in game and let the game load last save.

Seriously this helps sometimes.

[DarkStar88]

HavocPL, on 12 Feb 2013 - 11:37, said:

Maybe this is problem with corupted save?To fix this kill yourself in game and let the game load last save.

Seriously this helps sometimes.

This happens even when starting a brand-new game, even if I do nothing after the tutorial but run straight for Megaton, talk to Sherrif whatsisface, and make a beeline for the saloon.

 

EDIT: I just confirmed this and recorded it in Fraps, start to crash. Only two things active in FOMM are Fallout3.esm and Fook2 - Main.esm

Edited February 12, 2013 by DarkStar88

[IAmWeaselegend]

Hey DarkStar88, I'm running Fook2 and don't have this issue. Did you apply the hotfixes for FOOK2? There's a little bit of confusion concerning FOOK2 1.2 and the hotfixes so I'll pass on the info I got from a comment made by freddy_farnsworth. If you do have them, disregard the next bit, but maybe it'll help someone else.

 

The data file is listed as having been uploaded in December 2011 and the hotfixes are listed as June 2011, but there's a catch. There were more than 2 downloads for 1.2 and apparently the person who was/is in charge of FOOK2 simply bundled them for convenience and then reupped them. So, as far as version goes, the data files are from March 2011 and the hotfixes, from june 2011, are still necessary. I have no idea what the hotfixes fix, but you need them.

 

Note that if you use BOSS for load order it will erroneously flag the hotfixes, saying you need to upgrade to FOOK2 1.1. Even if the hotfixes were deprecated, this error wouldn't make sense to me as the 1.2 files listed as old versions were uploaded before the hotfixes. Additionally, the current main file's upload date is before that of the hotfixes.

 

Other than the above, my modding/troubleshooting knowledge is extremely limited and I can't really be of any help. Keeping the previous sentence in mind, you say F3.esm and FOOK2.esm are the only things active in FOMM, but shouldn't you also have FOOK2.esp and calibr active?

 

It would also help to post your load order, because even if you fix this problem, there may be others you're not aware of, or that haven't surfaced yet. I probably won't be able to help, but someone else might.

 

edit:baked spelling.

Edited February 13, 2013 by IAmWeaselegend

[DarkStar88]

IAmWeaselegend - what I was trying to do was track down a specific problem to a single mod. When I run FO3 with Fook2 enabled - even only the bare minimum data file - it crashes upon entering the saloon. When I run Fo3 without it, no crashy. That's about as specific as I can get due to my amateur modding status, unless there is SOME kind of crashlogger to figure out WTF is exactly choking the system. But it plain CTD's without even as much as a generic Windows error "sorry but this has to close" box.

Reapplied the sound/mesh fixes in case I'd forgotten them, though upon looking neither of them have anything to do with Moriarty's Saloon. Turned on the hotfix esps. No dice.

 

Current load order:

Fallout3.esm
CALIBR.esm
FOOK2 - Main.ESM
FOOK2 - [DIK] DLC Improvement Kit.ESM
FOOK2 - Main.esp
FOOK2 - [DIK] DLC Improvement Kit.esp
FOOK2 - Main [Hotfix].esp
FOOK2 - DIK [Hotfix].esp

Total active plugins: 8
Total plugins: 81

[IAmWeaselegend]

First, I knew you were looking for a specific fix for a specific issue, I only mentioned the hotfixes because more than a few people have overlooked them. As I didn't run without them, I didn't know if your issue could be caused by not having them, that's all. I didn't intend to come across as patronizing, if that's how it seemed.

 

Anyway, there are only a few other things I can suggest. Create a merged patch using FO3edit and try to run it that way. I've only ever run my FOOK2 setup with one, so if you haven't, you could try making one.

 

I noticed you have 81 total plugins. Again, my modding knowledge is very limited, but there might be a potential incompatibility between F2 and another installed mod (I know that the others aren't active).

 

When you were installing mods, at what point did you install F2? Could something have overwritten any of FOOK's files? I know you said you reapplied the folders from the hotfix folder, but did you try reapplying the folders from the base F2 data folder first?

 

The only other thing I can think of is the ini tweaks to use threaded ai and limit threads. Again, you may have already done this and it may not have any bearing in this problem. I'm just throwing out the little information I have.

 

When all is said and done, the only person I know of who could maybe help you is freddy_farnsworth. I've seen him help more than a few people in the comments thread for FOOK2, so you could try sending him a pm.

 

Wish I could have been of help, best of luck finding a fix.

Edited February 16, 2013 by IAmWeaselegend

[M48A5]

Darkstar88,

Uninstall and delete the Fook 2 [DIK] DLC Improvement Kit.esm and .esp and the [DIK] Hotfix. You do not have any of the DLCs so there is nothing to improve or hotfix. This should correct the problem.

[IAmWeaselegend]

@ M48A5 - He says in the first post that he has the dlc (he deactivated it while troubleshooting).

 

What I don't know is whether or not the FOOK2 dlc plugins require all the dlcs, or just improve whatever dlc you have. I believe it requires them, but I don't know. I also don't know whether Darkstar has them all or not.

 

@ Darkstar88 - When you were troubleshooting this and minimized your load order to what you posted in post #5, did you forget to reactivate the dlc? Or was it active in your load order but you just didn't post it?

[DarkStar88]

@ Darkstar88 - When you were troubleshooting this and minimized your load order to what you posted in post #5, did you forget to reactivate the dlc?

 

I left the DLC's inactive for troubleshooting purposes, but then forgot to de-act the Fook2 files for the DLC's.

 

That said - problem has been definitely solved. I highly suspect that the main data files themselves had gotten borked for God-knows-what-reason.

 

If anyone else has the problem I had, here are the steps I took to fix it.

 

1. Re-downloaded the Main and Data files from the Nexus site, plus the hotfixes, which at the time of this post is at http://fallout3.nexusmods.com/mods/4448

2. Replaced all .esm and .esp files currently in my Fallout 3 "Data" folder. At this stage I noticed a size difference in the .esm that I had and the one that I was copying over it.

 

3. Copy-pasted data folders first from the main mod, then from the hotfix, letting them overwrite whatever each other.

 

4. (OPTIONAL) Re-copied the textures from NMC's texture mod.

 

5. Test-ran the game with nothing but the main FO3 esm and the Fook 2 files, not including ones dealing with DLC's. At this point I could enter the Saloon without issues. Re-activated mods (yes all 81 of them!), checked load order and re-arranged a couple. All runs well.

 

I'm pretty sure the main Fook2 mod file got borked by something.

[IAmWeaselegend]

Good to see that you were able to fix it, and good on you for posting your solution for others who might have the same issue. Many people often just say something like "nevermind, fixed it", and when someone else comes along with the same/a similar situation, they have no idea what fixed it for you.