Jump to content



Photo
- - - - -

Help required! Falling at the first hurdle here...


  • Please log in to reply
38 replies to this topic

#1 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 21 September 2016 - 03:13 PM

HI,

I'm trying to get this app to work but I cannot get very far. Here is the log file output...

 

 

21-Sep-16 13:31:38 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

21-Sep-16 13:31:38 - Starting up - version 3.02
21-Sep-16 13:31:38 - 0 LEDWiz device(s) found
21-Sep-16 13:31:38 - 0 FTDI (Sainsmart) device(s) found
21-Sep-16 13:31:38 - No valid devices for DOFLinx were found ...... sorry about that

 

As you can see, no valid device was found. I have a PacLED64 working just fine with DOF R3 and Visual Pinball. The DOFLinx files are in the same directory as all the directoutput files as required.

 

Here is my .ini file (the bare minimum, I beleive?)...

 

DIRECTOUTPUTCONFIG=C:\Program Files (x86)\Visual Pinball\Tables\plugins\directoutput\config\directoutputconfig20.ini

PROCESSES=Pinball FX2
L_FLIPPER_OUTPUT=101
R_FLIPPER_OUTPUT=113
L_FLIPPER_KEY=A2
R_FLIPPER_KEY=20
 

 

I'm stumped here! Please help... :(


Edited by greeze, 21 September 2016 - 03:13 PM.

Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#2 Vizzini

Vizzini

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts

  • Flag: United States of America

  • Favorite Pinball: ???

Posted 21 September 2016 - 11:53 PM

Any reason why you are not using the sample DOFLinx.ini in the download? I'd try that.

 

Also, it might just be the way you have your system set up. But, my DOF output config file does not have a 20 in it. Mine is: directoutputconfig.ini. Not sure if that might help.



#3 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 22 September 2016 - 06:24 AM

Thanks for the reply Vizzini. 

 

I'm using the stripped down .ini file as I read somewhere that this was the bare minimum amount of info required to start DOFLinx. As for the '20' in the filename, if I remove that (from the actual file itself), DOF doesn't run at all.

 

I'll try and remove that '20'. I don't know how that got there TBH.


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#4 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 22 September 2016 - 08:33 AM

Okay, the '20' is added from the config from the DOF Configtool  page (screenshot below).

 

I don't know if this is a problem or not? I also don't know how to get the DOF Configtool page to generate a config without the additional '20'.

 

 

1ZZY501.png

 


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#5 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 22 September 2016 - 11:06 AM

Howdy.  The file name is not an issue.  The file could be called "Fred.ini", it wouldn't matter.  So long as its your file with the colours defined it will work.  The details in your first post for the INI look fine.

 

Yes that is the minimum INI file, also fine.

 

You issue will be that with a PacLed64 you need to add a command line argument as DOF doesn't test and report back valid PacLed64 devices as it does with SainSmart and LedWiz.

 

From the guide page #2

 

"

PACLED64=

Not surprisingly, only of interest if you have PacLED64 device(s).  This option is valid for Set and Forget or Launch Before setups.

Under DOF PacLed64 devices can be numbered 1,2,3 or 4.  You need to know what device number(s) you have.  Once you know simply place them, comma separated, on the command line, is DOFLinx PACLED64=1,2 or DOFLinx PACLED64=1.  When using a Windows shortcut just put the PACLED64=3 command line option at the end of the ‘Target’.

 

"

 

Let us know how you get on.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#6 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 22 September 2016 - 02:43 PM

Thanks mate! It's working now :)

 

Now I need to sort out the configuration.


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#7 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,955 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 22 September 2016 - 05:47 PM

What are you using your PACLED for in your cabinet?

 

I'm just curious to see how people use it in a pinball cabinet versus an Led-Wiz. I assume it would be great to use for almost all toys, provided you have the proper drivers / amps / relays to power your devices.



#8 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 22 September 2016 - 05:53 PM

