You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per bluerobotics/BlueOS#2892, MCM t3.12.1 had support for switching between the available camera streams in QGC1, which seems to no longer work as of at least MCM t3.12.4 (possibly earlier).
I haven't looked into QGC or MCM logs, but I imagine this is to do with how MCM lists the available streams over MAVLink, since if QGC isn't receiving that list in a format it understands then it understandably can't make use of the information.
MCM was tested within BlueOS (on a Raspberry Pi 3B), so there's some possibility of it just being a MAVLink routing issue, although that seems unlikely.
Main receiver testing was in QGC 4.3.0, on macOS Sonoma 14.5.
Footnotes
with a joystick button or with a dropdown available from the cog icon at the right side of the recording widget ↩
The text was updated successfully, but these errors were encountered:
Per bluerobotics/BlueOS#2892, MCM
t3.12.1
had support for switching between the available camera streams in QGC1, which seems to no longer work as of at least MCMt3.12.4
(possibly earlier).I haven't looked into QGC or MCM logs, but I imagine this is to do with how MCM lists the available streams over MAVLink, since if QGC isn't receiving that list in a format it understands then it understandably can't make use of the information.
MCM was tested within BlueOS (on a Raspberry Pi 3B), so there's some possibility of it just being a MAVLink routing issue, although that seems unlikely.
Main receiver testing was in QGC 4.3.0, on macOS Sonoma 14.5.
Footnotes
with a joystick button or with a dropdown available from the cog icon at the right side of the recording widget ↩
The text was updated successfully, but these errors were encountered: