Probe matching issue on v1743 [Fixed]

Ran into an issue when attempting a probe match on the latest release. I have an HTL license.

The .bpd files created during the probe matching process only contain 1's and 0's for the x/y/Y data.

Here's the .bpd text for my spectro:

<?xml version="1.0" encoding="UTF-8" ?>
<builder_color_space name="[1121339] 9-9-2023 - sony - spectro" version="2">
<head>
<x red="1" green="0" blue="0" white="0" />
<y red="0" green="1" blue="0" white="0" />
<L red="1" green="1" blue="1" white="1" />
<gamma>1.000000</gamma>
</head>
</builder_color_space>

And here's my colorimeter .bpd text:

<?xml version="1.0" encoding="UTF-8" ?>
<builder_color_space name="[C3-22.B-02.017395.03] 9-9-2023 - sony - colorimeter" version="2">
<head>
<x red="1" green="0" blue="0" white="0" />
<y red="0" green="1" blue="0" white="0" />
<L red="1" green="1" blue="1" white="1" />
<gamma>1.000000</gamma>
</head>
</builder_color_space>

I've gone back to the previous version, and probe matching is working normally.

what even worse, is that any attempt to modify (with measure all) a bpd, does not update anything

Ok - the first issue I can easily repeat - No idea what's happened there - but we'll sort it.
Edit:
Oh - Modify All is exactly the same as the first issue!
Any Manually entered values are ok

Steve

Ok - bug found!
Should have a new release shortly.

Steve

But now .1747 works as always has worked before (i.e. without the Added catch to prevent identical names being used in Probe Matching)!

I get the Error Message pop-up here.

Steve

Error

I don't. If I put an already existent bpd name to a new probe match the software just goes on and write it over.

Works here... weird.

Steve

Ah!
Just realised the issue.
See the thread on Overwriting Probe Match files.
I'll explain there.

Steve

Steve,
I am curious, if you don't mind. What sequence have you used to generate the error message you displayed above?

See the linked info.

Steve