Beta Engine: R^3 [Updated 6/5/14]
Collapse
X
-
Re: Beta Engine: R^3 [Updated 7/26/13]
You average (first) off the amazing frame, Give or take (second).
If the second number is large, you just aren't hitting accurately, if the first number is large and the second is small, adjust offset/judge etc. So by playing a song you are familiar with, you can minimize your own error and determine with the first number what an appropriate offset would be to correct your timing.Last edited by omega_grunt666; 02-7-2014, 07:59 PM.Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
Thanks! So is there a way to get rid of the receptor flash when you hit an arrow. That's Extremely distracting.You average (first) off the amazing frame, Give or take (second).
If the second number is large, you just aren't hitting accurately, if the first number is large and the second is small, adjust offset/judge etc. So by playing a song you are familiar with, you can minimize your own error and determine with the first number what an appropriate offset would be to correct your timing.Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
the flash really isn't much of a distraction, but if you really find it annoying, try the dark mod, it should mitigate a lot of its effectsComment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
I tried it, but the flash seems opaque in my mind. kind of like a mindblock on an easy chart, irritating to the point of unplayable.Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
I like the concept, the songs load faster. But I have some complaints, I don't know if it's only me but I feel the arrows are out of sync with the music and they have a light 'shadow' when coming up, makes them harder for me to see them. But apart from that everything is cool, it's easy to get used to it
Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
Cross post from another thread to help with the sync issues:
Play with those settings until you find something comfortable, and then let us know how you like it~Receptor Spacing: Just the horizontal space between the arrows. Larger numbers make the game appear wider, smaller ones do the opposite.
Framerate: FPS the game runs at, has to at least be set to 30. Many people use 60 or 120 to make the game look and run much smoother.
Rate: Speeds up the song you're playing, 1.5 makes everything 50% faster, 0.5 slows the song down, etc. Use it to make easy songs harder or hard songs easier.
Global Offset: Audio sync
Judge Offset: Video sync
Also advice for finding a judge offset that works for you:
Hide judge popups in settings, play through a song you're confident you can play well. On the results screen right click on the "Speed:" line under your score. The first number it gives (not the +/- one) is what you should use as judge offset. Keep checking it after a few songs and see how stable it is. Using a high framerate makes this process more accurate.
more explanation on the offsets:
If you aren't sure how they work, here's the breakdown:
Global offset is how the song and arrows sync up. Moving the offset +1 on global results in the notes being shifted 1 frame later in the song than they previously were. So this should be used to get the general idea of when the music should line up with the arrows/receptors.
Judge offset is used on a smaller level, determining when you can hit the arrows. If you're seeing a lot of perfects/goods instead of amazings, you need to analyze whether you're hitting early or late more and adjust accordingly. If you seem to be hitting a bunch of early goods even though to you the receptors are "lined up" then go ahead and shift the judge offset +amount that way you "hit" those values a little earlier than the normal window, etc.
Comment
-
Comment
-
-
Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
I think I had this a few times, but I'm not sure if it's just me being stupid or not. An annoyingly frequent problem for me is when it does register, just a good bit after I press the key, resulting in a miss and a boo. :/
Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
Hmmm very interesting. I have always blamed it on my keyboard, which is honestly still quite possible. But, every once in a while I do have random misses that I clearly pressed. Still, at this point I will continue to blame my keyboard unless there is any factuality to this whole "r3 makes you miss" business.

I'm just an old boy nowComment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
the R^3 makes me feel like a noob again. songs I can FC regularly on the velocity engine I can't even get a B rating on with R^3. Imma stick with the new one though. I'll get used to it at some point. I think my whole ability to play this game relies on the shorter window. my life is a lie! ugh! it's why I can kick ass at velocity FFR and just cant' seem to cut it on Step mania.... I think... ah well. thems 'r' my rambles on the matter.Comment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
Well sometimes I do wonder if it could be my keyboard, as my d, j, and k keys are all missing paint because of my hardcore mashing. I'm not trying to make excuses, I just want to make sure it's not this engine and if it is me, I'm going to be pretty mad at myself for ruining some otherwise good scores. xDComment
-
Re: Beta Engine: R^3 [Updated 7/26/13]
You might have to change your offset. When I first played on this new engine I was getting a crapload of boos, misses, and goods until I changed my judge offset to 1. I was like: shit this judge is damn hard. Apparently people that are used to the old Velocity Engine might need to do that. Read the OP.the R^3 makes me feel like a noob again. songs I can FC regularly on the velocity engine I can't even get a B rating on with R^3. Imma stick with the new one though. I'll get used to it at some point. I think my whole ability to play this game relies on the shorter window. my life is a lie! ugh! it's why I can kick ass at velocity FFR and just cant' seem to cut it on Step mania.... I think... ah well. thems 'r' my rambles on the matter.
Edit: oh yeah, is this the right place to make a request?Comment









Comment