DirectQ

[Magnus]

The FPS issue doesn't affect me, I was just bringing it to your attention, but it seems like you know whats up.

I remember proquake did that console print thing as well with the tab, just didn't display it. I'd REALLY like it if I could simply disable the console report all together when I hit tab. This way its easier to look over recent loc reports from players, etc..

con_notifytime works great!

Any way to make it display more than 4 messages at once?

The only other thing I could think of is the ability to type longer messages in chat.

Thanks!

[MH]

The number of console messages is hardcoded into the engine, so it can't be changed at present, but it's a good idea and one that I'll definitely do.

I'm definitely fixing the spam from hitting tab, don't worry about that.

I've also made previous attempts to increase the chat buffers but seem to have failed. One to look over again.

[=peg=]

I've also made previous attempts to increase the chat buffers but seem to have failed. One to look over again.

Actually, that one works fine for me

Oh and did I say THANK YOU yet? Well THANK YOU anyways

[Magnus]

ISO new DQ release W/DM fixes so I can RA3P, pst w/DAIT!

KTHX!

[R00k]

I think it was Smokey who asked, the console was constantly filled with centerprint messages over and over..
scr_centerlog is default to 1. The menu on ClanArenaX servers are centerprinted so you will get alot of console text there. Just set that cvar to 0 and all is fine.

[MH]

New release just out by the way; this one should fix the .loc file issues that some have reported. I did inadvertently leave in a "loaded %i locations" message on map load (that should have been silent) but it doesn't affect gameplay so for now I'm not too bothered. I'll remove it in the next one.

I think it was Smokey who asked, the console was constantly filled with centerprint messages over and over..
scr_centerlog is default to 1. The menu on ClanArenaX servers are centerprinted so you will get alot of console text there. Just set that cvar to 0 and all is fine.

There isn't a one-size-fits-all default for this one unfortunately. Center print logging was actually on request from an MP person, yet here we have a clear case where it's not desirable. Right now I don't log a message if the last one recieved hasn't yet been cleared. That should relieve a lot of the console spamming but there will be still corner cases where this doesn't quite work for everything. Pushing this behaviour out to another cvar is - IMO - offloading responsibility for something that I should be doing right on to the player, and that's unacceptable to me.

With hindsight this might have been a case of "when in doubt err on the side of doing what ID Quake did" but I fear it's too late for that, and removing centerprint logging would generate more complaints than leaving it in (but flawed).

[R00k]

The "motd" in CAx is printed every 1.8secs. Anything greater than this and it blinks, less than this and it just spams the client.

I'm not sure how fast RuneQuake displays it's centerprint menu though.

[Magnus]

Yea scr_centerlog 0 is what I used to have to avoid console spam, and it seems to work again.

The HUD in cax and crmod do not print to the console with this newest version.

locs also work.

This is the new directq version I'll use to DM.

Thanks!

[Spike]

if it contains more than 2 newline chars, don't log it, perhaps?

or log them only when the centerprint times out (or changes) rather than for each new one, though that'll break really quickly with CuTF still.

quakeworld has so many centerprints messages and menus and things that logging them on the console is somewhat futile.