Did you remove /oos or fix desync?

"

jabi wrote:

I understand how the desync happens and I know it's a hard issue to fix. All I want to say that some people - like me - are hit by this issue so hard that we can't play at our prime time. At least we can't enjoy the fun of hardcore or progressing in cruel/merciless. It's hard because we can't know if we are in the room we see or not. Monster hit us so we can't evade/kite them and using ranged skills is impossible.

Earlier I could play the game while using /oos when needed, but for example yesterday I had to quit because it was too hard to keep alive. Until this issue is fixed I can't keep playing at evening, at all.

Ps. Kudos for you GGG anyway for this great game.

"

tritonxiv wrote:

People need to remember this is a FREE game that is STILL IN BETA..

Sorry to say, but you are wrong. If you can spend money on a game it's not free by any meter.

"

Chris wrote:

/oos was removed because:

/oos allowed people to have a fight with no apparent sync problems, then type /oos and see that the corpses shift around so they complain about how bad sync is. The whole point of the prediction system we use is to be a little out of sync in order to hide latency.

"

anubite wrote:

But POE isn't a FPS. How many FPS games do you know let there exist up to 12 player-clients and up to 100 or more NPC-clients?

"

In a map several times the size (in coordinates) of most 32-server FPS games? Coding for a FPS and coding for RPG are different things; if 100 monsters attack at once with projectile attacks, we now need to network 100 projectile entities.

"

Politely, I must inform you, "You don't know shit." Stop making assumptions about coding when it's clear to me you have no experience doing it.

"

As for why GGG implemented this kind of architecture - that's a moot quesiton (They aren't going to-rewrite their entire network code from scratch) - but the reason why they did is BECAUSE not everyone lives in a 1st world country with 40 ms ping. GGG is a small company which can only afford a small number of server clusters, so 200-300 ms needs to be acceptable. They ALSO chose the current implementation of sync because there are no NZ servers; THEY PLAY THE GAME THEMSELVES AT 200+ MS. If POE were designed like LOL, they couldn't even play their own game!

"

genericacc wrote:

3) They will not implement aggressive compensation, ever, because you should miss due to desync issues.

"

genericacc wrote:

"

anubite wrote:

But POE isn't a FPS. How many FPS games do you know let there exist up to 12 player-clients and up to 100 or more NPC-clients?

Savage let you have 64 players and an undefined number of NPCs the last time I played it. Mind, in practice, the server would go down if you triggered actions from several hundred NPCs at once since it would take too long to resolve a server frame, but that only happened when we purposefully tried to see how much crap you could throw on one map before you had issues.

An instance in this game, on the other hand, is capped at six players; and everything else has actions which can be predicted on both ends of the connection, seeing as how they're rather automated. Desyncs resulting from mobility skills would seem to indicate that this isn't stable when there's a sudden change in player position, though.

"

In a map several times the size (in coordinates) of most 32-server FPS games? Coding for a FPS and coding for RPG are different things; if 100 monsters attack at once with projectile attacks, we now need to network 100 projectile entities.

Projectiles don't need constant updates. A projectile with constant velocity only needs a (t_0, x_0, y_0, z_0, v_x, v_y, v_z) tuple to dictate its position across all of time in 3-space, actually, which will take 28 bytes or so per projectile using 32-bit floats. Of course, you also need a word or so to specify what the projectile type is, putting us at ... another two bytes. Nothing could possibly handle that network load.

How is map size relevant here? Number of mobs maybe, but you can make quite a few helpful assumptions there.

"

Politely, I must inform you, "You don't know shit." Stop making assumptions about coding when it's clear to me you have no experience doing it.

Yeah I do, actually. Given your brilliant example above, you probably shouldn't be insulting others quite yet.

"

As for why GGG implemented this kind of architecture - that's a moot quesiton (They aren't going to-rewrite their entire network code from scratch) - but the reason why they did is BECAUSE not everyone lives in a 1st world country with 40 ms ping. GGG is a small company which can only afford a small number of server clusters, so 200-300 ms needs to be acceptable. They ALSO chose the current implementation of sync because there are no NZ servers; THEY PLAY THE GAME THEMSELVES AT 200+ MS. If POE were designed like LOL, they couldn't even play their own game!

The current implementation of sync is "re-sync only when the client tries to make an illegal move" as far as I can tell. I have a healthy degree of confidence that there exists an intermediate solution somewhere, but as evidenced by the massive pile of complaints, the current solution doesn't work too well even with very low ping.

300ms isn't an acceptable ping for playing this game unless you're running a minion build that plays the game for you.

"

Jcap wrote:

In fact you didn't even have to be moving or fighting to see a mob desync, it happens frequently just when they try to go through doorways. You'll see them walk out, waddle around, and then mysteriously pop back into the other room.

"

He said that the possibility of missing is increasing desync issues.