FFR Suggestions

[One Winged Angel]

My only qualm with allowing rates higher than 1.0 to record on the same scoreboard is for instances where a higher rate actually makes the song easier to PA, and these instances do exist given FFR's timing and the way the converter adjusts frames for the file on specific rates. If the song is legitimately more difficult on the higher rate (which it will be 99.5% of the time), obviously the player is more than capable of doing just as well or better on a lower rate, so why not record it?

The argument Fission posted that was supposedly mine is incredibly dumb and I'm upset that my name is being tagged to it lol

[TheSaxRunner05]

Originally Posted by One Winged Angel

My only qualm with allowing rates higher than 1.0 to record on the same scoreboard is for instances where a higher rate actually makes the song easier to PA, and these instances do exist given FFR's timing and the way the converter adjusts frames for the file on specific rates.

Maybe these songs just need framer fixes.

[axith]

Originally Posted by One Winged Angel

My only qualm with allowing rates higher than 1.0 to record on the same scoreboard is for instances where a higher rate actually makes the song easier to PA, and these instances do exist given FFR's timing and the way the converter adjusts frames for the file on specific rates.

I imagine it would make Story of Snowman and Sunshine Girl easier to AAA. Or make files with barely non-jumptrillable rolls easier too. As for the 'easier to grind for GTS and creds' arguement. I say that anyone who cares to mash for vrofl, or Dendrite v2 can do it. It sucks to mash for them. Getting scores recorded on higher rates won't really make mashing for them suck any less.

I don't know if the site architecture is such that a score with rates can be put toward credit count and gts, but not to the levelranks. But if this is an option, I think I'd prefer it. Otherwise. I like the idea of scores on rates 1.1 and higher recording.

[Fission]

not really that legit of a reason imho. you can just modify vrofl requirements and credit counts for higher rates. problem solved.

Originally Posted by One Winged Angel

The argument Fission posted that was supposedly mine is incredibly dumb and I'm upset that my name is being tagged to it lol

i already said that if you didn't make that argument, feel free to correct me. i was just really convinced you did, but i'll take your word for it.

Originally Posted by mi40

higher rates would cause worse frame placements in every single case so idk

it makes rolls easier in the sense that it makes the frames closer together so they are more forgiving if you aren't as consistent. same with hitting trills as jumps on higher rates.

[ryuyasha]

Originally Posted by Fission

not really that legit of a reason imho. you can just modify vrofl requirements and credit counts for higher rates. problem solved..

But would you want to have to balance all that out? That is not something you could just slap a coefficient on and have it work, or even a standard function curve.

[mi40]

i hope this gets discussed between the site admins cause it would add a LOT more replay value to the game

(with incentives of course, like being rewarded for AAAing beethoven virus on 1.5, which would be an AAA in levelranks + same GT/creds you would've gotten as 1.0)

[YoshL]

i'd like to say, AJ (TC_Halogen) tried to test this theory with something like, Skeletor. At around maybe 1.2/1.3, the rolls would basically be jumptrillable, leading to easy AAA right?

yeah, even at his level, he says the initial first half is dumb, and even the speed of the roll gets super dumb

basically, cool, frame gaps get fixed, but you're still playing the song faster than before, and the "cheating patterns" may be easier, but you're still playing a faster, more draining song.

[Fission]

+1 to adding rate incentives

[mi40]

credit counts & GT are the same for higher rate songs & 1.0 songs

the only thing is the time spent

but for the most part the time saved playing a song on a higher rate goes into an increased difficulty (harder to FC, thus harder to score on, thus leading to a lower GT and credit count)

[YoshL]

posting a new post so it doesn't get lost in debate lol

look at SM. People don't go wow you put an ez quad file on rates and still quad it that's definitely going against what was originally intended, you don't have the skill to sit through a longer song. bluh

It's not a skill or even like, hard to sit through long songs. It's just tedious, and makes playing FFR not fun. Make FFR more fun. let higher rates record.


Although someone made a point a while back to maybe only let rates at an increment of .1 to record so you don't have people going like 1.0461x to manipulate frames or some dumb crap

also i dare someone to try SSSG on like 4x, seriously that's the most funny crap ever, all the vibrating needed.

[Fission]

Originally Posted by YoshL

look at SM. People don't go wow you put an ez quad file on rates and still quad it that's definitely going against what was originally intended, you don't have the skill to sit through a longer song. bluh

It's not a skill or even like, hard to sit through long songs. It's just tedious, and makes playing FFR not fun. Make FFR more fun. let higher rates record.

^^

[ryuyasha]

Originally Posted by YoshL

also i dare someone to try SSSG on like 4x, seriously that's the most funny crap ever, all the vibrating needed.

That was so ick. Even after I found a reasonable speedmod (3x).

[mi40]

made by the people for tha people....

[mi40]

why would GT/credit count be prioritized and not levelranks lol

[HalfStep]

The game doesn't change the frame structure though, it just compresses the whole file, frame gaps and everything.

Example of what I mean, put Pure Ruby on isolation at 1206, and check the roll structure on different rates. It stays the same no matter what.

[One Winged Angel]

Originally Posted by HalfStep

The game doesn't change the frame structure though, it just compresses the whole file, frame gaps and everything.

Okay I just dicked around a bit in R3 and you're right...I'm confused as to how this affects judgment though (the game can't possibly be running in 30fps at this point anymore even if I select that as my framerate option, so I don't know exactly where the perfect window starts and ends...arc?)

Anyways I just isolated the Skeletor wall at 1.1/1.2 and a few other rolly things (DeVouR etc.) I thought should theoretically be much easier to bs through given the higher roll speed, and yeah, I'm finding it much easier to AAA.

Obviously this problem doesn't exist for the vast majority of songs, but it's still there.

[arcnmx]

I already posted about this in the R^3 thread weeks ago but yeah, completely for this. Not allowing them does nothing more than discourage people from playing, while allowing them makes the game more enjoyable for players.

Originally Posted by One Winged Angel

Okay I just dicked around a bit in R3 and you're right...I'm confused as to how this affects judgment though (the game can't possibly be running in 30fps at this point anymore even if I select that as my framerate option, so I don't know exactly where the perfect window starts and ends...arc?)

Anyways I just isolated the Skeletor wall at 1.1/1.2 and a few other rolly things (DeVouR etc.) I thought should theoretically be much easier to bs through given the higher roll speed, and yeah, I'm finding it much easier to AAA.

Obviously this problem doesn't exist for the vast majority of songs, but it's still there.

Rates force the game into fps mode, so it uses the fps timing windows. You might want to compare 1.1 and 1.2 at 30fps with 1.0 at 31fps to force fps mode on. It certainly can make slow rolls easier to jumptrill since it compresses them.

[HalfStep]

It uses milisecond timing if you use 30 fps on rates, and keeps frame timing if you don't use rates.

[One Winged Angel]

Okay yeah ms timing on rates for rolls like that compared to how it's timed out on 1.0 makes it a joke to jumptrill through.

[HalfStep]

Even if it does help with walls and jumptrilling in general, it also makes the rest of the file much much harder. (The jumptrilling reason was why I wanted a minimum rate that would record, like 1.3 or something)