Greetings, glorious adventurers! If you're joining in our Alpha One spot testing, please follow the steps here to see all the latest test info on our forums and Discord!
Options
Code-In Input Delay
Sapiverenus
Member
96 milliseconds. Subtract Latency from this base delay and you get the player's Input Delay. I say 96 because it's simpler in binary. 00110000
Someone with 40 ms latency and someone with 90 ms latency can play the same game. Small shared delay lends itself to easing up and thinking about what you're doing. To be clear: They both play with about 96 ms latency this way.
40ms player and 180ms player can play a similar game, improving fairness and community. To be clear: One plays with 96 ms latency, the other with 180 ms latency.
Latency checks shouldn't be exploitable; it would definitely be attempted.
Someone with 40 ms latency and someone with 90 ms latency can play the same game. Small shared delay lends itself to easing up and thinking about what you're doing. To be clear: They both play with about 96 ms latency this way.
40ms player and 180ms player can play a similar game, improving fairness and community. To be clear: One plays with 96 ms latency, the other with 180 ms latency.
Latency checks shouldn't be exploitable; it would definitely be attempted.
0
Comments
At least 64 ms delay.
All I know is that as long as the game feels fluid and doesn't feel laggy, I don't care what they implement under the hood.
The OP gave you a 'like' despite some mild sarcasm ... your reputation precedes you.
Sounds good.
And yeah FPS cap can have benefits.
Input delay allows server-side to correctly process everything in proper sequence and send you the correct game state.
Delay on servers sending updated game state allows every player to be updated at the same time as well, so there's a good reason to have Delay on Server Output.
With 64 ms delay the server could tick the game state twice -> so half of players updated every 32 ms but every player waits 64 ms at least.
Keeps everyone playing the same game.
Let me explain why I think this is so out of place here:
1) this is a low level software problem that has probably been solved in many ways, why would the devs be looking on this forum for anything on this topic?
2) Delay based net code probably has its uses, but this didn't work out well for the Fighting Game Community. Recent years have proven that players do not like their inputs being delayed, and there are better solutions to this problem (ie: rollback net code)
This whole post has big "Dunning–Kruger effect" energy. Let the Devs make the game, and you can provide feedback during alpha 2 (or when the game comes out) that you don't like the way the game feels, or that there are specific bugs/exploits. Back seat game designing is one thing...but back seat programming in this manner makes me cringe.
It's not solved. Everyone has different latency and an MMO needs to make sure a crap ton of people are updated correctly.
Nothing works well for the Fighting community because they need the lowest latency possible but physical distance and hardware creates latency.
The immediacy fighting games benefit from is not as much of a necessity for a hack n slash MMORPG. The amount of data a fighting game has to deal with is also microscopic compared to an MMO; there are different priorities.
You've shown your own Dunning-Kruger confidence with the rest of your message.
Why are you telling me what to do? Don't start telling people what to do. You should expect some animosity at this point.
You don't care about anyone else's experience. You don't enjoy sharing an experience with others but want an MMO?
Maybe you don't know what you want or just hate people? Every online game has delay; 64 ms might seem excessive to you but the real issue is when others have an advantage you don't.
What are you going to do when you have 120ms latency and everyone has an advantage over you? Change your mind because it affects you?
Choose a different server, upgrade my internet, choose a less ping-intensive class, move IRL (lol?)
I didn't really want to get into a discussion, I just wanted to place my vote for "No, no way!"
There is always latency. 40 - 90 ms is normal.
People can't even click 10x a second 99.999% of the time. Latency in early 2000s was often hundreds of milliseconds. You probably play most games at at least 64 ms delay as it is; there is nothing for you or most anyone to complain about.
People lack grounding; it is clear by these responses that they have no grounding and are baited into outrage from nothing. And no an online video is not an accurate reference.
You and everyone else has had to deal with over .1 second of delay in games and in real life from their own limited reaction time compounded by the reaction time of others their entire life.
Most reaction times are .25 - .45 seconds [250 - 450 milliseconds]. When things are unexpected but not necessarily startling, reaction times can be over a second.
I feel like I just trolled you all but you just trolled yourselves. Clearly your vote is meaningless.
Input delay is a great way to make a game feel bad.
I've had plenty of reasons for what I think and have referred to specific delays rather than an arbitrarily large amount; dont' characterize it as 'feeling' to suit your own.
Go ahead and tell me how quickly you can start and stop this stopwatch. Get a feel for the different milliseconds.
You will all have to deal with delay either way. All of you have dealt with delay in online games in excess of 64 ms.
Having a baseline delay makes the game somewhat more fair and allows for more coherent processing of inputs from all players.
As I've suggested, individual player latency would be subtracted from the delay. If it takes about 64 milliseconds or longer to reach the server then there is no delay on updating your client.
The combat isn't tight and reactive anyway. It's a hack n slash.
But a delay synchronizes everyone's gamestate and allows for coherent combat; no "oh he was actually 40 pixels to the right but my screen showed him dead center".
Server has 1 second delay. Everyone has 0 - .5s latency. With this arrangement, the server can collect everyone's inputs and place them in the correct order by calculating when their input was Actually sent; then the .5s delay individual is not always reacting late.
This is not ideal. 96 or 64 ms at least provides some correction and complete correction to those with low latency; those with higher latency are not as 'behind' as well since the delay would not apply to them.
36-42ms but that's due to LP MXspeed keyboard & 8K polling KB + Mouse. 70MS is a more generalized number for PC input latency.
The thing is Game code should already have allowances for up 200ms offset because 100ms upload, 100ms download.
My concern is A lot of ashes is tested locally.
As someone who has done some specific tests in their Alpha-1, I will only say:
"On right track, don't worry about it."
I will hope that from your short experience here so far you understand why I am not inclined to say more.
36 -42 ms from keyboard and mouse? I don't think that's right. It should be 1 - 3 ms each. I'm referring to difference between input and server updating the game; so network latency.
Since many games measure inputs on release I can see how an unnecessary delay can and should be removed though. Input on press not release is important.
Yeah who knows how Ashes is handling testing.
Players could be split between 2 game state updaters. Every 32 or 48 ms or whatever half of players can be updated. Having everyone on the same game state is pretty good though; How do good PvP games usually do it lol.
Maybe 64 ms delay upload/download is good; 128 ms delay for everyone. Should be played out.
Alright.
Depressing stuff. Keyboards and mice apparently have a high delay.
So, we have to stop using keyboard&mouse now, too?
Youre not using a hotas system for mmorpgs? Cringe!