POE WILL BE THE NEW VANGUARD IF THEY DONT CHANGE SHIT UP

Punishing the 99.98 percent of us with dysync because you are worried people will exploit is dumb. I personally have not died to dysync because I am a projectile build, also have grown used to it but I constantly see my flicker strike comrades die in maps at level 95 and feel terrible for them.

When you attack faster than the server can even respond, don't expect any improvements to desync as a whole to solve that problem.

As I was reading this thinking about slayer's response and whether or not that was a prediction model issue the monsters my character was attacking stopped moving and about a second and a half later I rubberbanded through a wall into an area I hadn't been yet lol.

We love you desync...

Another rage thread that just doesn't understand anything due to lack of care.

Will these forums ever get better?

"

Natharias wrote:

Another rage thread that just doesn't understand anything due to lack of care.

Will these forums ever get better?

I desynced twice today within about 1 hour of playing, moving more or less not at all, playing a witch with flameblast. Both times both my char and the blast were not where I clicked them to be.

So what is there to understand? That it takes time?

people still believe that desync is there to remove 'cheats'.

Faster attacks OP!

I've heard it all now: don't run too fast, don't jump, don't run around obstacles, don't run past mobs, don't attack too fast...

Menwhile GGG servers are running on hamster wheels.

Solution: permanent temporal chains for everyone, all skills that make you move are made legacy and the only weapons that drop from now on are slow kauri mauls.

"

newbsauce87 wrote:

Punishing the 99.98 percent of us with dysync because you are worried people will exploit is dumb.

Bullshit; actually, it's smart to avoid security holes. Desync is a massive problem, but hackers are a worse problem.

"

SL4Y3R wrote:

When you attack faster than the server can even respond, don't expect any improvements to desync as a whole to solve that problem.

Bullshit; actually, I do hope for improvements.

The big problem with desync discussions on these boards is the belief you "can't have your cake and eat it too," which is a principle which only applies to mutually exclusive situations. This causes people to either side with "eat your cake" or "have it," leading to the type of insipid squabble this thread is thus far.

But they're not mutually exclusive. Let me explain by analogy.

Let's say you and I are both taking a class (with very lax plagiarism policies). You're a lot smarter and dependable than I am, so it's agreed that relying on me to provide you with answers to homework has disadvantages; on the other hand, you don't want to have to do more work than you have to. This leaves us with two options:
1. I trust you to provide me with answers, I don't work them out myself at all, and I wait on you to give them to me.
2. You trust me to provide you with answers, you don't work them out yourself at all, and you wait on me to give them to you.

So which of these two choices is the right choice? Consider that meet-ups to exchange answers are intended to happen, but may fall through, making a meet impossible before key deadlines.

If you actually chose one or the other, shame on you, because obviously the correct answer is
3. Each of us works out the answers by themselves, but we consider yours more authoritative than mine if we discover we disagree on something.

The same thing is true with desync. "Not trusting the client" is not synonymous with a client which does none of the work on its own and is utterly dependent upon the server for continuous updates.

So fuck the idea of opening up PoE to additional security risks in order to make the gameplay experience smoother. Also, fuck the idea of not making the gameplay experience smoother. These are not mutually exclusive things.

Of course, if you're familiar with GGG policy on desync, they make it sound like it is have your cake or eat it too. But that's just a convenient excuse they use because it gets them off the hook, and gets the SL4Y3Rs of the world on their side. But it's a bunch of bullshit, and perhaps the only example I can think of where I'm upset with GGG for psychologically manipulating its community.

Bottom line: It's about prediction.
When the client predicts properly, there is no desync; therefore, the more often the client predicts properly, the less often desync occurs.

The PoE client virtually never predicts properly, because GGG has thoroughly neglected the client prediction system in favor of relying heavily on server-taxing resyncs.

The only thing that's truly difficult to predict is the actions of players. In a single-player situation, this is information the client possesses before the server. Therefore, the client is in a position to predict gamestate in a way which matches the server answer the vast majority of the time.

"

ScrotieMcB wrote:

The only thing that's truly difficult to predict is the actions of players. In a single-player situation, this is information the client possesses before the server. Therefore, the client is in a position to predict gamestate in a way which matches the server answer the vast majority of the time.

It's way more difficult to correctly predict 20 mobs, that are all at the same time trying to get to you through a series of obstacles and inter-mob-collision avoidance pathfinding.

Make those mobs use whirling blades, teleportation, leap slam or run very very fast, and you have a disaster. Couple it with hamster wheel servers and you have Desync: Champions, where despite 40 - 50ms latency, the game takes half a second to calculate a hit. Using cleave, not cyclone.

However you put it, this prediction model is pure crap. Maybe it would work in a chess match, but not in a fast paced combat environment.

PoE's client could get many optimizations about desync : when you eye can see, can notice the desync through your screen, but that the client does not do anything about this, it's because there is a lack of some tests to force resync in obvious situations.

So there is room for improvement, but there will most-likely always be people dying to desync because you cannot predict correct outcomes often enough to prevent it.