@plasius/gpu-renderer 0.2.57 → 0.2.58

package/CHANGELOG.md

@@ -11,6 +11,22 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+- **Added**
+  - (placeholder)
+
+- **Changed**
+  - (placeholder)
+
+- **Fixed**
+  - (placeholder)
+
+- **Security**
+  - (placeholder)
+
+## [0.2.58] - 2026-10-28
+
+- Pack shared instance records across device-bounded texture rows with bounded uploads, padded storage diagnostics and early TLAS byte-budget checks.
+
 - **Added**
   - (placeholder)
 
@@ -1347,3 +1363,4 @@ All notable changes to this project will be documented in this file.
 [0.2.55]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.55
 [0.2.56]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.56
 [0.2.57]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.57
+[0.2.58]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.58

package/README.md

@@ -132,6 +132,15 @@ residency. A larger instance count adds transforms and scene-index nodes without
 multiplying the underlying geometry. Large buffer uploads use bounded sequential
 staging to reduce temporary upload pressure. Recreate the runtime to replace instances.
 
+Instance records pack across both texture dimensions, so the texture height is
+not an instance-count ceiling. The granted device texture dimensions, buffer
+binding limits and `memoryBudgetBytes` determine admission. The memory snapshot
+reports logical `instanceBytes` and padded `instanceTextureBytes`; allocation
+diagnostics include the actual requested texture size and TLAS buffer. Instance
+texture uploads also use sequential chunks no larger than 8 MiB. More instances
+still require ray traversal and shading work: qualify performance at your target
+resolution, sampling and material complexity.
+
 ## Choose a rendering API
 
 | API | Purpose |