Greg

When you initially arrive at the property for your Hearthfire home, you'll find a container with a very minimal amount of items, a clay deposit, a stone deposit (with a seemingly infinite amount of clay and quarried stone) and a crafting station for your house. The first step is to hoof it to the nearest mill to purchase logs to get started. Also note that you do not have any smithing equipment so you may as well hoof it over to the nearest smith to create a big batch of nails, hinges, and iron fittings. With the basic Hearthfires DLC you'll need to hoof it over to a mill about 50 times if you purchase 20 sawn logs at a time; hoof it over to a smith about 1,000 times to craft nails, iron fittings, hinges, and locks if you craft small sets at a time; hoof it all over the map multiple times to find find enough ore to melt into ingots; slaughter enough goats to feed the entire Imperial army to collect goat horns for the lights; and purchase a truckload of glass. All of the smithing equipment can be created in the basement of the house, but you can't create the basement until you build the basic house. If you have Hearthfire Extended, you can craft basic smithing equipment outdoors before you craft the house and this will save a ton of trips to the nearest smith, but it still takes forever with a lot of trips all over the map to gather the stuff required. I used to build these houses (and still do when I need to thoroughly test), but I don't bother in my own personal playthroughs because it's too much hassle. Also consider that the point of Hearthfire is to allow the player to craft homes for adoptable children so why in heaven's name are all Hearthire homes in deadly areas? All of them also have bandits randomly spawn at the backdoor.

Open Steam Settings, click the Download tab, and click "STEAM LIBRARY FOLDERS" button. Add a new folder pointing to the folder you want the game to be moved to. Once the new folder is setup, go to Library, right click on the game you want to move, click Properties, click the Local Files tab, and you see the "MOVE INSTALL FOLDER..." button. If you click this button, Steam should move the game to the new folder. How can I move an installed game from one Steam library folder to another? You can also move the entire Steam folder and all games to a new folder, although this one seems to be a bit dicey. Basically try it and hope for the best. If it doesn't work, uninstall and reinstall from scratch. Moving a Steam Installation and Games

Having an empty uvfs log indicates that the hooking process is not working so verify your antivirus or other software is not interfering with the hooking process. If you are on Windows 10, you may also need to ensure none of the *.exe and *.dll files in the Mod Organizer folder are blocked. Open the Mod Organizer folder in Windows Explorer, right click each file, and select Properties. If you see an Unblock button, click Unblock and click OK to close the dialog. Also note that the hooking process can also fail if you run the game or any tools as an admin from Mod Organizer but Mod Organizer is not run as an admin. This is because Windows refuses to allow a non-admin process to hook an admin process, although you really shouldn't need to run Mod Organizer, the game, or any of the tools as an admin. Also ensure you are at least on Mod Organizer 2.1.13 from Nexus, although you might be interesting in picking up the latest Mod Organizer 2.1.14 dev build from #builds on discord. Your syntax for the parameter to LOOT confuses me. I think it should be more like this in the Arguments textbox: --game="Skyrim Special Editiion" EDIT: It seems to be correct in your ini file so it may just be the way you typed it in your post that's throwing me off.

The empty uvfs log indicates the hooking process is not working so verify your antivirus software is not interfering with Mod Organizer. Also note that if you run LOOT or the game as administrator, you *must* also run Mod Organizer as an administrator or hooking process will not work -- although I strongly recommend against running anything else administrator.

If you copy the mods folder, be sure to also copy the profiles folder -- or at least the relevant profile folder for the profile you are currently using. This is where Mod Organizer stores the install order of the left pane. the load order of the right pane, and the list of mods that are active or inactive.

If you are using Mod Organizer the Skyrim folder should be relatively clean so you shouldn't need to reinstall Skyrim. You might try backing out the presmash patch, smash patch, bash patch, etc. and re-enabling any mods that got merged into these patches and hope for the best. The difficulty I run into here is trying to remember which mods were merged into a patch and which may have been deactivated for some other reason so I usually end up hiding plugins if I merge them before creating all the patches. Using separate profiles also helps... just before you start creating all the patches, copy the existing profile to a new profile and then do the patches in the new profile. If it blows up, you can easily go back to the original profile to try again.

This should not have anything to do with this issue. I currently have Skyrim on C: and Mod Organizer on F: and it runs fine, although I want to move Steam and Skyrim over to F: at some point in the future to get it off the boot drive.

The i7 7700k normally runs hot under load but the peak temperature should be less than 85°C. If your CPU is hitting 98°C and 100°C during a stress test, I question whether the cooler/heatsink is properly installed on the CPU. There should be a good layer of thermal paste between the CPU and heatsink and the heatsink/fan assembly should be mounted tight so it does not wiggle if you touch it.

