And it also breaks in the wrong place and won't give access to variables by mouse hovering.
A better way is to set a break point in the routine where you want to debug.
Still no good if all the values are perfectly within normal parameters though. That is why I go into another routine (one which calls the one I want to debug), break it there with a break point, then modify values from the immediate window. Hit the go button to continue past the break point then see if you can force a crash in the routine that you are trying to debug.
That was the way I checked the Maxspeed, shell, mass and so forth earlier.