GrantSP

There isn't anything wrong with the file, just with the connection you have and the server Nexus assigns you for that download. If you are trying to get this file via MO, or even NMM, try manually downloading it with your browser instead. Windows may be interfering with the multiple connections that are used to grab these larger files and it may think MO is trying to do something odd.

Are you using NMM? That looks like a very common error made by NMM users? Take note of the location that the log is saying the tool is running from! NMM mistakenly calls the FNIS tool from a temp location used after extraction and not from the installation folder. It may also be possible you have set that yourself in which case you will need to change that to point to the true location. Generator: C:\Users\PC\Downloads\FNIS Behavior V6_3-11811-V6-3\FNIS Behavior 6.3\Data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe The bold section is incorrect, it should be from the Skyrim installation.

If you think you have fixed the message then you must have installed it manually.

Welcome to STEP @LokiFenrir1228 Is FNIS Creature Pack activated, ie. checked, in the left-hand pane? FNIS is very intuitive as to what is or isn't installed so if says it isn't installed, as the log snippet above shows, then it is correctly installed. The packaging of FNIS Creature Pack needs a bit of work to make it function correctly in MO, it is 1 level deeper than it needs to be. Have you installed it manually AND set the "Data folder" to remove the message: "No game data on top level"?

You can also use a Steam Workshop Downloader. This URL will download that Steam link.

You may have to re-evaluate what you are doing as this description of your process shows you have a misunderstanding of what is taking place. The files you clean are *.esm files, not *.bsa as you contend. ESM stands for Elderscolls Master files and BSA is Bethesda Softworks Archive, two very different types of files. The file sizes you posted here are in fact accurate. So the question here is: what are the files that WryeBash is complaining about? Perhaps the cleaned *.esm files are now in MO's 'Overwrite' and the backups are what WB is now confused about?

Please post your logs and MO.ini here so we can see if there are any oddities.

That's ok, just 'chill' for a while and play a game or two of something and then come back to it. It is a rather lengthy first time process and I know what you're feeling, I was there too.

Is Steam running before you try and launch the game?

Actually that is Techangel but he is known to be acute in his observations, though rarely are his comments obtuse. Most of the time he is right.

CTD's upon starting a game can be from a number of sources but the first thing you should look for are missing masters. Perhaps a mod that you had installed has now been deactivated or the plugin is missing or even if you merged any mods the specific plugin is now part of a merge. MO will tell you what plugins are missing in a save when you mouseover the save in the 'Saves' tab.

Don't worry too much about small issues like this. If you tried to install SMIM already you would've noticed that the options in the script have not changed and you can simply use all the same recommendations STEP provides with version 2.04 as it does with 2.03. To put your mind at rest I'll edit the SMIM page to reflect the version change. Also as you are now branching out of MO specific related questions, try posting new questions in the forum specific to the subject, such as either the main STEP guide page or perhaps the SMIM page. That way all related questions about things like this will be easier to find by newer users that may face these same things.

Use 127 in place of large numbers such as 97000. The guide will be updated as needed.

Some mod you have in your load order is triggering a script when you enter that cell and, for whatever reason that script is causing the crash. I've not heard of a vanilla CTD occurring specifrically in that location so you'll need to do a bit detective work to narrow the list of culprits. If you know the ID of the cell you might try looking in xEdit for mods that are modifying that and see if there is an issue with any of the scripts.

Is this Helgen Reborn or Helgen Reborn for SSE? The latter is currently hidden so I can't see what it is you are referring to.

Welcome to STEP @Uisca If your MO2 installation is in a UAC location, such as Program Files(x86), I suggest moving it to some other place. Steam may be trying to provide MO2 with the correct details but Windows may be hindering it. Since you can launch SSE from the desktop, or NMM, the correct registry settings are set so MO2 should be able to do so also.

Wow!, wow!, wow! on the import feature. That is simply brilliant.

Thank you. Only 10 minutes to implement a change? You're slowing down.

Would it be possible to have any Nexus links pressed on the Mod Picker page open in a new tab rather that taking over the existing?

