On Thu Feb 27 15:11:58 2025 +0000, Giovanni Mascellani wrote:
Actually that's correct, `Present()` is really expected to block in that situation, with the explicit frame latency waitable. So I was puzzled why it wouldn't do that on native, and it turns out that it did, but it also seem to have a 2 seconds timeout, which I implemented. But I also enabled an explicit frame latency waitable so that we don't waste time in useless waits.
In theory I could add tests for that, but they would likely be rather flaky anyway. And take at least two seconds on additional wall clock time. Let me know if you think we want that anyway.