38 replies to this topic

[Outhere]

Is there some command that you have to put in this sub.Ini so I can use the colors for FX2 games..

I have gone through the manual, looked over this thread and I'm just not getting anywhere

[DDH69]

I meant put the command

 

RGB_TRIGGER=FIXED

 

 into your Aliens.ini , and other game ini files.  They are all SUP_INI files.

[greeze]

Thanks DDH69.

 

We're getting closer; the undercab lighting is coming on now but it's white on both test tables.

 

Debug log FYI:

 

24-Sep-16 09:17:29 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

24-Sep-16 09:17:29 - Starting up - version 3.02

24-Sep-16 09:17:29 - 0 LEDWiz device(s) found

24-Sep-16 09:17:29 - 0 FTDI (Sainsmart) device(s) found

24-Sep-16 09:17:29 - DOFLinx device: 1 Initialising as PacLed64 #1

24-Sep-16 09:17:29 - DOFLinx device:1 PacLed64 setup with 64 outputs

24-Sep-16 09:17:29 - Reading DOFLinx.INI startup config file details

24-Sep-16 09:17:29 - Reading DOF config file

24-Sep-16 09:17:41 - Processing incoming message - SUP_INI=DOFLinxConfig\Aliens

24-Sep-16 09:17:41 - Processing parameter 'SUP_INI' with data 'DOFLinxConfig\Aliens' in real-time

24-Sep-16 09:17:41 - Reading real-time supplementary INI file DOFLinxConfig\Aliens.INI details

24-Sep-16 09:17:41 - Processing parameter 'RGB_OUTPUT' with data '133' in real-time

24-Sep-16 09:17:41 - Processing parameter 'RGB_STYLE' with data 'Dodger_Blue' in real-time

24-Sep-16 09:17:41 - Processing parameter 'RGB_TRIGGER' with data 'FIXED' in real-time

24-Sep-16 09:17:41 - Processing incoming message - GAME_NAME=

24-Sep-16 09:17:41 - Processing parameter 'GAME_NAME' with data '' in real-time

24-Sep-16 09:17:45 - Activated by process name : Pinball FX2

24-Sep-16 09:17:51 - Game name = 'AliensPinball'

24-Sep-16 09:17:51 - Named process detected and startup commenced

24-Sep-16 09:17:51 - Building restricted colour palette for game name = AliensPinball

24-Sep-16 09:17:52 - Key number #13 is activating device=1 output=16

24-Sep-16 09:17:52 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:17:52 - Key number #13 is activating device=1 output=16

24-Sep-16 09:17:53 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:17:53 - Key number #13 is activating device=1 output=16

24-Sep-16 09:17:53 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:17:54 - Key number #13 is activating device=1 output=16

24-Sep-16 09:17:54 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:18:15 - Activating process disappeared so stopping things

24-Sep-16 09:18:21 - Processing incoming message - SUP_INI=DOFLinxConfig\Alien_Isolation

24-Sep-16 09:18:21 - Processing parameter 'SUP_INI' with data 'DOFLinxConfig\Alien_Isolation' in real-time

24-Sep-16 09:18:21 - Reading real-time supplementary INI file DOFLinxConfig\Alien_Isolation.INI details

24-Sep-16 09:18:21 - Processing parameter 'RGB_OUTPUT' with data '133' in real-time

24-Sep-16 09:18:21 - Processing parameter 'RGB_STYLE' with data 'Lime_Green' in real-time

24-Sep-16 09:18:21 - Processing parameter 'RGB_TRIGGER' with data 'FIXED' in real-time

24-Sep-16 09:18:21 - Processing incoming message - GAME_NAME=

24-Sep-16 09:18:21 - Processing parameter 'GAME_NAME' with data '' in real-time

24-Sep-16 09:18:24 - Activated by process name : Pinball FX2

24-Sep-16 09:18:30 - Game name = 'Alien:IsolationPinball'

