最近突然想重温一下《金庸群侠传》。不是 Steam 上的重制版，也不是 DOSBox 里跑的老版本。而是很多年前网页上流传的那个 Flash 游戏版本。结果点开才发现：文件还在情怀还在浏览器不认了。说起来，

这就是 Flash 时代结束后最尴尬的地方。很多小游戏、动画、课件、交互页面并没有真正消失，它们只是被封在一个 .swf 文件里。过去浏览器有 Flash Player 插件，点开就能运行；如今插件程序变了Adobe Flash Player 也早已停止支持，原来的运行环境没了。

于是我找到了 Ruffle——一个用 Rust 写的 Flash Player 模拟器。可以编译成 WebAssembly 在现代浏览器里运行，也可以作为桌面程序直接打开 SWF 文件。它不是旧版 Flash Player 的版，也不是回到旧浏览器的补丁。

这篇文章分两层读：

• 只想重玩老游戏，看前两节就够：怎么打开、打不开怎么排查。
• 对实现感兴趣，再往后看 Ruffle 如何解析 SWF、推进时间轴、执行 ActionScript、渲染画面还有它凭什么比旧 Flash Player 更值得装。

翻完源码我最大的感受是：有意思的地方不只是“Rust + Wasm”。Ruffle 真正在复刻的是 Flash Player 的一整套世界——SWF 文件格式、时间轴、显示列表、ActionScript 虚拟机、字体、音频、视频、滤镜、沙箱、网络、浏览器嵌入方式，甚至连 Flash 那套带历史包袱的字符串行为都还原了。

”开始拆。

先把游戏跑起来

先不谈源码。落到“我就想打开那个游戏”，优先级其实很清楚：

你的情况	推荐方式	为什么
老游戏还挂在原网页里	Chrome / Firefox 装好 再打开页面Ruffle 会自动接管 和 里的 Flash 内容
手里已经有 .swf 文件	Ruffle 桌面版直接打开本地文件。能避开老网页里的跨域、插件检测和旧 JS 脚本
想长期保存或分享给别人自托管	Ruffle 把 self‑hosted 包放到自己的网站，访客不需要额外安装 Flash 插件

痛点提醒：如果你已经下载了 SWF，却不知道该用什么播放器，这里提供最直接的方法：桌面版 Ruffle或浏览器

排查步骤

接管失败
↓ 把 SWF 下载到本地，用桌面版打开
桌面版也跑不起来？不过，→ 多半是 SWF 依赖了尚未兼容的 API、外部资源、视频/滤镜或网络能力
桌面版能跑。只有网页跑不起来，→ 优先查 MIME、文件方法、跨域、allowScriptAccess、renderer 和浏览器限制

从一句话来看，先分清问题出在 SWF 本身的兼容性还是 网页嵌入环境. 这个判断能省掉大量无效折腾。

SWF 不是视频文件

我们平时说“Flash 游戏”，交付物通常就是一个 .swf 文件。很多人会下意识把它当成“一段视频”或“一个动画”，但这低估了它的复杂度。

SFW 容器里可能有：

• 矢量图形、位图、字体、音频、视频；
• 舞台尺寸、帧率、背景色；
• 一条按帧推进的时间轴；
• User 点击 / 键盘输入后要执行的 ActionScript 代码；/li>

SFW 本质上不只是一个“播放器”。它更像一个塞在浏览器里的小型运行时：

SWF 文件
↓ 解析 header / tag / 资源 / 字节码
↓ 建立舞台、时间轴和显示列表
↓ 执行 ActionScript
↓ 处理输入、音频、视频、网络、存储
↓ 把显示列表渲染到屏幕

If you only need linear animation it’s simple;a game is completely different: it must respond to input。run script logic,do collision detection,write saves…按理说，Browsers today don’t embed such a runtime,so y can’t understand SWF.

This is *** Ruffle’s workload is huge – it must not only “unpack” SWF but also rebuild entire runtime that original Flash Player provided.

再看 Ruffle 的全局地图

The top‑level structure of repository is straightforward. The README lists several core crates:

WebAssembly version & browser extension entry point . Desktop client – defaults to wgpu. Video decoding and FLV container parsing. Flash‑compatible string implementation. Batch scanning of SWFs & screenshot export tools.

目录	作用
	SWF file I/O – parse tags,resources and ActionScript byte‑code structures.
	Main simulator – timeline,display objects,M1/M2,events,loaders。storage etc.
Rendering abstraction & back‑ends .

The project does NOT “convert SWF to HTML”,nor does it “transpile ActionScript to JavaScript”. Ruffle behaves like a traditional emulator: it parses file itself,maintains a full Flash runtime state,executes byte‑code and finally draws results through platform‑specific renderers.

