It looks like there is no valid object handle returned by oapiGetObjectByName (no object of that name was found) - according to Autos the `str` variable is an empty string (""). IIRC, no OrbiterAPI functions check for NULL pointers, so there's most likely an access violation exception inside oapiGetVesselInterface after you passed the invalid object handle (NULL pointer) to it, which breaks the execution of the code at a point before your set breakpoint (somewhere inside oapiGetVesselInterface function).But not sure why is breaks at the arrow and not the break (red Dot)
No symbols loaded for Orbiter.exe is not an issue. It's normal, as you don't have the sources or a debug build of the Orbiter core. You don't have to worry about it at all, and safely ignore it. You can eventually view disassembly of the code if you want to see where exactly at which instruction inside Orbiter the exception occurred.Ok ran across this while running the debug. No symbols loaded.
