Open GoogleCodeExporter opened 9 years ago
I think this has to do with client-side prediction. Some things to consider:
- Should bounce be predicted?
- Something else
Original comment by buckyballreaction
on 16 Dec 2013 at 4:18
If a seeker hits a wall, what's supposed to happen? I think it explodes, no?
If so, why would the client ever think the seeker would bounce?
Original comment by watusim...@bitfighter.org
on 16 Dec 2013 at 9:57
hmm can the seeker be calling the rebound function of bouncers and bursts?
Original comment by Cory.Pou...@gmail.com
on 19 Dec 2013 at 7:40
Maybe this is lag/prediction issue after all. I can reproduce with a large
simulated lag; it appears that all seeker steering happens on the server, and
the client just accepts passive updates.
What if the seeker transmitted its target to the clients, so they could do
better prediction?
Original comment by watusim...@bitfighter.org
on 13 Jan 2014 at 10:43
Original comment by watusim...@bitfighter.org
on 17 Jan 2014 at 3:08
Original issue reported on code.google.com by
watusim...@bitfighter.org
on 1 Dec 2013 at 11:23