Author Topic: debug spew  (Read 1451 times)

0 Members and 1 Guest are viewing this topic.

Offline Bobboau

  • Just a MODern kinda guy
    Just MODerately cool
    And MODest too
  • 213
I was wondering how do I add stuff to the debug spew?
like if I want to make sure a value is set to what I think it should be at a certan time, it'll get tossed up out into that little window and\or the log
also anything about the debug spew I should know, like what all goes into the Debug_filter.cfg

and post anything alse along the line of debug stuff too
Bobboau, bringing you products that work... in theory
learn to use PCS
creator of the ProXimus Procedural Texture and Effect Generator
My latest build of PCS2, get it while it's hot!
PCS 2.0.3


DEUTERONOMY 22:11
Thou shalt not wear a garment of diverse sorts, [as] of woollen and linen together

 

Offline penguin

  • Eudyptes codus
  • 28
  • Still alive.
1. you have to use the debug version; it's not compiled into the release builds

2. use the mprintf macro.  It works like printf(), except you must double your parentheses:
Code: [Select]

mprintf(("%i frames executed in %7.3f seconds, %7.3f frames per second.\n",
      Framecount,
      cur_time - Start_time,
      Framecount/(cur_time - Start_time)
));

I fixed an issue that was preventing it from being written to the logfile, it might be related to the Debug_filter.cfg file -- I assumed we can write everything to the file, and filter afterwards...
your source code slave