bevy-website
rr
bevy-website | rr | |
---|---|---|
16 | 102 | |
182 | 8,665 | |
1.6% | 1.1% | |
9.4 | 9.6 | |
2 days ago | 3 days ago | |
JavaScript | C++ | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bevy-website
-
The Bevy Foundation
https://github.com/bevyengine/bevy-website/issues/1097 Yep, on our wishlist and will be added :)
-
Bevy 0.11: ECS-driven game engine built in Rust
We'd like to open the floodgates on Bevy Book development asap. This taking so long has largely been my fault ... I've been overly protective of the Bevy Book while also not giving it the attention it deserves. Here is our current plan: https://github.com/bevyengine/bevy-website/issues/623#issuec..., which I'd like to execute during the next cycle.
-
Android support?
Latest Progress: https://github.com/bevyengine/bevy-website/pull/550/files
-
Bevy 0.8
I do want previews though.
-
Programming a Rogue-Like with Rust
API docs, examples and the revised book: https://github.com/bevyengine/bevy-website/pulls?q=is%3Aopen...
Strongly agreed on the need for better introductory material; the existing book is extremely incomplete.
> I don't have this clear. Are 5/6 teams actually building commercial games with Bevy, or they just planning to do it in the future? This is a crucial distinction.
I know of 2 released commercial projects, the CAD team, a few indie devs who have started and 3 or so small studios who are looking to start. There's a little thread in the Discord where I've rounded folks up: [Bevy in production](https://discord.com/channels/691052431525675048/995713618526...).
- Bevy 0.6 to 0.7 Migration Guide
-
How Bevy uses Rust traits for labeling
We also do some real cleverness around split borrows in order to enable automatic system parallelism. This draft book page goes into more concrete details :)
-
Bevy 0.6
Can do
-
Not Snake - my first game released made with Bevy
I used the unofficial bevy cheatbook a lot to learn the ropes. Everyone on the discord is super friendly and helpful and the official documentation is being updated, you can check out the PRs on the book branch
-
Bevy’s First Birthday: a year of open source Rust game engine development
If you're curious about the ECS side of things, that chapter is now ~approximately complete, and should make an excellent learning resource: https://github.com/bevyengine/bevy-website/pull/182
rr
- rr: Lightweight Recording and Deterministic Debugging
-
Hermit is a hermetic and reproducible sandbox for running programs
I think this tool must share a lot techniques and use cases with rr. I wonder how it compares in various aspects.
https://rr-project.org/
rr "sells" as a "reversible debugger", but it obviously needs the determinism for its record and replay to work, and AFAIK it employs similar techniques regarding system call interception and serializing on a single CPU. The reversible debugger aspect is built on periodic snapshotting on top of it and replaying from those snapshots, AFAIK. They package it in a gdb compatible interface.
Hermit also lists record/replay as a motivation, although it doesn't list reversible debugging in general.
- Rr: Lightweight Recording and Deterministic Debugging
-
Deep Bug
Interesting. Perhaps you can inspect the disassembly of the function in question when using Graal and HotSpot. It is likely related to that.
Another debugging technique we use for heisenbugs is to see if `rr` [1] can reproduce it. If it can then that's great as it allows you to go back in time to debug what may have caused the bug. But `rr` is often not great for concurrency bugs since it emulates a single-core machine. Though debugging a VM is generally a nightmare. What we desperately need is a debugger that can debug both the VM and the language running on top of it. Usually it's one or the other.
> In general I’d argue you haven’t fixed a bug unless you understand why it happened and why your fix worked, which makes this frustrating, since every indication is that the bug exists within proprietary code that is out of my reach.
Were you using Oracle GraalVM? GraalVM community edition is open source, so maybe it's worth checking if it is reproducible in that.
[1]: https://github.com/rr-debugger/rr
-
So you think you want to write a deterministic hypervisor?
https://rr-project.org/ had the same problem. They use the retired conditional branch counter instead of instruction counter, and then instruction steeping until at the correct address.
-
Is Something Bugging You?
That'll work great for your Distributed QSort Incorporated startup, where the only product is a sorting algorithm.
Formal software verification is very useful. But what can be usefully formalized is rather limited, and what can be formalized correctly in practice is even more limited. That means you need to restrict your scope to something sane and useful. As a result, in the real world running thousands of tests is practically useful. (Well, it depends on what those tests are; it's easy to write 1000s of tests that either test the same thing, or only test the things that will pass and not the things that would fail.) They are especially useful if running in a mode where the unexpected happens often, as it sounds like this system can do. (It's reminiscent of rr's chaos mode -- https://rr-project.org/ linking to https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo... )
-
When "letting it crash" is not enough
The approach of check-pointing computation such that it is resumable and restartable sounds similar to a time-traveling debugger, like rr or WinDbg:
https://rr-project.org/
https://learn.microsoft.com/windows-hardware/drivers/debugge...
- When I got started I debugged using printf() today I debug with print()
- Rr: Record and Replay Debugger – Reverse Debugger
-
OpenBSD KDE Plasma Desktop
https://github.com/rr-debugger/rr?tab=readme-ov-file#system-...
What are some alternatives?
wgpu - Cross-platform, safe, pure-rust graphics api.
CodeLLDB - A native debugger extension for VSCode based on LLDB
gdnative - Rust bindings for Godot 3
rrweb - record and replay the web
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
bevy_prototype_lyon - Draw 2D shapes in Bevy
Module Linker - browse modules by clicking directly on "import" statements on GitHub
Godot - Godot Engine – Multi-platform 2D and 3D game engine
nbdev - Create delightful software with Jupyter Notebooks
bevy - A refreshingly simple data-driven game engine built in Rust
clog-cli - Generate beautiful changelogs from your Git commit history