Hi,
The 1st breakpoint will not be hit because it is not an actual statement that is executed at runtime (it's just a definition at compile time).
The 2nd breakpoint will also not be hit because it is a data structure (definition) and -again- not an instruction to be executed at runtime.
The 3rd breakpoint is not hit, because you've placed it at the declaration of the method.
If you move the 3rd breakpoint two lines down (line 50) it will be on an actual statement (an assignment in this case - HGA_status = DOOR_UP;, which will be executed at runtime*)
And as this is the constructor of your MSL_ROVER class (thus creating an instance of that), you can step over each and every assignment, method call, etc. pp.
Some methods will be called from the Orbiter core as "callbacks", placing a breakpoint at the first statement in such a function will trigger the break as soon as some code (from Orbiter-core or Graphic-Client or OS-Keyboard handling...) calls this method.
Try to get a feeling for where you can place breakpoints. Then step some lines ([F10] step-over).
After that you might like to step into some of you methods ([F11] step-into).
If the method you like to step into is not from your code, something like your 2nd sceen might appear as that method has no debug-information available.
In that case you could step into it at Assemby-Level, but that's a whole new dimension and unless you know x86 assembly and the connection between C-Language calls to them, you should at first keep away from that route.
If you however find, that you would like to look into such a method, this is where you definitely should carefully read the API documentation of that method and make sure that you
a) understand what it expects and
b) provide it with the expected parameters!
So, place some breakpoints, see when which one gets triggered, remove (or disable) those that do not lead directly to a crash until you're left with an idea what leads to the issue.
As said, it's not a "one click and you're done" job.
Be patient persistent.
/Kuddel
[*] at least in the Debug build, in a Release build this assignment might get optimized out.