Blender's GPU Accelerated UI, Decoupled from it's original codebase. Supports Rust, Python, JS, React, C & C++. Twice as good as GPUI
Merge upstream/main into linux-gpu-optimisations
nusaturnce9fb863df27
diff --cc CHANGELOG.mdindex 83963f0,83f5126..4a65702--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -7,13 -7,10 +7,17 @@@ All notable changes to **blenderui** (B## [Unreleased]### Changed+ - **README and website:** the FAQ says macOS has been tried by hand on two Apple Silicon Macs (it said nobody+ had checked), and a new FAQ entry and the roadmap list what people asked for: Vue and Angular (adapters+ over `@blender-ui/native`), and Lua (a community pull request is in review), Ruby and Go through cgo+ (over the C kit). None of them exists yet.+- **Linux GPU start:** the OpenGL context and device are created on a worker thread, as on Direct3D 11. The first frames draw on the CPU. A window switches to the GPU when the device is ready, also when it is idle (Linux and Windows; `BUI_raster_gpu_pending`).+- **Benchmarks on Linux:** `bindings/rust/bench/common/measure.rs` measures CPU time (`CLOCK_PROCESS_CPUTIME_ID`) and memory (`/proc/self/status`) on Linux, so `bui-bench`, `bench_frames` and `cargo test` build there; Windows is unchanged.++### Fixed+- **Rust windows:** a dirty window with a pending frame request waits for that frame instead of a 0 ms timer, so `requestAnimationFrame` callbacks run once per frame.+- **X11:** a frame callback that closes its window no longer renders into the closed window.+- **X11:** a window that closes while its GPU device starts releases the device before the X window is destroyed (`BUI_raster_gpu_release`), so Mesa no longer prints `failed to create drawable`.## [0.4.1] - 2026-11-06