It powers all the toys, lights etc. Terry. :)

 

I bought an 'all-in-one' kit from ZebsBoards.com ages ago. That kit came with everything required (perfect for a numpty like me!) and was pretty much plug-and-play. Excellent aftersales support too. Steve (Zeb) is a great guy.

 

I have a load of experimenting to do with this great app!


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#9 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 22 September 2016 - 07:27 PM

Okay then, so far so good :)

 

A question (leading to another question)... is it possible to set an RGB output to a single, permanent colour (eg, my undercab lighting). At the moment,when playing,it's constantly changing colour.

 

And, if the above is possible, is there a way of doing it on a game-by-game basis (so individual games have their own unique undercab colour)

 

BTW: I'm talking Pinball FX2 games here... ;)


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#10 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,955 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 23 September 2016 - 02:34 AM

Okay then, so far so good :)

 

A question (leading to another question)... is it possible to set an RGB output to a single, permanent colour (eg, my undercab lighting). At the moment,when playing,it's constantly changing colour.

 

And, if the above is possible, is there a way of doing it on a game-by-game basis (so individual games have their own unique undercab colour)

 

BTW: I'm talking Pinball FX2 games here... ;)

 

Yes you can set an RGB Output to a single colour instead of cycling colours. 

 

You have these choices (from the guide):

 

 

 

RGB_STYLE=[RAINBOW|RANDOM|CCCC]

Default is RAINBOW, this can be left out of the INI file.

This parameter determines how colours are selected for the RGB_OUTPUT devices.

RAINBOW cycles through the current colour palette list from beginning to end.  So that could be the default entire colour palette, or the sub-set defined by GAME_COLOUR.
RANDOM, as the name implies, picks the next colour at random from the current colour palette.
RANDOM_DIFF, picks a new random colour from the current colour palette that is different for each RGB device provided.
RAINBOW_DIFF, picks a new random colour from the entire colour range that is different for each RGB device provided.
CCCC, is any valid colour name in the entire colour palette.  This has the effect of setting the RGB output to a fixed colour

 

You can also chose to have game specific colours as well based on the GAME_COLOUR in the DOFLinx.ini file (PFX2 Game colours are already in there, but you can change them to whatever you want).  How you use / launch DOFLinx will determine how this works.

 

PFX2 (my setup)

 

I use a separate SUP file for each of my systems, but you may have a different type of setup. A separate SUP file allows you to have custom settings for each system, and even each game if you want. I have DOFLinx always running and I MSG to it when launching a table for PFX2. The executable that Pinball X uses to "launch before" PFX2 tables for DOFLinx is the "DOFLinxMsg.exe" file.

 

The parameters are:

 

SUP_INI="DOFLinxConfigs\DOFLinx-PFX2"#GAME_NAME=

 

In the specific case of PFX2, the GAME_NAME can be left blank. Other systems will require GAME_NAME="[TABLEFILE]".

 

What happens is, the DOFLinxMsg.exe tells DOFLinx (which is always running) to load "my" Pinball FX 2 SUP_INI file "DOFLinx-PFX2.ini", which is located in my DirectOuput\DOFLinxConfigs folder (which I created). The GAME_NAME (table) for PFX2 will automatically = the correct GAME_COLOUR located in the DOFLinx.ini   file.

 

 

Future Pinball, TPA, MAME, PC Games, etc.. (my setup)

 

For all other systems, including Future Pinball non DOFLinx'ed tables, TPA, MAME, PC GAMES, etc..., this is what I use (The Pinball Arcade's example):

 

The executable that Pinball X uses to "launch before" a table / game is still the "DOFLinxMsg.exe" file.

 

SUP_INI="DOFLinxConfigs\DOFLinx-TPA"#GAME_NAME="[TABLEFILE]"

 

 

