Bart Wronski 🇺🇦🇵🇸

@bartwr.bsky.social

Engineering, Computer Graphics, Art, DSP, ML Culture, Techno, Industrial, and Electronic Music. Research Scientist at NVIDIA. Ex Google Research, Ex games (Sony, Ubisoft, CD Projekt). Politically leftist. He/they. https://linktr.ee/bartwronsk

Two cheap "gadgets" that are *dramatic* quality-of-life improvements: - General, everyone: USB type cable tester, both data + power (optionally extra power-only one). Saves sooo much time and frustration (which USB is that? Power only, how much W, or data?). - More "IT" folks: a cheap remote KVM.

Hopefully one last SIGGRAPH advertisement. I, myself, yours truly, will present on Haolin's behalf a data-driven method for joint adaptive sampling and quadrature for integration. Wed R408A. In the end of the talk I'll argue why everyone is doing the wrong thing. Paper: suikasibyl.github.io/nqr

Bild

I published vibrance-0.1.0 on Maven, now with support for Compose for Desktop (JVM). The APIs let you mix colors yourself, or draw gradients as modifiers or Compose brushes. Next steps: refine the model training to improve some color transitions, better alpha support. github.com/romainguy/vi...

BildBild

Ugh I don't comment on gamedev news. Not because I don't care or empathize, but because it's an equivalent of the shitty "thoughts and prayers." Doesn't change anything, powerlessness probably depressing for the affected/victims. But the recent days/weeks/months... Holy shit. Capitalism sucks.

my #1 grizzly beard protip for (game) dev is: if you have a bug that you dont understand the cause of immediately, dont try to fix it; add & iterate visualization / inspection tools until the cause is plain to see. the accumulation of 'observability' in your system's state will pay off many times

Implicit surfaces are everywhere in vision and graphics applications that optimize shapes. If we adjust the surfaces through a "learnable" deformation field, how can we ensure they stay close to the undeformed state (e.g. a template)? Our latest paper offers a simple and effective ARAP regularizer🧵

The code, including handle deformation and stylization demos, is available here: gitlab.com/tobidju/arap... Or, just run `pip install iarap` if you only want to use the regularization term. Thanks to @tobidju.bsky.social for leading the project + coauthors @ugoalone.bsky.social and Marc Alexa.

Tobias Djuren / ARAP-Regularization-for-Implicit-Surfaces · GitLab

Source code for the paper 'As-Rigid-As-Possible Regularization for Implicit Surfaces' at SGP 2026.

gitlab.com

Scapegoating AI (HBMs!) for the DRAM prices is so silly and the "same old" story over again. Corps and price fixing cartels getting away with their stuff thanks to "useful idiots" (sanctimonious luddites). Real systemic issues -> convenient clickbaity scapegoat -> we'll never get a systemic change.

lex luddy@lexluddy.xyz · last mo.

Reminder that memory manufacturers (including Samsung, Hynix, and Micron) were found to be an actual dictionary definition "cartel" back in the 2000s and were accused of illegal price fixing again in the late 2010s. They have been trying to screw you for literal decades.

Some vibe coding + old/new hobby (HA, IOT, microcontrollers) + eInk + my domain expertise... Claude claims to have had fun as well: ;) "This has been a genuinely fun build— from "blank panel / SCL held low" all the way to a blue-noise-dithered, OKLab-tuned, area-normalized colour weather station.🌤️"

colorful eInk display bedroom dashboard - main pagecolorful eInk display bedroom dashboard - weather forecast page

Funny coincidence: reading about all those "cyberdecks" (super cool gadgets, and who doesn't love gadgets?) I decided to "build" (=configure) one for myself, also as a laptop replacement, from... the first Steam Deck I had sitting idle in my closet since purchase. 😅 SD card boot to Debian, 1/

...and they said their brain is incapable of operating this way. They truly put effort and felt "guilty" about it. I 100% believe them. Our brains are wired differently, sometimes at a fundamental level. We think, conceptualize, visualize, and operate differently. Hundreds of different axes. 3/3

tech artists, who implemented complex unrolled parallax occlusion mapping + mip-based blur for "cracked ice shader"... all in noodle graphs! Terrible, unreadable, slow mess, they were aware of it, asking me to port it to code. They attempted multiple times to switch to code, with our help... 2/3

I agree with all your points, and hate noodle graphs when I "have to" use them myself (like in audio environments). But IMO you are committing a common tech fallacy: missing the "human element". Some people have (irrational?) resistance against text/code. I worked with incredibly technical 1/3