236 replies to this topic

[Totaltimo]

 

 

 

 

While Pro Pinball is running can you open a command prompt and run "tasklist".  Its the lines related to Pro Pinball that are of interest.

 

 

Yes, I can :-)

 

I have three "ProPinball.exe" tasks - one for the backglass, one for the dmd and one for the game itself:

 

https://www.dropbox....er_cmd.png?dl=0

 

The PROCESSES-line in the INI file looks like this:

 

PROCESSES=Pinball FX2,Pro Pinball,ProPinball.exe

 

I also tried to exchange the order of the tasknames, e.g. "ProPinball.exe" in first place, but that doesn't make a change.

 

 

In that case the name should be "ProPinball" with no spaces.  So "PROCESSES=Pinball FX2,ProPinball".

 

If this doesn't work I have a little app that lists all running process names using the same code that detects them in DOFFX2.

 

 

Cool! You made my day :-)

 

That was my mistake! It works! Thanky you so much!

[Mace]

DDH69,

 

Been testing all day, v2.04 is rock solid, working happily with the Freedom board and Pro Pinball, TPA DX9 & DX11, BAM for TPA, TPAFreeCamMod, DMDExt, Pinball FX2, Zaccaria Pinball and its happy to hide in the background while Future Pinball and the various Visual Pinballs are running. It even lets PinballX run the Ledwiz plugin and puts up with LEDBlinkey.

 

Congratulations, this is the first piece of code I've allowed to run in the background without slamming it shut with the TASKKILL command after every table closure. 

 

Please PM me your PayPal, I'd like to buy you a beer.

 

M

[sasa12345]

I'm trying to FP or not to go..

Can someone explain to me where the mistake

v2.04

kl25z

I need to put this command in the table script LoadExternalScript command ?

####
# The config file for DOFFX2
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# Note - this works with LEDWiz, PacLed64 and Sainsmart (FTDI devices)
#
# Output devices outputs are entered in the format of
# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes
####

# location of your standard DOF outut configuration file
DIRECTOUTPUTCONFIG=C:\games\Visual Pinball\Tables\plugins\DirectOutput\Config\directoutputconfig8.ini
# If you want to list the processes that will wake up DOFFX2, comment it out if you just want Pinball FX2
#PROCESSES=Pinball FX2,Future Pinball,VPinball_9_9_1,VPPhysMod5
# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=117
R_FLIPPER_OUTPUT=125
# The keyboard hex code for the key that is used for each flipper from https://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# 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=109
# 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=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
# The button(s) to turn on when FX2 starts, ie the exit button LED
BUTTONS_ON=102 104
#BUTTONS_ON=
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=32 101 35 106 36 105
# 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.
# In Pinball FX2 this means when I nudge it all goes red.
KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when Pinball FX2 stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_FX2=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
# Game specific colours in the formnat of a CSV of Game Name,Colour#1,Colour#2 - colours as they appear in your directoutputconfig
GAME_COLOUR=Plants VS. Zombies,Lime,Green,Yellow,Gold,Lawn_Green,Chart_Reuse,Green_Yellow,Forect_Green,Dark_Green,Yellow_Green,Light_Green

28-Aug-16 21:28:49 - DOF for Pinball FX2 - DOFFX2 by DDH69
28-Aug-16 21:28:49 - Starting up - version 2.04
28-Aug-16 21:28:49 - 1 LEDWiz device(s) found
28-Aug-16 21:28:49 - DOFFX2 device: 1 Initializing as LEDWiz #8 with ID=0
28-Aug-16 21:28:49 - DOFFX2 device:1 LEDWiz setup with 32 outputs
28-Aug-16 21:28:49 - 0 FTDI (Sainsmart) device(s) found
28-Aug-16 21:28:49 - Reading DOFFX2.INI startup config file details
28-Aug-16 21:28:49 - Reading DOF config file

greeting

Edited by sasa12345, 28 August 2016 - 09:16 PM.