24-Sep-16 09:18:30 - Named process detected and startup commenced

24-Sep-16 09:18:30 - Building restricted colour palette for game name = Alien:IsolationPinball

24-Sep-16 09:18:33 - Key number #13 is activating device=1 output=16

24-Sep-16 09:18:33 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:18:33 - Key number #13 is activating device=1 output=16

24-Sep-16 09:18:33 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:18:34 - Key number #13 is activating device=1 output=16

24-Sep-16 09:18:34 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:18:35 - Key number #13 is activating device=1 output=16

24-Sep-16 09:18:35 - Key number #13 is de-activating device=1 output=16

24-Sep-16 09:18:36 - Right flipper pressed

24-Sep-16 09:18:36 - Key number #32 is activating device=1 output=13

24-Sep-16 09:18:36 - Right flipper lifted

24-Sep-16 09:18:36 - Key number #32 is de-activating device=1 output=13

24-Sep-16 09:18:37 - Left flipper pressed

24-Sep-16 09:18:37 - Key number #162 is activating device=1 output=1

24-Sep-16 09:18:37 - Left flipper lifted

24-Sep-16 09:18:37 - Key number #162 is de-activating device=1 output=1

24-Sep-16 09:18:37 - Left flipper pressed

24-Sep-16 09:18:37 - Key number #162 is activating device=1 output=1

24-Sep-16 09:18:37 - Left flipper lifted

24-Sep-16 09:18:37 - Key number #162 is de-activating device=1 output=1

24-Sep-16 09:18:37 - Right flipper pressed

24-Sep-16 09:18:37 - Key number #32 is activating device=1 output=13

24-Sep-16 09:18:37 - Right flipper lifted

24-Sep-16 09:18:37 - Key number #32 is de-activating device=1 output=13

24-Sep-16 09:18:37 - Right flipper pressed

24-Sep-16 09:18:37 - Key number #32 is activating device=1 output=13

24-Sep-16 09:18:38 - Right flipper lifted

24-Sep-16 09:18:38 - Key number #32 is de-activating device=1 output=13

24-Sep-16 09:18:38 - Left flipper pressed

24-Sep-16 09:18:38 - Key number #162 is activating device=1 output=1

24-Sep-16 09:18:38 - Left flipper lifted

24-Sep-16 09:18:38 - Key number #162 is de-activating device=1 output=1

24-Sep-16 09:18:43 - Activating process disappeared so stopping things

[DDH69]

Hmmm, I can't see a logical reason for this just looking at the log.  I'll have to try it out on my cabinet tomorrow morning and see what I can find.  I'll get back to you then.

[greeze]

Okay, thanks. No worries...

[DDH69]

Well I've run up my system this morning and split the INI files the way you had them in your previous post (plus the RGB_TRIGGER=FIXED) and it works as expected, Dodger_Blue is displayed on my RGB_OUTPUT.  So now I'm really fascinated!

 

I'll PM you a version of DOFLinx with a couple of extra DEBUG messages so that we can try and figure this out.  Please run it as you have been, show the LOG, base and SUP INI files as they are currently.

[greeze]

Aliens.ini

RGB_OUTPUT=133

RGB_STYLE=Dodger_Blue

RGB_TRIGGER=FIXED

 

Alien_Isolation.ini

RGB_OUTPUT=133

RGB_STYLE=Lime_Green

RGB_TRIGGER=FIXED

DOFLinx.ini

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=133

 

# 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=1

 

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

 

DOFLinx.log

25-Sep-16 08:03:09 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

25-Sep-16 08:03:09 - Starting up - version 3.04

25-Sep-16 08:03:09 - 0 LEDWiz device(s) found

25-Sep-16 08:03:09 - 0 FTDI (Sainsmart) device(s) found

25-Sep-16 08:03:09 - DOFLinx device: 1 Initialising as PacLed64 #1

