emerald VS pixels

[dependencies] emerald = { git = "https://github.com/Bombfuse/emerald", branch = "master", default-features = false, features = [ "physics", "aseprite"] } inline_tweak = { version = "1.0.8" } futures = { version = "0.3.18", optional = true } lazy_static = { version = "1.4.0", optional = true } flume = { version = "0.10.9", optional = true } bytemuck = "1.7.3" steamworks = { git = "https://github.com/Bombfuse/steamworks-rs", branch = "master", optional = true } image = { version = "0.23.14", default-features=false, features = ["png"] }

Now for the rusty bits, the game is written on top of Emerald which is built on top of various rust gamedev libs. This community has been amazing and extremely helpful throughout the development process, I wouldn't have gotten this far without you, thank you!

Here's another one: https://github.com/Bombfuse/emerald

Emerald engine that aims to be cross platform and can target WASM. Emerald is built over miniquad which is what macroquad is built over.

Emerald: This is a recent game engine that uses miniquad and kira for audio.

Been working on this for a few months, the game is built on top of Emerald, a game engine I'm writing to be as portable as possible. Wishlist the game on steamto be notified on release, aiming to release sometime this September!

https://github.com/parasyte/pixels

That gives you a simple software framebuffer, and it builds as a native app or for the web.

On a more recent machine, that same (well, more primitive) app with pixels or softbuffer struggled beyond acceptable. But was definitely poorly written.

I’ve ported the application from being based on pixels crate to the powerful bevy game engine

Well, it depends on how you use it; writing to an image buffer isn't much less efficient than writing to any normal buffer (in fact, although displaying your scene to a window efficiently is important, your main bottleneck will be the actual ray tracing loop). You may want to read this article for a practical example of using an ImageBuffer to create and draw a texture with Piston. Other window backends you could use, apart from pixels which was already mentioned in another comment, include minifb and Mini GL, though I haven't personally used them.

You can use wgpu instead of opengl as in the pixels example: https://github.com/parasyte/pixels/tree/main/examples/minimal-fltk

It might be possible but with a raycaster you probably want to be able to easily set all pixels and create your own small engine. Something like the pixels crate should fit your purpose: https://github.com/parasyte/pixels

The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!

Also, if you just want to get-things-done, then https://github.com/parasyte/pixels might be a bit better, to avoid reinventing the wheel.

However, I recently got a new M2 Macbook Air and started noticing some super weird behavior. While playing Pokemon Silver with an unlocked framerate, I'd notice that the game would slow down to below 60FPS, even on a release build. After printing a little debugging info I found the culprit in the rendering logic which was handled by the MiniFB crate. At first I thought switching to a GPU renderer (such as https://github.com/parasyte/pixels) would help, and it... kinda did?

pixels uses wgpu and runs fine.