With adtg_gui loaded (no raw_rec or mlv), zooming 5x in photo LV causes weird display. 10x causes LV freeze.
Taking the first shot in raw_diag "compare 2 shots" or "compare 2 shots HL", and then powering off camera before second shot, causes the module to show the graph after the first shot, and then break raw_diag completely where none of the options work. Restart camera enables all other options again, but attempting to compare 2 shots, causes the issue again.
Deleting RAWSAMPL.DAT and restarting the camera, solves the issue.
Ran into an issue yesterday, where the iso_regs module was loaded, but not displaying in the debug menu. I think it happened after waking the camera from sleep.
My build is 11 days old though (needed to check for show stopper bugs before shoot), so I'll update tomorrow and see if I can find the same bug.
With adtg_gui loaded, and dual_iso loaded and enabled (didn't check if the problem also occurs with dual_iso only loaded, and not enabled).
With adtg_gui loaded, and digic registers enabled.
In both situations, no registers had been changed. These weird frames occur on the second, and subsequent images, in high speed continuous shooting mode (didn't check other modes). This problem effects DR calculations also.
Raw files with this issue can be found at the 5D3.123 pull request.
Another issue that is much less frequent, and as yet, I haven't been able to find a way to consistently reproduce, is the same image gets written to CR2, on subsequent photos. That is, take photo, problem occurs, all subsequent photos are the same image, with increasing WB. This issue occurred after taking a screenshot of a weird frame, but I haven't done sufficient testing, to confirm any actual relationship with the screenshot function.
Note: _46A4032.CR2 is an actual valid image. And _46A4034.CR2 is a problem frame, trying to make me believe I can freeze time :P
I am at changeset: d76742634eee+ with 5D3.123 and iso_research branches.
Starting the camera in movie mode LV with either raw video module loaded, results in the debug menu modules not being shown in the menu (adtg_gui, raw_diag). The modules are still active in their last state, ie: raw_diag continues to function, they simply do not display in the menu.
I assume you removed 'is_native_movie_mode' in some of the latest changes to unified.
On 6D.116 (didn't check 113) merging to 497b816 is fine. After this, adtg_gui and dual_iso no longer perform any actions. I can change registers and the patch manager seems to show these changes, but nothing actually changes except the UI.
I seem to recall having issues with patch manager previously, but didn't have the time to debug back then, and obviously forgot to revisit the problem.
Just double-checked the stubs and they should be fine. Strings match and the functions are similar to those for 5D3.113, so I don't know why this doesn't work. I'll try to look into it, but it may take some time, as I'm really busy at work atm.
Revisiting this. Enabling adtg_gui and taking a photo results in card led remaining active. Pressing buttons on rear of camera enables backlight of LCD. Requires battery pull to restore functionality.
This is before or after your 1.1.6 stub update?
Before. It works as expected now, although those two entries still display red.
"Cache is locked down (not exactly clean)."
That's fine - red should disappear as soon as you turn it off.
time & nerves to update this so I can get rid off the failure described here: