[resolved] Failed to display the 'Watch Replay' and 'Retry' buttons‬ · forum‬

taroxd

Joined January 2012

Topic Starter

taroxd 2016-04-03T14:01:38+00:00

Problem Details: The 'Watch Replay' and 'Retry' buttons are not displayed after the latest update. It seems that something went wrong with the skin.

Video or screenshot showing the problem:
Current Version:

Previous Version:

My skin: https://github.com/taroxd/osu-skin/tree/bug

osu! version: 20160403.4

Last edited by taroxd 2016-04-04T08:13:30+00:00, edited 1 time in total.

---------------_old_1

---------------_old_1 2016-04-03T14:50:51+00:00

well I didn't download and test out your skin since I don't know how to use github.

But I didn't find the "pause-replay" picture in any of your folder, so that's one problem. But, nevertheless, you should still see something.

Question: With this skin, do you not see "watch replay" or "retry" at all? Because what I think happen is that you somehow lost your local replay.

taroxd

39 posts

Joined January 2012

Topic Starter

taroxd 2016-04-03T23:18:14+00:00

--------------- wrote:
well I didn't download and test out your skin since I don't know how to use github.

But I didn't find the "pause-replay" picture in any of your folder, so that's one problem. But, nevertheless, you should still see something.

Question: With this skin, do you not see "watch replay" or "retry" at all? Because what I think happen is that you somehow lost your local replay.

As in the picture, the button simply does not appear. If I switch back to the default skin, it will appear.
And the 'retry' button is expected to show after every play, whether success or failure.

I does not include "pause-replay" in my skin, so I think the default picture should be used. Actually I changed very few elements in my skin.

Skin download: https://github.com/taroxd/osu-skin/archive/bug.zip

Last edited by taroxd 2016-04-04T01:07:48+00:00, edited 1 time in total.

Pawsu

osu! Alumni

5,213 posts

Joined February 2013

Pawsu 2016-04-03T23:22:40+00:00

Pretty sure this is caused by an update error - should be fixed in the next update.

taroxd

39 posts

Joined January 2012

Topic Starter

taroxd 2016-04-04T00:47:04+00:00