First thing to know is that MO is just a tool, it is not the thing modding the game, you are and therefore you need to know which mods are downloaded and installed. Update flags. e.g. 1) Embers HD is a mod in your list that is shown as needing updating. Now regardless of whether you used the "Download" button at the top of the page of the one beside the 'Main' file, the same download takes place (This is not always the case but in this instance it is.). If you check in the 'Downloads' tab of MO, you can filter the list by typing: embers, you will see that the file you got is version 1.32. The problem is simply in the the author's lack of versioning in the install script and the mod shows as only 1.3. Simply follow the MO wiki guide and change the version number if the update flag is distracting. e.g. 2) Skyrim Improved Puddles is a mod that will provide you with the WRONG file if you chose the "Download" button at the top of the page. Doing so will give you the 2048 size version and not the 1024 version STEP recommends. You will need to check which file you installed using the method I described above. Now this brings us to the reason why MO will flag some mods as being out-of-date when they aren't. This mod's page has as the latest version available: 1.1b whereas the file we want to use is: 1.1a. MO can only check the Nexus page's latest version as shown on it's home page, not each download listed. It will always show as wrong no matter how many times you download the correct file. This is why MO has the ability to manually change version numbers, as is explained in the MO wiki. This is why MO has no automated update of flagged mods, because 99% of the time they aren't out-of-date! Conflict flags. The thing to remember with conflicts is: there aren't a bad thing! Indeed the very concept of conflicts is what makes a mod, a mod. Let's take the base game file Dragonborn.esm. Double-click on that listing in your left-hand pane and the 'Conflicts' tab should be visible. All those listings in the top panel are 'conflicts' with other base game files such as from Dawnguard or Hearthfires. Clearly the developers aren't providing a broken game so these 'conflicts' are necessary and make the game work. This same process is at play with mods you install from mod authors but the trick here is to know what needs to 'win' in the conflict and thus the need for guides such as STEP. You, the player, need to gain some understanding the process so as to make future modding sessions less worrisome and more of a joy. As mentioned before it is highly recommended to be familiar with the tools you will be using so please acquaint yourself with the MO wiki and videos showing how to use them. All the points you raised and are discussed here are explained in these resources. With that in mind though feel free to ask anything you like here in the forum. We though are a worldwide forum and the timeframe you expect an answer in may not be the same as that the rest of us exist in, that and it is now well into the holiday season and many users may be away from their computers.

Using LOOT in MO2 is exactly the same as using it in version 1. Add it to the list of executables in MO and either run it via the dropdown menu or set a toolbar icon. The setup for it should look something like this in the executable list: 5\title=LOOT 5\custom=true 5\toolbar=false 5\ownicon=false 5\binary=D:/Games/Utils/LOOT/LOOT.exe 5\arguments="\"--game=Skyrim\"" 5\workingDirectory= 5\steamAppID= Substitute the arguments line with these variations for whichever game you are running: "--game=FalloutNV" "--game=Fallout4" "--game=Fallout3" "--game=Oblivion" "--game=Skyrim Special Edition" Calling LOOT from MO2 will give LOOT the set of mods in the current profile and it will function as it would if called from outside MO.

Are you sure you are running the patched game executable and not the launcher or NVSE? I've been using that patcher since Roy first released it and there are no inherent issues with the process, in fact it is noticeably faster on execution and less fiddling in MO to get it set up. Assuming you are doing things correctly, try a redo of your MO setup. Delete the ModOrganizer.ini and set things up again. If you wish you can post that ini here first so we can examine it.

Confirmed. @LePresidente is currently looking at picking work on MO2 so the best option for now is to add it as an issue to his GitHub repo issue tracker and if he can get around to it, it will be fixed. If you are unable to do so I can post the report for you, as I can see exactly what the problem is with my logs.

Pleas read the STEP Citizenship Guidelines linked here or at the bottom of every page.

Issue 1: Confirmed. Nothing I change in the settings will make any difference to the way MO2 loads the game. Curiously MO loads and launches the game with no issue but even after I get MO2 to see my FO3 install I cannot launch the game and get presented with Windows 10 complaints that this app may not work. MO has no such issue. Issue 2: Also confirmed with this proviso. If I change the %base_dir% to something other than that which MO2 used on install then the other profiles are not seen but if I create new profiles under the default install location, ie. %appdata%\Local\ModOrganizer\, then they show up. MO2 isn't seeing the base directory correctly if it is changed in the settings. Issue 3: Can't replicate this, but as I have not changed the default %base_dir% for this game I assume it is related to the previous. Issue 4: Can't replicate however there does seem to be an issue with how LOOT is called as a heavily modded game creates a HUGE log file when LOOT is run. LOOT itself runs properly in my setup but with all the extra overhead of creating processes and logging them perhaps there is some isse? Issue 5: As noted above MO2 refuses to launch Fallout 3 either via FOSE or the game's executable. MO has no such issue however it is impossible for me to launch Fallout 3 on Windows 10 without MO as Windows complains about the app. Issue 6: Can't replicate. MO2 loads any game without or with SKSE. Issue 7: Again no problem with my installation, game loads perfectly.