Also, I know we can set the RGB Output brightness in DOF with the DOF config Tool....
Would it be possible to specify the brightness of an RGB Output (or all) in DOFFX2 separately from the "master" setting we configured with the DOF config tool?
I'm also trying to understand more the "intent" of the MSG app. It seems to be specifically used for when DOFFX2 is sleeping...am I right? So if I launched Future Pinball with a SUP file and DOFFX2 woke up...but then wanted to have something changed on the fly while FP is running, then the MSG app commands won't work at all, and I can't change anything until DOFFX2 is closed / restarted?
I know you have "plans" coming up, I'm just making sure I'm not trying to use the MSG app for something it wasn't meant to do? I was originally going to have DOFFX2 "always" running with Force Active=0....then when FP (MAME, TPA, etc) is launched, DOFFX2 will wake up to that specific process and the SUP file I have for that system. I hoped it would take effect until I quit the game and then DOFFX2 will "sleep". Then when I run a different system, DOFFX2 will "wake" and change its configuration based on the SUP file for the new system.
However, I can only get the first SUP file / system to take effect. Afterward, when I quite the game, DOFFX2 sleeps,...then when I launch a different system , DOFFX2 "wakes" but doesn't re-configure with the new SUP file. I get this with, or without using the MSG app.....
Is using DOFFX2 as a "Launch Before" (and not always running) the only way to do this? This is how I currently run it, then I use the MSG app to "quit" DOFFX2 when exiting back to Pinball X.
A couple of questions about the brightness.
1) Would it need to be set per RGB device or overall?
2) Do you know how brightness is performed? is it simply a matter of taking the RGB values and multiplying them by a brightness constant, ie if brightness is 50% and White is $FFFFFF, then are the outputs set to $7F7F7F ? if Crimson is $DC143C is 75% brightness $A50F2D ?
The intent of messaging DOFFX2 via the Msg app provided, VBScript or any other method, is to allow changing of DOFFX2 parameters without shutdown / startup. There are a couple of commands (ie QUIT) and manually turning on outputs / colour that will process at any time, ie DOFFX2 doesn't need to be active (unless you have a SainSMart device which can only take commands from one source at a time). IN addition almost any parameter can be changed while DOFFX2 in "asleep", ie between activation. This allows for reconfiguration using messaging via 'Launch Before' and 'Launch After' messages.
You can send messages about Game Names, Game Flag Files, and in fact reconfigure almost everything. You can even point it toward a SUP_INI file 'on the fly', so have parameters in a file rather than on the command line.
So you wouldn't use messages to reconfigure DOFFX2 while FP was running. You could message it while FP was running to activate an output or colour from some other program you have running in the background (I can't think of an example, but its possible)
The way you describe using messaging sounds right. It not working sounds wrong. The changes should be in effect until you change them to something else, they replace, not just remporarily change. As always happy to work through this with you. A couple of things to check with DEBUG=1 do you see "Processing incoming message ......"? If your sending a SUP_INI= message do you see "Reading real-time supplementary INI file ....."? After that you will not see debug messages per parameter unless you give an invalid parameter that doesn't cause a fatal exit, so you could try setting KEY_TO_COLOUR with a colour of "TerryRed" and you should see "KEY_TO_COLOUR has an an invalid colour of 'TerryRed' ". The first two messages should come up regardless of DOFFX2 being awake or asleep, it would only get to the last (error) message if it was asleep, as processing of that parameter will not happen while awake. Of course, I am human, so I program bugs, not aware of one here, but I never say never! Feel free to PM if we need to get into the real detail (some may think this is detail enough!).
The "plans"
are very close. The messaging above is not related to the "plans". FP is messaging DOFFX2 in real time for 16 toys and RGB on my cabinet at present. Today I plan to add fans, strobes and RGB flashing commands. I'll be PM'ing you (and a few others) to test this out shortly. Its taking me more time to modify the FP script than the code the program. Just proves I'm no table author!
Hi DDH69,
first of all, thanks for your DOFFX2!! I have so much fun now while playing PFX2!
My RGB "undercab complex" works fine with it. I have also mapped the left and right flipper buttons to the green and red channels of two RGB flashers, so I have nice color flashes when pressing the flipper buttons - while the RGB stripe goes through the rainbow colors :-)
Now I wanted to activate DOFFX2 when starting "Pro Pinball'". So I uncommented the "PROCESSES" line. It looks like this now:
PROCESSES=Pinball FX2, Pro Pinball
Unfortunately DOFFX2 doesn't start when running Pro Pinball. What have I done wrong? I've also tried with "ProPinball.exe" as task name, but whithout success.
This did it for me --- DOFFX2 set to "run as administrator
http://www.vpforums....e=8#entry354535
Thanks - I've added this to the V3 guide.