Civil 3D 2015 Service Pack 2 API Bug

If you have a program that you wrote for Civil 3D and find a random crash in your routines, you may want to check to see if you are setting the ElevationMin for a profile view. If the ElevationMin property is set first Civil 3D will quickly crash without warning, even error catching can catch it. I’m guessing someone is trying to divide by zero causing the catastrophic crash. To get around this error set the ElevationMax first and then the ElevationMin. This seems to fix the issue. Alternatively you can set an elevation max and min values in the UI and it should start working correctly. This leads me to believe someone is dividing by zero in the property setting of the profile view.