commander-lol/bevy_capture_media

Event based image & video capture for Bevy

Hey

I write a lot of code; mostly in Node.js and Rust, other languages when required. I run an environmental tech company, working on tracking plastics. I also build games, mentor developers, make art, bake things, and make parody YouTube content.

---

Projects

Most of my projects live on https://lab.lcr.gr

Web Games:

• 🛰️ Deep Space Derelict - A short sci-fi roguelike; desktop browsers only
• 🐑 Open Baba (source) (Old) - A web implementation of the "Baba Is You" game mechanic, with a basic level editor

Game Dev Libraries:

• 🕺 Bevy Sprite Animations - Full fat spritesheet animation system for 2d sprites
• 🎵 Bevy Musicbox - Heavily opinionated system for managing game audio
• 🏗️ Bevy 2d Template - Quickstart game template, including cross platform builds (desktop, web, arm64), networking, asset loading, etc

Misc Tools:

• 🖼️ Crunch - Reproducable image manipulation piplines: transform, crop, recolour images
• 🌐 Flit - Templated HTML transforms to run after your site generator does its thing

bevy_capture_media's Issues

Expose Raw Frame Buffers

MediaCapture abstracts over the need to manage any of the internals of how bevy_media_capture works. This also means it isn't easy / obvious to figure out how to get the raw frame data being stored.

Consider adding some methods to make this a first-class function (and to provide more utility with all encoding formats disabled).

Possible ideas:

get_last_frame and take_last_frame - for getting a clone of the most recently captured frame, or popping it from the stack and taking it, respectively
get_stored_frames and take_stored_frames - for getting a clone of the stored frames, or taking sole ownership of the stored frames, respectively

Support `PerspectiveProjection`

Camera tracking currently only happens for cameras with an OrthographcProjection, but should at least support PerspectiveProjection as well.

Making systems generic over impl CameraProjection would go a long way to solving this. Trackers would need some way of identifying the type of camera they're tracking, so that they can retrieve the correct component when syncing.

Supporting custom projections is out of scope right now, but a solution should keep in mind the desire to support custom projections in future

Bevy 0.9.1

Hi. Thanks for making this - it's exactly what I needed.

Any chance of making it compatible with Bevy 0.9.1 - I've had a go over here and it seems to be working (everything compiles and the the basic_orthographic example is taking screenshots) but I can't guarantee I've got everything right.

Thanks, Mark

Track Target Resizing

Trackers currently mimic the transform and projection of the camera they track, but the backing Handle<Image> does not get resized. This means that any trackers are locked to the size they were when created

`attachments have differing sizes` crash

I'm not sure if I'm doing anything wrong, but even just adding mut capture: bevy_capture_media::MediaCapture to a startup system in my game causes it to immediately crash wish this error: (on bevy 0.8.1)

thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In a RenderPass
      note: encoder = `<CommandBuffer-(0, 2, Vulkan)>`
    In a pass parameter
      note: command buffer = `<CommandBuffer-(0, 2, Vulkan)>`
    attachments have differing sizes: ("color", Extent3d { width: 2180, height: 1226, depth_or_array_layers: 1 }) is followed by ("resolve", Extent3d { width: 1920, height: 1079, depth_or_array_layers: 1 })