So remember....  "[TABLEFILE]"   =   GAME_NAME   =  GAME_COLOUR.   All of your GAME_COLOUR entries for every system should be in the "DOFLinx.ini" file. The PFX2 entries should already be there. Add in any Future Pinball, TPA or other systems custom colours you want. Just remember that the GAME_COLOUR needs to match exactly the Game Name in the Pinball X Game Manager, including any extensions it may show.


Edited by TerryRed, 23 September 2016 - 02:39 AM.


#11 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,805 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 23 September 2016 - 04:20 AM

What go's in this file --> DOFLinx-PFX2.ini



#12 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 September 2016 - 05:13 AM

What go's in this file --> DOFLinx-PFX2.ini

 

TerryRed is using this file for settings related to his Pinball Fx2 - DOFlinx preference.

 

I also use a supplementary INI for the different emulators.  This tactic allows me to set things like which button LEDs turn on, what RGB devices I use as flashers vs cabinet lighting differently from emulator to emulator.  In my case I assign my "Start" and Coin" buttons when using Pinball FX2 to trigger relays and drive things like camera adjustment.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#13 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 23 September 2016 - 07:18 AM

Thanks guys.

 

I'm finding this hard going so please bear with me! (I have the manual printed out now too - sorry about the noob questions previously)

 

How do I define a single RGB output to a single colour? For example, if I want my undercab lighting red, how do I do that? RGB_STYLE=RED ??? How do I define that for the undercab lighting only? (In my case it's device 1, port 33 i.e. 133)


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#14 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 September 2016 - 07:28 AM

Hey no problem.  This is a very flexible tool, so lots of set up and tweaking is possible.  Usual expectations of trying to help yourself first, so just read and try and work it out first, then keep the conversation going and we'll help you build up a piece at a time.  (and hopefully I don't give you a bum steer along the way)  THe tool is also reasonably new, so its conversations like this that build up some material for others to read later.

 

Yes,

 

RGB_OUTPUT=133

RGB_STYLE=Red

 

This will set your undercab device to Red for any emulator that activates DOFLinx in keyboard intercept mode.  For a Future Pinball coded table (if you're using that), it will use the undercab for whatever the FP author assigns.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#15 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 23 September 2016 - 10:55 AM

Thanks for the help so far Gents, appreciated. Unfortunately,I'm still a little lost. I've been playing around with the ini files this morning but still cannot achieve what I want. What I want (at this stage) is...

 

1. For the flipper buttons to activate left and right solenoids, left flasher and right flasher.

2. For the 'Launch Ball' button to activate the strobe.

3. For my undercab lighting to change for individual tables (colour to be defined in a supplementary ini file).

 

1 and 2 are working fine (this info is defined in the DOFLinx.ini file) for all PBFX2 tables.

3 however, isn't working as expected (this info is defined in supplementary ini files).

 

Here's my DOFLinx ini file:


 

DIRECTOUTPUTCONFIG=C:\Program Files (x86)\Visual Pinball\Tables\plugins\directoutput\config\directoutputconfig20.ini

 
#PROCESSES=Pinball FX2,Future Pinball,VPinball_9_9_1,VPPhysMod5
 
#DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=122
R_FLIPPER_OUTPUT=124
 
# The keyboard hex code for the key that is used for each flipper
L_FLIPPER_KEY=A2
R_FLIPPER_KEY=20
 
# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds
MAX_FLIPPER_ON=5000
 
# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma
#RGB_OUTPUT=
 
# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file
#RGB_STYLE=RANDOM
 
# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
#RGB_TRIGGER=TIME
 
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
#RGB_MIN_TIME=500
 
# The button(s) to turn on when DOFLinx starts
#BUTTONS_ON=133
 
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=A2 101 20 113 0D 116
 
# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.
#KEY_TO_COLOUR=A2 101 Green 20 113 Green
 
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.
FORCE_ACTIVE=0
 
# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_PROCESS=0
 
# Set to 1 to output the game name to the log regardless of the DEBUG flag setting.  Set to 0 to simply follow the DEBUG flag.
# Quite useful when you trying to get the FX2 window game name for setting game specific colours
OUTPUT_GAME_NAME=1
 
# 0 = OFF (normal operation), 1 = ON 
DEBUG=0
 
GAME_COLOUR=Alien:IsolationPinball,Medium_Blue,Lime,Dodger_Blue,Lime_Green
GAME_COLOUR=Alien vs. Predator Pinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green
GAME_COLOUR=AliensPinball,Medium_Blue,Dark_Golden_Rod,Dodger_Blue
GAME_COLOUR=American Dad! Pinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green
GAME_COLOUR=Marvel's Ant-Man,Medium_Blue,Dark_Red,Dodger_Blue
GAME_COLOUR=Archer Pinball,Medium_Blue,Yellow,Dodger_Blue,Blue_Violet

 

And this is my supplementary ini for Aliens (as said, all I want at this stage is for the underab lighting to change:


 

RGB_OUTPUT=133

RGB_STYLE=Dodger_Blue

 

And this one is for Alien Isolation;


 

RGB_OUTPUT=133

RGB_STYLE=Lime_Green

 

My Pinball FX2 options in Pinball X look like this:

GUVZxQP.png

 

My folder structure and supplementary ini filenames looks like this:

0dR56lF.png

 

Clearly, I'm doing something wrong here; I just can't get my head around what it is! I'm sorry for all the hassle. :(


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#16 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 September 2016 - 11:15 AM

OK, in your PinballX, Pinball FX2 Launch Before parameters you want to

1) parse a SUP_INI file name that is based on the TABLEFILE parameter that PinballX translates to a name per table.

2) set the GAME_NAME to nothing so that the Game name from the Pinball FX2 window is used (or in your case not used as you are fixing a colour).  These are the names included in the sample DOFLinx.INI file.

 

