Damien
Yeah, I can't see how it can be anything but - when you have a current collisioncount value, then check each index number directly after the countcollision command and it bombs out, it has to be a bug(?).
As an stopgap I'm just using the first collision and have put the issue on the list of things to look at later.
Yeah, I can't see how it can be anything but - when you have a current collisioncount value, then check each index number directly after the countcollision command and it bombs out, it has to be a bug(?).
As an stopgap I'm just using the first collision and have put the issue on the list of things to look at later.