25-Sep-16 08:03:09 - DOFLinx device:1 PacLed64 setup with 64 outputs

25-Sep-16 08:03:09 - Reading DOFLinx.INI startup config file details

25-Sep-16 08:03:09 - Reading DOF config file

25-Sep-16 08:03:09 - Processing incoming message - SUP_INI=DOFLinxConfig\Aliens

25-Sep-16 08:03:09 - Processing parameter 'SUP_INI' with data 'DOFLinxConfig\Aliens' in real-time

25-Sep-16 08:03:09 - Reading real-time supplementary INI file DOFLinxConfig\Aliens.INI details

25-Sep-16 08:03:09 - Processing parameter 'RGB_OUTPUT' with data '133' in real-time

25-Sep-16 08:03:09 - Processing parameter 'RGB_STYLE' with data 'Dodger_Blue' in real-time

25-Sep-16 08:03:09 - Processing parameter 'RGB_TRIGGER' with data 'FIXED' in real-time

25-Sep-16 08:03:09 - Processing incoming message - GAME_NAME=

25-Sep-16 08:03:09 - Processing parameter 'GAME_NAME' with data '' in real-time

25-Sep-16 08:03:22 - Activated by process name : Pinball FX2

25-Sep-16 08:03:28 - Game name = 'AliensPinball'

25-Sep-16 08:03:28 - Named process detected and startup commenced

25-Sep-16 08:03:28 - Building restricted colour palette for game name = AliensPinball

25-Sep-16 08:03:28 - Setting fixed RGB style of 'Dodger_Blue' to colour to index=67 with name=DODGER_BLUE

25-Sep-16 08:03:30 - Key number #13 is activating device=1 output=16

25-Sep-16 08:03:30 - Key number #13 is de-activating device=1 output=16

25-Sep-16 08:03:30 - Key number #13 is activating device=1 output=16

25-Sep-16 08:03:30 - Key number #13 is de-activating device=1 output=16

25-Sep-16 08:03:30 - Key number #13 is activating device=1 output=16

25-Sep-16 08:03:31 - Key number #13 is de-activating device=1 output=16

25-Sep-16 08:03:31 - Key number #13 is activating device=1 output=16

25-Sep-16 08:03:31 - Key number #13 is de-activating device=1 output=16

25-Sep-16 08:03:34 - Left flipper pressed

25-Sep-16 08:03:34 - Key number #162 is activating device=1 output=1

25-Sep-16 08:03:34 - Left flipper lifted

25-Sep-16 08:03:34 - Key number #162 is de-activating device=1 output=1

25-Sep-16 08:03:34 - Left flipper pressed

25-Sep-16 08:03:34 - Key number #162 is activating device=1 output=1

25-Sep-16 08:03:35 - Left flipper lifted

25-Sep-16 08:03:35 - Key number #162 is de-activating device=1 output=1

25-Sep-16 08:03:37 - Right flipper pressed

25-Sep-16 08:03:37 - Key number #32 is activating device=1 output=13

25-Sep-16 08:03:37 - Right flipper lifted

25-Sep-16 08:03:37 - Key number #32 is de-activating device=1 output=13

25-Sep-16 08:03:39 - Right flipper pressed

25-Sep-16 08:03:39 - Key number #32 is activating device=1 output=13

25-Sep-16 08:03:39 - Right flipper lifted

25-Sep-16 08:03:39 - Key number #32 is de-activating device=1 output=13

25-Sep-16 08:03:42 - Key number #13 is activating device=1 output=16

25-Sep-16 08:03:42 - Key number #13 is de-activating device=1 output=16

25-Sep-16 08:03:49 - Processing incoming message - quit

25-Sep-16 08:03:49 - Processing parameter 'quit' with data '' in real-time

25-Sep-16 08:03:49 - Shutting down

25-Sep-16 08:03:49 - Program close

 

Thanks 

Edited by greeze, 25 September 2016 - 07:46 AM.

[DDH69]

