Suvanto

I came here from Steam forums and haven't yet figured out Nexus forums that well, so I did not notice that page search does not find content from spoiler field. Let's remember that next time. :laugh: Well, in that case it is in the wrong place. LOOT does not yet sort them correctly. Real Shelter.esp should be first ESP file to load in your list, after Unofficial High Resolution Patch.esp. RSPatch.esp should be the last file to load, right above Bashed Patch, 0.esp. This is also the order that mod author recommends. Problems with file locations has been notable enough that I included it in to my load order template in Steam. If moving Real Shelter files and darstyler's links do not fix your problem, then could you also post your mod list, as sorted according to priority? I would just want to check that known exceptions are not causing trouble.

Don't remove mods from ongoing game. Skyrim bakes script data to save files. If you have done so in the past, then this may explain your current problems. It is also worth to make sure that your master files are not damaged. - Close Steam. - Go to your Steam folder and open folder named appcache. Delete everything from inside. - Close your computer. Let it shut down, before starting it again. - Start Steam. It may load a few seconds, while inspecting your games and creating new content to appcache folder. - Steam client Library view, right click the game. - Properties > Local Files > Verify Integrity of Game Cache. One file will always fail to validate. It is your graphic card configuration file and it is not a problem. Game will verify it automatically when you start the game.

I noticed that you have RealShelter USLEEP Patch.esp in your load order, but not Real Shelter.esp that it requires. Have you also sorted resource priority conflicts from the MO left panel?

It was not about you. I posted that note to wrong thread. It was meant to post to another thread, where player posted a new question about new problem in the middle of another conversation. Sorry about that. I should not write replies around 4:00 at morning. :ermm: You misunderstood my attitude. I have spent years in Skyrim Steam forum, providing help and writing tutorials. I decided to see if I could come active in Nexus as well, now that I have more time in my hands.

And please make your own post about the problem. Solving one problem in on thread is always better. Trust me on that.

32bit MO can't handle 64bit applications. That's the problem. You need to launch applications through MO - including applications like SKSE or Skyrim launcher - for them to work. This is the problem. If MO can't handle these applications, then they can not be launched through it. BTW. Nice to know that you are active in Nexus forums as well. :)

SKSE support for Special Edition confirmed. Yes. Mo is 32bit application and requires an update to run with Special Edition. Edit: About mod compatibility; Pete Hines seems to believe that saving older mods through SE CK will allow them to work properly in game. How well this works is still unconfirmed, but I suspect that majority of mods that would conflict with 64bit Skryim can be made combatibile this way.

We have a follow-up thread and conversation in Steam forums. I know that all of you are not following that forum, so I try to post relevant changes to this thread. I do not yet have FO4, but it was brought to my attention that it has a tool to convert Skyrim meshes to FO4 compatible meshes. If Skyrim CK will get updated to match that (expected, but not yet confirmed) then fixing anticipated 64-bit problems with meshes and lights may be a lot easier than we feared.

What do you mean by "My game CTD after play new game"? Do you mean that it crashes after Bethesda logo? As darstyler pointed out, Papyrus log is not a crash log. It should be provided when especially asked for by a mod author troubleshooting his or her own mod. Unless there is obvious spam in it, then it is mostly useless to rest of us. It records everything, but rarely the script that crashed it - if it even was a script that crashed it. It was helpful to see your mod list, but your load order might be more useful. Add a bit better description about what is going on, so that we know what to look for.

If there is a problem in my instructions, then I will need to fix them. Thank you for your input. - Make sure that your Overwrite folder in MO (bottom of the left panel) is always empty, before running any tool like Wrye Bash or SkyrProc patcher tool. - Running such tool places the gameplay information in to MO Overwrite folder. - Right click the Overwrite folder with content in it. Select Create Mod. Name it accordingly, for example Output Bashed Patch. In this case the folder would have Bashed Patch, 0.esp and Documents. - Set the folder active in MO. Done. When you next run the tool, you can just copy the content from Overwrite over the old, or clear the old information before doing so. Script order for MO is usually easy to set up, because BSA-archives have ESP files so that they would load. This is why the script order in left panel follows very closely LOOT sorted right panel. If mods you have merged have scripts or other resources in them, then the order of the files matter for merged mods as well. If not, then it is irrelevant from resource priority point of view and the load order itself will determine the order these files take effect in your game.

Debate about that has been going on. It depends a lot how they are going to implement this. It likely that several mods will require tweaking to play nicely with Special Edition. We will see. :) Thank's for the linki disi30.

Thanks. I need to update that to my follow-up thread in Steam. Now I only need to find where he said that.

Few moments ago Bethesda's Global Community Lead Matt Grandstaff confirmed 64-bit update to Skyrim in upcoming Special Edition. This happened in twitter reply here: https://twitter.com/gstaffinfection/status/742818176497385472