Something to be aware of with the above setup (its not an issue but will aide understanding) is that your SUP_INI file will use the disk file name for the table and the GAME_COLOUR= in your DOFLinx.INI file will use the common Pinball FX2 name.  ie disk name (PinballX TABLEFILE = citadel, FX2 common name = Sorcerers Lair)

 

So, Launch Before becomes

SUP_INI="DOFLinxConfig\[TABLEFILE]#GAME_NAME="

 

Your actual SUP_INI file on disk in your DOFLinxConfig folder becomes

citadel.ini

 

Now, if I've got any of this wrong I'm sure TerryRed will correct me (still on some decent drugs after surgery today :stunned: ). 


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#17 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 23 September 2016 - 12:36 PM

First, I hope you're feeling better soon! :)

 

I'm sorry, but it's still not working. Where am I going wrong?!?  :hmm:

 

My 'Launch Before' parameter is: SUP_INI="DOFLinxConfigs\[TABLEFILE]#GAME_NAME="

I'm only experimenting with Aliens and Alien Isolation at the moment and I have changed the supplementary ini names to: Aliens.ini and Alien_Isolation.ini (which are the disk file names) but the undercab lighting is not coming on at all. 

 

I can't see the wood for the trees here!  :unsure:


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#18 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 September 2016 - 01:02 PM

Thanks, resting and recovering.  I just won't be standing at the cabinet for a few days, so doing too much testing will be a bit hard.

 

Don't be sorry, remote problem solving can take a few iterations.

 

Anyway, switch on debug and grab a DEBUG.LOG from startup, open the table from PinballX, hit the flippers a few times, exit back to PinballX.  Also can you scren shot your Pinball FX2 tables folder - I trust you about the naming, just want to ensure we're not overlooking the obvious.

 

Its getting late here now, so I'll get back onto it tomorrow and we'll sort it out ...... unless others figure it out first.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#19 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 23 September 2016 - 01:14 PM

Okee dokee, debug log is:

 

23-Sep-16 14:04:56 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

