If you play on the Velocity engine and would like to transition to the R^3 engine, I'm gonna make it a bit easier for you.
Step 1: Speedmod
R^3 is a different size than the previous engines. Therefore, you will need to use a faster speedmod to accomodate that. To get your new shiny speedmod, simply take your speedmod on velocity and multiply it by 1.085 and round to the nearest nice number to get your R^3 speedmod.
For example, if I play on 2.2x on velocity, my adjusted speedmod for R^3 would be 2.2*1.085 = 2.387, which rounds up to 2.39.
Step 2: Editor
Raise the blue bar 1/5 the way up the screen
(I believe this is the default???) in the editor located in options. This, along with your new speedmod will replicate the feel of the velocity engine.
Example:
Step 3: Random Other Settings
Global Offset - Toy around with this until the notes seem the most on-sync with the music. Don't worry about accuracy judges just yet, just increment or decrement the global offset by whole numbers until it feels the best. You can mess around with decimals if you really want to..
Receptor Spacing - I believe Velocity uses 72, whereas R^3's default is 80. I prefer 72 myself.
Framerate - 30 is good for me. 60 makes it look a bit smoother and gives it kind of a StepMania-ey feel if that's what you'd like. If you want to play a song that is longer than 8 mins 30 secs, you will need to use an FPS higher than 30 or else the song will crash at that 8m30s mark.
Visual & Game Modifiers - A big difference between velocity and R^3 is amazing accuracy. If you would like to turn this off, uncheck the "Show "Amazing" Accuracy" box while keeping the "Show "Perfect" Accuracy" box checked. The other options are pretty self-explanatory and subjective.
Judge Offset -
(For a detailed explanation of Global and Judge offset, please visit YoshL's Tutorial.) This will control your accuracy. To get a good number to set your judge offset to, pick a song that you think you can totally nail with very good accuracy. This can be a 5 or a 95. Just play the file as well as you can, being sure to hit the arrows as accurately as you possibly can. Do not worry if your PA is total garbage, just play confidently so we can get a good number to set your judge offset to. After the song is over, right click your speedmod in the results screen and you will get a window showing your suggested judge offset. Put that number into the Judge Offset field in Options and you should be good to go.
Example of Judge Offset suggestion:
I would enter the 1.107 into the Judge Offset box.
Quote:
Originally Posted by TC_Halogen
From experience, offset of judgment for Velocity is one frame less than the amount you would use for R^3. Velocity also has a general appearance of looking slightly earlier visually in terms of timing.
If you're used to the overall early appearance on Velocity and want to replicate that same 30 FPS environment, you would want a judgment offset of 0. This is going to cause all of your charts to be earlier by a frame; if you find that the offset is too early, then you can add a frame to your global offset.
With that being said, anyone with an offset of 0 on the Velocity engine should theoretically be able to play on offsets 1/1 or 2/0, OR 2/1 and 3/0 (it's one of these two; I can't remember what's correct since I use an offset of 1), with 1/1 or 2/1 making a slightly late appearance and 2/0 or 3/0 with a slightly earlier appearance.
It is also worth mentioning that partial judge offsets will not work if the engine is being used at 30 FPS. EDIT: fixed
For 31+ FPS, I've found that having a judge offset of 0 has been effective in terms of appearance. I just apply the difference between what the right click context menu is telling me to my global offset, rather than the judgment offset.
|
Happy FFRing
