https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alberto Salvia Novella from comment #2)
We could make the documentation to clarify that, because I thought that TRACE was the highest priority.
FIXME usually is the one causing trouble, as it spams the same message over and over again in some games. For example if certain texture has a failure, it will spam the message for every loaded texture.
Most likely only ERR is relevant to the average user, so to let them know why the software stopped working.
WINEDEBUG=warn-all,fixme-all,trace-all
The only thing that the average user should really care to see is anything in the "winediag" channel, which is always ERR. So really the recommended usage should be WINEDEBUG=-all,+winediag or -all,err+winediag. I'll edit the page to try to make this and some other things clearer.