Sascha Willems

I don't think that makes sense for a branch. That branch is also heavy work-in-progress and people shouldn't use it.

There is no need to report these. The new synchronization is still very much work in progress, and the way the ui overlay is handled will be completely reworked too.

Thanks for the kind words. Very much appreciated :+1:

There are a few examples that didn't make the cut, but with things settled I plan on adding some more demos that cover some of the stuff I'v been missing....

- My samples run fine on a plethora of platforms - Base validation is clean, sync validation is relatively new and I haven't had the time to test this -...

Don't worry. No offense taken :) I'm aware that synchronization needs improvement, esp. as so many people refer to my samples.

That may be right. I'll check and add a `vkCmdFillBuffer`.

Yes, you're right. Any hardcoded limit shouldn't exceed the lower limits of what the API specifies. I'll change the compute shader samplers to check against actual hardware limits.

The dreaded sparse residency sample ;) I never got myself to put much work into it. Thanks for raising this issue and posting your fix. I'll take a look at...

Thx for the PR. Adding simple single thread toggle is a great addition. Will merge once I got time to review the changes.