@DDH69;
Thanks again! I greatly appreciate the info you provided and for sharing your work with us.
I get the feeling that FX sends a notice to DOFLinx when the nudge button is pressed, but DOFLinx just uses the direct keypress to detect FX3 nudge button presses.
(I deliberately had not configured my buttons in doflink.ini, yet DOFLinx detects nudges for FX, but not for FX3.)
I'm not specifically interested in nudge feedback. I'm just getting a feel for how things work and that provided an easy way to test DOFLink's operation.
- Mark
Essentially yes. In more detail;
PinballFX
DOFLinx receives all events from PinballFX via a DLL that I wrote and Zen kindly integrated with. So real time interprocess event handling. Freezy provided moral and technical support. These events essentially the game ID selected, flipper, nudge, in play, in lane at menu, and dependent on the table a bunch of other events. We're all still working out some of the table events.
DOFLinx sends key strokes for nudge, and at present unsuccessfully, plunger.
PinballFX3
DOFLinx monitors the memory of the running process for changes and generates its own triggers for this for table events and flipper.
DOFLinx sends key strokes for nudge, and plunger (for some as yet unknown reason, plunger has stopped working.
Nudge and plunger are slight exceptions to the logic.
So the logic of FX3 is that no nudge event is received, DOFLinx only knows that its sending a key stroke to initiate nudge. As such, DOFLinx runs its nudge actions knowing, that all working well, a nudge will occur. If this was done with PinballFX then you'd get the nudge action trigger twice, once on sending the nudge keystroke and the second because a nude event is received, hence for PinballFX its send key, wait for event, run action. For FX3 its send key, run action.