hecs VS vulkano

For Rust, I really like Bevy's, but it gets too much in the way. I'd probably use macroquad instead with something like hecs (I tried macroquad with Bevy ECS and didn't go well).

The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion

My current design has struct Core that is basically "everything you need to save in a savefile", it has a hecs ECS (which needs a bit of boilerplate the hecs docs show you how to write to serialize it), and a bunch of simpler gamestate stuff like the discovered map positions, the current player etc. Everything is tree-like and serializes into a text file. Entity handles from hecs serve as "pseudo-pointers" that can represent cycle-like structures without running into endless cycles.

Out of the other Rust engines we've tried I think Macroquad was the most interesting option, and even though I've only made a few small projects in it worked extremely well and was what I'd expect from a game framework. While working in Bevy I felt like it was "writing fun Rust", but it wasn't really making a game. Macroquad on the other hand got immediately out of the way, and using it together with hecs was a painless experience where the whole time I felt like I was working on "the game" rather than "building systems that are invisible to the player".

The last crate worth mentioning is probably hecs for ECS, which we don't really use as heavily as some ECS fans would assume, but it made working around some problems between GDScript and Rust easier by storing things in ECS, passing around handles and querying ECS instead. Initially we did this with a global object and lots of state (which we still use for some things), but as the number of "things" grew it became easier to put it into ECS.

I use the awesome Vulkano for rendering and computation, and Rapier for simple physics. Contour is used for the initial shapes, but rapier forms the physics colliders from it. Hecs is used as well. And you might recognize Egui as gui :). I gotta say, I'm starting to be pretty happy with the rust ecosystem overall.

In the hecs documentation there is a section, Why Not ECS?. In it, the author states, "If your game will have few types of entities, consider a simpler architecture such as storing each type of entity in a separate plain Vec."

Usually, what I do is creating large, robust components in Rust. In my game, most of the logic lives inside the Factory node, which inside holds a full ECS (currently using https://github.com/Ralith/hecs) as well as other associated resources. This node takes care of holding the state and simulating all the machines in the factory and their interactions.

Generally, spatially-indexable data gets special treatment in games. (See Why not ECS for example, from the hecs ECS library.)

That impl basically says that Leftwalker is a System (or implements a System interface, to use a different parlance). Why exactly do Systems need lifetime is something better asked of the authors of the ECS library the tutorial uses. (personally I use hecs https://github.com/Ralith/hecs instead because I find it easier to use, no lifetime in sight :p)

There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.

Understand Wayland concepts: Familiarize yourself with the basic concepts and principles of Wayland. This will help you gain a solid understanding of how the system works. You can refer to the official Wayland documentation (https://wayland.freedesktop.org/docs/html/) and the Wayland book (https://wayland-book.com/). Learn Rust: If you're not already proficient in Rust, take some time to learn the language. The Rust Book (https://doc.rust-lang.org/book/) is a great place to start. Study existing Wayland compositors: Since you mentioned Anvil and smallvil, you can study their source code to gain insights into how they're designed and implemented. Try to understand the structure and how different components interact with each other. Dive into Smithay: Smithay (https://github.com/Smithay/smithay) is a Rust library for building Wayland compositors. Familiarize yourself with the library and its components. You can start by studying the provided examples and reading the API documentation. Learn graphics programming: Since you're interested in graphics effects, you'll need to learn about graphics programming concepts, such as shaders, framebuffers, and texturing. Vulkan (https://www.vulkan.org/) is a popular graphics API that you can use with Rust. Check out the following resources to learn more about Vulkan and graphics programming in Rust: Vulkan Tutorial (https://vulkan-tutorial.com/) gfx-rs (https://github.com/gfx-rs/gfx), a Rust graphics library Vulkano (https://github.com/vulkano-rs/vulkano), a safe, pure-Rust wrapper around the Vulkan API Start small: Break down the compositor project into smaller, manageable tasks. Begin by implementing basic functionality, like setting up a window and drawing simple shapes. Gradually add more features, such as input handling and window management. Ask for help: Join the Wayland and Rust communities to ask questions and seek advice. You can find them on forums, mailing lists, and chat platforms like Discord or IRC. The Wayland mailing list (https://lists.freedesktop.org/mailman/listinfo/wayland-devel) and the Rust programming subreddit (https://www.reddit.com/r/rust/) are good places to start. Iterate and experiment: As you progress, keep experimenting with different graphics effects and shaders. Try to implement the features you're interested in, such as blur, window previews, and window switching.

Something like vulkano in Rust or zig-gamedev in zig might be a much more enjoyable approach: They're similarly bare metal languages but have a lot of advantages over C++ (borrow checker's safety, simpler syntax). However, they're not commonly used by big studios.

Huh? What makes you think that? The commit history looks pretty active.

I use rust with the vulkano library.

rpm-ostree install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm sudo rpm-ostree uninstall akmod-nvidia sudo rpm-ostree install akmod-nvidia-470xx rpm-ostree kargs --append=rd.driver.blacklist=nouveau --append=modprobe.blacklist=nouveau --append=nvidia-drm.modeset=1 sudo systemctl reboot sudo rpm-ostree install nvidia-settings-470xx xorg-x11-drv-nvidia-470xx-power sudo rpm-ostree uninstall xorg-x11-drv-nvidia-cuda sudo rpm-ostree install xorg-x11-drv-nvidia-470xx-cuda sudo rpm-ostree install xorg-x11-drv-nvidia-470xx-devel sudo rpm-ostree install xorg-x11-drv-nvidia-470xx-cuda-devel sudo rpm-ostree install cuda-samples sudo rpm-ostree install vulkan-tools vkmark mesa-vulkan-devel sudo rpm-ostree install libshaderc-devel sudo rpm-ostree install clang clang-tools-extra libstdc++-devel sudo rpm-ostree install glib2-devel glib-devel avahi-gobject-devel sudo rpm-ostree install cairo-devel pango-devel gdk-pixbuf2-devel sudo rpm-ostree install graphene-devel gtk4-devel cairo-gobject-devel sudo systemctl reboot modinfo /usr/lib/modules/$(uname -r)/kernel/drivers/video/nvidia.ko | grep ^version find /usr/lib/modules -name nvidia.ko -exec modinfo {} \; sudo lspci -v | grep -A 20 VGA git clone https://github.com/Rust-GPU/Rust-CUDA.git git clone https://github.com/vulkano-rs/vulkano.git git clone https://github.com/Relm4/relm4.git glxgears glxinfo glxgears glxinfo vkcube vkcubepp ./teapot ./triangle ./occlusion-query ./interactive_fractal

I use the awesome Vulkano for rendering and computation, and Rapier for simple physics. Contour is used for the initial shapes, but rapier forms the physics colliders from it. Hecs is used as well. And you might recognize Egui as gui :). I gotta say, I'm starting to be pretty happy with the rust ecosystem overall.