I think FFR should use Ruffle.

[Usuario]

Thoughts?

[Velocity]

Re: I think FFR should use Ruffle.

There's currently a few challenges using Ruffle with FFR:
- Legacy and Velocity engines are retired due to age and maintainability.
- R3, the current version of FFR uses AS3/AVM2 which is still missing support a lot of features that we use within the game.

R3 missing features also extend farther since we use several features only available to Air, not Flash, which are unlikely to ever be supported in Ruffle.

Ultimately at this time, the game still has issues when running under Ruffle that isn't easy to solve, but will likely get better at a later point in time, if FFR continues to use Flash in the future.

[gold stinger]

Re: I think FFR should use Ruffle.

God damn Velo ninja'd me.

Ruffle's AS3 (ActionScript 3) support just came out late 2022 and is still very much in-development. A lot of the basic stuff is there, but FFR uses a set amount of non-standard API-related tools that Ruffle hasn't covered yet, including Sound (So, goodbye streaming audio).

Maybe it will be better in the future, but it's not like Ruffle is necessarily making changes to accommodate us specifically. They're likely racing to preserve other more important titles considering our downloadable version still works.

[Travis_Flesher]

re

standalone flash player 32

[WolfTypist]

Re: I think FFR should use Ruffle.

I think that the browser version should stay up on the website for as long as it can, just for a little time capsule ig.

[Mihari]

Re: I think FFR should use Ruffle.

I didn't even live through that era