MQ2 debug spam?

[flatlined785]

Any chance of stopping the debug output spam MQ2 makes? -
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0


.. looks like it happens once per frame. Makes watching debug output pretty annoying ;p

 

[htw]

Any chance of stopping the debug output spam MQ2 makes? -
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0
[14368]
[14368] [MQ2] List: index is 1
[14368]
[14368] [MQ2] List: index is 0


.. looks like it happens once per frame. Makes watching debug output pretty annoying ;p

Yes. In your macroquest.ini, under [MacroQuest] section, set (or change): FilterDebug=1

Save and restart MQ2.

htw

 

[flatlined785]

Thank you! That's so much better

 

[eqmule]

If it happens once per frame you should probably figure out WHY it does it cause that will slow you down even if you "filter" it out.

 

[flatlined785]

I agree, but it's part of the build from this site, not my personal compile.
Maybe one of the plugins, maybe core, but again, all from here.

 

[Fry]

I agree, but it's part of the build from this site, not my personal compile.
Maybe one of the plugins, maybe core, but again, all from here.

Start unloading plugins one by one ingame, and see if you can figure out which plugin is causing it. If you can figure it out, let us know and we should be able to resolve it.

 

[htw]

Something is referencing the List member of the Window TLO. We don't need the debugspew call, so I took it out of our build for next release (it's part of core code).