HNHacker News
TopNewBestAskShowJobs

FredrikNoren

179 karma · joined August 20, 2013

submissionscomments
FredrikNoren··on Ambient: The Multiplayer Game Engine
Hi, Ambient CPTO here.

1) Yes, we're currently working on this and progress is good, so stay tuned for that! 2) We actually built a collaborative editor for this, which we've been using in-house for a year now. We choose to not release it right now, as there's still some things we need to work out with it, but it's coming too! 3) We plan to monetize services around this, such as game server hosting and tools for people to monetize what they create. 4) So the runtime is completely open source, so anyone can look into the code anyway. If you build something on top of this, you will also be able to choose if your own code should live on the server, client or both. If it's server only it won't be sent to the clients. 5) We've experimented with partial html UIs, but support for it on Rust native isn't great yet. We do have a fairly decent UI implementation (see examples here: https://github.com/AmbientRun/Ambient/tree/main/crates/ui/ex...) though it's not exposed to user code yet, but yeah I hear you that there's a lot of people who know html based UI tech. We'll see exactly where we end up there, but most likely the first step will be to expose the UI library we've built already to users.

Thanks!

FredrikNoren··on Ambient: The Multiplayer Game Engine
Ambient CPTO here; We're not quite on the web just yet! We're currently working on it though and it's looking promising, so stay tuned
FredrikNoren··on Ambient: The Multiplayer Game Engine
Ambient CPTO here; We're working on expanding the docs on this, here's the GitHub issue: https://github.com/AmbientRun/Ambient/issues/150
FredrikNoren··on Ambient: Multiplayer-first game engine, powered by Rust, WebAssembly and WebGPU
Yeah agreed, and we recognize that there will be lots of multiplayer scenarios this won't solve. But we hope to solve a large chunk of the "middle ground" multiplayer game scenarios, and make it easy for people to explore what happens when you involve other people in your game!
FredrikNoren··on Ambient: Multiplayer-first game engine, powered by Rust, WebAssembly and WebGPU
That's great! The first thing I would recommend is to try to build something in it, so that you get a feeling for how it works. If you can even create tutorials or examples for others, that would be a huge help for us! There are also issues labeled "good first issue" on the repository.
FredrikNoren··on Ambient: Multiplayer-first game engine, powered by Rust, WebAssembly and WebGPU
The current networking stack is pretty straightforward; it's built on top of QUIC so we do get reliable and unreliable UDP with multiple channels so the latency is really low, but we don't do anything fancy. We used to do rollback networking but removed it to simplify things; we realized it was overkill to have it on everything and it would make more sense to implement prediction on the entities that actually benefit from it (like player camera). We're currently working on deploying Ambient to the web too, where we'll probably use WebTransport, which is built on top of QUIC and should give us similar characteristics. For filtering which entities are stream; we haven't implemented that yet but we'd like to do it one day.

For lobbies/matchmaking; yes we're planning to implement a service for that. Steamworks integration is a bit further down the line but would be nice one day too.

FredrikNoren··on Ambient: Multiplayer-first game engine, powered by Rust, WebAssembly and WebGPU
Thanks! Yes! The renderer completely relies on multi_draw_indexed_indirect_count to batch everything, but I don't think it's available on the web spec yet. Without it, GPU culling and LOD-ing are a lot more toothless as we need to download the results from the GPU to the CPU.
FredrikNoren··on Ambient: Multiplayer-first game engine, powered by Rust, WebAssembly and WebGPU
After 18 months in development, we're stoked to open source Ambient, our high-performance multiplayer-first game engine!

Happy to answer any questions about it.

FredrikNoren··on Under the hood of my neuroevolution game/god simulator
This is a blog post about the technology behind Pixling World. Pixling World is an evolution/god simulator I'm building where you can have up to 1M neural network agents running simultaneously at 60 updates per second, all competing for survival. The game itself is built in WebGL, so it's all actually running in your browser.
FredrikNoren··on Changing the Ungit license from MIT to Faircode
Whoopsie, the error messages are still a bit rough but it looks like the recaptcha wasn't clicked? I've improved the errors on the frontend so should give you a nicer error message if it isn't now! Lmk if that doesn't fix the problem.
FredrikNoren··on Changing the Ungit license from MIT to Faircode
Your wish has been heard; I just added a dual licensing option to the platform :) Enjoy!
FredrikNoren··on Generating Martian Terrain with Neural Networks
Author here. Feedback/comments welcome!
FredrikNoren··on Ungit – Git UI that makes you understand git
Yup you're absolutely right, this was something I just left from the dev days and didn't think too much about. I've merged the PR.
FredrikNoren··on Ungit – Git UI that makes you understand git
I actually started of having the staging area use git add etc. and being just a reflection of what was staged. But that meant I either had to manually add each file (or have an "add all" button), or automatically stage them. The first option felt wrong because most of the time you just want to commit all the changes, so in most cases it's just more work for the user. The second option felt wrong because I didn't want to change around the git structure "behind your back" (just starting ungit shouldn't mess up your repo); so I went with just having it in the ui and doing the real git work on commit. In general I want it to be as close to git as possible but I hope this trade off made sense with this little explanation :)
← PreviousPage 2 of 2