This looks like a great project! Very cool. :tops:
Thanks dev_akm; that's kind of you to say (not that I personally contributed
that much to FOIP).
so i finally got into "the mall" (washington memorial area)i had to swap the weaponmodkit.esp and the weaponmodkit - fook + fwe.esp which is in contrast to the recemended load order. now i cant get into the lincoln monument. i tried swapping the load order back it's recomended settings but as soon as the door becomes selectable i get CTD please help.
i did and that didn't change anything. But, i did start working but i have know idea why. i want into the game and waited alittle bit then tried going in and it worked. not sure what happened. before that i had tried systematicly disabling each mod and combanation of mods and rearranging load orders but none of that did anything. i still dont know what happened. if i had to guess i'd say somthing was in the area that the game couldn't render correctly but once it moved from the area everything worked fine. when i say something i mean like a creature or item on a creature allowing it mobilaty. damn i wish i'd thought making a save so i could further trouble but right now i just want to finish the game. right now i'm finding that weapon mod kit doesn't seem to be working but i can live without that till i start a new game.
The load order given for FOIP-related plugins is what is required for the affected mods (and the compatibility patches) to work as intended together. I can only speak directly for Weapon Mod Kits and the WMK-FOOK compatibility patch as that is all I made myself, but the FOIP compatibility patches were
made to be used in the load order described on the FOIP pages: if someone (and this isn't directed exclusively at you, freakydoo) is getting CTDs, it is unlikely to be caused by the load order of FOIP-related plugins (as described here). That said, it's always possible to have different mods disagree with one another in some unexpected way (though it's less likely to be an issue between FOIP-related mods, for obvious reasons).
Mesh files with problems can cause graphical anomalies for some (apparently) and CTDs for others (I've experienced this problem before myself). This can make the CTD-culprit harder to find if the problem mesh file is from a replacer rather than part of a plugin...
Anyway, on a specific note, if you change around the load order of WMK and WMK-FOOK-FWE as you described, then the WMK-FOOK-FWE patch will no longer work as intended. I don't know if that would cause the problem you're getting with WMK based on the info you've given. How exactly is it not working for you?