Poison ticking too fast on 120 FPS?

[Phi Zero]

Either I'm going insane, or the poison damage ticks way too fast on 120 FPS. I tried switching to 60/30 FPS, and it seems HP goes down much slower.

Anyone else noticing this issue?

[BlueDragonXD]

Interesting comment. Maybe it's related to this...
https://steamcommunity.com/app/2530980/discussions/0/510695968495110353/

Might be a few ways you can fix it if it is an issue. But we likely need someone like Kaldaien to chime in on this?

When I get to a point where I can reliably be poisoned. I might test this out a little. Now for all I know I may already have my GPU settings configured where this is not an issue. In such case I might come back and just report that it works for me at least.

[Phi Zero]

Yeah, I confirmed that it's ticking at double the rate at 120 FPS: https://www.youtube.com/watch?v=aNCUnq7a4QE

- On 120 FPS, one tick is 72 HP damage.
- On 30 and 60 FPS, one tick is 36 HP damage.

Sometimes it seems to even tick twice in succession (causing 72/144 HP loss in the time of one tick).

And sometimes on 30 FPS, it doesn't even tick at all? Maybe it's some mechanic I'm missing? But it seems to always tick on 60/120.

EDIT: Noticed I have VSync off still, but this doesn't seem to change anything.

[AceMan#1]

I was wondering why poison seemed stronger in this remaster, thank you I turned it down to 60fps.

[AceMan#1]

There might be other bugs at 120fps as this game is based off the ps3 version that ran at 60fps max.

[BlueDragonXD]

I know some people are making tools that help with Stutter and so forth. But I wonder if this is beyond them. We might need some DEV patches up in the house. My fear though is will they care enough?

[AceMan#1]

Oh weird I wonder why I didn't have any stutter on my Lenovo Legion Go gaming handheld and my $200 Lenovo Intel graphics laptop?

[Phi Zero]

Seems this has been fixed on the latest update from Feb 7th.

[Kaldaien]

Weird, I played the game at 175 FPS and didn't realize poison was going any faster.

I'd call this a relatively minor problem though, all things considered :) When we modded Tales of Zesteria for 60 FPS, we had to re-write part of a cutscene because the physics of the NPC's camera didn't work right at > 30 FPS and one of the NPCs would get stuck and the cutscene never ended. Had to modify the pathing ever so slightly to avoid the collision.