DOF Config tool generates a bad config file.

[beachgarcon]

Am I the only one getting this when starting my DOF (in DirectOutput.log):
 

2022.07.19 22:05:32.395 Failed: E11BEIGE7

2022.07.19 22:05:32.395 Warning: Cant parse the trigger part E11BEIGE7 of the ledcontrol table config setting E11Beige7 Blue 10 AT0 AL0 AH10 AW40 AS400 ADL L25.

2022.07.19 22:05:32.395 EXCEPTION: Could not parse setting E11Beige7 Blue 10 AT0 AL0 AH10 AW40 AS400 ADL L25 in column data ON Red L13 AT0 AFDEN40 AFMIN75 AFMAX250 [...]

 

I checked and this comes from my directoutputconfig30.ini, under [Config DOF] for the tables acd_168[h/hc] and acd_170[h/hc]

Is that coming from a bad Config Tool update? I get my config files on every boot from the DOF Tool puller util.

 

EDIT: it seems to come from the ACDC Limited Edition table, see screenshot... this is the first time I'm looking into these things .. am I missing something? 

I seem to have fixed this by changing my local Candidate Configuration to this and re-exporting my configuration files!

I honestly have no clue if that's how it works, but it seems like the "beige" might have been a bad copy paste in there from some past revision?!

 

 

 

[outhere]

1 minute ago, beachgarcon said:

Am I the only one getting this when starting my DOF (in DirectOutput.log):
 

2022.07.19 22:05:32.395 Failed: E11BEIGE7

2022.07.19 22:05:32.395 Warning: Cant parse the trigger part E11BEIGE7 of the ledcontrol table config setting E11Beige7 Blue 10 AT0 AL0 AH10 AW40 AS400 ADL L25.

2022.07.19 22:05:32.395 EXCEPTION: Could not parse setting E11Beige7 Blue 10 AT0 AL0 AH10 AW40 AS400 ADL L25 in column data ON Red L13 AT0 AFDEN40 AFMIN75 AFMAX250 [...]

 

I checked and this comes from my directoutputconfig30.ini, under [Config DOF] for the tables acd_168[h/hc] and acd_170[h/hc]

Is that coming from a bad Config Tool update? I get my config files on every boot from the DOF Tool puller util.

 

EDIT: it seems to come from the ACDC Limited Edition table, see screenshot... this is the first time I'm looking into these things .. am I missing something? 

I seem to have fixed this by changing my local Candidate Configuration to this and re-exporting my configuration files!

I honestly have no clue if that's how it works, but it seems like the "beige" might have been a bad copy paste in there from some past revision?!

 

 

On the DOF website submitted to have it fixed