15 replies to this topic

[DDH69]

Update available here.

 

- Fix bug where RANDOM as a colour was not working correctly for FL_FD and FL_FL based flasher commands from FP script

- Include missing command instructions for KEY_TO_COLOUR_TIMER and KEY_TO_OUTPUT_TIMER in the guide

- Fix fading for LED button abd flashers from FP table link with low fade times

 

Still can't believe that I wrote commands and forgot to add them to the guide since about V1.somethng!  Anyway, each update is an improvement to the code and the documentation .... progress.

 

[TerryRed]

 

Update available here.

 

- Fix bug where RANDOM as a colour was not working correctly for FL_FD and FL_FL based flasher commands from FP script

- Include missing command instructions for KEY_TO_COLOUR_TIMER and KEY_TO_OUTPUT_TIMER in the guide

- Fix fading for LED button abd flashers from FP table link with low fade times

 

Still can't believe that I wrote commands and forgot to add them to the guide since about V1.somethng!  Anyway, each update is an improvement to the code and the documentation .... progress.

 

 

 

I didn't even think about those commands missing from the guide....  I've been going back to old e-mails for reference.  

 

 

Link doesn't show the download....just like MOTU...some weird stuff happening with the forums...

Edited by TerryRed, 27 September 2016 - 11:46 AM.

[DDH69]

I would expect DOFLinx to get released (like any other upload) within 24 hours.

 

So MOTU is still not available?  (I can see it as the person who uploaded it)  Sorry I forgot about this one.  I'll post into the site issues forum and ask for release to occur.

[Malenko]

For some reason I dont have permission to download the file ?

[TerryRed]

It's the same problem I was mentioning... I think the site owner has to verify the file before we can download it.

[Outhere]

What a great little program

Edited by Outhere, 04 October 2016 - 04:28 PM.

[dani3l]

Hi there,
 
I hope I am on the corret place and you can help me with DOFLinx.
 
I am stucked ride on the beginning when opening DOFLINX.
I get a error message like: could not load type "DirectOutput.Cab.CabinetOwner" from assembly.
 
I command out the Doflinx.ini peace by peace but its seems that there is no influence from the ini file in this error message.
 
what elese can I do?
 
regards
Daniel
 
(I run as admin)

Edited by dani3l, 07 October 2016 - 02:49 PM.

[Outhere]

Do you have (DOF) R3 Beta installed and working

http://www.vpforums....showtopic=33080

[DDH69]

Excellent pick up Outhere, almost certainly DOF R2 not R3.  I've just enhanced the logging message a little more for this error in V4 when it comes out.

[dani3l]

Hello there,

 

thanks for your answer.

 

I belive to remember that I have installed DOF R2 at first and then copy DOF R3 over it. Like it was recommended in the installtion tutorial on this side.

 

But I will double check!

 

regards

Daniel

 

--- EDIT 07/10/2016 ---

 

Hi there,

 

its works now very fine. The hint to install R3 beta was correct!

 

Thanky ou very much!

Edited by dani3l, 09 October 2016 - 12:21 PM.

[Outhere]

Is Your Dof working in visual pinball?

If not did you check this?

Did you re-Register it?

you might need to unblock the files of the Dof framework

Please exceute the following procedure for all dll and exe files of the DirectOutput installtion:

• Right click the dll and exe files and select Properties in the context menu.
• Select the General tab in the properties window.
• If you find the text _"This file came from another computer and might be blocked to help protect this computer" or somthing similar on this tab, click the Unblock button. This should fix the issue.

[Outhere]

If I use this in a future pinball game  FF_Colour "Random",RGB_TT,.5   and set my outputs in the "RGB output" and if I use the same outputs for these settings the RGB lights will not work

LINK_FLOL=126,120
LINK_FLIL=124
LINK_FLCN=120
LINK_FLOR=121
LINK_FLIR=123,117

is that normal?

 

####
# The config file for DOFLinx
# 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, KL25Z and Sainsmart (FTDI devices)
# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.
#
# 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.  Keep this as the first item in the file
DIRECTOUTPUTCONFIG=e:\DirectOutput\config\directoutputconfig.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=204
R_FLIPPER_OUTPUT=208
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=27
R_FLIPPER_KEY=25
# 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=2000
# 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=117,120,123,126
# 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=Random
#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 DOFLinx starts, ie the exit button LED
BUTTONS_ON=101
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=25 122 27 127
# 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 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

####
# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.
####
FP_ATTEMPT_LINK=1
LINK_LF=208,150,2000
#LINK_LF=120,50,1000
LINK_RF=204,150,2000
#LINK_RF=127,50,1000
LINK_LS=208,50,500
LINK_RS=204,50,500
LINK_ML=208,50,500
LINK_MC=204,50,500
LINK_MR=204,50,500
LINK_BL=208,50,500
@LINK_BC=204,50,500
LINK_BR=204,50,500
#LINK_SH=122,200,5000
#LINK_GR=126,150,1000
#LINK_KN=124,120,500
LINK_ST=102
#LINK_EX=
#LINK_CN=105
#LINK_EB=
LINK_LB=101
LINK_SR=103
#LINK_FR=
LINK_FLOL=126,120
LINK_FLIL=124
LINK_FLCN=120
LINK_FLOR=121
LINK_FLIR=123,117


####
# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=

 

 

-

