You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation MoltenVK doesn't enforce a barrier when sampling a timestamp, in which case the timestamp may be sampled while some previous shaders are still running. As a result, the timings are totally unusable because they don't correctly represent the time spent on my dispatches. Is it possible to give it a YES to the withBarrier params?
In the current implementation MoltenVK doesn't enforce a barrier when sampling a timestamp, in which case the timestamp may be sampled while some previous shaders are still running. As a result, the timings are totally unusable because they don't correctly represent the time spent on my dispatches. Is it possible to give it a
YES
to thewithBarrier
params?MoltenVK/MoltenVK/MoltenVK/Commands/MVKCommandBuffer.mm
Lines 1004 to 1016 in bf097ed
The text was updated successfully, but these errors were encountered: