Is this a common problem for others?

[strawbqwerty]

It seem we may have a new bug with our new Skyrim. I am not the only one with this issue and I would like know if any one else is having the same issues. If your game is at a reasonable rate is C.T.D check you papyrus logs. There seems to be a issue with mods doing a maintenance and mod integration checks which should be OK in its self. If the mod can not find the mods it could possibly interconnect with it will run with out them. But it seems that new Skyrim has a issue with all this checking. For me It was Wild cat and I need looking for other mods. Another post indicates Wet and cold also was a issue. If enough people bother to look for this issue and indicate that they too have the same problem , then we may need to look at a solution. Not from me though I can just barely find these problems.

[DoctorKaizeld]

I have no idea what you're talking about

[MotoSxorpio]

I have no idea what you're talking about

Yeah, I'm lost too. Either REALLY BAD google translate or this is generated by a bot. <_<

[strawbqwerty]

Go to your documents open the folder my games then open skyrim special edition folder. In this folder you will find two files one is your Skyrim special edition ini and the other is your Skyrim special edition prefib ini. If you open your Skyrim ini then scroll down to a section with the heading Papyrus. You then enable logging, trace, and debug information. This creates a folder in documents / my games / Skyrim Special Edition / logs / script . There will be at the most four logs at any time. You need to check the first one. Scroll way down to the last few lines of text. This will be the last entries before the game stopped. These last lines should tell you what the game was doing at that moments before it stopped. You can note down these lines and have the game stop several times. Each time the game starts it generates a new log file so you can then see if the last entries are the same. If you have as I have and others have in the last lines of the papyrus log messages stating X mod is checking for integration with other mods then you have the same issues.

[DoctorKaizeld]

Oh the crash log? That makes a bit more sense

[cdcooley]

Oh the crash log? That makes a bit more sense

There is no crash log for Skyrim. The Papyrus log files are for script debugging and don't have any direct relationship to crashes. (Turn them off for better game performance.)

 

 

If you try to run mods from the original game in the Special Edition (or mods that weren't converted correctly) you'll have problems.

For me It was Wild cat and I need looking for other mods.

 

It's possible Wildcat wasn't converted correctly (but unlikely) or that it's interacting badly with some other mod (more likely) or you were trying the new experimental version that was just released and it actually has bugs.

[DoctorKaizeld]

 

Oh the crash log? That makes a bit more sense

There is no crash log for Skyrim. The Papyrus log files are for script debugging and don't have any direct relationship to crashes. (Turn them off for better game performance.)

 

there are crash logs. look up how to find/get them on google.

[cdcooley]

The only thing Google returns to me are links pointing to the Papyrus logging feature and the SKSE mini dump feature. Despite what mean people assume (and keep repeating to each other) the Papyrus logs are for debugging scripts and are virtually useless when trying to solve crash problems. The SKSE memory dump file is only readable by an expert, so it's pretty useless to the average person too.

 

Crashing for the original Skyrim is most often because of memory limits (which shouldn't be a problem for Special Edition) and mod conflicts. With Special Edition meshes and even textures that haven't been converted properly can cause crashes. The classic case of mod conflicts causing crashes are mostly related to one mod deleting some reference from the original game and then a second mod trying to access that deleted reference. The fix for that problem is to use SSEEdit to clean the mod with the "Undelete and Disable References" option.

[DoctorKaizeld]

 

Go to My Documents/My Games/Skyrim and open up Skyrim.ini.

Then add this:

[Papyrus]fPostLoadUpdateTimeMS=500.0bEnableLogging=1bEnableTrace=1bLoadDebugInformation=1

If the section [Papyrus] already exists, then you might add it without the section identifier. Next time you start the game you should see a new folder called "logs" inside that folder. And there is another folder called "scripts" and inside that 4 new log files.

the Papyrus log is not a crash log as you said but by doing the above you can acquire a crash log

[jones177]

Hi

 

Wet & Cold dose not have issues if you don't have Frostfall. It is fine with weather mods. If you have Frostfall the CTDs are random & a pattern will not show up over time in the Papyrus log.

 

Papyrus logs are good for spotting 3 way mod conflicts that may cause CTDs.

For example: Some of Ordinators pecks will cause CTDs when the player interacts with some NPCs that use modded magic but only when the player use magic that only conflicts when the other two are present. Meaning the perk, the certain NPC & the modded weapon.

This is the realm of the Papyrus log. Patterns will forum in the logs & you will either be able to fix the issue or avoid the issue.

 

All the CTDs I have had in this game have been from improperly formatted textures. If the mod has loose files I can fix them. If they use a BSA I remove the mod. These types of CTDs will not show up in Loot or the Papyrus log.

 

This game, like Fallout 4 is easy to mod free of CTDs, but you can't just pile them on. You need to add a few at a time & test.

 

Later