GrantSP

Are you trying to perform consecutive tasks in a single xEdit session. ie. cleaning and then applying bash tags?

You don't need any arguments to FNVEdit if you have it named FNVEdit.exe, as you do. The argument is designed to force it to start in the FNV game mode if it is named xEdit.exe, or similar. The logs we need are not from xEdit but rather the logs from <path_to_MO_install>\logs\ Delete all the current ones, if you wish, to ensure only the needed logs are there and run the task and post the log here. Remember to use spoiler tags or use PasteBin. Any images will need to hosted elsewhere and you can post the links to them. Have a look at the STEP guidelines if you are unsure what can be done or how to do it. A link to it is found at the bottom of every STEP page.

As I mentioned to you in the other thread, please post an example of the logs from when you try to do what you described. In addition your MO INI will show us where you have everything configured. As far as MO is concerned it makes no difference at all where xEdit is installed as long as you give the full path to that executable in the settings.

Start a new thread here at STEP in the MO section and post your INI and your logs from a typical issue experience. Give as much info as possible to try and pinpoint the problem. Lastly eliminate as much extraneous stuff in your testing setup so that only the bare minimum is being used. There is a Discord channel but that is focused on MO2 and you may not get as much traction there as here. Look at any Reddit threads or other forums you like. There are 1000s of users on various OSes that are running MO and the solution to your issue will come... eventually.

My advice is to find out why you are experiencing this odd behaviour and fix it before moving on. Workarounds and hacks are, by their very nature, not very helpful and you will possibly want to do more advanced modding later on. Having to move plugins and the assets for those mods around is just not a good idea. However it is your call. As for installing MO anywhere else, it is such a small install with little to worry about that what ever you do with MO is fine, just keep it out of the game folder.

No. Since you can snap me like a twig I think it's safer to remain quiet. Rest assured it was nothing bad, just different. The cat silhouette gives a certain vibe.

Funny that's NOT the mental image I'd built up of what you look like.

Okay I think your MO install may be in trouble, those logs look wrong. A lot of needless fluff and nothing of any benefit. Backup the "mods & profile" folders and then remove your existing MO install and re-install to a location away from Fallout. Afterward move those folders back to replace the empty ones just created. Open the settings in MO2 and check that they are pointing to the correct folders, they should by default. Create a new empty profile and start the game to verify that everything is fine. If it loads then change to the profile you're currently using and try again. If it fails post both logs here. Be sure to use [spoiler]text that is hidden[/spoiler]

What version of MO2 and where did you get it?

Are you sure that is all the log? It seems truncated. Create a new profile and load just one simple mod, one that you can quickly check is working, and start the game. If it works then your load order needs some work to clear out the culprit(s).

I want to see the USVFS log to see if MO2 is loading all the mods you told it too or if the problem you see is due to what @GSDFan mentioned. With 225 active mods I tend to think he may be right.

You just said that you tried and it didn't work. Was that not after you posted that log? Also that isn't the USVFS log.

So apparently STEP is awash with old guys playing PC games! That doesn't make sense. If you've not changed anything the same process will apply, MO doesn't change for no reason. All of the video tutorials and guides for MO1 are still largely applicable to MO2 as very little functionality has changed. Using "spoiler" tags, or a service like PasteBin post the last USVFS log here.

What have you changed since you posted that log?

MO2 is installed either as: "portable ie. everything is in the one place" or "instanced ie. all relative folders and configuration is in %Appdata%\Local\ModOrganizer\Fallout 4\" MO2 doesn't need to be installed anywhere near the game. In fact it is often better to install it somewhere else as most users have their games inside a UAC folder where Windows takes control of it. e.g. Program Files (x86) Sounds like you have an instanced install. Keeping everything there is fine, it is just a matter of choice. %Appdata% is usually hidden so the option is given so newbies don't fret where their stuff is stored. If you can post your mo_interface.log here I can see what you have configured.

Glad you got it sorted. 61 eh! So I'm no longer the oldtimer around here.

Give me an example of a mod that uses them and I'll see if I can replicate. Don't do a lot of FO4 modding so I haven't seen what you're describing.

Not sure what you're trying to do exactly. Why the need to manually add *.json files and why are you worrying about their not having meta tags. Also what do YOU mean by "meta tags"?

You don't need to compress anything to use MO. Each mod installed via MO resides in a sub-folder off your MO\mods folder. So if you want too change a texture of a mod you have installed, there will be a textures folder inside the folder structure I mentioned above. Simply copy the new asset into that folder. However, if what you want to do is get your mod to use textures/meshes that you specify just create a new mod and have MO load that last. This way it use the last set of files, those with the highest priority number and the game will work with those. Look at on the guides for the various games here on STEP. This is how those authors have configured their games.

We're you missing the FCO - Roberts Patch.esp?

do you have any other games that MO manages?

STEP and MO are not the same thing. @Tannin, MO's author believed that feature is a good idea but also realises that others may have a different idea. STEP has already checked whether the mods it uses have conflicts so as I mentioned above: follow the guide and disregard the messages. Open "Settings -- Plugins" and set Basic diagnosis plugin to 'False'

Please note this thread. The STEP guide has already carefully examined any conflicts and determined the optimal install sequence. Follow that guide exactly and your modded game will be fine.

If you run MO as admin then that may be giving xEdit access problems. This is why I generally advise against running anything as admin, unless the author of the tool/mod specifically says to. I saw nothing in your logs that would indicate an issue with MO's VFS not working correctly, which means I have no idea why your system can't get xEdit to run from MO. Sorry!

Though that is an issue with the build you were using it actually wouldn't affect MO2's use or the game. MO2 does not, nor will it, restore the function to enable BSAs without their plugins like MO1 did. The feature that is being restored is that which uses the BSAs in showing conflict resolution information. The backend of the code will stay but most likely the actual 'Archives' tab will once again be removed.