Titan issues that need addressing.

[LunaHoshino]

-snip-

That's the graphical lag I'm talking about. It's caused by having a low-power graphics card or processor. WotL is extremely graphic-intensive; if your graphics card isn't all that great, there will be a short delay between when the cast actually starts and when it gets rendered on your screen.

[Gyson]

Exactly. There's a very simple way to tell if it's actually lag: are you getting hit by Landslides? If you're experiencing true lag, you can be two inches out of the Landslide on your monitor and be sent flying anyway.

If you aren't having any trouble dodging those, though, then it isn't lag.

How is that "true lag"? If the cast bar on Landslide starts before the telegraph appears and the telegraph persists after the cast bar has completed, you have exactly the same issue shown in the original post (which you just stressed was caused by slow video hardware a few posts up and not latency issues between the server and client). That same problem can lead to you believing that you escaped the landslide by "inches on your monitor", yet got tossed from the platform anyway.

That's the graphical lag I'm talking about. It's caused by having a low-power graphics card or processor. WotL is extremely graphic-intensive; if your graphics card isn't all that great, there will be a short delay between when the cast actually starts and when it gets rendered on your screen.

I completely disagree that there is anything even remotely "extremely graphic-intensive" about the *telegraphs* for WotL, which are showing up late compared to the cast bar. Combined with the fairly simple (and small) environment of this trial I'm having a difficult time buying into this excuse.

[AdamFyi]

That's the graphical lag I'm talking about. It's caused by having a low-power graphics card or processor. WotL is extremely graphic-intensive; if your graphics card isn't all that great, there will be a short delay between when the cast actually starts and when it gets rendered on your screen.

Which is what the OP is asking for, I think? However, to be fair, they can just preemptively move before it shows up if they are having such issues. But, it would be nice if they did lessen the strain on WotL's animation so that it gets rendered faster.

I completely disagree that there is anything even remotely "extremely graphic-intensive" about the *telegraphs* for WotL, which are showing up late compared to the cast bar.

From my understanding of Luna's post, the delay happens because of the graphic-intensive nature of the animations of WotL. Some graphics cards and processors have trouble rendering all that animation at once; which is why there is a delay with the animation. The cast bar shows up on time, but not the animation. WotL is a special case because multiple plumes pop up at the same time.

[Ayuhra]

Trouble with that is the more you rely on clients the easier it is to hack. If my position on my client decides if I take damage instead of the server, I only have to hack my client to adjust my position and I dodge aoes (teleport, speed hacks etc) because the server doesn't have a chance to check me 1st.

...

Oh absolutely. Teleporting hacks are much easier on client dictated games and can make botting more of an issue, plus the desync problem. When I say I wish the game were client-based I'm not kidding but I'm also speaking out of pure selfishness. I'm not saying the game would be objectively better that way.

I *am* saying that, given the game is server dictated some changes should be made to the timing of certain things as well more user friendly UI tweaks made.

[Arixtotle]

That's the graphical lag I'm talking about. It's caused by having a low-power graphics card or processor. WotL is extremely graphic-intensive; if your graphics card isn't all that great, there will be a short delay between when the cast actually starts and when it gets rendered on your screen.

Except that people with a low end computer would not even be able to run the game plus a video recording program without experiencing severe fps drops. At worst those people who made the videos probably have midrange computers.

[siverstorm]

I said nothing about the battle system. I don\\'t understand where you got that from. This is about this specific instance obviously not working as intended. You really think they meant for what the OP described to happen? Really? Did you even read the OP?

Based on the first two images the OP didn't move out of the weight before the cast finished and then got hit. Many other fights in the game are exactly the same. Friction in garuda ex, the heavy puddles in levi, radiant plumes in ifrit, thunder aoes not on the player in ramuh, and this is just primals, the list goes on and on and on for other content. That is a key feature throughout the battle system of this game. Ground effects are there to give a player indication of where the safezone is, if the cast is complete and you're still standing in it then you'll get hit. End of story. If you dodge a weight of the land before the cast bar finishes and you still take damage then you genuinely have lagged.

I was able to play this game a year ago with my toaster laptop and shoddy internet and still was able to dodge plumes and the like. I even had some major lag spikes back in the day because of my internet (the real ones where everyone stops moving for a few seconds and everyone just eerily stands in place). I was still able to get through titan hm/ex not getting hit by avoidable mechanics for the most part.

You still keep complaining about it not working as intended (because you would know what was intended) and being broken but that still doesn't change the fact that the average player nowadays has no problems dealing with titan hm.

[LunaHoshino]

Which is what the OP is asking for, I think? However, to be fair, they can just preemptively move before it shows up if they are having such issues. But, it would be nice if they did lessen the strain on WotL's animation so that it gets rendered faster.

Oh, I agree, I really wish they would do that. It is literally the only attack in the game that gives me issues, but I also recognize that the issues stem at least in part from me having a cheap bargain-bin computer with an integrated graphics card rather than something that was meant to play games on.

[Ayuhra]

Oh, I agree, I really wish they would do that. It is literally the only attack in the game that gives me issues, but I also recognize that the issues stem at least in part from me having a cheap bargain-bin computer with an integrated graphics card rather than something that was meant to play games on.

For whatever it's worth my computer can run Tomb Raider and Thief (2014) on max settings without too much of a hiccup, my processor is an i7 and I still see some delays in the game so some of the problem, at least, is lag related.

[DragonFlyy]

And that is where we disagree. In reality neither of us can confirm which is correct, but why do you think the server would send two bits of information (the trigger for the castbar and telegraph) separately to the player's client rather than as one single event? To do otherwise would be just asking for problems.

It's more than 2 actually. First Titan starts to cast (server side). Then the game asks the clients (all 8) for a position update. Clients send that back to the server, server calculates WoL locations and transmits to all 8 computers. If any of this was done client side, we could easily capture that event and spoof the server into thinking we are not standing there, thus not needing to move at all. Personally, I have not been hit by WoL since I moved to a closer server (my 1.0 character was placed on a Japan server and they offered free xfers back then.)

[Arixtotle]

snip

So the answer is no, you didn't read the OP. This is not about standing in stuff too long and getting hit. This is about how the cast bar starts ticking down before the indicators on the ground appear. This means that you literally have less time to get out of the way seeing as there is a period of time in the beginning where you don't know where the safe zones are. This is clearly indicative of a problem. The cast bar and the indicators, which the OP calls a telegraph, should start simultaneously.