Cockatrice: Unable to Seek During Replays

[D0nV170]

System Information:

Client Version: 2.7.4 (2020-03-20)
Client Operating System: Windows 10 (10.0)
Build Architecture: 64-bit
Qt Version: 5.12.6

---

I am unable to seek past about 25% during any replay that is long. If I try to seek any further, it moves it directly to the end or starts it back from the beginning. I don't know what the exact number of minutes is since I can't tell how long a replay is but anything that is more than an average 1v1 60 card deck game length seems to give the issue. Others have reported this issue as well and it's never affected me until yesterday when I had to watch a 4 player EDH game all the way. Other users have reported this same issue. It feels like the Replay Timeline is off in terms of scaling. Anything short, I can click right on the timeline and it seeks to that point in the game no problem. As for the longer ones, I can only seem to get the Timeline to seek into various parts of the first ~25% or to the very end.

[n21lv]

I can confirm this, happens with my replays all the time, regardless of how long I let them to run.

[tyler274]

Quite literally all my replays are unseekable as described.

[ZeldaZach]

This used to work, and I'm not sure what happened. This is a high priority to fix. Maybe @ctrlaltca or @ebbit1q ya'll have some ideas?

[ZeldaZach]

We can't reproduce this issue on Mac or Linux, so I'm assuming it's a Windods limitation.

[tooomm]

It works for me with the 2.7.5 release on Windows 10 64bit.
Is this still an issue for you with the most recent version @D0nV170?

[n21lv]

I just updated to 2.7.5 release on Windoes 10 64 bit and tried to play and old replay file, and it still has this issue. @tooomm can you can upload the one you were testing somewhere so I could check if it works for me? I'm not sure when I will get to play next time.

[tooomm]

The two replays I tried were 3y old... probably somebody else should check with more recent files. :D

[pulverize]

edit:
Windows 10
2.7.5 2020-08-23 x64

[ebbit1q]

can someone make one of these replays that are broken for them available here? I seem to be unable to reproduce this whatever I do.

[pulverize]

Can't attach the file. Does this work? https://drive.google.com/file/d/15S4LlkXbEi4FCgq083GlcQHrr_eN5NwO/view?usp=sharing

Happy to share debug info. If there's a way to capture it without running visual studio, let me know, otherwise I'll circle back within a week.

[n21lv]

Here's mine as well. https://drive.google.com/file/d/16UD7BMr5BDkml-QwlR91CUNhhhml_xJ0/view?usp=sharing

[ebbit1q]

thanks, this confirms that this is exclusive to windows, I was unfortunately unable to reproduce the issue, I accidentally however did notice a play error in @pulverize 's replay, at about 2/3rds of the game everyone draws 34 cards from grothama except only the controller of the damage should be the only one to draw :wink:

[ZeldaZach]

Both replays posted work as expected on my end, MacOS 10.15.7. Seems to be a Windows issue.

[tooomm]

I can confirm that both provided replay files are broken on Windows.

[pulverize]

@ebbit1q good catch, but I'm a bit disappointed you've revealed that glorious moment to have been a mistake...

@tooomm - replay posted by @n21lv is also exhibiting the issue for me, can't get past the first couple rounds. About the same percentage progress through the replay, so I can view about 15 minutes of mine and about 2 of his.

[n21lv]

Tried again today with a replay recorded in v.2.7.5 and the issue seems to be gone. Here's the replay: https://drive.google.com/file/d/1imXCAYE70NDBYoVlT732ftyj_gT0HxkB/view?usp=sharing

[D0nV170]

What about

https://drive.google.com/file/d/1A_6BOImYJWCXr7T4t83XoPjsTOWS4SxT/view?usp=sharing

[n21lv]

@D0nV170 I am unable to access the file without your approval. You should've received an email notification about this.

[D0nV170]

Sorry, I think I fixed it. I don't ever use Drive.

[n21lv]

@D0nV170 I can only seek that one up to this moment, then it resets back to start.

But if I click further in small horizontal increments, the replay eventually restarts until it reaches the _threshold_, and then resets again. It looks like the mouse clicks are registered as if they are outside of the seeking region, but at certain position X axis loops over and you seek through the same section of the replay.