Guest
home
beatmaps
rankings
community
store
help
forum
  1. Forums
  2. osu!
  3. Help
  4. Resolved Issues

[resolved] elements not aligned on lazer using specific skin

posted
Total Posts
13
Kenny_ta_god
3 posts
Joined July 2018
Topic Starter
Kenny_ta_god
Problem details:

in osu lazer my things arent lined up only on some maps
Video or screenshot showing the problem:
https://imgur.com/Mpqmlw5

osu! version: lazer
JustABeginner
1,221 posts
Joined December 2016
JustABeginner
Hi Kenny_ta_god!

A couple of steps you need to do to solve the overlap problem:

1.) Export your current skin as .osk file.
2.) Enable file extension - search "how to enable file extension" if you not sure how - and change from .osk to .zip.
3.) Unzip its file, and go to your skin.ini file.

From your skin.ini, add or change:
HitCircleOverlap: 170 (This requires trial and error)

4.) Save the skin.ini file, recompressed the folder as .zip file - make sure you name the folder differently.
5.) Rename its file extension back to .osk and drag the file into the osu!lazer application.
Kenny_ta_god
3 posts
Joined July 2018
Topic Starter
Kenny_ta_god
thank you so much!!!!
spaceman_atlas
osu!dev
285 posts
Joined July 2013
spaceman_atlas
I'm dumbstruck by whatever happened here.

  1. What is "misaligned" on the screenshots in the OP? I see nothing wrong?
  2. What is this advice on HitCircleOverlap or whatever? Why would it require "trial and error"?
  3. How did this help anything?
Can someone explain this to me?
Eyeonized
151 posts
Joined September 2017
Eyeonized
Kenny_Ta_God, you would be much better off using just numbers. The only good way to get double digit combo numbers is to use numbers under 'default-x.png' and the hitcircle under 'hitcircle.png' or 'hitcircleoverlay.png'.

as for spaceman, i hopefully have some answers below.

  1. What is "misaligned" on the screenshots in the OP? I see nothing wrong?
At a brief glace, the numbers on the circles are incorrectly proportioned. You can see 9 is fine, but 10 and 11 are seperated into two different hit circles.
(one with the number 1, and one with 0, for 10.
And one with the number 1, and another with the number 1, for 11).

  1. What is this advice on HitCircleOverlap or whatever? Why would it require "trial and error"?
Not sure, perhaps someone more experienced in skinning could help. i think its that the numbers for skins are actually 2 seperate hit circles and you have to adjust it in order to make the numbers look like they're together.

  1. How did this help anything?
Now for any combos above 9, they can read it properly. ill show you an example here.

This is a properly done skin, where the numbers are positioned correctly.



This is a poorly made skin (by me lol) where the numbers are not positioned correctly.

this image as it isnt working as an embed

I think this thread probably should've been made in here, but im glad they found help :D
Last edited by Eyeonized , edited 11 times in total.
Lyawi
Global Moderator
3,617 posts
Joined February 2015
Lyawi
And this didn't occur in stable aswell? It probably did?
spaceman_atlas
osu!dev
285 posts
Joined July 2013
spaceman_atlas

Lyawi wrote:

And this didn't occur in stable aswell? It probably did?
Yeah this is the part that bothers me the most here, how is this apparently a "lazer issue"?
Eyeonized
151 posts
Joined September 2017
Eyeonized
it probably isnt a lazer only issue, they just didnt test it on stable
my images were from stable
Last edited by Eyeonized , edited 1 time in total.
JustABeginner
1,221 posts
Joined December 2016
JustABeginner
To spaceman_atlas:

spaceman_atlas wrote:

I'm dumbstruck by whatever happened here.

  1. What is "misaligned" on the screenshots in the OP? I see nothing wrong?
  2. What is this advice on HitCircleOverlap or whatever? Why would it require "trial and error"?
  3. How did this help anything?
Can someone explain this to me?
Apparently Eyenoized answered most of the questions, but I'll add on the 2nd question.

HitCircleOverlap is one of the commands used in skin.ini. Feel free to refer in the wiki. Basically it helps to adjust the gaps in between the default-#. This is really helpful when people are using hitcircle as inside the skin element default-#, creating a gap in between after the default number reaches past 9. By using HitCircleOverlap, adjusting the value to positive decreases the gap in between the numbers starting from 10, so I chose vaule 170 since I referred to the similar question about it recently. You can check at my reply with Eyenoized below if you want to know why. As for the trial and error, I'm sure there's going to be a calculation on how to accurately do it, or I believe there's a tool for that, but I'm not entirely confident with them.

---------------------------------------------------------

To Eyeonized:

Eyeonized wrote:

Kenny_Ta_God, you would be much better off using just numbers. The only good way to get double digit combo numbers is to use numbers under 'default-x.png' and the hitcircle under 'hitcircle.png' or 'hitcircleoverlay.png'.
This is more than just "get double digit". This can give the skin an instafade effect.

What is instafade? Simply when you hit the circle, instead of fading it away, it instantly fades out.

Instafade:


Without instafade:


As you can see, the 2nd gif has a fade-like hitcircle when clicked compared to the 1st gif.

Not only that, this also able to give each number different colour. However, it is not able to use combo colour.
For example, look at this video I timestamped - at skin #45 and #46: Click here!

