#Bevy 0.17 is out now! It features Raytracing, Improved Observers / Events, UI Widgets, Rust Hotpatching, Light Textures, DLSS, Tilemap Chunks, Web Assets, Reflect Auto-Registration, Frame Time Graphs, UI Gradients, Raymarched Atmosphere, Virtual Geometry BVH Culling, and more!

https://bevy.org/news/bevy-0-17

Final stream for November (will continue in December) tomorrow at 11 AM PST! This time we will attempt to trace some rays. Hopefully in less time than bindless took today :D

https://youtube.com/live/N1OVfBEcyb8?feature=share

The next 3 articles in my CPU rasterizer tutorial series are done! These are all about adding full 3D support, with perspective projection, perspective interpolation, triangle clipping, and a depth buffer.

https://lisyarus.github.io/blog/posts/implementing-a-tiny-cpu-rasterizer-part-4.html

Speaking at Develop North conference about Godot Engine this week.

Just published a technical breakdown of Godot's extension approaches that didn't make it into the talk. Covers:
- Tool Scripts vs Add-ons
- GDExtension implementation
- Engine Modules
- Custom engine modifications

Decision flowchart for choosing methods

https://claire-blackshaw.com/blog/2024/11/godot_extend/

#GameDev #GodotEngine #Programming

I think people really don't appreciate just how incomplete Linux kernel API docs are, and how Rust solves part of the problem.

I wrote a pile of Rust abstractions for various subsystems. For practically every single one, I had to read the C source code to understand how to use its API.

Simply reading the function signature and associated doc comment (if any) or explicit docs (if you're lucky and they exist) almost never fully tells you how to safely use the API. Do you need to hold a lock? Does a ref counted arg transfer the ref or does it take its own ref?

When a callback is called are any locks held or do you need to acquire your own? What about free callbacks, are they special? What's the intended locking order? Are there special cases where some operations might take locks in some cases but not others?

Is a NULL argument allowed and valid usage, or not? What happens to reference counts in the error case? Is a returned ref counted pointer already incremented, or is it an implied borrow from a reference owned by a passed argument?

Is the return value always a valid pointer? Can it be NULL? Or maybe it's an ERR_PTR? Maybe both? What about pointers returned via indirect arguments, are those cleared to NULL on error or left alone? Is it valid to pass a NULL ** if you don't need that return pointer?