It seems that completion task can submit itself as the next completion task for simulation sub-stepping


I am working with sub-stepping of PhysX’s simulation, and I found some words in the users guide like this:

…A tricky point here is that a completion task cannot submit itself as the next completion task because it would cause an illegal recursion. A solution to this problem might to be to have two completion tasks where each stores a reference to the other. Each completion task can then pass its partner to simulate():


But I found that passing the completion task to itself is working well, so I wonder if the “swapping of completion task” is needed.

Thanks for any advise !