[DDH69]

I'm trying to FP or not to go..

Can someone explain to me where the mistake

v2.04

kl25z

I need to put this command in the table script LoadExternalScript command ?

####
# The config file for DOFFX2
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# Note - this works with LEDWiz, PacLed64 and Sainsmart (FTDI devices)
#
# Output devices outputs are entered in the format of
# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes
####

# location of your standard DOF outut configuration file
DIRECTOUTPUTCONFIG=C:\games\Visual Pinball\Tables\plugins\DirectOutput\Config\directoutputconfig8.ini
# If you want to list the processes that will wake up DOFFX2, comment it out if you just want Pinball FX2
#PROCESSES=Pinball FX2,Future Pinball,VPinball_9_9_1,VPPhysMod5
# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=117
R_FLIPPER_OUTPUT=125
# The keyboard hex code for the key that is used for each flipper from https://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# 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=109
# 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=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
# The button(s) to turn on when FX2 starts, ie the exit button LED
BUTTONS_ON=102 104
#BUTTONS_ON=
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=32 101 35 106 36 105
# 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.
# In Pinball FX2 this means when I nudge it all goes red.
KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when Pinball FX2 stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_FX2=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
# Game specific colours in the formnat of a CSV of Game Name,Colour#1,Colour#2 - colours as they appear in your directoutputconfig
GAME_COLOUR=Plants VS. Zombies,Lime,Green,Yellow,Gold,Lawn_Green,Chart_Reuse,Green_Yellow,Forect_Green,Dark_Green,Yellow_Green,Light_Green

28-Aug-16 21:28:49 - DOF for Pinball FX2 - DOFFX2 by DDH69
28-Aug-16 21:28:49 - Starting up - version 2.04
28-Aug-16 21:28:49 - 1 LEDWiz device(s) found
28-Aug-16 21:28:49 - DOFFX2 device: 1 Initializing as LEDWiz #8 with ID=0
28-Aug-16 21:28:49 - DOFFX2 device:1 LEDWiz setup with 32 outputs
28-Aug-16 21:28:49 - 0 FTDI (Sainsmart) device(s) found
28-Aug-16 21:28:49 - Reading DOFFX2.INI startup config file details
28-Aug-16 21:28:49 - Reading DOF config file

greeting

 

No, no LoadExternalScript or FP script modifications required .... yet.  Version 3 (not yet released) has full scripting support for FP.  At present this purely "listens" for your flipper keys when nominated processes are running and fires your solenoids.

 

It looks like you've got DOFFX2 starting up OK, just not configured quite right.

 

By default DOFFX2 only activates with the Pinball FX2 process is running.  To have it activate for other processes (in this example Pinball FX2 and Future Pinball) add the following line to your DOFFX2.INI file (or edit the commented out one in the INI you have);

 

PROCESSES=Pinball FX2,Future Pinball

 

