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
Iterating over all nodes, both used and unused, seems to cause continuous issues due to the complicated logic in the object pool and free list usage: #71, #59, #58
We should only iterate over the nodes which have actually been submitted this frame. We already maintain the list of submitted node indices, so it could be used for this purpose as well.
Once this is done, this commit can be reverted: f1bda72.
Secondary concerns
ObjectPool::free_list is updated every frame. It should be enough to add the free slot once to the list and retain it.
ObjectPool::in_use is not needed, if we can compare the submission indices of this frame and the previous frame.
The text was updated successfully, but these errors were encountered:
Primary concerns
Iterating over all nodes, both used and unused, seems to cause continuous issues due to the complicated logic in the object pool and free list usage: #71, #59, #58
We should only iterate over the nodes which have actually been submitted this frame. We already maintain the list of submitted node indices, so it could be used for this purpose as well.
Once this is done, this commit can be reverted: f1bda72.
Secondary concerns
ObjectPool::free_list
is updated every frame. It should be enough to add the free slot once to the list and retain it.ObjectPool::in_use
is not needed, if we can compare the submission indices of this frame and the previous frame.The text was updated successfully, but these errors were encountered: