6 ms·
Epic Citadel was a lot bigger than 14 KBytes ;)
by flohofwoe 5y ago
Epic Citadel was a lot bigger than 14 KBytes ;)
- pjmlp 5y agoTrue, the point was more about what was possible before Flash was sacked and is yet to be common with WebGL/WASM.
- aww_dang 5y agoUnreal 4 offers a WASM target. https://docs.unrealengine.com/4.27/en-US/SharingAndReleasing/HTML5/GettingStarted/ https://docs.unrealengine.com/4.27/en-US/SharingAndReleasing...
- pjmlp 5y agoI know, but that wasn't the question, rather what has been actually produced with it, given that Infinity Blade was created with Unreal 3 for iOS in 2008. An hardware that WebGL 2.0 is supposed to be much better. Instead most online games look like Amiga 500 stuff instead.
- badsectoracula 5y agoThis is more because there isn't an incentive (monetary or otherwise) to do that. When Flash gaming was big, web-based games were on the desktop but web games never took off on mobile which got pretty much all the audience they used to have on the desktop. Instead mobile games are largely native (or at least in app form). I agree that it took many years for HTML5/JS to reach Flash's capabilities (and some stuff like easily swapping around SWF files is still not as easy to do) and i dislike how Flash was forcibly killed instead of losing its popularity "naturally" (though it being proprietary technology instead of some open standard or at least an open source project help its murder considerably), but the reason you do not see Citadel-level stuff on HTML5/JS has more to do with not being much of an incentive to do something like that than the technology being able or not (demos like After the Flood[0], which has as much gameplay as Citadel yet it shows more advanced rendering techniques - you can even look yourself in the glass reflections :-P - show that it is technically possible). [0] https://playcanv.as/e/p/44MRmJRU/ https://playcanv.as/e/p/44MRmJRU/
- pjmlp 5y agoAfter the flood is from 2017, and doesn't work on my Vulkan aware mobile GPU.
- badsectoracula 5y ago> After the flood is from 2017 Citadel is from 2011, but this doesn't matter, the point is that you can do stuff like that on the web. > doesn't work on my Vulkan aware mobile GPU If the GPU is Vulkan aware then it might be an issue with your browser, though from [0] it looks like only Apple's devices do not support it - which wouldn't support Vulkan either, so i'm not sure why you'd bring that up. [0] https://caniuse.com/webgl2 https://caniuse.com/webgl2
- aww_dang 5y agoThen go out and build your ideal web game. The barriers to entry have never been lower. People still appreciate pixel art and simplicity. Some even love the Amiga.
- pjmlp 5y agoI rather take advantage of the latest native games and APIs instead. It up to Khronos and friends to keep the Web APIs relevants, after all why did they kill plugins?
- aww_dang 5y agoPlugins were a security nightmare. Webgames are generally more about free to play and accessibility. No install or trust required. They are usually more casual games and must work on the widest possible selection of devices. That's what WebGL is all about. If your looking for a memory intensive behemoth of a game, it makes more sense to look at native as opposed to WebGL. There's nothing wrong with either approach, but the web lends itself to one more than the other.
- pjmlp 5y agoAnd then everyone went to mobile native games instead, leaving WebGL behind for 3D visualizations of online shops, Google maps and shader toy demos, basically.
- Mikeb85 5y agoLiterally every major engine allows exporting to WebGL/WASM. So Unreal, Unity, Godot, etc... graphics can all be done in WebGL (without a few of the bleeding edge Vulkan/DirectX features).
- moonchrome 5y agoA few of the bleeding edge features ? You obviously don't know what you're talking about - WebGL 2.0 is not supported on Safari and iOS [1] and WebGL 1.0 is based on an API that was released in 2007 ! Even WebGL 2.0 is based on ES 3.0 which is from 2008... [1] https://caniuse.com/webgl2 https://caniuse.com/webgl2
- TazeTSchnitzel 5y agoSafari is already shipping experimental support for WebGL 2. It will be months, not years, before it is enabled by default. Also, OpenGL ES 3.0 is not from 2008. The specification was publicly released in August 2012, and of course it took years before enough devices supported it well enough (lots of driver bugs…) for it to be worth targeting. The web is certainly a few years behind the native-code state-of-the-art, but it's not a decade behind. There's a lot you can do with these mature APIs.
- pjmlp 5y agoAnd finally gets supported in Safari, on the year when graphics card are moving into mesh shaders and raytracing, with WebGPU still one year away as MVP 1.0.
- moonchrome 5y ago>It will be months, not years, before it is enabled by default. So in a few months we'll have feature parity with 2012 mobile HW ? I have quit 3D development around 2015 but I remember trying to use MRT on webgl to do some basic deferred shading and you could run on FF and Chrome desktop only. It's infuriating that 7 years later it's still the case. I used this technique when I was learning 3D programming in 2007. Calling this cutting edge is just...