Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unreal Engine in JavaScript/HTML5 – Citadel demo

unrealengine.com

Post reply on HN
Print view View original

121–130 of 159 posts

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#121

Post by nkozyra »

laumars wrote: post #72
OGC wrote: post #71

Earlier quoted context omitted.

I'd bet money OP didn't even try or doesnt know how to do that.

This is what I thought to. I've never once had an application in Linux crash the whole OS - or at least not so long as I've had physical access to the machine (I've had rouge database requests brick a server before because it took down sshd - but that's a different story) In fact on the laptop I'm on now, the parent link crashed Firefox. But it OOM'ed and got killed before I even noticed there was a problem (and that…

You should tell your database to go easy on the rouge - a lady keeps it subtle.

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#122

Post by BrendanEich »

matthew-wegner wrote: post #107
ricardobeat wrote: post #103

Earlier quoted context omitted.

Dude. (sorry) This is Unreal Engine, with physics, cloth simulation, particles, light & glare effects. It's not C++ on Native Client or a plugin, it's running in javascript . Just yesterday you couldn't draw a circle on a 2d canvas at 30fps.

It's probably a subset of the Unreal Engine. And it only works in Firefox, and even then only very well in Firefox Nightly. Those points aside, though, this is pretty amazing. I fully expect multiple engines to target HTML5 in the same way Unity/Unreal/etc were cross-compiling for the Flash runtime. It's just not quite there yet... (And it's good that demos like this exist to put pressure on browsers to fully support…

No, not a subset. It's UE3 cross-compiled by Emscripten from ~1MLOC of primary C++ source. Some configury to use OpenAL (mapped to WebAudio), and of course OpenGL-ES (mapped to WebGL).

/be

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#123

Post by mickt »

tomwalker wrote: post #39
eslaught wrote: post #10

Earlier quoted context omitted.

From the FAQ: - Chrome currently crashes, but is expected to be resolved by the Chrome team soon. http://www.unrealengine.com/html5_faq/

I wish I had read that first :/ Crashed my whole system Chromium 25.0.1364.160 Ubuntu 12.04

On Chromium 25.0.1364.160 on Ubuntu 13.04 just the running tab died.

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#124

Post by vladmoz »

matthew-wegner wrote: post #107
ricardobeat wrote: post #103

Earlier quoted context omitted.

Dude. (sorry) This is Unreal Engine, with physics, cloth simulation, particles, light & glare effects. It's not C++ on Native Client or a plugin, it's running in javascript . Just yesterday you couldn't draw a circle on a 2d canvas at 30fps.

It's probably a subset of the Unreal Engine. And it only works in Firefox, and even then only very well in Firefox Nightly. Those points aside, though, this is pretty amazing. I fully expect multiple engines to target HTML5 in the same way Unity/Unreal/etc were cross-compiling for the Flash runtime. It's just not quite there yet... (And it's good that demos like this exist to put pressure on browsers to fully support…

As Brendan said, it's UE3, all of it. See the video at http://www.youtube.com/watch?v=BV32Cs_CMqo (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

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#125

Post by kevincoughlin »

TazeTSchnitzel wrote: post #47
wlesieutre wrote: post #42

Earlier quoted context omitted.

It's using the control system from the iOS version, which is what Epic Citadel was originally a demo for.

I noticed that. It makes sense, since iOS is an OpenGL ES platform and WebGL implements OpenGL ES.

For what it's worth, I was able to navigate fine using WASD and the arrow keys on my laptop

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#127

Post by Rinum »

MatthewPhillips wrote: post #77

This is so awesome that I never want to see another WebGL demo again. This one proves it; you can make awesome games in WebGL. From now on I only want to read about non-demo WebGL games that are in development with a real release date.

The biggest issue I see is with distribution.

For example:

I'm not a fan of DRM, but there's nothing preventing anyone from downloading the game and selling/giving away copies with ease.

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#128

Post by lukifer »

Rinum wrote: post #127
MatthewPhillips wrote: post #77

This is so awesome that I never want to see another WebGL demo again. This one proves it; you can make awesome games in WebGL. From now on I only want to read about non-demo WebGL games that are in development with a real release date.

The biggest issue I see is with distribution. For example: I'm not a fan of DRM, but there's nothing preventing anyone from downloading the game and selling/giving away copies with ease.

MMOs solve this extremely well: you pay for access to the world, content, and community, not for the code.

Re: Unreal Engine in JavaScript/HTML5 – Citadel demo

#130

Post by gcb0 »

isalmon wrote: post #108
laumars wrote: post #74

Earlier quoted context omitted.

Chromium has been a little dodgy for me lately too. Lots of memory leaks and what not. I've had to kill it's parent process id on a number of occasions (but even then, there's no reason why a browser should take out the whole OS).

Same here. Google has to do something with all these memory leaks.

...Or releasing their iron grip on the repo.
Post reply on HN