23-Sep-16 14:04:56 - Starting up - version 3.02
23-Sep-16 14:04:56 - 0 LEDWiz device(s) found
23-Sep-16 14:04:56 - 0 FTDI (Sainsmart) device(s) found
23-Sep-16 14:04:56 - DOFLinx device: 1 Initialising as PacLed64 #1
23-Sep-16 14:04:56 - DOFLinx device:1 PacLed64 setup with 64 outputs
23-Sep-16 14:04:56 - Reading DOFLinx.INI startup config file details
23-Sep-16 14:04:56 - Reading DOF config file
23-Sep-16 14:05:04 - Processing incoming message - SUP_INI=DOFLinxConfig\Aliens
23-Sep-16 14:05:04 - Processing parameter 'SUP_INI' with data 'DOFLinxConfig\Aliens' in real-time
23-Sep-16 14:05:04 - Reading real-time supplementary INI file DOFLinxConfig\Aliens.INI details
23-Sep-16 14:05:04 - Processing parameter 'RGB_OUTPUT' with data '133' in real-time
23-Sep-16 14:05:04 - Processing parameter 'RGB_STYLE' with data 'Dodger_Blue' in real-time
23-Sep-16 14:05:04 - Processing incoming message - GAME_NAME=
23-Sep-16 14:05:04 - Processing parameter 'GAME_NAME' with data '' in real-time
23-Sep-16 14:05:07 - Activated by process name : Pinball FX2
23-Sep-16 14:05:12 - Game name = 'AliensPinball'
23-Sep-16 14:05:12 - Named process detected and startup commenced
23-Sep-16 14:05:12 - Building restricted colour palette for game name = AliensPinball
23-Sep-16 14:05:16 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:16 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:16 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:16 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:17 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:17 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:17 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:18 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:18 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:18 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:20 - Key number #13 is activating device=1 output=16
23-Sep-16 14:05:21 - Key number #13 is de-activating device=1 output=16
23-Sep-16 14:05:22 - Right flipper pressed
23-Sep-16 14:05:22 - Key number #32 is activating device=1 output=13
23-Sep-16 14:05:23 - Left flipper pressed
23-Sep-16 14:05:23 - Key number #162 is activating device=1 output=1
23-Sep-16 14:05:23 - Right flipper lifted
23-Sep-16 14:05:23 - Key number #32 is de-activating device=1 output=13
23-Sep-16 14:05:23 - Left flipper lifted
23-Sep-16 14:05:23 - Key number #162 is de-activating device=1 output=1
23-Sep-16 14:05:23 - Left flipper pressed
23-Sep-16 14:05:23 - Key number #162 is activating device=1 output=1
23-Sep-16 14:05:24 - Left flipper lifted
23-Sep-16 14:05:24 - Key number #162 is de-activating device=1 output=1
23-Sep-16 14:05:24 - Right flipper pressed
23-Sep-16 14:05:24 - Key number #32 is activating device=1 output=13
23-Sep-16 14:05:25 - Right flipper lifted
23-Sep-16 14:05:25 - Key number #32 is de-activating device=1 output=13
23-Sep-16 14:05:26 - Right flipper pressed
23-Sep-16 14:05:26 - Key number #32 is activating device=1 output=13
23-Sep-16 14:05:27 - Right flipper lifted
23-Sep-16 14:05:27 - Key number #32 is de-activating device=1 output=13
23-Sep-16 14:05:31 - Activating process disappeared so stopping things
 

 

Screenshot of the PBFX2 tables directory:

PLBsuQb.png

 

Thanks for the help so far :)


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#20 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,570 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 September 2016 - 10:39 PM

Well, I think that missing essential piece of information from the guide would help .... oops sorry  (I'll add it in the next guide update)

 

RGB_TRIGGER=FIXED

 

Add that to your SUP_INI file.  By default the trigger is TIME and needs to be overwritten. I think you're the first with this combination so I hadn't gone searching for this before.

 

This may not be the final answer, but it is required.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here