We have added a init script for g3e and g32 that should ensure measuring is possible. It will automatically home if not done and go to a safe position to enable z probe. So if you can confirm that g32 in new version does the same i would bet on that function doing it wrong. Then question is why it goes wrong and how to find what part computes position wrong which then would be the reason for the x crash. Would then check this when i am back.
