48,084
edits
AC DDR A: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Morning Blue (talk | contribs) (Minimum-maximum BPM showing has been around for a long time. A just had it on-screen at once.) |
Morning Blue (talk | contribs) No edit summary |
||
| Line 52: | Line 52: | ||
** Full combo lamps carry over, though appear as ASSIST clears due to DanceDanceRevolution A's scoring changes. | ** Full combo lamps carry over, though appear as ASSIST clears due to DanceDanceRevolution A's scoring changes. | ||
* When using the Screen filter option, if a chart ends with Freeze Arrows, the filter now disappears at the end of the arrows instead of at the start. | * When using the Screen filter option, if a chart ends with Freeze Arrows, the filter now disappears at the end of the arrows instead of at the start. | ||
* Successfully clearing a Shock Arrow now has the O.K. judgement and the combo increase appear immediately | * Successfully clearing a Shock Arrow now has the O.K. judgement and the combo increase now appear immediately. | ||
* Timing windows have been adjusted to remove the "magic BPMs" problem that existed in previous games: | * Timing windows have been adjusted to remove the "magic BPMs" problem that existed in previous games: | ||
** As the Marvelous timing window is exactly 1 frame, and inputs and timing windows are measured by whole numbers of frames only, the resulting roundoff error would cause the Marvelous window to drift back and forth throughout the song, making obtaining a Marvelous Full Combo prohibitively difficult. (For example, a song with a BPM of 160 has a beat every 22.5 frames, so even a frame-perfect player aiming for a Marvelous Full Combo would have to hit some beats 22 frames apart and some beats 23 frames apart, as the Marvelous windows would be anchored on/rounded to whole numbers of frames.) The only exceptions to this problem were songs whose BPMs were factors of 3600 (such as 225, 200, 180, and 150), which would have an exact whole number of frames in between beats and be immune to the roundoff error problem. Effectively, songs with these "magic BPMs" were the only ones where it was reasonable to obtain a Marvelous Full Combo. This game fixed the problem, though it is unknown whether inputs and timing windows are now measured at the subframe level, or whether the rounding for the timing windows now rounds away from center (which would also fix the problem without having to measure subframe inputs or change how inputs are measured). | ** As the Marvelous timing window is exactly 1 frame, and inputs and timing windows are measured by whole numbers of frames only, the resulting roundoff error would cause the Marvelous window to drift back and forth throughout the song, making obtaining a Marvelous Full Combo prohibitively difficult. (For example, a song with a BPM of 160 has a beat every 22.5 frames, so even a frame-perfect player aiming for a Marvelous Full Combo would have to hit some beats 22 frames apart and some beats 23 frames apart, as the Marvelous windows would be anchored on/rounded to whole numbers of frames.) The only exceptions to this problem were songs whose BPMs were factors of 3600 (such as 225, 200, 180, and 150), which would have an exact whole number of frames in between beats and be immune to the roundoff error problem. Effectively, songs with these "magic BPMs" were the only ones where it was reasonable to obtain a Marvelous Full Combo. This game fixed the problem, though it is unknown whether inputs and timing windows are now measured at the subframe level, or whether the rounding for the timing windows now rounds away from center (which would also fix the problem without having to measure subframe inputs or change how inputs are measured). | ||