Unreal Engine 3 in Firefox with asm.js
FirefoxCited 5× on HN, 2013-2022
245K views · 13 years ago · demo · dated
Mozilla's short demo of Unreal Engine 3 running in Firefox, ported by Mozilla and Epic in four days using Emscripten and asm.js.
HN cites it as proof of how capable browsers became, a landmark for asm.js and WebAssembly.
9:03Unreal Engine 5 Revealed! | Next-Gen Real-Time Demo Running on PlayStation 5
Unreal Engine
19.2M views • 6 years ago
44:59Google I/O 2011: Kick-Ass Game Programming with Google Web Toolkit
Google for Developers
106K views • 15 years ago
10:30Unreal Engine 4 - GT.TV Exclusive Development Walkthrough
GameTrailers
972K views • 14 years ago
37:11CheerpX: a WebAssembly-based x86 virtual machine in the browser, Yuri Iozzelli
WebAssembly NA
7K views • 6 years ago
2:46Godot Engine - Apps & Tools - 2022 Showreel
Godot Engine
172K views • 4 years ago
31:31Blink Questions Answered
Google for Developers
35K views • 13 years ago
29:47The Truth about Rust/WebAssembly Performance
Greg Johnston
218K views • 3 years ago
13:44Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 2: Demo
𝓖𝓷𝓸𝓶𝓮💫𝓢𝓪𝓷𝓮
13K views • 10 years ago
25:55React.js Conf 2015 - Beyond the DOM: How Netflix plans to enhance your television experience
Meta Developers
26K views • 11 years ago
45:05Servo Architecture: Safety and Performance
linux conf au 2017 - Hobart, Australia
12K views • 9 years ago
9:43Meteor Screecast
meteorscreencasts
50K views • 14 years ago
2:15Real-Time In-Camera VFX for Next-Gen Filmmaking | Project Spotlight | Unreal Engine
Unreal Engine
1.1M views • 7 years ago
29:51Keynote: What is a Component (and Why)? - Luke Wagner, Distinguished Engineer, Fastly
The Linux Foundation
7K views • 3 years ago
27:56Unity DOTS vs Handbuilt: Sample Project
Nick Caston
687K views • 6 years ago
15:00Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 1: Rust
𝓖𝓷𝓸𝓶𝓮💫𝓢𝓪𝓷𝓮
19K views • 10 years ago
5:05New Voxel Engine Reveal - Crystal Islands Experiment
John Lin
394K views • 5 years ago
1:11:55ElixirConf 2019 - Day 1 Morning Keynote - Brian Cardarella, Luke Imhoff, Paul Schoenfelder
ElixirConf
8K views • 7 years ago
6:59TypeScript types can run DOOM
Michigan TypeScript
485K views • 1 year ago
1:16:07React Helsinki February 2020
Fraktio
42K views • 6 years ago
27:27Faking RTX Global Illumination vs. RTX | 100% Ray-Traced Game, Pt 1
Gamers Nexus
260K views • 7 years ago
5 comments from Hacker News
I'm not sure if I agree with all of this. People forget flash kinda sucked. One of the most significant ways in which flash sucked was the performance. Imo, the most famous flash game of all time is Binding of Isaac, which basically couldn't achieve a respectable, consistent frame rate even on the most powerful rigs. It's native rewrite, Rebirth, never had performance issues. >You can't do pixel-perfect rendering Sure you can, with canvas, and if you want to have absolutely perfect control, there's WebGL (and nice stuff like PixiJS) >No nice pipeline for integrating vector animations/art into games You can render SVG sprites into bitmaps, and use them in WebGL or canvas, as you mentioned, you needed to do this too in flash as well if you wanted decent performance. >easy to make fancy + good-looking interactive UIs If I remember correctly, most fancy game UIs were built with some framework, like flixel, which used low-level drawing primitives and built-up the UI from scratch. Alternatively you could use the full power of HTML+Js frameworks to build arbitrarily complex UIs and overlay them on your game scene. >many of the html runtimes for new engines (Unity for instance) feel waay heavier/more sluggish in the browser True, but they are meant to be, and meant for bigger games than flash/html5+js is. But for modern engines, HTML5 export sucks, there's no doubt about that. But that's a failure of execution, not technology. I remember Epic citadel a decade ago, which ran by compil
▶ this video Unreal Engine 3 (may 2nd release vid) very cool! Can I use WebASM to do amazing music visualizations?
Surely there's a trade off, as we add more and more features to browsers, w3C specifications, add ons, JavaScript updates etc, a browser will inevitably get slower. Yes older browsers were fast, but they did little in comparison to today's virtual machines. The fact that you can do this ▶ this video in a browser should tell you we've come a long way from them just being Document readers.
As mentioned in other comments, we also ran other UE3 games, like Sanctuary. We demoed that in a booth at GDC last month where people could play it. That's a full UE3 desktop game with bots, AI, normal FPS mouse control (not tablet-like), etc. etc. You can see it in action in the 2nd half of this video ▶ this video And it's using the exact same code as this demo. You literally use the same compiled JS, and just swap in a different set of game assets.
As Brendan said, it's UE3, all of it. See the video at ▶ this video (second half of video) for the Sanctuary UT3 map, complete with bots, shooting, etc. Once the engine was ported, we threw random UE maps at it, and it worked fine. It works in any browser that has solid JavaScript and WebGL support. Audio will work with Web Audio, but it'll gracefully not have audio effects if it doesn't. There's no Firefox specific magic here. If you're on Aurora/Nightly, then you get asm.js/Odinmonkey optimizations and it runs even faster; that's it. Edit: UE3 was chosen because it's known stable and optimized tech. This isn't the pinnacle of what can be done, far from it. But neither us (Mozilla) nor Epic wanted to be working with code that was still under active development for a next generation engine while simultaneously trying to port it to a new experimental platform. One step at a time! :p