10th Official FFR Tournament

[Rapta]

Originally Posted by samurai7694

pepper your angus

If the file for round 6 is going to be harder than I had anticipated, looks like I won't be getting a day off of playing FFR until next round starts. If I do this, then MAYBEEEEEEEE I won't drown in the piss water.

[hi19hi19]

Originally Posted by PrawnSkunk

When will D5 get hard?

Sorry what was that I can't hear you because of all that piss you're drowning in

You best fix that soon son

[AlexDest]

96 confirmed next round for D7

[xAlphaWolf]

wow prawn

[DJzAIKz]

prepare for buying a new keyboard

[XelNya]

[Tim Allen]

i still laugh at emo nerd

[GammaBlaster]

Originally Posted by PrawnSkunk

What about D5?


When will D5 get hard?

your HARD bag gives me a HARD-on x)

[XelNya]

Originally Posted by Tim Allen

i still laugh at emo nerd

I really wish I had gotten me punching out my screen on camera

I was playing Frictional Nevada, I was over 70% through it with a BF

and I missed

Thing is, the screen was going out and I had already ordered a new one

It showed up 5 minutes or so after I punched it out. I laughed my ass off when my brother had brought it upstairs.

I wonder how poorly it would have been titled

[The_Halomaster]

It makes me happy to know that even gods at the game are human xD

[Tim Allen]

Epic fail compilation # 14 - fucking gay nerd *** smashes computer screen and more xd

[minhtam2448]

Division 2, I formally surrender. There is no way I can be able to pull off a 4-0-0-0 on tabi shirabe given the equipment that I currently have. I can't run the R^3 engine smoothly enough on this computer to have the timing input properly work, and as for Velocity, the correct offset on that engine for my equipment is somewhere between 1 and 2, and Velocity doesn't accept decimal offsets, thus I cannot time my pattern with the music.

[TC_Halogen]

Originally Posted by minhtam2448

Division 2, I formally surrender. There is no way I can be able to pull off a 4-0-0-0 on tabi shirabe given the equipment that I currently have. I can't run the R^3 engine smoothly enough on this computer to have the timing input properly work, and as for Velocity, the correct offset on that engine for my equipment is somewhere between 1 and 2, and Velocity doesn't accept decimal offsets, thus I cannot time my pattern with the music.

What's your frame rate on R^3?

[minhtam2448]

Originally Posted by TC_Halogen

What's your frame rate on R^3?

Default is set to 30, and I've had tried both 20 and 15. 30 gives me more issues than a lower number, but if I go too low, it would improve the performance the arrows themselves would then start skipping on the screen, making it difficult for me to figure out when I should be tapping the arrows.

[smartdude1212]

Hmm, you should be raising the frame rate, not lowering it. Try 45 or 60 to start with.

If you're like me, those two will run too smoothly and make you go cross-eyed. It's worth trying though.

[TC_Halogen]

Originally Posted by minhtam2448

Default is set to 30, and I've had tried both 20 and 15. 30 gives me more issues than a lower number, but if I go too low, it would improve the performance the arrows themselves would then start skipping on the screen, making it difficult for me to figure out when I should be tapping the arrows.

- try 31 FPS.
- take 2 off of your global offset and 1 off of your judge offset to emulate the same play on 30 FPS. As an example, I play the song Cold Heart and can AAA it on 3 global/1 judge -- on 31 FPS, I can AAA it on 1 global/0 judge with relatively close accuracy.

Playing on 31+ FPS triggers the secondary engine code that allows for more precise values in timing -- this means that you will be able to utilize decimal offsets while still appearing to play 30 FPS. (Decimal values do not work at 30 FPS, and setting your FPS to under 30 just makes it play 30.)

[TheSaxRunner05]

Originally Posted by TC_Halogen

- try 31 FPS.
- take 2 off of your global offset and 1 off of your judge offset to emulate the same play on 30 FPS. As an example, I play the song Cold Heart and can AAA it on 3 global/1 judge -- on 31 FPS, I can AAA it on 1 global/0 judge with relatively close accuracy.

Playing on 31+ FPS triggers the secondary engine code that allows for more precise values in timing -- this means that you will be able to utilize decimal offsets while still appearing to play 30 FPS. (Decimal values do not work at 30 FPS, and setting your FPS to under 30 just makes it play 30.)

I've tried this myself, and it made me worse. Doesn't it make it ms timing like Stepmania or something? Correct me if I'm wrong.

[andy-o24]

I am in such a poor mental state because of this tournament.

-o24

[Lambdadelta]

Is it round 6 yet, no?

k then...

[Jonlovesddr]

attention to anyone in d4 please don't improve