24 Mar
2023
24 Mar
'23
8:41 p.m.
On Fri Mar 24 15:46:37 2023 +0000, Giovanni Mascellani wrote:
Basically what the comment says: that lowering the maximum frame latency (here going from 3 to 1) doesn't cause any change in the semaphore state (which had value zero just before these lines and still has value zero here). When I realized that raising the maximum frame latency causes the semaphore to be released I wondered what would happen when lowering it. For example, it could wait on it. However, it seems it doesn't (this is apparently also confirmed by vkd3d-proton's implementation).
Oh, duh, I understand what this is doing now. Chalk that up to me not properly understanding the code before reviewing.