[FUBAR-BDHR]

Forgot to change from debug to regular build when playing multi as a client.  I do have th -no_warn flag set and while the game didn't crash the screen kept minimizing over and over again.  It would auto-restore back to full screen.  I think it's doing it when it is writing warnings ans some other things to the log file.  !PAIN being one of the suspected culprits whatever that is.  Not really a bug since it's a debug only thing but can it be changed so the game doesn't loose focus?  It wold be a pain in the butt if you ever need to track a client side bug down. 

[karajorma]

I'll try take a look but I've been very busy the last few days. I'm not entirely sure why we write !PAIN to the network log anyway though so I might comment out  that line while I'm in there.

[FUBAR-BDHR]

Yea I'm sure there are a lot more important things then this.  Just thought I'd mention it before I killed the brain cells it's residing in. 

[FUBAR-BDHR]

Noticed last night this also happens on the host side when the client changes weapons in the loadout screen.  Seems to be when the .ani load messages are written to the log file. 

[taylor]

Found what is most likely the problem: the Assert() macro.  The macro calls gr_activate(), which will minimize/maximize the screen, but it doesn't actually need to do that since it's called in the actual assert function as well.  A quick change to the macro and to the WinAssert() function to log properly with -no_warn should be all that's need to fix it.

I'll get those changes in SVN later today.


Oh, and was there a Mantis bug on this?

[FUBAR-BDHR]

No I never put it in Mantis since it was a debug mode only thing.