Stephen Dade

Yes, that's an issue with the new wp (and rally/fence) modules not being compatible with mav10. You'll need to use the old wp module instead: ``mavproxy.py --master=127.0.0.1:14550 --mav10 --default-modules=log,signing,oldwp,ftp,param,relay,tuneopt,arm,mode,calibration,rc,auxopt,misc,cmdlong,battery,terrain,output,adsb,layout`` Yes,...

Definitions are in pymavlink (https://github.com/ArduPilot/pymavlink/blob/master/mavutil.py#L1887), so we'd need to add the extra definitions there. We'd also need to edit ``./modules/lib/wx_addlink.py`` to update the GUI parts of MAVProxy. Agree it'd be...

Can you update to latest github source and try again?

> File "/venv-ardupilot/lib/python3.12/site-packages/MAVProxy/modules/mavproxy_map/mp_tile.py", line 210, in init self._loading = mp_icon('loading.jpg') This is actually line 213 in current master: https://github.com/ArduPilot/MAVProxy/blob/master/MAVProxy/modules/mavproxy_map/mp_tile.py#L213, so your source code doesn't match what is in the repository....

Thanks for reporting this. It is indeed a bug and is fixed in #1584. Could you confirm this patch fixes your issue?

> Just tested it. Graphing seems to be working, and the save icon does work on the "canned" graphs I tested, but when I tried just graphing something from the...

That means your master connection ``udp:0.0.0.0:14550`` is not emitting any MAVLink packets. Check your setup and IP addresses/ports.

> case that the physics rate and simulation performance (RTF) is related roughly lineary Yep. In particular the IMU sensor appears to be the limiting factor with performance.

> Thomas — 11:03 how does www.github.com/eProsima/Micro-XRCE-DDS-Client/issues/407 relate? It _may_ help with the SITL CI issue. I was definitely seeing that issue on real HW (DDS via PPP UDP) when...

>Thomas — 11:03 i have an indirect comment on the latter, see the PR i linked. For #31027, it's unrelated as this is a SITL-only PR. In SITL, we need...