(note the only spaces are in the emulator names.

[sasa12345]

ok, thanks a lot in this case I will wait V3.0,not to spoil the full enjoyment

[jesperpark]

I have a question, I have your program working on a PacLED 64 running through zebs output board. When i exit and usually when i load a fx2 game 1 or more channels will turn on for maybe 1 second.  Is this a normal thing?  Just when something like a random light or my blower or even shaker motor comes on makes me wonder if that is normal?

 

Thanks

[DDH69]

I have a question, I have your program working on a PacLED 64 running through zebs output board. When i exit and usually when i load a fx2 game 1 or more channels will turn on for maybe 1 second.  Is this a normal thing?  Just when something like a random light or my blower or even shaker motor comes on makes me wonder if that is normal?

 

Thanks

 

I've heard this mentioned once before, I think on a KL25Z board.  No its not normal, no it shouldn't happen.

 

If you run the program with DEBUG=1 it will report any output it turns on / off / action it takes.  Perhaps start it up with DEBUG=1, observe the issue, immediately shutdown, post me the log along with a description.  I'll be able to let you know if the program triggered an event, or if we're hunting something else completely.

[Mace]

I have a question, I have your program working on a PacLED 64 running through zebs output board. When i exit and usually when i load a fx2 game 1 or more channels will turn on for maybe 1 second.  Is this a normal thing?  Just when something like a random light or my blower or even shaker motor comes on makes me wonder if that is normal?
 
Thanks

 
I've heard this mentioned once before, I think on a KL25Z board.  No its not normal, no it shouldn't happen.
 
If you run the program with DEBUG=1 it will report any output it turns on / off / action it takes.  Perhaps start it up with DEBUG=1, observe the issue, immediately shutdown, post me the log along with a description.  I'll be able to let you know if the program triggered an event, or if we're hunting something else completely.

I was the 'other' KL25Z owner mentioned by DDH69, my board was kicking simply because I was running the program with forced activation set to on and slamming it shut after every table with a TASKKILL /F command. I changed this to allow the program to run in the background and detect the programs it supports as and when they are run. In that config there are no kicks at all.

If you exit the program by closing it from the task bar this does not happen but I have still not found a way to stop it running as I leave PinballX as then I still run a mass set of TASKKILL commands to make sure that nothing is running in the background. this causes the LED's to light in the same way as they do when the program first activates.

Just a thought DDH69 but a quick fix may be to prevent DOFFX2 from activating any output until the first user input, this could be added to the ini as an option too and it may help with future issues when it has to work with other code.

[DDH69]

Thanks Mace, replied quickly without going back and reading who it was.  Good advice given.

 

Remember the neatest correct entry to stop DOFFX2 is to send it a QUIT message via the little message app (DOFFX2Msg) or via a VBS like the included sample.  "DOFFX2Msg QUIT" will do it.  A neat shutdown ensures that the devices its linked to are closed properly.

 

DOFFX2 needs to activate the outputs you tell it to turn on, ie buttons, etc before user input.  It only activates the outputs you tell it, nothing else, so unsure how such a flag would help - happy to hear more though.

[jesperpark]

Well as typical with strange electrical things, I can't reproduce the error when needed. I tried about 10 times with Everything working as expected. I will leave the Debug on over the next few days and try and get it to repeat the problem, if no further issues then good for me

 

Thanks again

[DDH69]

Well as typical with strange electrical things, I can't reproduce the error when needed. I tried about 10 times with Everything working as expected. I will leave the Debug on over the next few days and try and get it to repeat the problem, if no further issues then good for me

 

Thanks again

 

OK, let me know if you get anything.

 

I looked very closely at the code today.  DOFFX2 definitely only turns on the devices specified on startup.  What it does do though, is arbitrarily set all outputs to 0 and refresh each device.  This should be fine, but just in case, in v3, I've changed it to only update to 0 if the output is non zero for some reason (they never should be), and only update the device if it makes a change.  I thought this would stop any unexpected side effects of forcing it back to zero.  I believe this will not change a thing, but its a bit more thorough, just in case.

[Mace]

Thanks Mace, replied quickly without going back and reading who it was.  Good advice given.

 

Remember the neatest correct entry to stop DOFFX2 is to send it a QUIT message via the little message app (DOFFX2Msg) or via a VBS like the included sample.  "DOFFX2Msg QUIT" will do it.  A neat shutdown ensures that the devices its linked to are closed properly.

 

DOFFX2 needs to activate the outputs you tell it to turn on, ie buttons, etc before user input.  It only activates the outputs you tell it, nothing else, so unsure how such a flag would help - happy to hear more though.

Well I suppose if I had read the manual then I wouldn't have wasted your time or mine Doh sorry, :-(

 

I 'forgot' the DOFFX2 folder and it's content as I have been working with the copy in the main DOF folder.......RTFM, RTFM

[Vizzini]

DDH69. Amazing work here! Having my flashers, beacons, shaker, and RGB buttons alive makes FX2 so much more fulfilling.

 

Suggestion: Would it be possible to add an option define two RGB sets in the configuration?

 

Imagine the 5 flashers. Position 1, 3, and 5 would be one set. Position 2 and 4 would be the other. The GAME_COLOUR list would control both. But, two individual random numbers would drive each set...using the random toggle. Or, using the rainbow toggle, one set would start on color 1 in the list and the other set would start on color 2.Then, instead of one bank of all the same color, we could have alternating colors.

 

From this R R R R R to R G R G R, for example.

[Vizzini]

I'm making nice progress creating custom game colors.

 

But, I can't get DOFFX2 to recognize the Bob's Burgers and Star Wars Darth Vader GAME_COLOUR= list. I've tried the actual names (i.e. Bob's Burgers Pinball) from the log as well as the file names (BobsBurgers.pxp). There may be more not recognized that I haven't found yet.

 

