Thanks for the quick reply. Looks like I was looking at the 2.4 spec 😅 I should probably remove my local copies of the old specs now
maxwellpirtle
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
Post
Replies
Boosts
Views
Activity
Excellent! Excited to try it out
Monotonicity did resolve the issue in the end. Are you sure that you're waiting for the appropriate value with the command buffer? Are you sure that you're using the same event for each iteration? Also, the synchronization in the demo project that you linked differs from the synchronization that is used in this example. The shared event synchronizes work between the CPU and GPU during the execution of a command buffer, whereas the demo project describes how to limit the CPU from going to fast and accidentally overwriting buffers the GPU is using. They're related in that they both synchronize the CPU and GPU. but at different times.
That is, a shared event is for one set of resources that the CPU and GPU use within the same execution context (i.e. in the same or across command buffers) whereas the semaphore method is meant for a set of resources
Thanks for the info! I'll be sure to look into that one
The project linked is in Objective-C...