30 replies to this topic

[MrChucky]

I reinstalled Doflinx again and used a new Ini file and altered the output and input numbers , now DOFLinx works partially, flipperoutput solenoids work, slingshots work, rgb flashers work fine but no start/launch ball/coin/exit button leds, beacon, and strobe.

 

I see errors on the button leds, but don't know the cause.

Failed to button #15 with data '213'

Failed to button #16 with data '215'

Failed to button #18 with data '214'

Failed to button #17 with data '216'

Failed to button #19 with data '212'

Invalid device for interpretation of 216

 

I've linked the ini and log files.

https://drive.google...S4T-diBklXsoWDa

 

 

 

[Outhere]

I had the same error

 

DDH69 will have to look into this

 

Try This -- Add to each line -->  ,MONO

LINK_ST=213,MONO

Edited by Outhere, 21 November 2019 - 07:11 AM.

[DDH69]

@outhere you are correct with the ,MONO for >= V7.0

 

Is there something that you want or need me to look into?

[Outhere]

The format is now LINK_xx=D00,CCCC where CCCC is the colour for a RGB button, or set to MONO or left blank for a single LED illuminated button

 

I was under the impression you would not have to add MONO to the line

[DDH69]

The format is now LINK_xx=D00,CCCC where CCCC is the colour for a RGB button, or set to MONO or left blank for a single LED illuminated button

 

I was under the impression you would not have to add MONO to the line

 

It certainly was intended to work that way and I thought it was.  I've checked further tonight and there was a bug with this.  I've fixed it and will load a new version in the coming days, but for now, yes, just add ,MONO

[MrChucky]

Ok I've added ,MONO to the lines of the buttons like so

 

LINK_ST=213,MONO

LINK_EB=215,MONO

LINK_CN=214,MONO

LINK_EX=216,MONO

LINK_LB=212,MONO

 

The errors are gone from the log but the buttons are not lighting up with FX3.

 

When the line  'BUTTONS_ON=216' is added to the ini file the error "Invalid Device for interpretation of 216" comes up, but the button lights up then.

[DDH69]

So, three things ....

 

1. Great, the ,MONO has solved the issue you had - yay

2. With BUTTONS_ON=216 the error message is invalid, my bad, fixed in v7.01.  It is working as it should turning on the button, there was an error in the move to be able to use DOO format and named buttons.

3. What buttons are you expecting the FX3 game to light up?  FX3 triggers do not operate button LEDs just toys.  Generally what you do is turn on the button LEDs you want at startup of the FX3 game and off again at the end.  There are two FX3 SUP files in the release INI folder that I use for ON and OFF actions

[MrChucky]

Hi DDH69,

Thanks for your excellent support, I will have a lookout for version 7.1.

I did not know the button lights were not working by default in fx3 but will look into the SUP Ini files to make them light up maybe.

Are you sure the other toys like beacon and strobe work ? Have not seen them light up in the game.

[DDH69]

Just about to upload V7.01 now.

 

The beacon and strobe are certainly used in various games, but not all.  What games are your favourites?  I'll have a look if they are used in those and what you need to hit / do.

[mwnation]

@DDH69 they did it again. so i just got it working last night for the first time. i went to use it today and steam caused a missing dill issue. so i reinstalled PFX3 and after a hour of fixing dll issues (thanks microsoft) i got your warning alarm and today they released "the big fix" https://store.steamp...20/Pinball_FX3/

 

just a heads up for anyone else looking at this. Good news is this is most likely the last patch

[DDH69]

@DDH69 they did it again. so i just got it working last night for the first time. i went to use it today and steam caused a missing dill issue. so i reinstalled PFX3 and after a hour of fixing dll issues (thanks microsoft) i got your warning alarm and today they released "the big fix" https://store.steamp...20/Pinball_FX3/

 

just a heads up for anyone else looking at this. Good news is this is most likely the last patch

 

I will look into this tonight