PsychoYoshi Posted December 15, 2023 Posted December 15, 2023 Updated today on Nexus. Version 1.12.0 # [1.12.0](https://github.com/alandtse/CrashLoggerSSE/compare/v1.11.1...v1.12.0) (2023-12-15) ### Features * add support for SkyrimVRESL ([3ce7829](https://github.com/alandtse/CrashLoggerSSE/commit/3ce782980148f554c77809735032ea7bfe6943ee))
Mercury71 Posted December 22, 2023 Posted December 22, 2023 Updated on Nexus: Version 1.12.1 ## [1.12.1](https://github.com/alandtse/CrashLoggerSSE/compare/v1.12.0...v1.12.1) (2023-12-22) ### Bug Fixes * fix log directory for AE 1.6.1130 ([2f20505](https://github.com/alandtse/CrashLoggerSSE/commit/2f20505f2fd383d1758eab7782daf539da4b8c52))
z929669 Posted December 23, 2023 Posted December 23, 2023 9 hours ago, Mercury71 said: * fix log directory for AE 1.6.1130 ([2f20505](https://github.com/alandtse/CrashLoggerSSE/commit/2f20505f2fd383d1758eab7782daf539da4b8c52)) This is good. I noticed that crash reports were not being made since the update.
Mercury71 Posted December 23, 2023 Posted December 23, 2023 6 hours ago, z929669 said: This is good. I noticed that crash reports were not being made since the update. A bit OT but i have not yet updated the game to 1.6.1130 since i am in a playtrough. Do you think i can update my game and STEP? Or should i wait until more mods are updated or i am ready to stop playing my current save?
z929669 Posted December 23, 2023 Posted December 23, 2023 4 hours ago, Mercury71 said: A bit OT but i have not yet updated the game to 1.6.1130 since i am in a playtrough. Do you think i can update my game and STEP? Or should i wait until more mods are updated or i am ready to stop playing my current save? I would wait for the supposed next Bethesda hotfix update.
ButchDiavolo Posted December 23, 2023 Author Posted December 23, 2023 2 hours ago, z929669 said: I would wait for the supposed next Bethesda hotfix update. I agree completely. History teaches us that Bethesda WILL put out a fix to fix the fixes they fixed after a few months. And then this starts all over again. I am good staying on 640 for the time being. At least I know all the mods I am using work. 1
Mercury71 Posted October 13, 2024 Posted October 13, 2024 Version 1.15.0 # [1.15.0](https://github.com/alandtse/CrashLoggerSSE/compare/v1.14.1...v1.15.0) (2024-10-12) ### Bug Fixes * fix clobbering of privateResult ([9004231](https://github.com/alandtse/CrashLoggerSSE/commit/90042315817398d2a65b0f9c4843a56d6ba8c618)) ### Features * demangle symbols ([0d116c6](https://github.com/alandtse/CrashLoggerSSE/commit/0d116c6857c34d15b9ccd2ed2e28cc80bd2fe35e)) * expose more exceptionrecord info ([f2e606f](https://github.com/alandtse/CrashLoggerSSE/commit/f2e606fb058f55455b2198086ce9f39e5e5d3b06)) * fix path handling using utf-16 ([d5c0951](https://github.com/alandtse/CrashLoggerSSE/commit/d5c09517603d0487dc3a739d6e2b66264e746822)) * use SEH translator ([9806785](https://github.com/alandtse/CrashLoggerSSE/commit/980678596f9e68ecb479b29cec3393d295b795c2))
Bushranger Posted November 25, 2025 Posted November 25, 2025 I've found that Skyrim Crash Decoder is an excellent tool that vkukko123 has made. Go to the website, paste the crashlog into it so it can generate a report that is much easier to read and understand. I couldn't decipher the crash report I got tonight while going through Helgen but this tool helped a lot.
Gothkatiel Posted December 26, 2025 Posted December 26, 2025 (edited) My crash logs from 1.16 version of this mod (updated, btw) appear to be extremely truncated compared to others I find online, even at log level 0 (trace). (I've also (somewhat blindly) changed SSE Engine Fix's bVerboseLogging to true with no noticeable effect.) I'm completely unsure why my logs look this way and would appreciate some help with that. Edit: forgot to add, this may be of some help? Edited December 26, 2025 by Gothkatiel
z929669 Posted December 26, 2025 Posted December 26, 2025 9 hours ago, Gothkatiel said: My crash logs from 1.16 version of this mod (updated, btw) appear to be extremely truncated compared to others I find online, even at log level 0 (trace). (I've also (somewhat blindly) changed SSE Engine Fix's bVerboseLogging to true with no noticeable effect.) I'm completely unsure why my logs look this way and would appreciate some help with that. Edit: forgot to add, this may be of some help? Apparently, you don't have a crash. You posted the Crashlogger SKSE log it seems.
Gothkatiel Posted December 27, 2025 Posted December 27, 2025 (edited) 3 hours ago, z929669 said: Apparently, you don't have a crash. You posted the Crashlogger SKSE log it seems. First link is (should be) the game's crash log named crash-2025-12-25-10-38-45.log. Second link is to the Crash Logger's nexus page for the changelog. Third link is the Crash Logger's log (named CrashLogger.log) that I'm hoping might help to explain why my game's crash log is so... the way that it is. Edited December 27, 2025 by Gothkatiel
z929669 Posted December 27, 2025 Posted December 27, 2025 17 hours ago, Gothkatiel said: First link is (should be) the game's crash log named crash-2025-12-25-10-38-45.log. Second link is to the Crash Logger's nexus page for the changelog. Third link is the Crash Logger's log (named CrashLogger.log) that I'm hoping might help to explain why my game's crash log is so... the way that it is. I see it now. Yeah, that crash log was truncated for some reason. That's not typical, so you may want to reinstall the mod and/or research your issue on the mod's Nexus pages.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now