Has/Can this be done yet?

[urielmanx7]

Well, now that I got your attention, my question. 

 

So, well, you know that Skyrim has been out by almost 3 years now, and with the increasing amount of mods, also came an increased amount of the already many CTDs situations on the game experience, and the other day I was thinking, since tracking what of who is causing a CTD it's very difficult, I was wondering, if there's a program/mod/add-on out there that can at least tell you why did you game crash? We all know CTDs are rotted to unexpected things Skyrim cames across, like a missing mesh, or going overboard with the VRAM, so if there would be something that can detect the issue before the game closes, and make a log on what went wrong, like, it could be a program that monitors all the resources Skyrim is using (meshes, textures, files) and checking them against what it tries to load, so when a mismatch happens it records it so we know what went wrong; I think that would help inmensily modders and players alike I think, modders could make their mods more compatible, and players won't have to make thread after thread seeking help on CTDs.

 

I'm aware that I probably know the answer to my own question, but I thought it was at least worth the shot. This whole idea came from my experience in college when I used Visual Basic, there was a function on that software that was able to catch a type of error that made your program crash, like an incorrect input by the user, like a number where a letter was supposed to go, so that function made it possible to protect data from corruption for example, if you were doing a database program, and the program tried to close due to an unexpected data input or whatever, then you could just acknowledging the error and continue the process, without closing itself. So I wondered if something similar could be done here.

[h38fh2mf]

You can attach a debugger to any application but the information you get is too difficult to analyze without source code. You could make a guess perhaps in what section the exception occurred but it's not all that useful to know that for example the section is perhaps related to animations somehow.

[Spyder Arachnid]

Why not just use papyrus logging? It shows what is running and creates a log file, so if you crash, you can see what was the last thing that was running when you crashed.

 

Just open your Skyrim.ini and change these settings as follows:

 

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

 

Gotta run the game once to get it started, then exit and start the game again to get it running. But it will log everything for you so you can see what is causing errors and what is causing crashes. Then it's just understanding it and cleaning up your mods to get rid of the culprits that causes all the errors.

[...0...]

It have to do with how bethesda made the game modders can do little mods like safetyload are best to avoid annoying CTD/longloading screens.

 

Unless game is rewritten from scratch im affaid not much can be done.

 

But iwth right mods and carefully install mods that all work well together alot can be prefented.

 

Don't forget most who come on forums about CTD is becouse of lack and knowledge pc and installation and wrongly use of there system and just think install plug and play, well thats not how pc gaming works it will never be a console power and play.

 

Most just dont research nothing they think it all works right away but its not and come to forums making topics CTD PLS HELP

[...0...]

Why not just use papyrus logging? It shows what is running and creates a log file, so if you crash, you can see what was the last thing that was running when you crashed.

 

Just open your Skyrim.ini and change these settings as follows:

 

[Papyrus]

fPostLoadUpdateTimeMS=500.0

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Gotta run the game once to get it started, then exit and start the game again to get it running. But it will log everything for you so you can see what is causing errors and what is causing crashes. Then it's just understanding it and cleaning up your mods to get rid of the culprits that causes all the errors.

 

And even when you do that payrus it will still eventually crash payrus is only a tool see what happens thats all.

 

Even sjyrim vanilla with no mods at will crash eventually.

[Spyder Arachnid]

 

Why not just use papyrus logging? It shows what is running and creates a log file, so if you crash, you can see what was the last thing that was running when you crashed.

 

Just open your Skyrim.ini and change these settings as follows:

 

[Papyrus]

fPostLoadUpdateTimeMS=500.0

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Gotta run the game once to get it started, then exit and start the game again to get it running. But it will log everything for you so you can see what is causing errors and what is causing crashes. Then it's just understanding it and cleaning up your mods to get rid of the culprits that causes all the errors.

 

And even when you do that payrus it will still eventually crash payrus is only a tool see what happens thats all.

 

Even sjyrim vanilla with no mods at will crash eventually.

 

 

I never said it will solve your crashes. I said you can use it to view what is causing errors and then clean up your mods to get rid of the culprits. There is plenty of fixes online to fix the vanilla errors, so if you see any of those in your papyrus log, you can easily download the script fixes to clean those up.

 

Most crashes though are causing by mods, rather than the vanilla game. Papyrus logging helps you identify what is causing those errors and crashes, so you can remove/fix those mods that are causing it. Not sure what your objection is about it, as the OP asked for a way to tell what was causing issues and crashes in their game, and papyrus does exactly that. They didn't ask for an auto-fix program to fix everything, they wanted a logging program to identify what is causing their errors/crashes.

[Uriel]

From my experience, things that papyrus logs are completely irrelevant to CTD's i encounter. You can CTD every second with clean logs, and you can play with logs full of script errors.

[...0...]

 

 

Why not just use papyrus logging? It shows what is running and creates a log file, so if you crash, you can see what was the last thing that was running when you crashed.

 

Just open your Skyrim.ini and change these settings as follows:

 

[Papyrus]

fPostLoadUpdateTimeMS=500.0

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Gotta run the game once to get it started, then exit and start the game again to get it running. But it will log everything for you so you can see what is causing errors and what is causing crashes. Then it's just understanding it and cleaning up your mods to get rid of the culprits that causes all the errors.

 

And even when you do that payrus it will still eventually crash payrus is only a tool see what happens thats all.

 

Even sjyrim vanilla with no mods at will crash eventually.

 

 

I never said it will solve your crashes. I said you can use it to view what is causing errors and then clean up your mods to get rid of the culprits. There is plenty of fixes online to fix the vanilla errors, so if you see any of those in your papyrus log, you can easily download the script fixes to clean those up.

 

Most crashes though are causing by mods, rather than the vanilla game. Papyrus logging helps you identify what is causing those errors and crashes, so you can remove/fix those mods that are causing it. Not sure what your objection is about it, as the OP asked for a way to tell what was causing issues and crashes in their game, and papyrus does exactly that. They didn't ask for an auto-fix program to fix everything, they wanted a logging program to identify what is causing their errors/crashes.

 

 

No its good you point this out but only few will undertsannd what to do, most take this kind of info as if it solve there crash problem which it don't unless you realy take prefenting messures so you have less crashes.

 

Most should first do some research and read guides which many dont do this im affraid, it would prefend alot more frustration if they did.

 

Sorry if i said it wrongly english is not my first language ill prolly make not much sense with my sentence.

 

[h38fh2mf]

From my experience, things that papyrus logs are completely irrelevant to CTD's i encounter. You can CTD every second with clean logs, and you can play with logs full of script errors.

 

This. I played for quite a while so that papyrus log spammed 10 errors per second in log (I didn't realize). After little bit of playing log was 10-15 mb - no CTD. And then I get CTDs when there are no errors in papyrus log. Also the parts that actually do cause a crash aren't logged into papyrus because the game crashes first.

 

The log is good for finding scripts that are broken and it's very useful to let mod author know because broken scripts can cause some unwanted behavior in game and there are some papyrus commands that just crash if used incorrectly but don't expect to solve many CTDs using the papyrus log.