Thanks for all the feedback, one important point, are you now seeing the correct colour displayed not just white?

[greeze]

No, it's still white (on both tables)

[DDH69]

OK, well the log is clearly showing that its sending the codes for Dodger_Blue, so we'll need to check some other things.

 

Try just running DOFLinx in DEBUG=1 mode, right click on the window and use the test tool for "Test RGB / Flasher" and see how your colours display on device 133.  Let's check the obvious, that is colours displaying correctly.  Check a few colous, certainly Red, Blue, Green, White and Dodger_Blue.  Let's see what you get displayed.

[greeze]

Okay, that yielded some interesting results... it appears that dodger_blue is one of many colours that do not display correctly through my RGB output. Dodger_blue displays as white and so do many of the others (I haven't tested them all obviously - there're loads!)

 

However, the more common names, red, blue, green, yellow, purple etc work just fine. As these are the colours I was using for undercab lighting, I can live with this. I can also edit the GAME_COLOUR info on DOFLinx.ini to reflect my working (and preferred) colours (I assume).

 

New Aliens.ini

 

RGB_OUTPUT=133

RGB_STYLE=BLUE

RGB_TRIGGER=FIXED

New Alien_Isolation.ini

 

RGB_OUTPUT=133

RGB_STYLE=GREEN

RGB_TRIGGER=FIXED

New Alien_vs_Predator.ini

 

RGB_OUTPUT=133

RGB_STYLE=WHITE

RGB_TRIGGER=FIXED

 

I have absolutely no idea why dodger_blue (and others) don't display correctly; any ideas???

 

However, in summary, I think we have a workable solution here. Very many thanks for your help and patience. Much appreciated. 

[DDH69]

The old trick, when everything else fails check the obvious!  Glad we made progress.

 

Probably time to now check if your RGB device has the capability for a wide range of colours, and that your PacLed64 can display them all.  I'm not really sure how you do this.  Is there some sort of PacLed64 test program that you can use to try and display a series of colours, including those you've got difficulty with?

[greeze]

I'm not sure about a test program, I'll have to have a Google later and see what I can find.

 

Thanks again; both for the help and this great app.

[greeze]

My config is coming on nicely! What a great little app

 

Anyway, a question: is there any way to turn off an RGB output after a certain amount of time? The reason I ask is that I have some RGB outputs set to activate on flipper button presses. These RGB devices stay lit until I press the flippers again. Ideally, I'd like them to turn off until I press a flipper again (say, after half-a-second or so).

 

Is there a command for that currently or is it something that could be added please?

 

