@Arseny Kapoulkine
Independent. Previously: TF@Roblox
meshoptimizer, pugixml, volk, calm, niagara, qgrep, Luau
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
Blender is cool and all, but also! Here’s Ren sending regards from Poland, Czechia, Austria and Italy.
https://cdn.masto.host/mastodongamedevplace/media_attachments/files/116/929/299/077/582/417/or...
@nprofile1q... Challenge for a future Blender release: Ren on the splash screen
Perfect, today lobste.rs has both an article suggesting to add branches to code to speed it up, and an article suggesting to remove branches from code to speed it up.
meshoptimizer 1.2 is out! Featuring support for tangent generation, a significantly faster vertex decoder for Intel/AMD CPUs, several new smaller algorithms (cluster position compression, triangle filtering, clusterlod BVH) and various optimizations and improvements. GitHub stars and retoots appreciated!
https://github.com/zeux/meshoptimizer/releases/tag/v1.2
https://github.com/zeux/meshoptimizer/releases/tag/v1.2
@nprofile1q... Toes thought they’d be safe from a footgun but they forgot they are parented to the foot.
@nprofile1q... Right I guess where I am going is that the inner context objects (inside BVH) must correspond to some other parallel fors that are long since completed. So if parent pointers to dead contexts exist for cancellation I wonder what else is in there that refers to other possibly dead objects which never gets cleaned up.
@nprofile1q... Definitely not because I am, but the stale context variable is quite a footgun irrespective of cancellation. Was it not used before outside of the actual build? Or is the usage of the context itself safe except for internal cancellation machinery?
«ray tracing in one weekend» means the frame takes 48h to render right?
Accidentally quadratic? Please. This code is intentionally and proudly quadratic.
1