Tool data from Wrye Bash and SkyProc patchers should be made as mods for MO left panel. My tutorial post explains how. Left panel manages your resource priorities. It determines the order that scripts, meshes, textures and character data takes the effect in your game. It is similar with order of installation of files with NMM. Tedious part is that you will have to sort out the left panel, when you first build your new mod list. Easy part is that you only need to check that any new files that you add does not create a problematic conflict. You can see if mod is winning or loosing conflicts against other mods from +/- signs next to it's lightning icon marking the conflict. Not all conflicts are a problem. Problem is to know which one of them are needed. For most cases this is really obvious though. Script content in your left should usually follow the order in your right panel load order. You are free to solve conflicts between meshes and textures as you prefer them to appear in your game, as far as it does not harm any practical compatibility. Using SMIM as example, it has a list of how files should be installed in NMM. Same rules apply in MO, except that ones marked to get installed before should be above SMIM and ones marked to install after should be below SMIM in left panel. This is not as complex as it sounds. Left panel is a bit tedious to sort out first time, but after that you can use MO's Merge and Replace options, when updating files and thus avoid all sort of messing around with files and installation order. This is the strength of MO, but also initially the confusing part. I have linked one of Gopher's MO tutorial videos at the end of the tutorial post. It does visually present what resource priorities are. Note that Gopher speaks them as "mod priorities", but at least Steam forum has adopted the phrase "Resource priorities", due to it being more fitting description.

Your left panel is unsorted and your Real Shelter files are in wrong positions. LOOT does not yet sort RS files correctly. It also looks like your tool output data is left unmanaged. I don't have any resources about this in Nexus, but I have made a post about this to Steam Skyrim discussion. It should present how to set your left panel and proper positions for your Real Shelter files. Load order and resource priority basics http://steamcommunity.com/app/72850/discussions/0/523890681419356033/

Mod organizer has it's own set of configuration files for each profile. You need to edit changes to them. MO > Tools > INI Editor Tools is the puzzle piece in left top bar.

Papyrus log is not a crash log. It records everything, but rarely the script that crashed it - if it was even script that crashed it. Your load order and mod list would probably be more useful to us. It would also be good to know if there is any consistency between your crashes - meaning exactly in which kind of situations does your game crash?

Do you have any camera or first person mod, like Skyrim Enhanced Camera? That would explain the situation.

Just to be sure that your master files have not been damaged and your configuration files have not been messed up, try validating files again, but this time clear the appcache folder and remove configuration files from Documents > My Games > Skyrim. if you made some needed configurations to Skyrim.ini and SkyrimPrefs.ini, then write them up, but test the game first without them. I have instructions how to validate files with cleared cache in Steam Skyrim forum. Wording is a bit bad, because you do not actually need to delete the folder, but only what is inside of it. I will rewrite it soon. [Quick link] Validating master files http://steamcommunity.com/app/72850/discussions/0/535150948617437868/

Your load order does not seem to be sorted out correctly. Start from that and see if it helps. I do not see exceptions here, so you can just run LOOT. Remember that initializing does not sort your load order. Click three lines and then APPLY, ones tool has finished running. LOOT https://loot.github.io/

Skyrim will always complain about missing files. In this case it will do it only once, when you first time initialize the save that misses the content. It should not be a problem with USLEEP and the warning no longer appears, when you load the save that you have made after that event. If Skyrim would warn about some other files missing, then that could be a problem, seeing how Skyrim bakes script data to save files. Changes from Unofficial HF patch are added to USLEEP. It is true that some mods are not and never will be updated to USLEEP. It is more important to note that current and new mods are unlikely to get ever updated for USKP, now that it is no longer getting any updates.

I advice against disabling USLEEP. Old patches do not get any new updates and several mods have already updated for USLEEP and away from USKP. Only old files that no one has ever bothered to update are still using USKP as master. Recommended fix. - Disable old patches for now. Do not yet remove them. - Run LOOT to see which file are still expecting USKP to be as a master. LOOT will display this as number of Errors and target files are appearing in the report. Write them down. - Enable old individual patches. USLEEP needs to be in your load order as well. See USLEEP Swap Masters Script page how to position them. - Install script to TES5Edit as explained. - Run TES5Edit. Select "Select None" and then set all Unofficial Patches and USLEEP active. Then select the first problem file active and run TES5Edit. - Once TES5Edit stops loading, right click the problem file with your mouse, select "Apply Script" and select USLEEP Swap Masters Script from the list. Run it. - When you are done, close TES5Edit and store changes selecting "OK." Make sure that only the problem file appears in the closing screen. - Repeat to another file, if needed. - Remove old individual patches from your load order. - Done. Does this sound long or complex process? It really is not. :smile: The whole thing only takes less than a minute per file, once you have installed scripts.

Link to LOOT is also in the tutorial I linked, with instructions how to run it. Edit: Sorry. Wrong post. Link was in my guide that was linked above. Here is the direct link to LOOT. LOOT https://loot.github.io/

Errors are there, because USLEEP includes all the changes from old individual Unofficial Patches. You should not use them with USLEEP. Also, your load order is unsorted. Use LOOT to sort it out. LOOT https://loot.github.io/ If game crashes from missing master due to USKP changes, then use this script with TES5Edit to swap masters. You need to do this before uninstalling old individual patches. You still need to sort the load order properly, before running the script. You can safely remove all old individual patches, once masters has been swapped. I would recommend keeping copies of them in your hard drive though, just in case you need to swap masters to some mod again. LOOT and/or TES5Edit will show which files are crashing from USKP being set as a master for them. USLEEP Swap Masters Script http://www.nexusmods.com/skyrim/mods/71316/?

You can stop the spinning by opening the console. That will halt the game and prevent screen chasing after your mouse cursor. Perhaps something has changed your keys from default settings. Go to ...SteamApps/common/Skyrim and open file enblocal.ini. Make sure that following keys (default) are set under INPUT category there. KeyCombination=16 KeyUseEffect=123 KeyFPSLimit=36 KeyShowFPS=106 KeyScreenshot=45 KeyEditor=13 KeyFreeVRAM=34 KeyBruteForce=66