GDFireFrog

A similar fix for projectiles is coming shortly, thanks for your patience.

Sorry, child game.

An issue with /gg was brought to our attention so we disabled it temporarily, but we'll bring it back.

TY for reply

You are welcome. And fair enough Mr_Picky, I see you are not ready to accept my theory that the package loss issue is making you think all that. Let's agree to disagree, and I will keep your advice in mind :)

Don't get heartbroken yet man :) We are gonna add a lagometer to the game, when we do if you haven't given up on the game feel free to drop me a screenshot on DM either on Reddit or on Discord. I think you must have some packet loss issues that are exacerbated by an issue that we are planning on fixing. Whatever the case, we'll get it fixed.

Yeah I know the issue, just collecting evidence, that way when it's fixed we can go through all and check that they all match what has been fixed.

Pretty sure in most cases this is about the way we present projectiles/beams in 3rd person. They come from the actual muzzle of the rocket launcher in the case of the rockets as the weapon is animated at that moment. This makes it so that you can get rockets going through corners if the weapon of the shooting eggbot is occluded by the corner. The severity of this is exacerbated by the wide span of the eggbots and the way they pose for shooting. Then the severity can increase beyond that due to network conditions that make that position diverge from the position of the eggbot. The severity can also increase even further if there's a visibility problem when determining the position of the muzzle (as an optimisation we don't resolve joint positions in things that are not visible, in that case the logical position of the player is su...

I would like to see it if you can find it to add it to what we have, thanks.

Regarding anticheat, the person that is in charge of that was swamped this week and we haven't been able to process all cheat reports during the week. These reports take time to process because we want to avoid banning people wrongly. We are doing some changes to our backend so that this process is more efficient. Enforcement of anti-cheating should be way better in the future than what you've experienced. Really sorry that you had such a bad experience.

About the netcode issues that you mentioned in your DM, the netcode as you experienced it last night is not a true representation of the game, in case that weighs into your negative impressions. There are other general issues with the netcode that we know about and we have a few fixes coming that should give you, at the very least, a sense of progress.

We'll win you over some day Mr_Picky. Appreciate your passion for the genre.

Consensus seems to be that the particular issue this thread is about is fixed, so I'm assuming you have older issues. Regarding the shaft, we have identified a potential problem that would make hit registration specially bad with shaft among other things if you are having some lag/packet loss to a server. Look for a patch note mentioning shaft in the next versions.

Regarding the ghost rocket, there is a known ghost rocket issue about rockets that kill somebody then continue on but it's purely cosmetic and it's not a real rocket at that point (we'll still fix it as soon as we can anyway, of course). Lag could also potentially cause some other issues described as "ghost rockets". We are going to add a lagometer and you should be able to see if you are having lag episodes to our server or packet loss.

I have noticed that sometimes my rockets go straight through my enemy even if they deal damage like a direct hit.

There is a known issue where the visuals of the rocket will keep going if that rocket kills the player. We'll fix this. This is a cosmetic issue with no logical side effects.

Also I have seen enemy rockets go straight through me without dealing damage to me. I play on 20-30 ping.

A lag episode may cause this. We are going to implement a lagometer component into the hud and it should allows us to understand and act upon feedback like this better.

To address all of the threads about this at once, there were serious netcode issues tonight due to a mistake during the release process, leading us to internally test a different thing than what was eventually released. Sorry for the inconvenience. We have made changes internally so that this specific type of issue doesn't reoccur.

The issue has been addressed with a server update, so there is no need to update the client, any game started after 9:30am CEST 12/09/2020 will work correctly.

The issue about grenades not bouncing has been fixed for 344.

This is fixed on 342. Sorry, dumb bug that we should have fixed earlier.

We've expanded the mute functionality to also mute chat, this will be on 343.

We've fixed this for 342, thanks.

OK, I'm going to guess that you are saying that the necessary sounds are being played when they should be played, but they are not audible enough (whether they need to louder, more compressed, or more emphasised through mastering/mixing of the global sound pool).

A hypothetical question for the sake of understanding the issue: do you imagine that the issue that you are describing would be solved if for example we were to substitute the enemy jumping, landing and footstep sounds with really strident, piercing tones? Not that we are gonna do anything resembling that, just to make completely sure we are on the same page to pass along the feedback. If that is the issue it means we may need to look at frequency/compression/timbre/tone/levels of those sounds against other sounds, for example.

Replying here for visibility. We'll get to this soon, there will patch notes tomorrow for the past week listing what we have been focusing on so far.

It'd be very helpful to accelerate progress to talk to people who hate the current audio. In the past we've had groups for specific issues like performance or netcode and it's been very productive. Anyone who is on Discord and fits the description, feel free to DM me, you can find me in our public server.

Regarding the directional sound, here's a few aspects to this that I'm going to mention because in the past sharing info like this has helped people come forward with more actionable feedback.

• We've had some issues with 5.1 or 7.1 headphones in the past, where specific channels in some orientations remained completely silent, making directional sound very terrible indeed because you'd actually be hearing nothing from some directions. As far as I know, we generally fixed these issues but it could be that ...

We've fixed this. The fix should be live sometime today.

Np :)

If you re-read what I've said carefully, you'll find I've addressed all of that :) Yes, SSAA is not a proper solution for most people. And yes, there's a difference even in that scenario but the point is we are thinking in that scenario of setups that could run the game at very high fps, so the extra time that you are adding to each single capped frame is very small, and not the kind of latency that makes things feel bad, so I still expect more people to just use SSAA as years go by. I do agree with the sentiment, I would not want any extra latency either. In any case, we should be able to implement MSAA, so you can choose.