Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
It only reveals crashes if you're crashing because of Papyrus, which is pretty much just edge cases.
If the game has made an bad call to Windows you can find these in Windows viewer, but again you can't control why the native game made such a call.
I am guessing you are looking for mod crashes. For this you need to use Mo2, Loot and xEdit. These also won't give you a crash report per say, but will warn you about conficts with the mods.
Also about crash reports(if they could even be retrived) would only tell you the ML address in which the fault occured. This info is usless because you don't have the games sourse code.
This is the real reason there is no such thing as crash reports. To get the line you crashed at would require you to be monitoring the code at the time. (which as I mention is not available)
The game itself has such a tool(in-game console) but when you crash so does it.