Advice fixing #13683 (DirectX mouse overlay?)

[Ken Thomases]

On Feb 16, 2014, at 3:06 AM, Christopher Thielen wrote:

> No luck so far: I ran the application for about 30 seconds and generated a 975 MB log file but a case insensitive "overlay" appears not at all.

To keep the log size down, you could try a warn+ddraw,warn+d3d,warn+d3d_surface log, instead.


> Since this missing secondary mouse cursor only appears during certain game states, one idea I had is to look at the 'fixme's in the log and see if any roughly correlate to when the cursor should be on-screen. This is assuming the log growth correlates to game-time, which it probably does with the exception of program start and stop.
> 
> I don't know if that's the next best way to debug this but there are two fixme lines that come up a lot (hundreds and hundreds of times):
> 
> fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00.

The wined3d_debug_location() function is used in other tracing lines.  So, to figure out what is affected by it, you would want to read the next line or two from the log.

> fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000

Same here.

These both may go away if you reduce the logging to just WARNs (and ERRs and FIXMEs which are enabled by default).  It's possible they were only be generated by TRACEs.

-Ken