View Single Post
Old 07-2-2014, 10:29 AM   #12
TC_Halogen
Rhythm game specialist.
Retired StaffFFR Simfile AuthorFFR Music ProducerD8 Godly KeysmasherFFR Veteran
 
TC_Halogen's Avatar
 
Join Date: Feb 2008
Location: Bel Air, Maryland
Age: 32
Posts: 19,376
Send a message via AIM to TC_Halogen Send a message via Skype™ to TC_Halogen
Default Re: ATTN: Velocity Players who want to play R^3

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.

EDIT: this is generally helpful information; stickied.

Last edited by TC_Halogen; 07-2-2014 at 10:44 AM..
TC_Halogen is offline   Reply With Quote