Beta Engine: R^3 [Updated 6/5/14]

[SC_coolguy44]

Originally Posted by badman7772

Too bad having higher frame rates makes the score not record.

Ya. They should have it record in the next build of R^3.

[Poison-]

Cool new features, I just can't seem to get less than 100 goods on any songs...

[~Zeta~]

Is there a way so we can see how judge offset is working? Like a red line or something that shows were the middle perfect is? Or have a feature similar to screencutting allowing personal placement of the middle perfect (with the rest of the accuracies set around this, of course)? Still having tremendous issues with finding the right window/offset for this engine.

[EDIT: or be able to move the arrows some pixels to set offset?]

Question:

How do decimal offsets work? Do they work for judge offsets and file offsets? I'm wondering because the difference between +1 judge offset and +1.1 is a late perfect frame on +1 but on +1.1, it feels like there's absolutely none.

[bmah]

I stuck a little note in the tips and tricks section on the first post:

• If you formerly used the Velocity engine, most people have found that the equivalent in this engine is a Global Offset of 2 with a Judge Offset of 0.

It's silly to expect people to find a value like this on their own when transitioning. I figured everyone else should know.

[PrawnSkunk]

Holy crap. RATO is actually a beautiful song on 0.7x

[Ozo194]

TGWP isn't working

[arcnmx]

So, new update, many changes. The universal multiplayer is here in preparation for the multiplayer tournament, which will work in conjunction with the soon-to-be-updated Legacy and Velocity engines so go sign up now! Judging on FPS mode has completely changed again, and needs much more testing wrt how it feels compared to the old 30fps mode. Also, as requested replays can now be saved with rates/framerates.

New Sekrits:
1) Right-click on the "Speed/Mods" line on the song results screen to view your recommended judge offset. A good idea might be to turn off all judge/pa feedback settings, play a song, then check the suggested offset.
2) Right-click on "Judge Offset" to find a menu for setting custom judge windows. An example would be the following:
-58,5:-42,25:-25,50:-8,100:8,50:25,25:42,25:58,0
Each entry is separated by a colon and consists of two numbers comma-separated. The first number in an entry is the window's position in milliseconds (0 is the sweet-spot center of the note), the second number is the score value (Amazing is 100, Perfect 50, Good 25, Average 5, Miss 0).

06/14/13
• Now saves last-used rate and framerate settings
• Rates now work on all old and legacy songs
• New universal multiplayer support
• More robust judge timing with high FPS
• Rates and framerates no longer disable replay saving
• Mouse cursor now hidden when in-game

Random replies below...

Originally Posted by awein999

In case this hasn't been requested yet:
In random play I'd love an option to play any random non AAA'd song. Right now all I see if 1-99 filter if that's correct?

All this will be possible once filtering and searching actually gets worked on. The random filter really was only done early because it was kind of required for the multiplayer :P

Originally Posted by Wayward Vagabond

rates are broken for me. it worked for a song but then every other song when trying to play on rates just breaks the mp3 and plays the song at like 2.0. the file scrolls at the selected rate the song just shits itself though

This should be fixed now.

Originally Posted by cedolad

hey arc, how hard would it be to add in a bpm display?

Well, gathering the bpm from all songs could take a bit of effort. BPM can be roughly inferred from the chart's arrow colours, assuming the song isn't all blue notes. It could be a bit useful with deciding rates, I'm not sure it's worth it though.

Originally Posted by cedolad

also how do you guys feel about a separate scoreboard for rated scores?

I think other things are going to take priority over something like this, even if it'd be nice to have. I'd imagine that the rate would be factored into the scores, and a similar problem to combo scoring could exist where decent scores on a certain rate might be overwritten by "worse" scores that are just worth more on a higher rate.

Originally Posted by SC_coolguy44

Ya. They should have it record in the next build of R^3.

Originally Posted by popsicle_3000

so if i understand, 60fps = no recorded score? is there plans to make it record eventually?

Soon. Two problems still exist:
1) Songs with backgrounds need to have score saving disabled in 60fps mode.
2) Songs with audio that start late (Autumn Insomnia Session, The Big Crunch, others I think?) still need to be fixed.
If anyone's up to making a list of songs for both of these categories that would help immensely :P
Also 3) Again extensive testing needs to be done for fps mode's timing windows

Originally Posted by ~Zeta~

Is there a way so we can see how judge offset is working? Like a red line or something that shows were the middle perfect is? Or have a feature similar to screencutting allowing personal placement of the middle perfect (with the rest of the accuracies set around this, of course)? Still having tremendous issues with finding the right window/offset for this engine.

Decimal offsets should feel a lot more consistent now, and the sekrit mentioned above should help a bit with finding a good judge offset that works for you. A more interactive way of setting up offsets for the future will be considered though, it would definitely be a nice feature to have.

Originally Posted by Ozo194

TGWP isn't working

It only works in non-30fps mode, since it's the fps changes that made it possible.

[EzExZeRo7497]

Is there a way to show the cursor ingame for only the Editor? It gets pretty annoying when you're trying to adjust screen cut, haha.

[ilikexd]

Originally Posted by arcnmx

New Sekrits:
1) Right-click on the "Speed/Mods" line on the song results screen to view your recommended judge offset. A good idea might be to turn off all judge/pa feedback settings, play a song, then check the suggested offset.
2) Right-click on "Judge Offset" to find a menu for setting custom judge windows. An example would be the following:
-58,5:-42,25:-25,50:-8,100:8,50:25,25:42,25:58,0
Each entry is separated by a colon and consists of two numbers comma-separated. The first number in an entry is the window's position in milliseconds (0 is the sweet-spot center of the note), the second number is the score value (Amazing is 100, Perfect 50, Good 25, Average 5, Miss 0)..

