TechAngel85

I would personally install them early to ensure you don't miss any optionals/patches for the new worlds. The answer is right there on the Guide starting with Nomenclature and ending with the Mod Tables Legend: Okay, now we know what a STEP:Core and STEP:Extended installation is. So how do I know which mods are Core and which are Extended from the mod tables? Answer: So Core mods are all the mods with a green bar to the left of the table. That means all the mods missing a green bar to the left are Extended mods. Install all the mods in the order they're listed in the tables for a complete STEP:Extended installation. (This is also mentioned multiple times in the Guide.)

I haven't checked that mod (at work), but you can reinstall MO without losing your stuff without issue. Just download MO and copy and paste the contents into your MO directory. It'll overwrite all it's own files, but leave your profile intact. Btw, you shouldn't need to switch to the NCC installer manually at all. MO knows when to run it so just leave the settings to enabled and trust MO. The only mods MO runs it for are mods with C installers.

Thanks for the reply guys. I've looked into LOD generation in the CK and it would seem I'm a bit early in development to be worrying about that.

Well, if it's set to 1024 in the ini, then yes.

You might have an issue between two or more mods. Make sure you have all the patches. After that, all you can do is check in TES5Edit to see if there are any conflicts between the mods. If there are, you'll need to make a custom patch. That's a whole different ballgame if you've never done it before.

You haven't hit 512 yet, so you're still good. You will see ( 512 256 ) when you hit the limit.

The reason for "xEdit" is to abbreviate and cover all version of "xEdit" whether it be TES5Edit or FO4Edit. "xEdit" is common use in the modding community. Might as well get used to that one. Our order is correct, TexGen before Worlds. The official Guide doesn't take into account every single user running TexGen and says it's for "advanced users". Well, it's not that complicated and there's no reason not to use it for custom LODs. This is what STEP does so you will need to run it first, before generating the worlds. The last several sounds like you don't have the latest version of xEdit or you didn't install the scripts right. I would simply uninstall xEdit, download the latest (yes, it's FO4...same thing), rename the .EXE to "TES5Edit.exe", and then install the stuff from DynDOLOD again. You just need to copy the "Edit Scripts" folder into to root xEdit folder where the .EXE is located. Overwrite anything it asks to overwrite. Finally, don't forget to update your MO executable for the new xEdit installation and don't forget to re-add the argument for the output.

It's Boris...so no. ::

I knew that. Was just letting Kesta figure it out on his own. Haha! He only says 1 is better because it fixes one or two places he found that the game crashes 100% of the time. If users run into that, they can turn it on for that part of the game and then turn it back off after.

The first value ( xxx/xxx ) before the "/" tells you your current usage. If it hits your set value for your default heap in the SKSE.ini minus 256, then you've hit your limit. So if you have it set to 768, when the first value hits 512, you've hit you limit.

The HT and more cores comes in handy, not so much in game, but with other background tasks (assign cores manually, if needed) and for the editing and encoding software.

@Sheson, Is there something specific worldspaces must have before they are picked up by DynDOLOD? The reason I ask is because I am creating a new mod with an exterior worldspace, but that worldspace is not listed when I run the DynDOLOD script. Right now there isn't much in the space besides some exterior buildings.

Install the DX Runtimes.

I don't see why any of those mods would interfere with SKSE memory settings. I would try enabling one by one until you start to have issues. That will at least narrow it down.

Current MO (32-bit), will not likely be changing anytime soon, so you're video for that would likely be good for a long while. I would wait on MO2 until it is on an official release.

I have an Nvidia card so I'm not aware of how the AMD side runs. I agree that I would recommend a Core i7 for capturing, encoding, editing, steaming video. The benefits from the extra cores and HT would be worth if, if you're planning to do a lot of that type of stuff.

That's not going to happen with MO2 being 64-bit. No need to update the old when the new has it. I am hoping Tannin gets 32-bit games working on MO2, though. That would be ideal. If that's not going to happen either, I'm sure he'll update the v1.3.x line a bit more. I know of one FOMOD issue that still needs to be fixed. I'm sure there are other bugs that would be a release-worthy fix release. Right now, Tannin is only developing MO2, though.

Making sure you don't have anything unnesarry running in the background is about the only thing you can do since you don't have a "K" model Intel. If you had a K model, you could get better cooling and overclock it.

Start and following quote: https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4891&start=150#p71078 Topic mostly about THREADS section: https://enbseries.enbdev.com/forum/viewtopic.php?f=2&t=4880

Correct. When I checked before messaging Boris, it was indeed set to 1. I messaged him and he's set it to 0 now saying this: With the given quote from Boris, are you sure about that statement?

As a rule of thumb, never alter the original ESP. Rather, make a new esp that is your own custom patch. Then sort it with LOOT to check it's placement. Add meta rules in LOOT, if need be, so that LOOT will sort it properly.

I've updated the warning text to be more specific.

What the hell, Boris?! Why is DataSyncMode defaulted to 1? I'll notify him that it should be changed. Values should reflect what is in the note. I had no idea it was defaulted to being 1. EDIT: I've posted a message to him to see if he'll change it.

Don't copy anything that says "Navmesh". Those are combined at runtime, so there is no reason to copy them.

Some large files require a refresh. Either right-click and click refresh the list or restart MO.