Bite bite bite, not dead :(
dePARA
Join Date: 2011-04-29 Member: 96321Members, Squad Five Blue
I dont know if this is an real issue or only imagination.
But since 267 i miss so many bites, so many swipes.
I read a few post in in forum that other players have the same problems so there might be an hidden issue.
Example:
Marines have armor 1.
I was able to sneak behind 1 marine running straight in an long corridor whitout jumping.
What happened?
Parasite, bite, bite , bite (i turned around cause i was 100% sure he is dead, ok not dead), another bite (oops a bite in the air, but i was only 1 meter away). Im dead.
This happen so often in 267 now,cant count. I play this game a while (3,5 years), never had that before.
Its like the hitbox is 1 meter behind the physical model.
I tried it with physic multicore and without, no difference.
Has someone the same issues?
But since 267 i miss so many bites, so many swipes.
I read a few post in in forum that other players have the same problems so there might be an hidden issue.
Example:
Marines have armor 1.
I was able to sneak behind 1 marine running straight in an long corridor whitout jumping.
What happened?
Parasite, bite, bite , bite (i turned around cause i was 100% sure he is dead, ok not dead), another bite (oops a bite in the air, but i was only 1 meter away). Im dead.
This happen so often in 267 now,cant count. I play this game a while (3,5 years), never had that before.
Its like the hitbox is 1 meter behind the physical model.
I tried it with physic multicore and without, no difference.
Has someone the same issues?
Comments
But a least there is an issue and im not totally mad
While running behind another player I've noticed a lot more position correction and warping.
If you notice any kind of those issues: enable net_stats, cheats 1 + collision damage and look how colision updates with the players movement with having a look at possible network and server issues (net_stats will show those ways better in 268 than in any build before)
Good news is that with 268 the collision updating will improve a lot so it will be as exact as never before
And at the same time, I've been moving at high speed past a marine, turned sideways and bit him from over a meter away- almost as if the server was taking into account my speed and then putting the bite cone way out in front of the direction I was facing without regard to whether or not I was facing the direction of travel. But what do I know
@GhoulofGSG9 I hope these changes will have some effect on this, it sounds like they might.
5 bites from behind. Mr Marine A0/W0 do a 180°, booya! skulk dead. hmmm Wait a minute.
On marine side I'm not the best shot but not the least.
I open fire at a skulk and hear the bip sound that confirms the bullet hits (on my side at least). Then more bips... and half the clip is gone. Then more bips... and the clip is gone. ok, i draw my gun. some more bips. So many bips and no skulk died... Ok i play with nasty bastards like I am but sometimes i feel it can't be real.
I tested my map with bots and it's the same. Some "out of alignment" stuff.
It would be good to have a system like mobile phone (1 to 5 bars) to get a better idea of ping/cpu related issues. It can be on the score board or on a status command.
What i mean is, you can have :
good/bad ping
good/bad FPS
good/bad server tick
It would be nice to be able to measure other things like the real delay (network + server computation lag) between players. If not fixed on the performance topic; at least we would be able to measure/compensate and play accordingly.
Hit sounds and draw damage is server side - if you hear those sounds you definetely connected. You may be conditioned to placebo or confirmation bias.
I'm not saying there's not a hitreg issue, far from it, but I'm fairly certain that the server-side hit indicators are very accurate.
@UncleCrunch
What you described is a pack of skulks waiting for you.
So you hit 3 or 4 skulk but from your point of view it was only one.
And with regeneration the already chipped skulks are back in business in around 15 sec.
The other day I crept up on a gorge and fired a whole clip in to him only to do 310 damage with 62% accuracy. Where the other 19 bullets went I will never know but 19/50 is an unbelievably substantial number of bullets to not register.
I once had a lerk "W" into me and the first 3 pistol shots didn't reg but the next 7 did. Literally no change in movement from him or me in movement/mouse orientation. Blood check, damage missing...
I understand the good intentions the CDT has and that volunteering their time is very kind of them, but since b267 my gameplay experience has been hurt more than fixed.
I alt-tab with a 50-50 chance of crashing. Previously I never crashed on alt-tab.
I get so many more rifle-jam bugs than previously. Previously I was lucky enough never to have rifle-jam.
The hit reg is so much worse than before.
Alt-tabbing I can learn to not do but it's frustrating.
Rifle-jam is annoying but I can kind of deal with it.
Consistently poor hit reg just ruins the FPS experience and surely is the key component of the FPS side of the game. To ruin this is almost criminal.
Like I said, I appreciate the intentions of CDT, but for me at least, the actual results of the CDT have been bad to put it simply.
I've watched your stream sometimes, and I'll confirm that it's definetely not in your head. I've had some hitreg issues myself, but on your end it seems particularly severe from my point of view.
Slippity Slope Selection 2.
In that, Hit-reg keeps falling off the edge - and it keeps loosing it's icepick.
Trust me, it'll be fixed next patch - broken the one after.
Are you joking? It's not about proof. I'm sure the CDT are aware. It's about getting a clue to where the problem is.
For f sake people...
last patch I took the first time 20mins and the 2nd 1hour of testing without any mods, on a local server, with netstats and rstats on. I could reproduce, record, show and report.
Know what the hardest part of that was? Waiting for the bug to finally appear. Recording the bloody thing was a simple as 'press F10 to start vid' with fraps. (I also supplied plogs)
Everywhere here is always complaining about hitreg, yet noone bothers to invest the time to just record a vid with netstat and report.
Ive seen folk complain ingame and on forums complain about this issue, for far far more time investment then a video record would take.. unbelievable.
Ive reported bugs in the past and I dont always have to supply vids. They ask for vids IF NEEDED.
Im done with this topic.
And it's not just UWE or the CDT. How many times have you seen people exploit Call of Duty? Or graphical glitches in Dota? Even after patches? AAA devs have the same issues.
This is a game. Things happen. Bugs appear and glitches are found.
Welcome to gaming. Get over it.
ironhorse and the CDT know that the issue is there , pinpointing it is the issue. Videos provided as evidence will help us reproduce this. This is where you, the community, can help shape this great game. Thank you.
PSA might help reduce the number of complaints about this issue then.
This is silly. Of course you can be negative and critical of mistakes and poor implementation, it's one reason why developers and teams of any description work to make sure their stuff is decent quality; so they don't get negative remarks.
Bending over when hit registration (no 1 important thing in FPS gameplay) gets ruined is ridiculous. You can't expect no outburst.
Also people shouldn't necessarily hold their standards to other flagships in an industry. They should aim to be true to the highest standard possible regardless of what competition is offering.
I expected the volunteers to do a worse job (in terms of actual implementation) than paid professionals. I appreciate CDT efforts, but it doesn't stop me being disappointed when they do change something important badly.
Hey RejZoR, somewhere I have buried treasure. I promise that it's there. Other people have verified that this treasure exists. And I'll even tell you it's within the continental US.
That's not a very helpful list of clues is it? That's what you're telling a coder when you say "There's a bug that happens sometimes." The great majority of bugs only appear when certain criteria are met, like a satanic rube goldberg machine. It may only apply to people who have X wireless card, or when server load is greater than X, or when the commander has more than 5 drifters, etc etc.
But now you're saying "But tons of people have seen this issue!" and you're right. That's because a bug may not have anything to do with PC hardware or software, and is in the game itself. An ongoing game has hundreds if not thousands of variable changing every second. Player HP, player count, ping, unit count, lighting levels, mods, player positions, and so on. So the magic recipe for a bug may manifest for only a few seconds in the middle of a game, and quickly disappear again. Only to appear again the next time Jupiter, Uranus, Alpha Centari and Iceland are in perfect alignment. Which could be 8 seconds later, or never.
That's why they want to know the net_stats data, the server load, your hardware and software setup, etc. They can better identify the conditions that the bug appears in. You're building the CDT a map, giving them a search area.
"Ok, the treasure is in Nevada, north of I-80, west of the 95. It only appears on sunny days on leap years" is an impossible sounding task, but much much easier than "Somewhere in the US."
Recordings and such aren't just about proving whether or not a bug exists, but WHERE it exists.
It's been quickly noted in the live build how hit reg is poor for multiple players at multiple levels. How this can get through playtesters is mind boggling because shooting/biting is the staple of the game. If the patch was pushed through with knowledge of hit reg issues, that's poor implementation.
Like I said earlier, sure alt-tab is annoying, and sure rifle jam is frustrating, but simple hit reg is a serious infringement of basic gameplay which you can't just pass off as "part of gaming"
PSA: All videogames have hitreg issues, thats inevitable, no code or network/ client/ server/ connection conditions are perfect.
I havent personally encountered any obvious hitreg issues in NS2. Cant say that for many other games.
The fact that people claim theres hitreg issues but theres been no video proof presented makes me skeptical.
There is video evidence on twitch, you'd just have to sort it out cuz nobody highlighted it. But I've seen it on wobs and sykniks channel before. Strangely enough, on wobs channel it was mostly on marine side, while on sykniks it was mostly on alien side and a lot more rare compared to wobs.
Oh and let me add. It's not strange that there is not much video evidence, for the same reason that there are hardly any streamers. The game simply doesn't have the optimisation that allows for people to maintain a high enough framerate that they can actually play the game well while streaming.