 |
Thanks for have a look at this mister. |
 |
Working on this from time to time. Nearly done. Dmap uses the standard common->Printf interface. It has 2 levels of verbosity: the current default, which is very verbose. And an even more verbose alternative, activated by the "v" option. That option sets a flag in the dmapGlobals struct: dmapGlobals.verbose = true; I've changed it so that dmapGlobals.verbose isn't a boolean on/off, it instead holds a value from a new enum, so we can have more than 2 levels on offer: // Added in 0004123: "Unbind VSync from DMAP". // Allow more concise dmap to speed it up. typedef enum { VL_CONCISE = 0, // Suppress most console output, the new default VL_ORIGDEFAULT, // The default mode pre-TDM 2.04 VL_VERBOSE // The original extra-verbose mode } verbosityLevel_t; And I've added a new function to dmap.h, that dmap will use to send its console output: void PrintIfVerbosityAtLeast( verbosityLevel_t vl, const char* fmt, ... ); That function filters the output according to verbosity level. I've set most of the current dmap output to VL_ORIGDEFAULT. Some interesting header output plus a header for each entity processed will still be printed at the new default VL_CONCISE level. I still need to dmap a few maps picking out messages that I missed (dmap code is widespread). We don't use the dmap code outside of dmap itself, but in case we ever want to it'll still default to VL_CONCISE. dmapGlobals.verbose is a static variable so will get initialized to 0 (i.e. VL_CONCISE) even if dmap itself hasn't been called or initialized. I need to downgrade some warnings to mere messages, e.g. "backwards triangle in input!" -- which is normal dmap operation, and not a real warning situation. All remaining warnings will not be filtered. |
|
|
I'll also try to fix it so the console stays open, so the mapper can see the CM and AAS compilation steps. I'll need to add an "Open" command for the console, because the CM compilation needs to close it. |
|
|
I'll keep this open a few days pending feedback. Committed at rev 6500 /trunk/framework/Console.cpp /trunk/framework/Console.h /trunk/tools/compilers/dmap/dmap.cpp /trunk/tools/compilers/dmap/dmap.h /trunk/tools/compilers/dmap/facebsp.cpp /trunk/tools/compilers/dmap/map.cpp /trunk/tools/compilers/dmap/optimize.cpp /trunk/tools/compilers/dmap/output.cpp /trunk/tools/compilers/dmap/portals.cpp /trunk/tools/compilers/dmap/shadowopt3.cpp /trunk/tools/compilers/dmap/tritjunction.cpp /trunk/tools/compilers/dmap/ubrush.cpp /trunk/tools/compilers/dmap/usurface.cpp |
|
|
I'm marking this resolved despite suggestions in the forum for better and more meaningful output. Most of the junk still being spat out comes from different parts of the code that are not exclusive to DMAP and won't respond to the same method of controlling it. The issue itself is fixed: dmap is no longer affected by vsync, and as a bonus it's faster with or without vsync. If we want to improve it more later, we can. |
- Anonymous
