Configtool - RGB Fire in PBX and PBY

[DJOMaverick]

Having an odd issue with Configtool (legacy and beta both) in configuring both PinballX and PinballY, in the same way.  Unclear if it is on configtool's end or the frontends.

 

So I've got an RGB Fire button which is set up in the cabinet config.  It appears to work fine in games that use it.  However, if I tweak either PBX or PBY configs to use it, the configuration line gets broken.

 

For example, PBY default config works as expected.  However, if I tweak the config to blink the fire button in a color, only one value goes into the final ini line which is read for the red channel only. It then acts like it expects to see separate G and B values after (which aren't being generated) and instead treats the next two values in the line (whatever they are) as if they were the G and B values.  This in turn causes all subsequent port values in the line to be offset by two, and get read by the wrong device (effectively screwing up every port after the fire R port).

 

I can correct this by opening up the resulting ini files and manually adding values for G and B.  If I do, the fire button works, AND it corrects the offset and fixes all ports after them.  Obviously, kind of a pain to do every time the .ini is updated.

 

Can attach files if needed; should be replicable on any cab config where the RGB fire button is not the last set of light ports.

 

Thanks,

[LynnInDenver]

Are you attempting to assign a color by value and not name in the toy assignment in PBX/PBY? And how are you trying to define it if so? Because it sounds like whatever you're putting in is effectively putting in a control character that makes DOF skip the last two values and then ignore the delimiting of the next two fields of the definition for PBX/PBY.

 

Looking at my config files, there's a load of color definitions at the start of the file so you can assign a color by NAME (like Red, LCyan, etc), each NAME definition comes with a four byte HEX code (RGB and what appears to be Intensity, Red=#FF0000FF for instance), which you might also be able to use as a custom color.

[DJOMaverick]

I rechecked based on what you said and it was just a straight up syntax error on my part.  Was invoking by name but in the wrong place in the line and it was apparently being ignored.  Whoops.

 

Problem solved, thanks!  Disregard-

[LynnInDenver]

You're welcome. Sometimes, just asking the questions can invoke taking a fresh look.