F4SE 0.7.2 and MCM 1.40 beta 2 not working with fallout version 1.10.984

[b1tbull]

Can someone confirm this is indeed not working so I know there is nothing I can do about it.
Recently installed Sim Settlements 2 with HUD Framework and Workshop Framework.
My previous mods were Snappy House, Mobile Mechanic and Scrap Everything.
So just 6 mods loaded but MCM ( Mod Configuration Menu ) and F4SE ( Fallout 4 Script Extender ) do not appear in the Fallout mod list after both are installed, either with vortex or manually.
Of course I am starting the game with F4seloader.exe and the game runs fine.
The getf4seversion command gives the correct running version and required files are present in Fallout 4 data folder.
In short : everything works ok just like MCM or F4SE were never installed.

Advise welcome.

[Charon]

F4SE will never appear in your mod list since it is not a "mod" but the script extender. Same goes for MCM (also no esp / esl file). MCM 1.39 will not run with 1.10.984 which is clearly stated on the mod page. You will need 1.40 Beta 2.

[sdack]

F4SE 0.7.2 is working. Make sure to update the Address Library, too. The version for it is now called AIO, because it includes all supported versions in one.

However, I have not tested MCM yet, but there is also a new version up 1.40 BETA 2. See the files section and make sure to get the latest version. The link on the description page might still be pointed to old versions:

- F4SE with Address Library (updated!)
https://www.nexusmods.com/fallout4/mods/42147
https://www.nexusmods.com/fallout4/mods/47327

- MCM (updated!)
https://www.nexusmods.com/fallout4/mods/21497

[b1tbull]

Thanks for the replies. Of course I used MCM 1.40 beta 2 ( my mistake in the title, corrected now). I was not aware of the AIO stuff, will try the links provided and report back.

[Equ1L1bR1sT]

Originally posted by b1tbull:

Recently installed Sim Settlements 2 with HUD Framework and Workshop Framework.

100% it won`t work.

[Fela Fragmeat]

F4se is not updated yet
Bethesda's "change management" is to blame
your only option is to wait for the devs at f4se to patch it
or disable all your mods that use f4se
or backgrade.
The f4se ppl should have been given a dev build of the update a couple weeks ago
no one can play with any f4se mods.
most environment mods are fine
things with skyui huds will probably all be broke.
bethesda should give them some devs to make it faster

[b1tbull]

Surprise : MCM is now working. Need to start the game with f4seloader.exe of course.
I guess the AIO mod made it complete.
The current fallout 4 version on my windows 10 pc is 1.10.984.0.1

For info :

f4se_loader.log
-----------------
f4se loader 00070020 01DAA8FF03C61BEC 6.2 (9200)
config path = X:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\f4se.ini
procPath = X:\SteamLibrary\steamapps\common\Fallout 4\\Fallout4.exe
launching: Fallout4.exe (X:\SteamLibrary\steamapps\common\Fallout 4\\Fallout4.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 0001000A
dwFileVersionLS = 03D80000
dwProductVersionMS = 0001000A
dwProductVersionLS = 03D80000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
version = 0001000A03D80000
product name = Fallout 4
steam exe
dll = X:\SteamLibrary\steamapps\common\Fallout 4\\f4se_1_10_984.dll
main thread id = 28160
hookBase = 000001A40F0C0000
loadLibraryAAddr = 00007FFA374E0800
getProcAddressAddr = 00007FFA374DB1D0
hook thread complete
launching

f4se.log
---------
F4SE runtime: initialize (version = 0.7.2 010A3D80 01DAA8FF0428447E, os = 6.2 (9200))
imagebase = 00007FF677170000
reloc mgr imagebase = 00007FF677170000
plugin directory = X:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\Plugins\
scanning plugin directory X:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\Plugins\
checking plugin mcm.dll
checking plugin PowerGridTools.dll
plugin PowerGridTools.dll (00000000 00000000) no version data 0 (handle 0)
checking plugin wsfw_identifier.dll
plugin wsfw_identifier.dll (00000000 00000000) no version data 0 (handle 0)
preinit complete
loading plugin "F4MCM"
registering plugin listener for F4SE at 1 of 3
plugin mcm.dll (00000001 F4MCM 00000009) loaded correctly (handle 1)
config path = X:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\f4se.ini
F4SE allocated 254 bytes from branch pool
F4SE allocated 345 bytes from local pool
init complete
RegisterPapyrusFunctions_Hook
save name is Exitsave0_D80D4BD4M53696D62756C6C_Commonwealth_000344_20240518082425_4_2
full save path: G:\Documents\My Games\Fallout4\Saves\\Exitsave0_D80D4BD4M53696D62756C6C_Commonwealth_000344_20240518082425_4_2.f4se
loading co-save
cleared save path

[sljones511]

I'm posting an additional question to a good discussion topic.
I've gotten to the part in my F4se.log except my log is missing the:
====
save name is Exitsave0_D80D4BD4M53696D62756C6C_Commonwealth_000344_20240518082425_4_2
full save path: G:\Documents\My Games\Fallout4\Saves\\Exitsave0_D80D4BD4M53696D62756C6C_Commonwealth_000344_20240518082425_4_2.f4se
loading co-save
cleared save path
===
My F4se.log doesn't indicate any save. exit save, path nada??
should it??