[Wanderer]

No more error or warning messages so it must be bugfree! Or then perhaps not...

Basically it seems like the latest builds (tested taylor's 7th Dec and 28th Oct builds) have the error. Error and Warning popups do not work - well with notable exception of LuaErrors which still function. There are no popups even if the generated debug spew (fs2_open.log with debug_filter.cfg in place) shows plenty of (minor, like DDS) errors and warnings. Also i managed - by deliberately nulling all species_defs data - to cause the game to freeze completely without any warning or error messages - it just hanged into the loading screen.

I thought this was important enough to post it here.

[Zacam]

But the FSO log file is still being created, yes? So, no problem.

I rather LIKE the fact that the error no longer pops up, being an annoying fiddly-tard that I have to click through.

I just like to load, play, read the log file later.

[karajorma]

Those warnings should absolutely pop up in debug mode. They're an indication that something is wrong.

If you only want to play the game you should be playing the release build anyway.

[taylor]

The popups are disabled because they screw things up.  I'm going to replace them with in-game popups before 3.6.10 actually ships in order to fix all of the problems with switching out to Windows and back.  Everything goes to the log now, but that's more for us than for anyone else.

This isn't anything new though.  I disabled that stuff almost a year ago in my Xt builds, and made no secret about it.

[Wanderer]

Ok.. I hadn't heard anything about that and was kinda mystified by it when i tried to start debugging the 3.6.10 betas...

[Zacam]

No karajorma, I like to find out about bugs that are not absolutely show stopping after I've loaded through everything.

I love the idea even more of _in-game_ pop up's rather than "let's disjoint your perspective entirely by switching you into your desktop just to tell you about a missing frame.".

Yes, an error log on debug builds is essential, that is what debug builds are for. Absolute "the game is horrendously broken" should obviously indicate that to you, but again, if the majority of what your getting are the "hey, where'd my frame go?" messages, I'd prefer to read about later.

[karajorma]

Missing frames are one thing but Errors should absolutely pop up. As should major Warnings (like "This ship isn't actually in the tables so I'm making it a Ulysses"). It's ridiculous to allow the user to continue playing the game after a major problem like that with no warning.

Whether they pop up in game or like they currently do is a completely different kettle of fish.

[taylor]

Error() still works the same as it did before, since it kicks you out of the game and therefore the problems introduced by coming from a popup back to the game aren't an issue.  At some point I'm going to have those logged as well, when I eventually move the new logging code out of a secondary tree and into my main working branch.  It's only Warning() that has been changed. 

[karajorma]

Ah, if Error() works then that's much better. Not that it affects me anyway. I use my own builds for everything.