I've given the matter some thought, and right now it's looking fairly likely that a Release 1.7.3 actually is going to happen. There are a few places in the recent code where I haven't set things up as cleanly as I would have liked, and so I want to go back and rework them. I also want to fix the name maker. These should have all been done for 1.7.2, but it ended up not being so owing to the requirement to get a bug fixed version out sooner rather than later.
I might also bring some of the changes I have planned for 1.8 forward to it, just so that there's a little bit more present than mere tightening up of code. This would also mean that 1.8 would contain less radical overhauls of code, meaning that it would be simpler and therefore less bug-prone, which is all good stuff.
So until you hear otherwise, you can assume that 1.7.3 will appear sometime towards the end of October or early November.
Tuesday, September 29, 2009
Next Release News
Posted by
mhquake
at
4:55 PM
Subscribe to:
Post Comments (Atom)
3 comments:
hi again, good stuff so far!
(i have not tested properly but 1.7.2 seems to run smoothly on the rather crappy GF5200FX card i did a quick test on)
from what i read here, it seems the timer for sv_cullentities uses a hard-coded value of 0.2 seconds..
i wanted to point out that most european servers run on a 0.015 ticrate, so maybe that trace-timer should never be more then the sys_ticrate to prevent flickering/artifacts?
keep up the good work!
k.r. =peg=
I think if it's higher than the ticrate it should be fine as entities will always be in the future. Lower would cause flickering.
It's only a problem if you're using DirectQ as a server anyway, which is something I wouldn't recommend owing to certain changes there.
ah i see.. that makes sense :D
(i just wondered about it, since baker will most likely adopt the same code for proquake4.x)
=peg=
Post a Comment