Replies: 2 comments 2 replies
-
This is a great idea, and one we've been discussing for some time. We'd like to allow website owners to customize exactly what features are included in the Ruffle builds they deploy, to allow optimization of load times and download sizes. For now, our AVM1 and AVM2 implementations are not cleanly delineated, but hopefully we can change that in the future. As for the long startup time, I believe is mostly caused by the additional rendering features that have been implemented recently, specifically blend modes. Each new set of features means an additional rendering 'pipeline' needs to be initialized before Ruffle starts, on the off-chance that the Flash content will use it. Maybe we can provide an option to disable blend modes and other expensive features to reduce initialization time. Another option, strangely enough, would be to compile Ruffle with a rendering backend that does not include an implementation of blend modes, because that lack of functionality reduces the startup time. If a feature I just implemented would be accepted, it would be possible to choose the rendering backend without even recompiling Ruffle. But judging from the comments of the core developers, that is unlikely to happen. |
Beta Was this translation helpful? Give feedback.
-
Different versions of Ruffle would be great |
Beta Was this translation helpful? Give feedback.
-
I've had a year old web hosted version of Ruffle installed on a site running AS1 swfs - it works brilliantly! Yesterday I installed the latest version of Ruffle, again all works great but there was a noticeable increase in load times. As Ruffle develops to accommodate AS2 and AS3 I suspect will probably increase further. My question therefore is would it be possible to create a version that solely support AS1 given most code is supported and work flawlessly.
Cheers,
Mark
Beta Was this translation helpful? Give feedback.
All reactions