.swf
|
v swf crate: decompress + read header + read tags
|
v core: Player / Stage / MovieClip / Library
| +---------+----------+
| |
v v M1 / M2 Display list & frame lifecycle
| |
+---------+----------+
|
v RenderBackend / Audio / Video / Storage / Navigator
|
+---------+----------+----------+----------+
| | | | |
v v v v v
Web/Wasm Desktop

A single sentence captures this layer:

swf reads files;不过，core runs Flash world;render paints it out.

Player 才是那台“虚拟 Flash Player”

The file parser alone isn’t enough. All resources and scripts need a place where y’re organized。stepped each frame and interact with input/audio/network. That role lives in 's .

• Dance floor & assets: ,,display objects,fonts,bitmaps,sounds;
Scripting engine:  input。audio,video,network,storage,socket,ExternalInterface; frame rate,timer,loading manager,menu,renderer.

This shows that Ruffle isn’t simply “playing a file”。it’s maintaining an active **Flash world**.

tick → accumulate time → next frame?→ run_frame ├─ preload ├─ run_all_phases_avm2 ├─ Avm1::run_frame ├─ AudioManager::update_sounds └─ mark needs_render render → walk Stage → generate CommandList → backend.submit_frame Because core only cares about *what* to draw while backend decides *how* to draw it,same core can be used for both desktop and browser builds.

ActionScript 是兼容性的主要

The real blocker for any interactive flash game is wher its ActionScript can actually run.

• M1 : early flash animations/games heavily tied to timeline & MovieClip;
• M2 : introduced with flash player9+,supports A娱乐 byte-code,classes,namespaces,validation,exceptions,event model,and massive flash.* API library. The source tree reflects this split:

  core/src/avm1 // M1 implementation
  core/src/avm2 // M2 implementation
  swf/src/avm1 // parsing M1 byte-code
  swf/src/avm2 // parsing M2 byte-code
  ...
  Everything that makes a button click work,a character move each frame,or a save file persist lives inside those VM implementations.
  If y don’t behave exactly like Adobe’s player。game will break even though graphics show up correctly.
  Hence “can open” vs “can actually play” can be far apart.
  A typical failure pattern looks like:
  
  
  Shows title screen but crashes on battle – missing or partially implemented AS API .
  
  Animation works but save/load fails – SharedObject not correctly mapped .
  
  Works locally on desktop but not in browser – MIME type or cross‑origin restrictions .
  These issues stem from eir **SWF compatibility gaps** or **embedding environment constraints**.
  
  再看渲染，不是把图片贴上去那么简单 
  
  After scripts finish ir work we still need to paint that frame.
  Flash rendering revolves around vectors and a display list:
  Stage holds MovieClips,S​hape​s​Bitmap​TextField​Button​Video…Each object may have matrix transform,color transform,mix mode,masks,filters。and depth ordering.
  The `` crate defines a `RenderBackend` trait that goes well beyond simple `drawImage`.
  It includes:
  
  
  Register shapes & bitmaps.
  
  Off‑screen rendering for filters/masks.
  
  Submit a full CommandList per frame.
  
  Create optional 3D contexts .
  
  Compile/run Pixel Bender shaders.
  
  Texture updates & quality settings.
  The concrete backends are:
   `  Pixel Bender shader handling.
  The web builder tries backends in order:
  wgpu-webgl → webgpu → webgl → canvas,or respects user`s preferredRenderer setting.
  If one fails it gracefully falls back to next.
  Thus performance and visual fidelity may differ across machines:
  one device might use WebGL while anor falls back to Canvas。leading to variations in filter support or speed.
  
  为什么用 Rust 和 WebAssembly 
  
  The biggest historical problem of Adobe's player was security.
  It was a native plugin loaded into browsers—prone to memory safety bugs &
  sandbox escapes.
  Embedding an arbitrary SWF could compromise whole browser session.
  Ruffle takes a different path:
  
  
  Core written in Rust — eliminates most classes of memory safety bugs.
  
  Web version compiled to WASM — runs inside modern browser sandbox.
  
  No need for legacy plugin interfaces or installations.
  
  JS layer only creates player instances,loads SWFs,and forwards DOM input/events.
  WASM here isn’t just hype—it provides stable performance across devices while keeping Rust’s safety guarantees under browser’s sandbox model.
  
  Ruffle 安全吗？按理说，
  
  
  
  
  
  
  后端
  / th>
  (用途
  / tr>
  
  
  
  Desktop primary path;also serves WebGPU/wgpu‑webgl fallback.
  
  Browser WebGL backend.
  
  Canvas fallback when WebGL unavailable.
  
   AGAL shader conversion for Stage3D compatibility.
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

---