Incorrect histogram display in FlyApp 1.14.2

Chrislaf · Oct 11, 2024

Filmarik said:
The process described above rolled back 1.14.2 to 1.13.9 on my RC Pro and histogram works correctly again.
My understanding is that v.14 was mainly released to accommodate the Neo drone. None of the Fly 1.14. iterations bring anything new or worthy to Mavic 3 users. I would suggest you stick with 13.9. That is what I have done and everything works just fine including the histogram.
Not sure what happened with your RC Pro. Power up your drone and RC Pro, open Camera View, click on the 3 dots in top right corner and look into last tab called "About". There should be App Version shown as 1.13.9. If that is the case you are good to go. Just do not forget to re-assign the functions to the programable buttons as you desire.

Ok thanks.

Chris

Filmarik · Oct 11, 2024

Chrislaf said:
Ok thanks.

Chris

Do you see the 13.9? Is the histogram working correctly?

Chrislaf · Oct 11, 2024

Filmarik said:
Do you see the 13.9? Is the histogram working correctly?

I now have my histogram back the way it should be. Rolled back to 13.9 and reset all my button customizations.

Thank you for the help. It was very much appreciated.

It’s confusing why DJI would make a change like this and take functionality away from the histogram.

Chris

Filmarik · Oct 11, 2024

Chrislaf said:
I now have my histogram back the way it should be. Rolled back to 13.9 and reset all my button customizations.

Thank you for the help. It was very much appreciated.

It’s confusing why DJI would make a change like this and take functionality away from the histogram.

Chris

You are welcome. I am glad to hear that we've managed to resolve your histogram issue. I was equally frustrated when I found out that the histogram was not working correctly after I updated to 14.2. Then I searched and researched untill I found solution which I was now able to share with you.
As to your other question about DJI, similar things happened in the past with other drones and other controllers too. It is usually a software bug. In this case affecting apparently some RC Pro controllers but not all. At least DJI gave us this time option to roll back. In the past when they ruined something, we had to wait for them to fix it. And sometimes it was a loooong wait or never..