GrantSP

Thanks Greg.

Doesn't she have her own site somewhere? I seem to recall seeing some of her documents hosted elsewhere. Sadly it's been so long since I've used any of her mods that I can't rely on my memory, it's flaky at the best of times.

This thread was first started in Sept. last year and a lot of work has happened since then. Even the post above your first one by @LePresidente indicated that a fix was coming. I have a working install of FO4 in MO2 with no need to manually create any folders to install MCM or indeed any other F4SE mod. I've now unstickied this thread to avoid confusion. I do not however have control over the Nexus pages and @LePresidente is not always around to do that.

Can you delete all the current logs and then run FO4 and then post the logs here in spoiler tags please. Ensure you set the logging to debug in your settings first, you can reset it after so it doesn't thrash.

What version of MO2 are you running? More to the point have you installed MO2 into a sub-folder of the game? If so please move it out.

MO 2.1.1 does not need to have any of the script extender folder structured outside of MO2. You can just install and use it as you would with MO1.

Just a heads up, @Arwen is a woman so "she" may have missed it. Aside from that I have always in the past found all her work to be of the highest quality. I don't use anything from her now though due to the fact most of it is rather extensive overhaul type mods, which I prefer to steer away from. This is also why I had nothing to offer with your OP, I simply had no idea what it was doing. Have you tried asking her about this issue? I recall her being very accommodating with her users.

Not the INI, no, but in the settings you can change the paths to a number of folders

Okay you're using MO2. The INI is in %AppData%\Local\ModOrganizer\<GameName>\ where <GameName> is the name of the game MO2 is managing. You posted in the MO forum so we just assumed you were using MO 1.

The same folder as the MO programme.

The biggest issue I see with your installation is the fact you are in: C:\Program Files (x86)\. UAC is a big problem with a lot of modding tools and this folder is one such case. If you could move your Steam install out of there and see if that is the reason. I can't see where you have MO2 installed but likewise with that, keep it away from any folder under Windows control and especially keep it out of the actual game folder. MO/MO2 does not need to be installed in close proximity to any of the games it manages so you can create a folder called MO2 off the root of you main drive if you wish and use that. If Fallout4 is the only game that you use MO2 for you can install it as a 'portable' install which will keep all the game specific folder structure under the same place, rather than use %AppData%, as it is configured now. This isn't a concern or the root of your issue here, just a preference matter, entirely your choice how you install it.

In your MO2 settings do you have anything in the "Start in" field? If so remove it and try again.

@crazy_eYes I suggest you continue this in just one thread, either here or the MO one but not both. As stated in the other thread posting a log of what happens when you do not use MO is not going to be helpful in troubleshooting your problem since it is to do with both DynDoLOD and MO.

No, I need to see the MO logs from when you call it.

@crazy_eYes Please post your logs, inside spoiler tags, so we can see what is happening.

@Xevious Have you installed F4SE manually outside of the MO2 environment? That needs to be done as MO2 cannot install script extenders as they need to go into the game's folder. If you post your logs here, inside spoiler tags, so we can see what is happening that would be helpful.

What version of MO2 are you using? Also are you sure you have the correct version of LooksMenu for the version of FO4 you have? I've just now grabbed it from Nexus and installed it and it works as described.

Can't say I've ever done a truly despicable player, I'd be very interested to see the results from this.

Yes, you merge the patch with the main download from the NVInteriors Rewritten page. I've added an extra sentence to that set of instructions. Please check it and let us know if that makes it more clear.

All the variants of xEdit are the same, just named differently to be used on various games. FO4Edit == TES5Edit == SSEdit == FO3Edit etc. The later versions should have no bearing on the matter as I stated earlier, the changes in them will not include any code that references the registry. If the version of xEdit you linked to works, sure, use that. I currently am still using 3.2 and seeing no issues so there is something odd with your setup that is creating that error.

This is most likely an issue with your skyrim.ini. Since you are using MO create a new profile using default INI settings and check to see that this new profile loads the game correctly. Some users have reported that switching back to their first profile also now works if however it doesn't you can either revoe the existing INIs and create news, use BethINI to generate new ones or otherwise edit the existing INIs to match the new default ones of the new profile. PS. A google search of "failed to initialize renderer" shows quite a number of results, perhaps you're Google searches were not specific enough.

You'll be fine, keep going.

No worries, oh and it's just Grant. That's the title I've given myself.

More to the point is why does the later version see the registry key when you were having issues before? That makes absolutely no sense, there were no code changes between those versions that are anyway related to that function. Are you sure you started the game launcher? Was there a system reboot in between these attempts?

Easiest thing to do is just drag/drop it onto the existing Brows mod. If the previous version of that plugin is there it will be replaced and if not this cleaned version will just take its place. You could create a new "Cleaned - Brows" mods, but that isn't really the best option. Whatever you do just remember that anything in the overwrite folder needs to be moved elsewhere as it is to be used as a temporary holding mod only, don't leave things in it during play, they will have priority and this may cause issues later on.