My Alien_vs_Predator ini file (to give you an idea of what I'm on about):

 

#Flipper colour & strobe outputs. A2=left flipper, 20=right flipper, 0D=strobe

KEY_TO_OUTPUT=A2 102 20 114 0D 116

 

#Set the colour of the undercab lighting

BUTTONS_ON_COLOUR=133,WHITE

 

#Flasher outputs - flasher left, flasher center, flasher right

RGB_OUTPUT=104,107,110

RGB_STYLE=RANDOM_DIFF

RGB_TRIGGER=FLIPPER

 

Thanks.

Edited by greeze, 25 September 2016 - 06:36 PM.

[DDH69]

Yes.

 

Two particular commands will be of interest to you.  One of them I forgot to document (along with another I just found ... oops!)  Anyway, just more functionality.

 

Sounds like you want either

KEY_TO_COLOUR_TOGGLE=

or

KEY_TO_COLOUR_TIMER=

 

The first turns on an RGB only while you hold the button down.  The second (which is not in the current manual, but has been around since about v1.4 along with its friend KEY_TO_OUTPUT_TIMER) will turn on an RGB for a set number of milliseconds.

 

I've cut in the manual sections below. (KEY_TO_COLOUR_TOGGLE was in the manual, the other two were not)

 

 

KEY_TO_COLOUR_TIMER=KK,DOO,CCC,MMMM[,KK,DOO,CCC,MMMM]

Default is no KEY_TO_COLOUR_TIMER activity, this parameter can be left out of the INI file.

A comma separated list in sets of four parameters key (KK), output(DOO), colour to set (CCC) and the time in milliseconds to display that colour (MMM).

This is used to set an RGB to a defined colour for a set time from when a key is pressed.  The RGB will revert back to colour that it was prior, or would have been in the RGB sequence when the timer expirers.  While active any RGB_OUTPUT activity on that RGB port is suspended.

 

KEY_TO_COLOUR_TOGGLE=KK,DOO,CCC[,KK,DOO,CCC,KK,DOO,CCC]

Default is no KEY_TO_COLOUR_TOGGLE activity, this parameter can be left out of the INI file.

A comma separated list in sets of three parameters key(KK), output (DOO), colour to set(CCC).

This is used to set an RGB to the defined colour while the key is pressed and then revert back to the colour that was there prior, or would have been in the RGB sequence, when the key is released.  While pressed any RGB_OUTPUT activity on that RGB port will be suspended.

 

KEY_TO_OUTPUT_TIMER=KK,DOO,MMMM[,KK,DOO,MMMM]

Default is no key KEY_TO_OUTPUT_TIMER activity, this parameter can be left out of the INI file.

A comma separated list in sets of keys (KK) and the corresponding output (DOO) to turn on for (MMMM) when its pressed.  The output remains on until MMMM milliseconds have expired.

This can be used to turn run a shaker, turn on a beacon for s short period as a key is pressed.

Keys can be defined more than once meaning that one key can be set to turn on multiple outputs for different time periods.

[greeze]

Thank you.

 

I'm about to head out on the 'school run' and will experiment when I get back but before I go, can I combine KEY_TO_COLOUR_TIMER with RGB_STYLE=RANDOM_DIFF somehow?

 

Ideally, this is what I'm aiming for:

1. Flippers pressed - random_diff colours displayed across three separate RGB flashers

2. Colours held on for a user-determined time and then off (or to 'black')

3. Repeat

 

It looks like the commands above will require me to define a colour and rather than turning off after the set time (or being set to 'black' - effectively off), the RGB will revert back to the previous colour. I'm wanting the flashers to do just that; flash, rather than stay on. Does that make any sense?!? Kinda hard to explain

 

Like I said, I'll have a good play around later this morning but I was just wondering...

[DDH69]

Oh, we can do anything!

 

If you want to use flashers to flash, then simply do not add them as a device in RGB_OUTPUT=.  The RGB_OUTPUT= devices are really for cabinet lighting, they are designed to cycle, etc.  Sounds like you want something different.

 

So, yes, you can have a different colour per flasher, use KEY_TO_COLOUR_TIMER= with something like this;

KEY_TO_COLOUR_TIMER= K1,D1,RANDOM,50,K1,D2,RANDOM,50,K1,D3,RANDOM,50  (clearly you need real key IDs and devices - but the colour is called RANDOM)

 

If you use your flipper key codes, then the above will define the same flipper key as triggering three different RGB devices (flashers in your case) for 50ms - a really quick flash, with random colours, just change the timing as you see fit.

 

SO because they start off, once the time period elapses they will return to the off state - a flash.  Using the "special" colour of RANDOM will ensure you get plenty of variety.

[greeze]

Superb! Thanks; that's exactly what I wanted to achieve. 

 

Job done.

[1toomuch]

hello greeze and terry, I am trying to follow this because I am having the same initial problem.  I have a PacLed device exactly like greeze.  Where does the command line for "pacled64=1" go?  I tried putting it in different spots in the doflinx.ini but it won't work for me.  I am not much of a programmer, so please speak in very basic terms. I really want to add this to my system.  HELP!

 

Figured it out by making a shortcut, sorry

Edited by 1toomuch, 02 November 2016 - 12:09 AM.