Error Parsing ini files... extra characters inserted in config files

[bele2009]

Guys,

 

I was looking ay my DOF log files and saw several parsing errors. 

 

The first one occurs with the "Big Trouble" table. Extra "L" are being inserted when I am generating the config:

 

String in DOF Config Tool (VPU Website):
E104 Cyan 50 AH100 ADU AS300/E304 Red AL0 AT40 AW100 AH10 L3/E301 Red AL0 AT60 AW100 AH10 L3/E500 Dark_violet L0 ...

 

What ends up in my directoutputconfig30.ini file:
E104 LCyan 50 AH100 ADU AS300/E304 LRed AL0 AT40 AW100 AH10 L3/E301 LRed AL0 AT60 AW100 AH10 L3/E500 LDark_violet ...
           ^                                                                     ^                                                                           ^                                                                            ^

I also see some "E500" events turning into "LE500" which is also incorrect.

 

Any idea ?

[jestermgee]

Sounds a bit like what I have noted in this bug post

Seems I also have extra characters being generated if some values in the tables config are empty. I have noted if Magnasave RGB buttons in my case are not populated an extra lot of 0,0,0,0 are added in the string which affects how these tables are handled. Think some of the code in the tool isn't generating the configs correctly.  Funnily enough, I have created my own config generator in google sheets and this created config strings that work 100% but using config tool the "fix" for me is I have to go into every table I have, add magnasave functions then save this and export the file.... Hope this can be addressed.