View Issue Details

IDProjectCategoryView StatusLast Update
0004153The Dark ModSEEDpublic25.07.2015 02:39
Reporternbohr1more Assigned Tograyman  
PrioritynormalSeveritynormalReproducibilityalways
Status resolvedResolutionfixed 
PlatformALLOSALLOS VersionALL
Product VersionTDM 2.03 
Target VersionTDM 2.04Fixed in VersionTDM 2.04 
Summary0004153: SEED Console Spam
DescriptionSEED currently produces large amounts of console messages which can make it troublesome to debug maps that use it. Further, as demonstrated by the recent DMAP vsync fix, console messages can have a non-negligible impact on performance so the spam may be eroding part of SEED's core purpose (optimization).

The current implementation appears to be a byproduct of the early unreliable nature of the feature where there was a need to constantly monitor it's actions to track down bugs.

SEED has proven to be reliable in many released maps over many TDM build versions so constant debug messages should be reserved for debug binaries only.
Steps To Reproduce1) Begin any map with an active SEED entity
2) Note continual console spam about SEED events
TagsNo tags attached.

Activities

grayman

grayman

24.07.2015 21:18

viewer   ~0007666

I've begun wrapping the spam in debug-only wrappers, since my current WIP has a LOT of SEED in it, and I finally got tired of not seeing what was behind the spam curtain.

Since I started, I'll finish the job.
grayman

grayman

25.07.2015 02:38

viewer   ~0007667

Last edited: 25.07.2015 02:39

Fixed in rev 6521.

The SEED code was using a variety of ways to suppress the messages:

1 - messages were commented out

2 - messages were controlled by the value of a variable

3 - messages were controlled by a couple of #defines.

4 - print all the time

Rather than bringing uniformity to this (too much work), I just added another #define, S_DEBUG to handle case 4. To get any SEED spam now, a special DLL needs to be built for whoever's having a problem.

Issue History

Date Modified Username Field Change
21.05.2015 01:03 nbohr1more New Issue
24.07.2015 21:16 grayman Assigned To => grayman
24.07.2015 21:16 grayman Status new => assigned
24.07.2015 21:18 grayman Note Added: 0007666
24.07.2015 21:18 grayman Target Version => TDM 2.04
25.07.2015 02:34 grayman Status assigned => resolved
25.07.2015 02:34 grayman Resolution open => fixed
25.07.2015 02:34 grayman Fixed in Version => TDM 2.04
25.07.2015 02:34 grayman Additional Information Updated
25.07.2015 02:38 grayman Note Added: 0007667
25.07.2015 02:38 grayman Additional Information Updated
25.07.2015 02:39 grayman Note Edited: 0007667