FFR Arrow BPM

[TC_Halogen]

Re: FFR Arrow BPM

That's odd. Maybe you should send a private message to one of the forum administrators about the problem? (Sprite-, Velocity, aperson, Zageron)

[Goron HD]

Re: FFR Arrow BPM

thanks I'll do that

[igotrhythm]

Re: FFR Arrow BPM

Going back to the OP:

We have to make a distinction between BPM, which is a parameter of the song (beats per minute) and scroll rate, which is the rate at which the arrows move across the screen towards the receptors.

To clarify:
BPM applies to the song.
Scroll rate applies to the steps.

Now that we've got that out of the way, Patashu is correct. The game screen for the Legacy engine, for example, is 550 pixels wide by 400 pixels high. This is slightly off from the 4:3 ratio that most computer monitors use, and most people when running Stepmania run it in full screen, so your timing will be slightly different. Also of note is the fact that the FFR perfect window is slightly wider than SM's default (Judge 4) marvelous window, a consequence of the way FFR is coded.

ONE IMPORTANT DIFFERENCE: In SM, chords (two or more arrows at the same place) have cohesion: That is to say, they are graded as a unit when the last arrow is hit, and the player receives one grading for the entire chord on the results screen. This is why step grade totals don't add up to the max combo of the song.

In FFR, on the other hand, each arrow is graded separately, forcing you to hit all the arrows in a chord at more or less the same time, which has its own set of issues. There is also the issue of "boos", where hitting a key when FFR does not sense an arrow to be graded leads to you receiving a small deduction to your score. Due to the limitations of the engine, "freeze arrows" are also impossible to include in a file.

The moral of the story: Play around until you find settings that you're comfortable with for both games. Some people even change their settings to try to do better on individual songs.