Just to expand on this, the problem was caused by using Px (the real part) and Py (the imaginary part) to set a new value of Px, and then using them again to set a new value of Py. In the second calculation it's easy to think that you are still getting the old value of Px -- it's coming from the same Get Data node after all. However, it's using the new value. That's what the Delay Set Data node solves.Daniel Brassard wrote:I was also asking myself why the details was stretched at the limit border, never though of the delay data node to correct it.
I've been tripped up by this before, and each time leads to great frustration eventually followed by a final "Doh!" moment. This, together with transforming vectors like positions and using out-of-bound array indices, is among the more difficult things to debug in ICE.
This is probably my last update. Zooming should be a bit more intuitive now.