08-Oct-16 23:06:43 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
08-Oct-16 23:06:43 - Starting up - version 3.05
08-Oct-16 23:06:43 - 1 LEDWiz device(s) found
08-Oct-16 23:06:43 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
08-Oct-16 23:06:43 - DOFLinx device:1 LEDWiz setup with 32 outputs
08-Oct-16 23:06:44 - 1 FTDI (Sainsmart) device(s) found
08-Oct-16 23:06:44 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
08-Oct-16 23:06:44 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
08-Oct-16 23:06:44 - Reading DOFLinx.INI startup config file details
08-Oct-16 23:06:44 - Reading DOF config file
08-Oct-16 23:06:47 - Activated by process name : Future Pinball
08-Oct-16 23:06:47 - Game name = ''
08-Oct-16 23:06:47 - Named process detected and startup commenced
08-Oct-16 23:06:47 - 1 LEDWiz device(s) found
08-Oct-16 23:06:47 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
08-Oct-16 23:06:47 - DOFLinx device:1 LEDWiz setup with 32 outputs
08-Oct-16 23:06:47 - 1 FTDI (Sainsmart) device(s) found
08-Oct-16 23:06:47 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
08-Oct-16 23:06:47 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
08-Oct-16 23:06:47 - Process has administration rights
08-Oct-16 23:06:47 - 64 bit OS detected
08-Oct-16 23:06:47 - FP full name=E:\Games\Future Pinball\Future Pinball.exe Size=28548096 bytes, Dated 3/13/2014 12:23:52 AM
08-Oct-16 23:06:47 - 12E=35 12F=1
08-Oct-16 23:06:47 - The FP executable being run appears to have its >2gb memory flag modified, you may experience issues
08-Oct-16 23:06:48 - Setting VQE return code to zero
08-Oct-16 23:06:49 - Setting VQE return code to zero
08-Oct-16 23:06:51 - Setting VQE return code to zero
08-Oct-16 23:06:52 - Setting VQE return code to zero
08-Oct-16 23:06:53 - Setting VQE return code to zero
08-Oct-16 23:06:55 - Setting VQE return code to zero
08-Oct-16 23:06:56 - Setting VQE return code to zero
08-Oct-16 23:06:57 - FP table running DOFLInx code found and link established
08-Oct-16 23:06:57 - Using full colour palette
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=26
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=20
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=23
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=17
08-Oct-16 23:07:03 - FP Link is turning on device #1 for 2000 milliseconds
08-Oct-16 23:07:03 - FP Link is turning off device #1
08-Oct-16 23:07:08 - Setting colour index #64 with action code=2 on-time is 70
08-Oct-16 23:07:09 - Setting colour index #70 with action code=2 on-time is 70
08-Oct-16 23:07:10 - FP Link is turning on device #4 for 50 milliseconds
08-Oct-16 23:07:10 - FP Link is turning off device #4
08-Oct-16 23:07:10 - FP Link is turning on device #3 for 50 milliseconds
08-Oct-16 23:07:10 - FP Link is turning off device #3
08-Oct-16 23:07:11 - FP Link is turning off device #1
08-Oct-16 23:07:11 - Invalid colour sent via message
08-Oct-16 23:07:12 - FP Link is turning off device #1
08-Oct-16 23:07:12 - FP Link is turning off device #2
08-Oct-16 23:07:12 - FP Link is turning off device #3
08-Oct-16 23:07:12 - FP Link is turning off device #4
08-Oct-16 23:07:12 - FP Link is turning off device #5
08-Oct-16 23:07:12 - FP Link is turning off device #6
08-Oct-16 23:07:12 - FP Link is turning off device #7
08-Oct-16 23:07:12 - FP Link is turning off device #8
08-Oct-16 23:07:12 - FP Link is turning off device #10
08-Oct-16 23:07:12 - FP Link is turning off device #11
08-Oct-16 23:07:17 - Shutting down
08-Oct-16 23:07:17 - Program close
 

 

Edited by Outhere, 09 October 2016 - 04:40 AM.

[DDH69]

BTW - good practice to start a new thread with a new issue 

 

With RGB_OUTPUT and LINK_FLOL both assigned to the same RGB device (126) the results will be that the last command for either that sets the colour, this may make it seem like its not working.  Best to assign one device to one task.

 

More importantly, whats the 0.5 time?  Who said you could use fractions!     (ha - always wanted to use that one!)   Values are 1 - 99999.  By the way 0.5 would be 5 milliseconds - good luck seeing that with the naked eye!  Can I suggest start with 50 (half a second) , ensure it works, then adjust.

 

Please don't take my tone the wrong way - just my sense of humour coming through.  I love the fact that you're coding DOFLinx into FP tables.

[Outhere]

LOL
It was set for 7 and it lasted for 7 seconds so I figured .5 would be a half a second

when the lights come on it seems to last a half-second because it's very easy to see lights

  Thank for the reply

[DDH69]

Actually I forgot that if you have RGB_OUTPUT and the same port defined as a flasher it automatically removes it anyway .... 

08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=26
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=20
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=23
08-Oct-16 23:06:58 - Removing flasher from RGB list, device=1 port=17

This message is a concern ...

08-Oct-16 23:07:11 - Invalid colour sent via message

[Outhere]

Yes I have to look into that to see what's causing it,  I must have something so stupid