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

[axith]

Re: Beta Engine: R^3 [Updated 4/13/13]

Well then, I'd like to know about updating the DWI converter to support 60 frames per second files..

That's one thing I've been wondering about for the last couple months. But I don't know enough about stuff to know if it would break legacy.

Anyhow, Thank you so much for bringing r^3 to multiplayer. The graph changes are awesome too.

[bballa48]

Re: Beta Engine: R^3 [Updated 4/13/13]

Any way to block your opponents combo/accuracy in multiplayer?

[retching oesophagus]

Re: Beta Engine: R^3 [Updated 4/13/13]

The new features are awesome, thank you so much. I played a little and I can't wait to try them out properly next week but it's lookin good.

[FissionMailed1]

Re: Beta Engine: R^3 [Updated 4/13/13]

But I don't know enough about stuff to know if it would break legacy.

To be honest, legacy files need to go. They are just detrimental to new players, and everybody that I have talked to about them finds them really awful to play.

[arcnmx]

Re: Beta Engine: R^3 [Updated 4/13/13]

Indeed, encoding songs at 60fps would break all the other engines, so it can't be used for FFR songs. The goal is to change R^3 to run fps-independent and move away from frame timing altogether, then it wouldn't matter what the songs are encoded at. This is something that will take time, but if an alt engine host wanted to encode songs at 60fps that would only work on R^3 I could implement some quick fixes that would make it work.

Any way to block your opponents combo/accuracy in multiplayer?

There is not an option for this currently. The MP interface itself is still very much a work in progress.

[FissionMailed1]

Re: Beta Engine: R^3 [Updated 4/13/13]

encoding songs at 60fps would break all the other engines

The issue with this is that FFR should be aiming for one universal engine, much like ThirdStyle already has. It just causes unnecessary confusion and complication when there is multiple engines for what could be a one-size-fits-all engine. Also, if you move FFR to MS timing, you are just going to make a direct competitor to ThirdStyle as well. Maybe that is exactly your intention, but do what you want.

[arcnmx]

Re: Beta Engine: R^3 [Updated 4/13/13]

Well, one engine is certainly the goal, but it will take time (and with how everyone is set in their ways, seems like it's going to be a long time).

While I can't comment too much on thirdstyle - since every time I try it the sync is off by a good half-second and the offset options do absolutely nothing - the goal is more about getting the game running smoothly for everyone and fps locks are a bad way to go about doing that. It doesn't necessarily mean ms timing though, just higher resolution timing at however fast you can manage to run the game (probably 60fps in almost all cases).

[FissionMailed1]

Re: Beta Engine: R^3 [Updated 4/13/13]

I was just using ThirdStyle as an example of standardization. In regard to people using different engines, that's just a matter of providing the appropriate customization so it behaves similar to people's favorite engines.

The crux of the issue then becomes getting everybody to run at 60 FPS instead of 30 FPS. I don't know difficulty this would be, since I don't have access to the source (wink wink nudge nudge). You could always include a 60 FPS and 30 FPS version of the charts though, assuming the player has a powerful enough CPU to run it at 60 FPS.

[Charu]

Re: Beta Engine: R^3 [Updated 4/13/13]

Oh yeah, folks. I was helping Arc with this when he was testing it out, but... you all might be wondering what he meant by this.

The game can also be used to play additional songs from alternate engine playlists.

Well, it's exactly what it sounds. With this new build, you can play alternate engine songs using FFR's R^3 engine. Better unifying an all in one package, oho.

For example sake, I'm going to use the Team Blaze engine since we have that.

Under options, you'll notice something called "engine playlist" and it'll ask for input. Well...

Using this link: http://teamblaze.zxq.net/r3.xml

And then selecting Team Blaze Engine as it loads up... You can access our playlist and even load our level swfs using R^3.

Arc can better explain this so everyone who has an engine up and running somewhere can have this work. But that's what he meant by that added feature.

EDIT: ALSO, here's a neat feature. You can actually play MP with alternate engine songs, granted the opponent is ALSO using R^3.

[m0de]

Re: Beta Engine: R^3 [Updated 4/13/13]

is there a way to screen cut?

[foxfire667]

Re: Beta Engine: R^3 [Updated 4/13/13]

Wow, there is some really insane stuff going on with this new update, this is awesome! I'm testing a lot of the features at the moment, and after playing a couple of songs my timing actually feels pretty much correct (even with judge options on the old R^2 or 3 I couldn't get it to feel right for some odd reason). I might even ditch the old Velocity engine altogether if it still feels decent with harder files.

The only thing I'm wondering from what I have tested so far is why when you play a song segment, you don't get any score for that file. I can understand disabling score recording for the other modifications (it would be even better to receive grand-total score from songs played this way, but not have them record on leader boards if possible) but isolation is just that. You are literally just playing a segment of a song, so it isn't like you could achieve a score that is better than your best or something because of the option. Even if you could, it's just you playing the song normally, only with less possible arrows to hit.

It isn't like it's a big deal, but I'm sure the GTS could rack up a bit if someone is practicing a fairly longer section of a song several times. Might as well give them the GTS and play counts they earned.

I'm really interested in this alternate engine support, especially with multiplayer. That sounds ridiculously amazing, perhaps even good enough to get some more people in the lobby again if they find out.

[Xx{Midnight}xX]

Re: Beta Engine: R^3 [Updated 4/13/13]

These updates are awesome, but if it could be re-sized ect to be just like the velocity / legacy engine I'd love it more because for some reason it reads and plays so differently and it drives me nuts.

But best to fix what's here first :3

[Tarrik]

Re: Beta Engine: R^3 [Updated 4/13/13]

Epic Updates

[DissonantMuse]

Re: Beta Engine: R^3 [Updated 4/13/13]

I knew there had to be a good reason for the engine not being accessible earlier. Awesome updates!

[arcnmx]

Re: Beta Engine: R^3 [Updated 4/13/13]

These updates are awesome, but if it could be re-sized ect to be just like the velocity / legacy engine I'd love it more because for some reason it reads and plays so differently and it drives me nuts.

It would be nice to basically have the game support themes and complete customization of the visuals so that everyone can feel right at home, haha. Will probably be a while though because other things do take priority :/

The only thing I'm wondering from what I have tested so far is why when you play a song segment, you don't get any score for that file. I can understand disabling score recording for the other modifications (it would be even better to receive grand-total score from songs played this way, but not have them record on leader boards if possible) but isolation is just that. You are literally just playing a segment of a song, so it isn't like you could achieve a score that is better than your best or something because of the option. Even if you could, it's just you playing the song normally, only with less possible arrows to hit.

It isn't like it's a big deal, but I'm sure the GTS could rack up a bit if someone is practicing a fairly longer section of a song several times. Might as well give them the GTS and play counts they earned.

You raise a good point, personally I feel like all the mods that disable score saving should still reward the player with GTS and credits. I believe there are serverside reasons why this won't happen but I'll look into it.

Arc can better explain this so everyone who has an engine up and running somewhere can have this work. But that's what he meant by that added feature.

Yeah, I should expand on this. An alt engine site requires a permissive crossdomain.xml file such as this and an engine XML which is the link you give to R^3. The format is pretty self-explanatory if you look at Charu's example, the legacySync stuff is optional stuff needed for some engines where the sync differs between songs with different levelids. Another optional flag is ignoreCache="true" where the game will always reload the song between plays (useful for testing out songs as you chart them, mainly). If you need help with it just ask, but it's mostly up to the people hosting alt engines to support it.

is there a way to screen cut?

There is not, it's something that still needs to be done.