Assuming I'm interpreting the graph correctly, it looks as if the GPU temperature starts at 46C (114F) and steadily climbs to 64C (147F) and the FPS drops do not correlated to GPU temperature. I'm not all that familiar with NVidia's thermal throttling so I could be mistaken. I use an AMD Radeon R9 290X Space Heater Edition... at least this is what I called it before I tuned the fan profile to get the temperature down. Now I all it the AMD Radeon R9 290X Jet Aircraft Edition. I also suggest running BethINI to optimize your INI files if you haven't already. I know a lot of performance issues can simply be caused by bad or unoptimized settings in the INI files. If you're using an ENB preset, you might also temporarily disable the graphics settings in enblocal.ini (set UsePatchSpeedhackWithoutGraphics=true in [GLOBAL]) or in game (I think the default shortcut is F12 to toggle ENB in game).

Are you running Mod Organizer from a shared folder on the local network? If not, do you have any idea what assembly it's trying to load from a remote network? I'm just curious because I've never run into this error with Mod Organizer before.

You can use something like C:\Games\ModOrganizer or C:\Tools\ModOrganizer or pick another folder name of your choice. I usually just create a folder off the root of a drive to keep the path relatively short.

The patches include only ModOrganizer.exe so you would download this on top of the existing ModOrganizer.exe in your install. I suggest reading the description and deciding whether it contains any fixes or features you want.

EveryonesBestFriend.esp deleted this dialog topic so I think the remainder of the record should be empty and I would leave it alone.

If you installed Mod Organizer in "instance mode" (which is the default), you should have only one copy of Mod Organizer installed. When you want to switch between Fallout 4 and Skyrim, click the button at the top left and select the appropriate instance to use. It sounds as if both copies of Mod Organizers are using the same instance to manage different games so you should probably create new instances from scratch. Create one instance for Fallout 4 and use this one only for Fallout 4 and create one instance for Skyrim and use this instance only for Skyrim. You can create as many instances as you want. I also suggest moving Mod Organizer (and any games) out of the Program Files folder because you'll bump into a lot of permission issues. Also do not install Mod Organizer in the game folder because the virtual file system does not work correctly if Mod Organizer is installed in the game folder.

The tag line under the Mod Organizer 2 Support title should read "MO2 support for Fallout 4, Skyrim SE and other games." The original release of Mod Organizer supported only the 64-bit games (Fallout 4 and Skyrim SE) but it has since been developed quite nicely so it now supports Fallout 3, Fallout New Vegas, Fallout 4, Oblivion, Skyrim Legendary Edition, and Skyrim Special Edition. I usually suggest installing Mod Organizer in its own folder off the root of the drive in a path like C:\Games\ModOrganizer or C:\Tools\ModOrganizer to keep the path somewhat short and to keep it away from the game folder and user-access controlled folders (like C:\Program Files). If you are currently using Mod Organizer 2.1.13 from Nexus, I suggest popping over to the #builds on the Mod Organizer discord and download the MO2 2.1.4 Dev Build 3 because this version fixes a lot of download issues (specifically detecting hung downloads, changes so the EU#1 Nexus server now works, fix resuming downloads, etc.). Immediately after you download this archive, open the folder where you saved the archive in Explorer, right click on the 7z file, click Properties to open the Properties dialog, click Unblock, and click OK to close the Properties dialog. Finally extract everything right into your existing MO2 folder and let it overwrite everything. Now run Mod Organizer 2 (run ModOrganizer.exe from Explorer while in this MO2 folder not from a shortcut). Ensure Mod Organizer is currently configured for Skyrim Legendary Editiion not Skyrim Special Edition -- this should be the first button at the top left with the tip "Open the Instance selection dialog to manage a different Game." Once this is sorted, click Settings (the screwdriver and wrench icon at the top) to open the Settings dialog, and click the Nexus tab. Check "Automatically Log-In to Nexus", enter your username and password, click "Associate with 'Download with manager' links". and click OK to close the dialog. Finally, click "Search nexus network for more mods" (the globe icon at the top) to open Nexus in a browser and try to download a small mod with manager. Hopefully it works fine. If this does not work, exit Mod Organizer and go back to Explorer (it should still be open and in the Mod Organizer folder). Double click to run nxmhandler.exe. NXM Handler should show a list two columns: Supported Game and Binary. Supported Game should be set to "skyrim" (without the quotes) and Binary should point to your Mod Organizer 2 executable (e.g. something like "C:\Games\ModOrganizer\ModOrganizer.exe" without the quotes). If you see multiple entries here, select the one most appropriate, and click Register active. If the list is empty, right click and select Add. Select Skyrim (not Skyrim SE) as the supported game, click the ... button to select the path to ModOrganizer.exe, and click OK. Click the new entry you just added, click Register active, and click Close. Go back to Mod Organizer, open Nexus, and try again. If it still doesn't work and you are using Chrome, curse Google once or twice and follow DoubleYou's directions. If you are using Firefox, curse Mozilla once or twice and follow DoubleYou's directions. These are right at the top tagging "BEST ANSWER".

