Thread: .3 Second Positional Update Delay (Requesting Dev Response)

Originally Posted by Astarica

*snip*

No need to argue semantics here. Not a single one of us knows 100% for sure what's going on behind the scenes, so arguing saying it's absolutely one thing over another is rather silly, and may end up taking away from the issue. I don't think the issue is truly intentional at this point. I do honestly think they don't know how else to code it, or don't want to spend the resources to fix it.

Originally Posted by Sunarie

No need to argue semantics here. Not a single one of us knows 100% for sure what's going on behind the scenes, so arguing saying it's absolutely one thing over another is rather silly, and may end up taking away from the issue. I don't think the issue is truly intentional at this point. I do honestly think they don't know how else to code it, or don't want to spend the resources to fix it.

If the issue is merely caused by coding incompetence or just being cheap, other MMORPG should suffer the same problem because there are a lot of bad MMORPGs out there that have no budget to work with.

FF14 1.0 didn't have jump as a basic feature. It's basically the same kind of issue here. There's a serious disconnect between the development team of this game and versus the standard of the industry. This is the only possible way why this game have problems that literally no other MMORPG have.

Originally Posted by Astarica

If the issue is merely caused by coding incompetence or just being cheap, other MMORPG should suffer the same problem because there are a lot of bad MMORPGs out there that have no budget to work with.

FF14 1.0 didn't have jump as a basic feature. It's basically the same kind of issue here. There's a serious disconnect between the development team of this game and versus the standard of the industry. This is the only possible way why this game have problems that literally no other MMORPG have.

My point was more along the lines you don't know, I don't know.. it's all speculation, so there's no point in arguing over it.

Originally Posted by Sunarie

No need to argue semantics here. Not a single one of us knows 100% for sure what's going on behind the scenes, so arguing saying it's absolutely one thing over another is rather silly, and may end up taking away from the issue. I don't think the issue is truly intentional at this point. I do honestly think they don't know how else to code it, or don't want to spend the resources to fix it.

there is no " they don't know how to code it" because its intentional, the 0.3 from purely technical aspect its fine. if they increased the margin of error for players then no one would complain about 0.3 snapshots.

Originally Posted by zaineal

there is no " they don't know how to code it" because its intentional, the 0.3 from purely technical aspect its fine. if they increased the margin of error for players then no one would complain about 0.3 snapshots.

How would you increase the margin of error for a binary result (get hit/don't get it hit), would the server give you a certain percentage of freebies even though it registers you as being hit? I'm pretty sure that would increase complaints not eliminate them.

The "they don't know how to code it" idea stems from the fact that the 0.3 update is just one part of the unresponsiveness the game suffers from, a game which has mechanics that were designed to require split second responses to succeed or fail, so I don't think you should be so quick to dismiss it. That being said, you could in fact be absolutely correct, and the animation lock, animations not being in sync with indicators, unreliable cast bars, etc, etc, are actually considered gameplay innovations by the developers, but if this is in fact the case, why wouldn't they just say so, rendering threads like this moot?

Originally Posted by Goreth

How would you increase the margin of error for a binary result (get hit/don't get it hit), would the server give you a certain percentage of freebies even though it registers you as being hit? I'm pretty sure that would increase complaints not eliminate them.

The "they don't know how to code it" idea stems from the fact that the 0.3 update is just one part of the unresponsiveness the game suffers from, a game which has mechanics that were designed to require split second responses to succeed or fail, so I don't think you should be so quick to dismiss it. That being said, you could in fact be absolutely correct, and the animation lock, animations not being in sync with indicators, unreliable cast bars, etc, etc, are actually considered gameplay innovations by the developers, but if this is in fact the case, why wouldn't they just say so, rendering threads like this moot?

What they can do is:Increase server snapshots to 0.1 server is now checking your position 10 times a second (this will now show who is just not skilled enough to move out of the bad) or increase cast timers for bad to be on par or above how slow/fast the server is checking your position,change how the client updates the server before animation lock this is now a cosmetic and has no influence on actually game play, where it is now.

Originally Posted by zaineal

What they can do is:Increase server snapshots to 0.1 server is now checking your position 10 times a second

I think the problem is more that the server location trumps the client (assuming the server has the client info). From my understanding, increasing the check interval is just going to cause more lag to SE's servers..and it wouldn't really fix the underlying issue, those with any sort of latency would still get hit by things they were out of. People have been able to play various other MMOs with less than optimal latency, and been able to dodge things. That issue is specific to SE, so something went wrong on a coding level regarding how the client and server communicate with regards to how whether you made it out of an AOE or not is calculated. Updating the interval (which they already did going from beta to release) is simply bandaiding the issue.

Same with increasing a cast bar timer. Though with the additional problem of making the content easier for those not experiencing the problem. I don't actually want that.

Originally Posted by Sunarie

I think the problem is more that the server location trumps the client (assuming the server has the client info). From my understanding, increasing the check interval is just going to cause more lag to SE's servers..and it wouldn't really fix the underlying issue, those with any sort of latency would still get hit by things they were out of. People have been able to play various other MMOs with less than optimal latency, and been able to dodge things. That issue is specific to SE, so something went wrong on a coding level regarding how the client and server communicate with regards to how whether you made it out of an AOE or not is calculated. Updating the interval (which they already did going from beta to release) is simply bandaiding the issue.

Same with increasing a cast bar timer. Though with the additional problem of making the content easier for those not experiencing the problem. I don't actually want that.

I agree completely the 0.3 is not the issue as it works however from what I'm seeing is that the server is not pushing out data correctly there could be a multitudes of factors to consider e.g. is the server just hiccuping(if this was it then everyone in the instance would well get hit) I'm more inclined to believe that how they are pushing data out has an underlying issue, there's just too many factors to involve with very little information as we don't work on there servers. Infact I believe they know what is the problem (if there is one!!) and are working on smoothing it out, more transparency from them would be great.

Originally Posted by zaineal

more transparency from them would be great.

SE don't 'do' transparency.

Well, they did, back when V1 was a disaster and they needed to keep players sweet, there was a huge amount of feedback from SE about what they were doing, the plans they had and what they were doing to deal with problems players were raising.

Just take a look at the Lodestone archive here: http://lodestone.finalfantasyxiv.com/pl/topics/index, or the forum archive: http://forum.square-enix.com/ffxiv/f...-Forum-Archive

ALL that discussion ended when V2 launched.

Originally Posted by zaineal

there is no " they don't know how to code it" because its intentional, the 0.3 from purely technical aspect its fine. if they increased the margin of error for players then no one would complain about 0.3 snapshots.

I agree. I started using Battleping and tried out Leatrix Latency Fix because of suggestions I saw on here. I'm able to dodge MOST AoE's now. But still, some fights are maybe a little too unforgiving. If they added even .5 seconds to some cast times, I don't think things like Titan would be an issue anymore. I know its a bandaid fix, but I'd happily take it. I just want some kind of response, I want to know they're aware of the problem and are working on it. And if they don't plan on fixing it at least design new fights with this issue in mind.