Anyone have them working? Ideas?

[TerryRed]

I find that naming the GAME_COLOUR the exact name that you see for the table's (game name) in Pinball X Game Manager is what will work for every system. If there's an extension, include it. If there isn't, then don't.

[DDH69]

I'm making nice progress creating custom game colors.

 

But, I can't get DOFFX2 to recognize the Bob's Burgers and Star Wars Darth Vader GAME_COLOUR= list. I've tried the actual names (i.e. Bob's Burgers Pinball) from the log as well as the file names (BobsBurgers.pxp). There may be more not recognized that I haven't found yet.

 

Anyone have them working? Ideas?

 

OUTPUT_GAME_NAME=1

 

This will log the game name picked up from the FX2 window into your DOFFX2.LOG file regardless of your DEBUG= configuration.  You should then be able to cut and paste that name from the LOG to the INI ensuring a match.  If that doesn't work then its on me, send me details and I'll fix.  I have Bob's Burgers so can test easily.

 

BTW - I'd love to grab your game colours when you're done    I've been too busy writing code to create some myself so am trying to get some fr personal use and to include in the base DOFFX2.INI provided with the download.

I find that naming the GAME_COLOUR the exact name that you see for the table's (game name) in Pinball X Game Manager is what will work for every system. If there's an extension, include it. If there isn't, then don't.

 

For clarity, the name used for GAME_COLOUR= is the full string provided via GAME_NAME= , or if no GAME_NAME= is provided for FX2 it gets the FX2 window title.  As such, I suggest providing a GAME_NAME= for non FX2 tables and let the system pick up the window title for FX2 games.  For FX2 that means you get the common game name not the file name (ie Sorcerers Lair vs Citadel)

[Vizzini]

Thanks for the suggestions guys. I have been using OUTPUT_GAME_NAME=1 and the log. Can't get it recognize.

 

From log: 03-Sep-16 08:51:48 - FX2 game name = 'Bob's Burgers Pinball' (Note: this is indeed the same name in the window title)

 

From Ini: GAME_COLOUR=Bob's Burgers Pinball,Navy,Dark_Red,Gold,Midnight_Blue

 

I have tried the PinballX names as TerryRed suggested. I thought maybe it was the apostrophe, but it recognizes Marvel's Ant Man, Marvel's The Avengers, etc..

 

DDH69- I'll certainly post my custom colors. I'd have none without you! 

[Vizzini]

Just FYI. I tried a few more of the Star Wars tables. All failing to be recognized.

 

STAR WARS™: DARTH VADER

Star Wars™ Pinball: Droids™

Star Wars™ Pinball: Episode IV A New Hope

[DDH69]

Vizzini, I'll look into it today and get back to you.

 

As I said, I can test with Bob's as I have that one.  I hadn't thought about the "TM" mark - I might have to filter that ... until later.

 

I'm keen to get my colours going, so this just MUST work!

[Vizzini]

Thanks. You keep coding and I'll keep adding the game colors.

 

Portal has an odd character too.

 

Portal ®