The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.gg/taleoftwowastelands

NVSE Error log - Bug Hunting

General modding guides and authoring tutorials.
User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

NVSE Error log - Bug Hunting

Post by RoyBatty » Sun Aug 28, 2016 2:42 am

Often times your game will crash, and you have no idea WHY it crashed. NVAC can be helpful in preventing crashes, but the log doesn't contain useful information for the average to intermediate modder.


If you enabled the error log in NVSE, it can be of GREAT help in finding out what caused your game to crash. It can also help authors and users alike debug the mods they make and use. Bear in mind that not EVERYTHING in the log is an error, it could be just a warning, or giving some information on things that may be potentially buggy. Learning to read and understand the information present is on YOU to figure out, it's not hard generally as it's pretty verbose.


To enable the error log, go to your Data\NVSE folder. Open the nvse_config.ini , if it does not exist, create it. It is a standard text file. Make sure you have "hide known filetypes" disabled in your folder view options or you'll have a file with the wrong extension.


Add the following section and line with notepad or whatever you like.


[Logging]

EnableGameErrorLog=1


Save and exit. Next time your game crashes you can open this log and scroll through it and be amazed at all the stuff that is broken in your mods, and maybe find out what crashed your game. :)


The log will be named falloutnv_error.log in the Fallout NV root folder.


Image

paragonskeep
Posts: 738
Joined: Thu Oct 25, 2012 6:19 pm

Thank you Roy!!

Post by paragonskeep » Sun Aug 28, 2016 2:45 am

Thank you Roy!!


If life is but a test, where's the damn answer key?!?!?

User avatar
zilav
Gary
Posts: 225
Joined: Tue Apr 09, 2013 4:03 pm

Opened my config to check,

Post by zilav » Sun Aug 28, 2016 11:21 am

Opened my config to check, and also found this option though I don't remember what does it mean and where I got it


[RELEASE]

LogLevel=2

 



User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

[Release]

Post by RoyBatty » Sun Aug 28, 2016 9:00 pm

[Release]


LogLevel=5


Is what's in mine, got it from hlp, and I think it's for the debug version of NVSE but I'd have to ask him to be sure.


Image

anstand
Posts: 223
Joined: Tue Feb 11, 2014 10:41 am

Where exactly can I find the

Post by anstand » Mon Aug 29, 2016 7:12 am

I am getting a lot of these errors


Invalid LOD tree type 0 found. TreeTypes file may be out of date or corrupt.

Invalid LOD tree type 6 found. TreeTypes file may be out of date or corrupt.


Invalid LOD tree type 1 found. TreeTypes file may be out of date or corrupt.

Invalid LOD tree type 2 found. TreeTypes file may be out of date or corrupt.


Invalid LOD tree type 4 found. TreeTypes file may be out of date or corrupt.

Invalid LOD tree type 3 found. TreeTypes file may be out of date or corrupt.


Has that something to do with the duplicate tree bug?



User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

Anstand: no, if you have used

Post by RoyBatty » Mon Aug 29, 2016 7:19 pm

Anstand: no, if you have used LODGen you'll get that in your log, ignore it.


Image

User avatar
zilav
Gary
Posts: 225
Joined: Tue Apr 09, 2013 4:03 pm

If you have an empty *.LST

Post by zilav » Tue Aug 30, 2016 9:59 am

If you have an empty *.LST file that defines Tree Types in LOD for a worldsapce to disable Tree LOD, then *.DTL files that reference Tree Types from LST file will cause such errors.


FO3LODGen and FNVLODGen use that trick to disable original Tree LOD and replace it with better Objects LOD. Ideally you need to remove *.DTL files too to avoid such internal errors, but they are benign and you can safely ignore them as Roy said.



anstand
Posts: 223
Joined: Tue Feb 11, 2014 10:41 am

Any idea what might cause

Post by anstand » Sat Oct 01, 2016 8:07 am

Any idea what might cause this (not sure what this even is)?



FalloutAudioMedia Synch: 588 = abs(-/+ 112562 +/- 113150)

FalloutAudioMedia Synch: 599 = abs(-/+ 112562 +/- 113161)

FalloutAudioMedia Synch: 599 = abs(-/+ 112562 +/- 113161)

FalloutAudioMedia Synch: 601 = abs(-/+ 112562 +/- 113163)

FalloutAudioMedia Synch: 601 = abs(-/+ 112562 +/- 113163)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)

FalloutAudioMedia Synch: 507 = abs(-/+ 112562 +/- 113069)

FalloutAudioMedia Synch: 507 = abs(-/+ 112562 +/- 113069)

FalloutAudioMedia Synch: 508 = abs(-/+ 112562 +/- 113070)

FalloutAudioMedia Synch: 598 = abs(-/+ 112562 +/- 113160)

FalloutAudioMedia Synch: 599 = abs(-/+ 112562 +/- 113161)

FalloutAudioMedia Synch: 600 = abs(-/+ 112562 +/- 113162)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 601 = abs(-/+ 112562 +/- 113163)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)

FalloutAudioMedia Synch: 507 = abs(-/+ 112562 +/- 113069)

FalloutAudioMedia Synch: 507 = abs(-/+ 112562 +/- 113069)

FalloutAudioMedia Synch: 508 = abs(-/+ 112562 +/- 113070)

FalloutAudioMedia Synch: 508 = abs(-/+ 112562 +/- 113070)

FalloutAudioMedia Synch: 599 = abs(-/+ 112562 +/- 113161)

FalloutAudioMedia Synch: 599 = abs(-/+ 112562 +/- 113161)

FalloutAudioMedia Synch: 601 = abs(-/+ 112562 +/- 113163)

FalloutAudioMedia Synch: 601 = abs(-/+ 112562 +/- 113163)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 501 = abs(-/+ 112562 +/- 113063)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 502 = abs(-/+ 112562 +/- 113064)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 503 = abs(-/+ 112562 +/- 113065)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 504 = abs(-/+ 112562 +/- 113066)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 505 = abs(-/+ 112562 +/- 113067)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)

FalloutAudioMedia Synch: 506 = abs(-/+ 112562 +/- 113068)




User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

USB headsets

Post by RoyBatty » Sat Oct 01, 2016 8:07 am

USB headsets/broken sound engine


Image

anstand
Posts: 223
Joined: Tue Feb 11, 2014 10:41 am

So, ignore it?

Post by anstand » Sat Oct 01, 2016 8:22 am

So, ignore it?



Post Reply