I've been working on some path traced rendering improvements in Avoyd, and the combo of using Renderdoc for the Vulkan compute shader along with a 'debug this pixel' developer button for the CPU path tracer has made checking for differences fairly simple.
It's still a lot easier to debug CPU code (especially with runtime compiled C++), so I'm able to get a long way with just debugging the CPU code and making the GPU code do the same (even with the GPU using wavefront style path tracing).
Doug Binks
npub1th…5wmja
2026-05-08 17:03:29 UTC
Author Public Key
npub1th46rew0fz9nwjq7l2esvp7xd0zkmmz8kg9xgrp03kwsm9lx8a0qj5wmjaSeen on
wss://relay.ditto.pubPublished at
2026-05-08 17:03:29 UTCEvent JSON
{
"id": "6c2d47107319e19172b149e123d97ddf7d34d93a3f8368ab6daeb2994b30765d",
"pubkey": "5deba1e5cf488b37481efab30607c66bc56dec47b20a640c2f8d9d0d97e63f5e",
"created_at": 1778259809,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.gamedev.place/users/dougbinks/statuses/116540034893936791",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "I've been working on some path traced rendering improvements in Avoyd, and the combo of using Renderdoc for the Vulkan compute shader along with a 'debug this pixel' developer button for the CPU path tracer has made checking for differences fairly simple.\n\nIt's still a lot easier to debug CPU code (especially with runtime compiled C++), so I'm able to get a long way with just debugging the CPU code and making the GPU code do the same (even with the GPU using wavefront style path tracing).",
"sig": "480c930e262fd262bdae099783adcffd3a9bf0e15dd89fee393a450c38930b5a6609583634f80cfdafba56b87b54fd3671be547d5486a57438ad6ca46e1eea82"
}