3D Real-time Unigine Crypt demo (WebGL)
crypt-webgl.unigine.com
crypt-webgl.unigine.com
But, from my experience[1], WebGL topics have a hard time getting tracktion on Hacker News.
I'm glad this got traction this time. It really is an impressive demo.
[1] http://www.hnsearch.com/search#request/submissions&q=web...
Uningine's news entry: http://unigine.com/news/2013/02/20/crypt-in-browser
A video of the demo they're running: http://www.youtube.com/watch?v=azKNaRD221M
Obviously they haven't implemented / turned off the bells and whistles. Which conflicts a bit with the news entry, which says "with all visual effects". Does anyone know how much they have implemented? I'm interested, but more information seems hard to find.
Sorry, but I'm not especially impressed - this is on a high end desktop machine custom built for gaming at 1920 x 1200(core i7, 12GB RAM, GTX670s etc.) - there's no hardware reason for it not to be perfect. Running Chrome 24.0.1312.57 on Windows 7 64 bit.
It didn't run on my Nexus 7 (no WebGL found) but then I'm not running a beta version of Chrome. Perhaps that would be the impressive bit.
EDIT: updated Chrome to 25.0.1364.97 m (the latest) and got the "Aw, Snap!" dead tab on reloading. State of web development as expected. Perhaps THAT'S why there aren't any AAA titles on WebGL...
Works fine in Firefox, but as is typical for WebGL demos in Firefox on my machine, looks like about 10 fps.
Turns out it requires S3TC compression which is not supported in Mesa drivers by default (only decompression is). After installing libtxc_dxtn.so it worked just fine in Chrome.
Also it doesn't work with Firefox 10.0.12, even if I enable WebGL. It does work with latest nightly (Firefox 22.0a1) though.
I really like WebGL, and I want it to succeed, but for this to happen developers are going to have to make sure that their code works on reasonably low end hardware (i.e. integrated graphics). This sort of GPU inconsistency is so common with WebGL right now that it reminds me of trying to browse the web on Linux circa 2000.
Not a pleasant experience.
Framerate was a bit low but maybe that's just me (Mid 2010 MBP 15").
Keep at it!
Maybe the javascript garbage collection?
Gotta say I've never been so impressed with the loading capabilities of a game engine before.
FF 19.0 OS 10.8.2.
Why?
(I'm one of the people that works on BananaBread.)
In fact, I was utterly blown away by how smooth (absolutely lag free and very fluid) yet detailed this demo was. Very impressive.
...you do realize this isn't a game, right?
There is nothing compelling about WebGL except that it is interactive.
If I wanted a non-interactive scene that repeats, I could do it in anything and upload it as a video on youtube.
Dynamic interactive 3d is the exciting thing about webGL and it is the the thing missing from this demo, so I too, am disappoint.
Edit: here are error messages from console:
[STDOUT] Could not create canvas - TypeError: Cannot read property 'inspectContext' of undefined game-setup.js:11
Uncaught TypeError: Cannot call method 'viewport' of undefined allengine_no_native.js:89
Edit2: Mystery solved, apparently problems are caused by some clashes with WebGL Inspector Chrome extension. Demo works after disabling it.