You already posted this information in another topic and as I responded there you should download and install Mod Organizer 1.3.15.

There's no need to use such a hack. Download and install Mod Organizer 1.3.15 from the Mod Organizer 2 page on Nexus. It's at the bottom of the Files tab as "Mod Organizer 1 Legacy".

Unfortunately, I think this is still an open issue that has not been completely resolved yet. I think OBSE works fine from Mod Organizer 2 with the retail (CD) and GOG versions of Oblivion but it does not work with the Steam version and it may not be quite so easy to fix.

This isn't a debug log so it doesn't really provide any information to go on. You'll need to open the Settings dialog (the screwdriver and wrench icon at the top), click the Diagnostics tab, and change Log level to Debug. You should delete all the log files first before running Mod Organizer to keep the uvfs log as small as possible. When you finish capturing a good debug log after reproducing the issue, change the log level back to info. The debug log captures a lot of useful information but it really slows the game. A few thoughts in the interim... Add an exclusion or temporarily disable your antivirus to ensure it is not interfering with the hooking process. Run Explorer, right click on ModOrganizer.exe, click Properties. If you see an Unblock button, you'll need to click Unblock and click OK. Rinse and repeat for all *.exe and *.dll files in the Mod Organizer folder and subfolders. This is mostly an issue with Windows 10 and I think I've reached my Windows 10 rant limit for the week so I'll be quiet. Do not install Mod Organizer in the Steam or Fallout 4 folder because this is known to cause issues with the virtual file system. Do not install Fallout 4 (or any other game you run from Mod Organizer) in Program Files, Program Files (x86), or any other folder controlled by UAC because this will cause permission issues that prevent the hooking processor or the virtual file system from working correctly. Always install Mod Organizer and the tools you use (like LOOT, Wrye Bash/Flash, etc.) in a folder you create as a user. If you are running Fallout 4 (or any game or tool) as an administrator and you are not running Mod Organizer as an administrator, the hooking process will not work because Windows prohibits a user process from hooking an admin process. If you must run the game as admin to get it to work, you have permission issues somewhere so see the previous point. Also keep in mind that any files (like your saves and the INI files) created by a process running by an admin may be created with admin as the owner and you as a user may not have access rights to these files. EDIT: I forgot to mention, you might also try the latest 2.1.4 dev build in #builds on the Mod Organizer discord. If you do this, be sure you unblock the zip file before you extract the files (right click the zip from Explorer, Properties, Unblock, OK). If you skip this step, every file extracted from this archive may be blocked and Windows 10 may have a hissy fit).

Wasn't there a similar issue if Mod Organizer is installed in the Steam path? I know the Skyrim folder is absolutely out of the question because Mod Organizer can run into issues finding files, but I though AL12 or Silarn had found similar issues with Mod Organizer installed in the Steam folder and recommended installing it in its own folder outside Steam.

Nexus also has different categories for all of the games so there really isn't one set of categories that can be used across the board. Gameplay Effects and Changes is 24 for Skyrim and 71 for Fallout 3. I also think Nexus categories are very poorly defined and completely disorganized. I mean armor and weapon retexture mods scattered across armor, miscellaneous, models and textures, visual and graphics, and weapons doesn't make any sense and it makes mods harder to find. I know this is just my personal opinion, but I tossed Nexus categories in the trash long ago. I really don't understand the difference between models & textures and visuals & graphics anyway. Both are basically mesh and/or texture changes.

Yes, report any issues you find on github so they don't get lost in the shuffle.

You can launch something like Free Commander from within Mod Organizer to view the virtual data folder as the game sees it. You'll need to use the x86 version with Mod Organizer 1 although you can use either the x86 or x64 version with Mod Organizer 2.

I'm not sure how you're doing this but you don't need the tags at all. To include images, all you need to do is click the image button just above the editor and paste the URL. Alternatively, you can use the img tag like this: [img=https://i.imgur.com/YeQbfmn.jpg]

This is a known issue with Mod Organizer 2.1.3 that should be fixed in 2.1.4. I don't think 2.1.4 has been released to Nexus yet so you can download the latest 2.1.4 dev build from #builds on discord. Just be sure to unblock the archive file (*.zip) before you extract the files or Windows 10 may make your life miserable. You can extract the files right on top of your existing MO2 install but you may want to back up your existing MO2 folder just to be safe. It's not that I expect the build to have any issues (most have been fairly solid so far), but I'd rather have that extra safety net just in case.