The FCMM forcing introduced with the above beta is always applied (off course with probe matching flagged), regardless the forcing flag setting.
I have noted that first comparing two bcs, one generated with the above forcing and an other on without: they are identical in measures.
So I remember having done some comparison between FCMM (my excel) and FCVM (CS probe matching).
So I repeated the same same FCVM probe matching I have done for that past comparison (luckily I had saved the bcs) an reapplied to it to the comparison.

Sorry - not sure what you are trying to say.
All you need to do is look at the various ColourSpace graphs with probe matching applied and toggle the 'Force simple matrix match on/off.
You will see the difference between the two modes.
As there was no FCMM option available previously, there is no other viable comparison.

Steve

What I have done. And I see a difference. But when I save the measures, they all have FCMM applied!

PS: I have done that test without connecting the probe. I will try also with probe connected.
PS(2): Also with probe connected, no way. What I see is that the file with probe matched that I have saved some time ago is different from the one I save now with FCMM (i.e. simple matrix) unforced. And If I look at comparisons I have done some time ago, generating on my own an FCMM correction, the FCMM set matches in XYZ what I save now (with a minimal error in the order of 10 exp (-13), as CS accuracy is not the same as Excel one).

Ok - am seeing a bug - but you really do need to simplify your feedback.
Your follow-up message has the needed info - "all profiles are saved with FCMM applied, regardless of FCVM being defined..."
(I have edited the thread title to be specific.)

We will fix.

Steve

Sorry, but it took a certain amount of time to focus the issue. It's not so trivial to recognize whether FCMM and FCVM is applied, and there also cases where the outcome is very close. I have tried to describe what I am sure of: i.e.: 2 bcs with the same measures regardless the FCMM flag and then, dangerous as well hidden, and difficult to demonstrate, that it is FCMM.

Actually, once I understood what you were trying to say, it was simple to define the issue.

Just open any profile, setup Probe Marching, and save in turn with the 'Force simple matrix' option off/on, and then re-open the profiles, and compare to the original profile with the 'Force simple matrix' option off/on...

Very simple.

Steve

Ok - the issue is actually NOT that simple.
There is a sync issue between the tick -box for 'Force simple matrix match', and the actual function being used.
If you can define more on when the saved profiles are correctly saved, and when not (as the issue will not always happen), that would be a help.

Steve

It's ok -we found the bug.
Fix will be released shortly.

Steve