Jump to content

EDIT: Disregard, Not a bug


jestermgee

Recommended Posts

EDIT

 

I have this the wrong way around and the issue is the opposite, I see what is happening now. 

 

If nothing is entered into the RGB led event slot in the config tool then all 3 channels for each device appear as 0 so this adds 2 additional value locations and if these are not included then it causes an issue but if you edit the string manually to add some RGB signal then these zeros have to be removed. 

 

I think that is how it appears to work. 

 

 

 

Hope someone can help me with a bug I seem to have found in the config tool after literally days and many hours of troubleshooting why things are not working correctly, it appears the config tool is the cause and if not generating a config correctly. 

 

For reference here is my output port mapping, this is all fine and works with everything attached and I can manually create a mapping within notepad and have it work without issue so on the front of configuration this is all good. 

 

image.thumb.png.84f5f10eb9f782dd3601169fe483717f.png

Now, according to my port setup above the generated string should correspond (and does) to this set of values: 

 

Table Name,Left Flipper,Left Slingshot,10 Bumper Middle Left,10 Bumper Middle Middle,10 Bumper Middle Right,Right Flipper,Right Slingshot,10 Bumper Back Right,10 Bumper Back Middle,10 Bumper Back Left,Beacon,Shaker,How To Play,Spare,Spare,[R/G/B] Flippers,[R/G/B] Magnasave Right,[R/G/B] Magnasave Left,Extra Ball,Coin,Launch,Start,[R/G/B] Fire,[R/G/B] 5 Flasher OL,[R/G/B] 5 Flasher L,[R/G/B] 5 Flasher C,[R/G/B] 5 Flasher R,[R/G/B] 5 Flasher OR,Strobe

 

It seems if the RGB Magnasave button's do not have any data within them in the DOF COnfig table, on my config it generates an additional set of zeros. 

Example: 

Here is a table I am testing with FunLand and I export the default config I get this string:


FunLand_1968,E101,E103,0,E106,0,E102,E104/E121,E107,0,E105,0,0,ON,0,0,ON Red,0,0,0,0,0,0,0,ON,0,E123 Blink,0,0,0,E103 Cyan FD500/E105 Red/E119 Pink/E120 Pink/E124 Blue FD500/E125 White/E129 Red/E130 Green/E131 Blue,E103 Cyan FD300/E105 Red/E106 Yellow/E119 Pink/E120 Pink/E124 Blue FD400/E125 White/E129 Red/E130 Green/E131 Blue,E103 Cyan FD100/E104 Cyan FD100/E105 Red/E106 Yellow/E107 Red/E119 Pink/E120 Pink//E124 Blue FD300/E125 White/E129 Red/E130 Green/E131 Blue,E104 Cyan FD300/E106 Yellow/E107 Red/E119 Pink/E120 Pink/E124 Blue FD200/E125 White/E129 Red/E130 Green/E131 Blue,E104 Cyan FD500/E107 Red/E119 Pink/E120 Pink/E124 Blue FD100/E125 White/E129 Red/E130 Green/E131 Blue,0

 

In BOLD are these phantom values that appear from nowhere if a table does not have anything in the RGB Magnasave locations. Here is the exact same code generated from DOF Config if In now place some data in the magnasave locations: 

 

FunLand_1968,E101,E103,0,E106,0,E102,E104/E121,E107,0,E105,0,0,ON,0,0,ON Red,RGB MAG R,RGB MAG L,0,ON,0,E123 Blink,0,0,0,E103 Cyan FD500/E105 Red/E119 Pink/E120 Pink/E124 Blue FD500/E125 White/E129 Red/E130 Green/E131 Blue,E103 Cyan FD300/E105 Red/E106 Yellow/E119 Pink/E120 Pink/E124 Blue FD400/E125 White/E129 Red/E130 Green/E131 Blue,E103 Cyan FD100/E104 Cyan FD100/E105 Red/E106 Yellow/E107 Red/E119 Pink/E120 Pink//E124 Blue FD300/E125 White/E129 Red/E130 Green/E131 Blue,E104 Cyan FD300/E106 Yellow/E107 Red/E119 Pink/E120 Pink/E124 Blue FD200/E125 White/E129 Red/E130 Green/E131 Blue,E104 Cyan FD500/E107 Red/E119 Pink/E120 Pink/E124 Blue FD100/E125 White/E129 Red/E130 Green/E131 Blue,0

 

Have I discovered a bug (that is fixable)? 

 

 

Edited by jestermgee
Link to comment
Share on other sites

  • jestermgee changed the title to EDIT: Disregard, Not a bug

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...