Gary Sweet

> won't work on GPUs that don't offer lazily allocated memory Ah yes, sorry about that. > I'll try to take a look at that and then also implement your...

This isn't just Android related. I've had to delete the cache files again today as it started crashing again.

This is becoming a pain point for me when trying to test new samples. I have a 96 core build server and I'm building with -j. The first 40% of...

As far as I'm aware nothing has been done to address this, so I don't think it can be closed.

I think you misread my comment. I said it can't be closed yet.

This change helps my build performance massively. A full build after clean previously took 9.5 minutes, and takes only 35 seconds with this change in place.

I suspect that no-one else will actually be able to test the direct-to-display changes, so this may be a code-review only change.

+1 for me on this. I'd love to be able to submit reports from our embedded hardware, but building Qt on those will be a serious pain. A simple CLI...

I can confirm that this builds for me without issue, but I can't test it as I can't run on Android.

> > I can only confirm that the sample correctly reports that we don't support dynamic sample state changing. > > Does it mean that the validation layers don't support...