Original Post — Direct link

[deleted]

External link →
over 3 years ago - /u/kkrazychicken - Direct link

It would be immensely helpful to get a video of this. Thank you.

over 3 years ago - /u/kkrazychicken - Direct link

Originally posted by [deleted]

[deleted]

Im sorry this doesn't really highlight the problem for me. Is there any other video footage?

Try to understand this isn't just for my sake. The problem here is that I want to get a ticket to our programmers. They need to see the problem to begin diagnosing it. Video is the best way to do this with issues like these because it seems related to lag. Lag-related issues are a bit harder to reproduce for internal testing.

over 3 years ago - /u/kkrazychicken - Direct link

Originally posted by [deleted]

[deleted]

There are a lot of different variables here that make this kind of bug hard to nail down.

1) The user doing the shooting could be having their shots appear on their screen, but not on your screen. The shots may be registering on the server, but not being replicated to your client.

2) The client doing the shooting could be seeing nothing appear. It could be his local latency is not sending the message up to our server and shots are not registering at all.

3) His voice could be lagging. He could be saying that he's shooting but the connection to the vivox server could be coming through delayed.

4) There are a tonne of client-side issues this could be as well. For example the aiming reticle could be outside of the allowable deviation, but still showing white for some reason.

5) A bonus would be if there is anything else you could think of that might replicate the issue. Just knowing that this issue occurs when its 'laggy' is useful, but there are many different kinds of latency. What kind of behaviour are you seeing. Rubber-banding players? Low framerate? etc.

The best thing to do is pop onto our discord at http://discord.gg/foxhole and fill out a bug report in our #bug-report channel. Please remember to read the pins and use the template and provide as much information as you can. Preferrably, a video is best. The one you linked is great, but it would help a lot more to get a video of the issue as its occurring on your client. IE - be the one doing the shooting and seeing this bug.

Thank you.

over 3 years ago - /u/kkrazychicken - Direct link

Originally posted by [deleted]

[deleted]

Thank you very much. This helps a lot. I'll make sure this gets addressed ASAP.