Guest
home
beatmaps
rankings
community
store
help
forum
  1. Forums
  2. Beatmaps
  3. Mapping Discussion
  4. Mapping Techniques

[solved] 0bpm be like

posted
Total Posts
6
ToothpasteXL
2 posts
Joined December 2020
Topic Starter
ToothpasteXL
https://clips.twitch.tv/SpicyFaithfulMushroomSoonerLater-rMCkHxyRDGuyj2gh
i don't know how some people get their beatmaps to 0bpm-6000000bpm (like confusion spell). is it something to do with computer strength or did a update remove it? it instantly crashes whenever i go back to the compose tab. thanks lmao
THAT_otaku
Global Moderator
3,925 posts
Joined February 2018
THAT_otaku
I wouldn't think setting it to 0bpm would be enough to crash your osu! (in most cases) as you can use negative numbers as big as 1E-298 (osu! sees this as infinite bpm) and it doesn't crash osu!, unless you do certain things. Perhaps your computer couldn't handle it, or maybe because you set an entire song to 0bpm? In my experience using infinte bpm (1E-298) and other extreme bpm values, I've only used it for like a few milliseconds at a time, so I'm too sure.
gummibar
92 posts
Joined January 2016
gummibar
your issue is that setting the bpm to 0 just crashes the game. you have to trick osu into rounding the number all the way down to zero, or something like that. whatever the case, here's how to do it properly: https://youtu.be/_sBP7ttRQog?t=37 this shows off how to make infinite and 0bpm points.

also, btw, while you're here, do what the above person said and dont make the first point in a map an unnatural bpm value. this is bad. don't do that. generally, avoid using inf or 0 bpm for more than 1ms at a time if you can.
Last edited by gummibar , edited 1 time in total.
DeletedUser_13957006
DeletedUser_13957006
the problem isn't necessarily putting 0 or infinite bpm at the first timing point - though it can extensively break some things that wouldn't otherwise. the game crashes if the editor loads on a weird timing point (either 0 or infinite).

additionally, it is possible to have 0 or infinite bpm as the first timing point of a map if:
  1. you have two timing points or more
  2. the map was last saved on a timing point which is not 0 or infinite
an example of this is Karoo's Acid Rain, where the first timing point is set to infinite bpm
Last edited by DeletedUser_13957006 , edited 1 time in total.
gummibar
92 posts
Joined January 2016
gummibar

Aiq wrote:

the problem isn't necessarily putting 0 or infinite bpm at the first timing point - though it can extensively break some things that wouldn't otherwise. the game crashes if the editor loads on a weird timing point (either 0 or infinite).

additionally, it is possible to have 0 or infinite bpm as the first timing point of a map if:
  1. you have two timing points or more
  2. the map was last saved on a timing point which is not 0 or infinite
an example of this is Karoo's Acid Rain, where the first timing point is set to infinite bpm
this is completely correct, and alot more accurate than what i was saying.
ToothpasteXL
2 posts
Joined December 2020
Topic Starter
ToothpasteXL

TheSpook39 wrote:

your issue is that setting the bpm to 0 just crashes the game. you have to trick osu into rounding the number all the way down to zero, or something like that. whatever the case, here's how to do it properly: https://youtu.be/_sBP7ttRQog?t=37 this shows off how to make infinite and 0bpm points.

also, btw, while you're here, do what the above person said and dont make the first point in a map an unnatural bpm value. this is bad. don't do that. generally, avoid using inf or 0 bpm for more than 1ms at a time if you can.
thanks! this solved my issue.
Please sign in to reply.

New reply

0
1 / 6