random133771

Oh ok that makes sense. Thanks!

Using Mod Oganizer 2.0.7 beta 3 for Fallout 4 1.6.9 (with F4SE): I've been trying to implement various ini edits suggested by mods as ini tweaks added to each mod package but they don't seem to be taking effect. I tested by adding the changes to Fallout4Custom.ini, seeing that the changes worked then commenting the changes out and activating the ini tweak in the mod package to find that the changes were not working. The following is a test edit [Display] fDefaultWorldFOV=40 fDefault1stPersonFOV= 150 which I saved as an ini tweak in a empty mod package and activated from the highest priority. I also tried it without F4SE. I'm not sure what I'm doing wrong... is there a global INI tweaks activation setting that I missed?

@GrantSP Awesome, that's good to know! Thanks for the response!

Hi, From what I've read in this thread it seems as though we can expect the 64bit version of MO 2 to support Bethesda's 32bit games once the program is stable. Given this, I was wondering if it's likely that we will be able to update (or export) our original setups in MO1 to MO2 (specifically keeping the package order in tact, but hopefully keeping other settings too). Could we expect the same for upgrading the beta version to the stable version while modding FO4? I ask because most of the older games were modded through Wrye Bash but I'd much rather use MO this time round and I don't want to have to set up my mods all over again with the release of the stable version. Thanks!