Files
2026-08-25 16:26:52 -04:00

1.5 KiB

title, type, source, source_url, author, handle, post_id, date, archived, draft, tags, description, in_reply_to
title type source source_url author handle post_id date archived draft tags description in_reply_to
Debug for majority-GPU-side game dev? Run-time recompile and hex viewer. archive twitter https://x.com/NOTimothyLottes/status/1742742039169573054 NOTimothyLottes NOTimothyLottes 1742742039169573054 2024-01-04 2026-08-25 false
archive
twitter
NOTimothyLottes
Debug for majority-GPU-side game dev? Run-time recompile and hex viewer.

Source

Thread

1/ @NOTimothyLottes ^1742742039169573054

Debug for majority-GPU-side game dev? Run-time recompile and hex viewer. If I want to see a value it is 'ramWI1.hxd[pos]=value;' (write to the memory that the hex dump reads from). Everything else is automatic, just save source and the results show up on screen. Zero's not drawn.

2/ @NOTimothyLottes ^1742743018929557805

IMO this is preferred to a 'debugger'. I can fill values from all workgroups simply by placing them at different positions, etc. Can get timings via shader clock for profiling even. It is transformative in dev productivity.

Branches: archive/threads/NOTimothyLottes/2024-01-04-debug-for-majority-gpu-side-game-dev-run-time/2024-01-05-kenpex-its-what-debuggers-should-be-debuggers-made-zero