Ahh sure that makes more sense. Just wanted to check it was that and not the JDK being weird (I was giving the early version of 7 a stab for a number of unrelated reasons.) I haven't looked at the code so this might be way off, but would it be to do with the corners overlapping too much before the collision is detected? If so then one methodology might be (if you're modelling it in a time based way) to step back and forth until you calculate the exact collision point then calculate the normal sizes from there. So say you've advanced t time between the last frame, computationally step back to t/2, check if that's the collision point, if it hasn't collided yet step to 3t/4, if it has step to t/4 - and then work that way. That may be completely irrelevant so apologies if that's the case but I thought I'd throw it in there in case it helps! Great work as always though, I always get a bit excited when you post something new :-)

Hmm, whilst dragging the dice around every so often it freezes up and I get the following message in the console: overload!! overload!! overload!! overload!! overload!! overload!! overload!! overload!! overload!! overload!! ...never seen that before! Is that something you've put in your code or is Java doing something rather special?

Hi - the best course of action would probably be for you to head over to the discuss group (http://groups.google.com/group/greenfoot-discuss) and post it there as a file along with an explanation of your problem, then we can have a look at it. I guess there's a chance this might be windows 7 specific, especially since you're using a beta and not the final release which has been out a while now... :-) Have you tried it on another OS just to be sure?