Question On Hitboxes
NGE
Join Date: 2003-11-10 Member: 22443Members
Join Date: 2003-11-10 Member: 22443Members
<div class="IPBDescription">Orginally posted by Nem0</div> <!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->From what we have gathered, the hitbox issues do in all likeliness not go back to our changes. Valve did a global update on HL netcode lately, which is why other big mods report minor hitreg issues (us being, as usual, significantly more affected), as well. Seeing that a) we have no clear lead, b) the ball might not even be in our court, and c) there're those 90.000 players out there who don't have access to the new version, we'll continue to investigate the issue, but not make changes in time for 3.0 final.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If this is true then why does Beta 5 lack the hitbox problems of beta 6?
If this is true then why does Beta 5 lack the hitbox problems of beta 6?
Comments
Thank you for clearing that up. It would seem that the problems are indeed on the NSDev's team end then. Good luck to figuring them out!
Thank you for clearing that up. It would seem that the problems are indeed on the NSDev's team end then. Good luck to figuring them out! <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Nem0 said that the new hitboxes will NOT be in beta6 (and thus probably wont make it in time for 3.0 final) but that they'll try to get them to work for (probable) 3.1 release.
You mean 4.0 right?
If this is true then why does Beta 5 lack the hitbox problems of beta 6? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
I questioned this too in a thread once. Never got an offical response. I remeber flayra said that he though it was a HL update. I qutoed him and asked him that if it was, it would have affected all Mods (and therefore B5) and that the last update was the one that got rid of the "last slot lagger" and B5 has been fine eversince.
Its obviously something in B6 thats causing the problem.
Beta6 was NEW code, and apparently from testing found to be buggy as all hell. They are trying to work the bugs out, but as for a public release, they want to go final on 3.0 ASAP, so they are going to leave the buggy new code out, and if they can find a fix, patch it in.
<!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Model clipping & the hitbox issues are not the same thing.
Incidentally, all the HL mods DO get some form of hitbox erroring, I've found. It's just NS brings it to the point where it's very noticeable simply because of the greater speed things travel at.
- Shockwave
First, thanks for the galling sarcasm, NGE. I appreciate it <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif' /><!--endemo-->
Second, what is the current situation, hitreg-wise?
We had serious trouble with the new hitreg code up until the first Constie release. Since no leads on the issue could be unearthed, we rolled back to B5's code. Since then, there are no big problems (aside from those you already know and that prompted us to do that code update in the first place) reported. A number of Consties and low ping - high skill PTs did however note that "something is a little off" for one reason or another. This is what my initially quoted comment was aimed at. There was a rumor of a small tweak on Valve's side going around at the time. This hasn't materialized into any more concrete form since then.
Third, Source. One of the main reasons we're still holding back on a final decision regarding the Source port is that there is currently no multiplayer physics solution, nor a MP hitreg solution in place. HL2DM uses singleplayer code for this and CS:S is based on homebrew code if I'm not mistaken, which might explain a few things to many of you. These updates <i>will</i> come, but until they do, Source is just not a really viable platform for a multiplayer game.
Fourth, 3.1.
Ho, ho, ho, another .1 iteration? <b>Ho </b>ho ho. More like version X+1.0, <b>ho ho ho</b>.
Funny. And so original.
The matter of fact is that with the current Source situation, we have to bridge a certain gap. Seeing that 3.0's balance, while, as usual, not perfect, shapes up to be at least solid enough to go for two to three months (with the possible help of a little strictly reactive balance tweaking, of course; we'll see), we decided to invest a little time into some 'trimming'; into a few not necessarily gameplay-centric things that we wanted to include for a long time, but could just not justify putting in over bigger internal issues. In other words, 3.1's scope will be decidedly smaller than that of the previous .1 iterations. Plus, this time it's me deciding when to stop and release, and as everyone in here can attest, I'm significantly bigger a jerk than Flayra...
Almost every patch I've seen discussed before released ends up being about 10x bigger then they planed. Stuff all ways seems to get added, maybe Nemesis Zero will be better at resisting that temptation.
Thats the first I've heard souce does not have a sever side hit-registration, though I'm not really up on all the technicle details of the engine. Client side seems so exploitable...
Do we know anytihng about DoD:S yet?
will it still be ussing the homebrew of CS:S?
Is it gona use an updates Sourse netcode/hitreg/WhatEverIsn'tInSourceATM