In resent master, in a multi-vehicle setup disarm confirm ui button (long press) disappears to quickly because of flickering UI.

[slovak194]

Have you checked the latest release for fixes?

• Yes, I’ve tested on the latest release

Description

Expected Behavior
When the disarm button is pressed in the multi-vehicle actions list and the confirm button appears at the middle top - it should stay there indefinitely until confirmed, or closed by pressing the little cross on its corner.

Current Behavior

1. I press disarm on 2 vehicles.
2. Confirm button appears, but quickly disappears in less than 1 sec. It is almost impossible to catch and long-press it.
3. Also main UI continuously flickers between "Ready to Fly" to "Flying", and it looks like this is what clears the "confirm" button.

Steps To Reproduce

1. Connect to 2 vehicles.
2. Put them into STABILIZE mode.
3. Amr
4. Observe flickering of the UI
5. Try to disarm both
6. Observe how the confirm button disappears.

System Information

QGC Version: master
QGC build: self-built from source
Operating System: Ubuntu 24.04
Flight Controller: IFlight Blitz H7 Pro
Autopilot Software (with version): ArduCopter 4.7.0-dev

Log Files and Screenshots

Screencast.from.2025-10-08.11-18-46.mp4

[DonLakeFlyer]

Flickering like this tends to happen when you have two vehicles with the same Id. Can you check that?

[DonLakeFlyer]

Flickering like this tends to happen when you have two vehicles with the same Id. Can you check that?

Nope. Don't think that's it. You would only see one vehicle in that case.

[slovak194]

Flickering like this tends to happen when you have two vehicles with the same Id. Can you check that?

Nope. Don't think that's it. You would only see one vehicle in that case.

I hope this is not the case. I have prebuilt firmwares for all the vehicles with hardcoded system IDs.
I'm also very eager to help with debugging/improving anything related to multi-vehicle operation. Just let me know. Also, have some other issues/improvements to come.

[DonLakeFlyer]

This doesn't reproduce for me. My gut says there is something strange happening on the firmware side. Are you able to reproduce this with SITL or only your hardware?