---------------------------------------------------------

To Lyawi and spaceman_atlas:

spaceman_atlas wrote:

Lyawi wrote:

And this didn't occur in stable aswell? It probably did?
Yeah this is the part that bothers me the most here, how is this apparently a "lazer issue"?
This is a skinning issue. And like Eyeonized mentioned, it belongs to the Skinning Subforum. It can occur at any client - either it be osu!stable and osu!lazer, so long as there's something inside the skin folder at its fault. Only that osu!lazer doesn't have a skin file location so it needed some extra steps to fix it.
Last edited by JustABeginner , edited 1 time in total.
Kenny_ta_god
3 posts
Joined July 2018
Topic Starter
Kenny_ta_god

JustABeginner wrote:

To spaceman_atlas:

spaceman_atlas wrote:

I'm dumbstruck by whatever happened here.

  1. What is "misaligned" on the screenshots in the OP? I see nothing wrong?
  2. What is this advice on HitCircleOverlap or whatever? Why would it require "trial and error"?
  3. How did this help anything?
Can someone explain this to me?
Apparently Eyenoized answered most of the questions, but I'll add on the 2nd question.

HitCircleOverlap is one of the commands used in skin.ini. Feel free to refer in the wiki. Basically it helps to adjust the gaps in between the default-#. This is really helpful when people are using hitcircle as inside the skin element default-#, creating a gap in between after the default number reaches past 9. By using HitCircleOverlap, adjusting the value to positive decreases the gap in between the numbers starting from 10, so I chose vaule 170 since I referred to the similar question about it recently. You can check at my reply with Eyenoized below if you want to know why. As for the trial and error, I'm sure there's going to be a calculation on how to accurately do it, or I believe there's a tool for that, but I'm not entirely confident with them.

---------------------------------------------------------

To Eyeonized:

Eyeonized wrote:

Kenny_Ta_God, you would be much better off using just numbers. The only good way to get double digit combo numbers is to use numbers under 'default-x.png' and the hitcircle under 'hitcircle.png' or 'hitcircleoverlay.png'.
This is more than just "get double digit". This can give the skin an instafade effect.

What is instafade? Simply when you hit the circle, instead of fading it away, it instantly fades out.

Instafade:


Without instafade:


As you can see, the 2nd gif has a fade-like hitcircle when clicked compared to the 1st gif.

Not only that, this also able to give each number different colour. However, it is not able to use combo colour.
For example, look at this video I timestamped - at skin #45 and #46: Click here!

---------------------------------------------------------

To Lyawi and spaceman_atlas:

spaceman_atlas wrote:

Lyawi wrote:

And this didn't occur in stable aswell? It probably did?
Yeah this is the part that bothers me the most here, how is this apparently a "lazer issue"?
This is a skinning issue. And like Eyeonized mentioned, it belongs to the Skinning Subforum. It can occur at any client - either it be osu!stable and osu!lazer, so long as there's something inside the skin folder at its fault. Only that osu!lazer doesn't have a skin file location so it needed some extra steps to fix it.
your solution worked, but i tested on both clients and still have the original skin file and it only happened on lazer still. pretty confusing to me as well im not a skinner or anything but i do have some like basic knowledge no clue why
spaceman_atlas
osu!dev
285 posts
Joined July 2013
spaceman_atlas
I guess the "instafade" explanation makes sense, it'd help if the skin was actually linked in the OP rather than there being a screenshot with little context, but I suppose that's explained now.

Still dunno why this is apparently a "lazer issue" but I think I'm going to just look away and pretend all is fine and resolved.
JustABeginner
1,221 posts
Joined December 2016
JustABeginner

Kenny_ta_god wrote:

your solution worked, but i tested on both clients and still have the original skin file and it only happened on lazer still. pretty confusing to me as well im not a skinner or anything but i do have some like basic knowledge no clue why
Perhaps in osu!lazer, you're still using the previous skin, and as for osu!stable you're using the updated one.
It's really hard to directly check the skin.ini in osu!lazer unlike osu!stable, so I'm hoping there will be an update that able to update skin.ini within that client - or even something better like involves easy adjusting. :b

But yeah, it's all about HitCircleOverlap to simply answer your original question.
And feel free to head to Skinning Subforum next time if you need help with skinning!

P.S: And glad we able to help you out too!
Last edited by JustABeginner , edited 1 time in total.
Eyeonized
151 posts
Joined September 2017
Eyeonized

JustABeginner wrote:

To Eyeonized:

Eyeonized wrote:

Kenny_Ta_God, you would be much better off using just numbers. The only good way to get double digit combo numbers is to use numbers under 'default-x.png' and the hitcircle under 'hitcircle.png' or 'hitcircleoverlay.png'.
This is more than just "get double digit". This can give the skin an instafade effect.

What is instafade? Simply when you hit the circle, instead of fading it away, it instantly fades out.

Instafade:


Without instafade:


As you can see, the 2nd gif has a fade-like hitcircle when clicked compared to the 1st gif.

Not only that, this also able to give each number different colour. However, it is not able to use combo colour.
For example, look at this video I timestamped - at skin #45 and #46: Click here!
Thank you, admittedly im not too great at skinning and didnt realise this, thank you for putting it in a way which other people and I can understand :)
Please sign in to reply.

New reply

0
1 / 13