Suggestion MCM Hotkey to enter build mode

[Unknown Zombie]

Could you give WS+ an MCM option to set a hotkey to enter build mode?

I'd like to just press a button once to enter build mode instead of having to hold down the view change button, which feels unresponsive sometimes.

 

[HyperLordBender]

The txt ones starting with f4se. Only the most recent ones

 

[Din'elen DarkStar]

Here you go.

 

[HyperLordBender]

Here you go.

It seems like your f4se version is different than mine. Same overall verson (0.6.21) but the imagebase is different as is some of the other numbers (I have to assume one of them is a sha). So either that doenst matter or you dont have the most updated one. Also, could you post the xSE PluginPreloader log? Thats just in the games root folder

 

[Din'elen DarkStar]

Here's the thing, I don't have this directory; plugin directory = D:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\Plugins\
Also I recently updated to the version on their site when I did a fresh install. I am wondering if MO2 virtual Data directory is not registering it right or something. All my other plugins are working correctly.

 

[HyperLordBender]

Here's the thing, I don't have this directory; plugin directory = D:\SteamLibrary\steamapps\common\Fallout 4\Data\F4SE\Plugins\
Also I recently updated to the version on their site when I did a fresh install. I am wondering if MO2 virtual Data directory is not registering it right or something. All my other plugins are working correctly.
View attachment 12896

Yeah, the MO2 stuff is stored separate from the game, then gets "attached" to the game directory when you run the game. You can see the result by running the virtual folder via mo2.

 

[Din'elen DarkStar]

Here you go.

 

[HyperLordBender]

Here you go.

Yeah, your missing a bunch of dll's.

MSVCP140_ATOMIC_WAIT.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll

 

[Din'elen DarkStar]

Yeah, your missing a bunch of dll's.

MSVCP140_ATOMIC_WAIT.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll

Ok so how do I fix that issue?

 

[HyperLordBender]

Ok so how do I fix that issue?

Reinstall the redistributables.

 

[Din'elen DarkStar]

@HyperLordBender Well it seemed that worked. I installed the arm one as well and repaired my other install. Thank you for all the help. I have been at this for a good month. I have done this a few times and the only difference was installing the ARM one as well.

 

[HyperLordBender]

@HyperLordBender Well it seemed that worked. I installed the arm one as well and repaired my other install. Thank you for all the help. I have been at this for a good month. I have done this a few times and the only difference was installing the ARM one as well.

Your welcome. Logs are always the best way to find out why something doesnt work since they arent physical so we cant kick them...

 

[Din'elen DarkStar]

Your welcome. Logs are always the best way to find out why something doesnt work since they arent physical so we cant kick them...

Ex programmer and still suck at reading log files... especially the one for F4SE and what not.