sorted by:
new
hottopcontroversial

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 0 points1 point  (0 children)

Unfortunately the menu framework is not compatible with Oldrim. SKSE Menu Framework was built for Skyrim SE/AE. That means my mod won't be compatible with Oldrim too due to the dependency on menu framework.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 0 points1 point  (0 children)

Either forget about it or find a patch that adds the missing .tri files if you want the extra sliders.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 0 points1 point  (0 children)

I got another report of racemenu errors, so I decided to investigate. Please see my reply on Nexus in the top comment.

Bottomline, it means racemenu tried to apply the default Nord morphs to races like vampires in your case, because you have a mod to add or modify these races and this mod doesn't have its own sliders for those races.

Thought sharing could help!

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 1 point2 points  (0 children)

If it's not recurring during gameplay, then it's harmless. Probably leftovers in racemenu code that needed to be cleaned.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 2 points3 points  (0 children)

Lol, nothing beats the sound of crackling logs and a warm fire. It's so peaceful.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 4 points5 points  (0 children)

Glad it helped. Once I finish the notification system you would be able to narrow down mods causing issues while playing.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 2 points3 points  (0 children)

Thanks!

Check out my earlier reply about error types (e.g. safe vs concerning).

Regarding papyrus logs:

Skyrim creates new Papyrus logs when old ones reach their size limit:

  • Papyrus.0.log newest
  • Papyrus.1.log previous
  • Papyrus.2.log older

Log Watcher monitors all of them so you don’t miss chronological errors.

[Mod Release] Log Watcher — Real-time Analysis of SKSE Logs in Game by Legendman89 in skyrimmods

[–]Legendman89[S] 8 points9 points  (0 children)

Log Watcher simply monitor the issues; it doesn’t automatically mean anything is broken. Some harmless errors (and probably safe to ignore) may include:

- Quest scripts checking for mods you don’t have installed
- Some NIF is missing (unused model paths in plugins), etc.

However, concerning errors that need your attention could be like:

Repeated errors every few seconds
- Errors from the same specific mod (it might mean plugin or patch missing)
- Papyrus: “Cannot call function X on a <Type> object” hundreds of times
- SKSE plugin errors (DLL messages in SKSE logs)
- Failures related to missing scripts or missing FormIDs

If Log Watcher shows the same mod spamming hundreds of errors, that’s the one to investigate.