This will be immensely helpful for someone like me who can't seem to get it right. Many thanks.

Edit: I don't know if 1) is working. I played a song multiple times hitting as accurately as possible then early on purpose and it just says Accuracy: 0.000 [+/- 0.000]

[arcnmx]

Originally Posted by EzExZeRo7497

Is there a way to show the cursor ingame for only the Editor? It gets pretty annoying when you're trying to adjust screen cut, haha.

lmao, what an oversight.

Originally Posted by ilikexd

Edit: I don't know if 1) is working. I played a song multiple times hitting as accurately as possible then early on purpose and it just says Accuracy: 0.000 [+/- 0.000]

Consider pretty much everything mentioned to only work in FPS mode (set to 31 fps or higher) unless otherwise stated. I'll throw it into the 30fps mode too when I get a chance, though.

[Garquillex]

Originally Posted by arcnmx

• Mouse cursor now hidden when in-game

^____________^

[___________]

Originally Posted by arcnmx

06/14/13
• Now saves last-used rate and framerate settings
• Rates now work on all old and legacy songs
• New universal multiplayer support
• More robust judge timing with high FPS
• Rates and framerates no longer disable replay saving
• Mouse cursor now hidden when in-game

flashflashrevolution.com/~arcnmx/

[~Zeta~]

Beautiful.

[kjwkjw]

Neat update, thanks arc!

Also it seems that rate settings are also saved for Flash 9. Meaning if you've played with rates on Flash 10/11 and want to go back to 9 for normal play, you have to change your rate back to 1.0 on either Flash 10 or 11. Would it be possible to have a workaround for this? (It's a very minor issue only players who use multiple versions of Flash might run into, so it's fine if there isn't a workaround, haha)

[foxfire667]

Oh man this custom judge window stuff, I love it! Here are some things I messed around with:

Amazing all the notes (boos and misses still possible, mashing causes arrow blinking at times):
-1000,100:1000,100


Normal timing with average on the other side of the window:
-116.6,25:-83.33,25:-50,50:-16.6,100:16.6,100:50,50:83.33,25:116.6,5:140,0

Only the amazing frame:
-16.66,100:16.66,100



It should be noted that if you set the window to an extreme number (like 1000+) hitting the notes very early or mashing can result in the screen blinking and the arrows disappearing for a short bit.

I should also mention that in order to turn off the custom judge window (since I don't see it in the post) you have to open the custom window setting again, actually type in 0, and press enter. It cannot be reset currently by setting your frame rate to 30, or by typing in 0 / 1 / whatever in the judge offset box. Even though the judge window modifier doesn't work on 30 FPS, it still shows it as a mod in the results screen and will not let me record a score.

Also, perhaps it was just the songs I tested, but I feel a decent improvement in scoring now when playing on rates with a higher FPS (60). Was able to AAA Excite Bike 3x twice in a row without any hassle, and pull 2g on Power 25x twice in a row, which is pretty awesome. Obviously playing on less ridiculous rates gives even better results for me in the songs I tried.

Fantastic update man, I love it!

[Zapmeister]

-1000,100:1000,100

i'll get an AAAA on this sometime

these new features are fantastic

[Xiz]

arcnmx 2013

[arcnmx]

Originally Posted by kjwkjw

Neat update, thanks arc!

Also it seems that rate settings are also saved for Flash 9. Meaning if you've played with rates on Flash 10/11 and want to go back to 9 for normal play, you have to change your rate back to 1.0 on either Flash 10 or 11. Would it be possible to have a workaround for this? (It's a very minor issue only players who use multiple versions of Flash might run into, so it's fine if there isn't a workaround, haha)

Aha, hadn't considered that. Will fix.

Originally Posted by foxfire667

Oh man this custom judge window stuff, I love it! Here are some things I messed around with:

Also, perhaps it was just the songs I tested, but I feel a decent improvement in scoring now when playing on rates with a higher FPS (60). Was able to AAA Excite Bike 3x twice in a row without any hassle, and pull 2g on Power 25x twice in a row, which is pretty awesome. Obviously playing on less ridiculous rates gives even better results for me in the songs I tried.

Fantastic update man, I love it!

Hm, one thing I should mention about the judge windows is that it sets the score for everything higher than the time given, so "-1000,100:1000,100" is the same as "-1000,100" which just means amazings for everything 1 second before the note and later.
So -16.66,100:16.66,100 should actually be -16.66,100:16.66,0

Improvement is good, I was hoping this scheme would feel a lot more consistent. The old one tended to feel like it dropped the windows randomly at points, this one should be a lot better about that. However, at the same time it shouldn't really be considered easier or more lax, just more consistent (or so I hope, that's what I need the most feedback on).

Originally Posted by ___________

flashflashrevolution.com/~arcnmx/

This needs to happen :P

Originally Posted by Xiz

arcnmx 2013

Does this feel any better to you on framerates? You're probably still getting that random input delay though :/

[~Zeta~]

Can you make it where the image uploader goes away when you hit the restart key?

[foxfire667]

Originally Posted by arcnmx

The old one tended to feel like it dropped the windows randomly at points, this one should be a lot better about that. However, at the same time it shouldn't really be considered easier or more lax, just more consistent (or so I hope, that's what I need the most feedback on).

Thanks for the info on the judge window, I'll keep that in mind the next time I play with it.

Yes, it feels more consistent, like the inaccuracies I obtain on the songs are mine, and not typically the result of the game handling rate judging strangely. The judging didn't feel lax compared to the normal judge window when I played, it felt like it should. I'll try it again more today, but from my last session messing with this I felt it was pretty solid in terms of window accuracy.