11 replies to this topic

[DDH69]

Work is underway on the next main release.  Some stuff is done, other stuff still underway.  I thought in a quiet moment I'd let everyone know some of what will be coming;

 

MAME support

Linking to MAME as a game emulator to accept and process the triggers that MAME already outputs.  There are reported to be about 1600 arcade games that output some sort of trigger.  Many are as simple as the player 1 / 2 indicators once credit is inserted, some a lot more such as knockers, etc.  I've yet to test anything except the arcade emulator, not sure about something like NES, etc as yet.  By telling DOFLinx to monitor your MAME (> v0.107 and only tested with the current v0.212) you can drive actions from these triggers.  So you can have your player buttons flash at the correct time, or you can drive flashers, solenoids and MX effects.  Combining the MAME triggers with current button press, timed (RGB) and other logic, the MAME cabinet is coming alive.

 

The triggers and actions will be driven from *.MAME files.  These are very similar to the FX2 / FX3 logic.  There will be no encryption on these files and fully editable for your setup.

 

 

Colour button support

RGB buttons can now be setup for all LINK_xx buttons.  This means a lot more flexibility for each game, or during game changes.

 

 

Improved analogue plunger for FX3

The analogue plunger will shortly hold on when the plunger is pulled and release when the plunger returns.  At present it reaches a pull and return trigger point them sends a single keystroke.  This will give far better control in FX3 from an analogue plunger.

 

 

No need to run as administrator

With help from mjr, DOFLinx will be able to run against FX2/3 and FP without the need to run as administrator.  This will require you to also not run FX2/3 and FP as administrator.  Of course, if you choose to run things as administrator then everything will continue as it does now.  This is purely for those who wish to get away from this elevated running of all cabinet applications.

 

 

New Buttons

Additional buttons have been added for better MAME support being Player 1/2 and Pause

 

 

Remote logging

To remove the need to have DOFLinx appear on a local screen when monitoring / debugging, if your cabinet is networked DOFLinx can now mirror all messaging via TCP to another computer.  This is very handy as you can set DEBUG=2, have no screen on your cabinet, but still see everything that's going on in real time.

 

 

I am currently building a standup arcade cabinet in parallel with developing the new version.  This means I can test a lot of the logic, but it also slows me down as the build of the cabinet tends to grab my attention.

The new version is likely to be released in about 4 weeks as I've got a couple of busy weekends.  For those in Oz, you'd know that Bathurst weekend is coming up, so nothing but playing happening then!

[captaincroutons]

Hey man, first off thanks for everything you've done for the community! Quick question, as Im having a hard time finding up to date info; is there a current way to use active backglasses with fx3? I know you had gotten it working a while back, but Ive since seen things saying it no longer works. Thanks!

EDIT: is there a build log for your standup cab? Im planning on doing a full size four player turtles themed cab eventually.

Edited by captaincroutons, 28 September 2019 - 11:02 PM.

[DDH69]

Hey man, first off thanks for everything you've done for the community! Quick question, as Im having a hard time finding up to date info; is there a current way to use active backglasses with fx3? I know you had gotten it working a while back, but Ive since seen things saying it no longer works. Thanks!

EDIT: is there a build log for your standup cab? Im planning on doing a full size four player turtles themed cab eventually.

 

Active backglasses have been working with FX3 for a long while now.  The only delay was getting any triggers working with FX3 when it first came out.  So, all is well, setup and play away, everything is good.

 

Yes I do have a build thread, its here.  I should be posting a few more images later today after this weekend's effort.

[captaincroutons]

Is there a guide to setting them up specifically? I tried VPX, and its amazing but I prefer fx3. Ill be patient and see what licensed tables they do.

[Outhere]

Comes with a guide

https://www.vpforums...&showfile=12318

[captaincroutons]

Beautiful thank you! Need to find a way to remote into my pincab pc while Im working my boring overnight security job...

[captaincroutons]

Ok, I read through the guide but I'm still missing something.

I already had nudge working in FX3 with my pinscape board using the other guide, but now I've broken the .ini apparently as I keep getting an error on DOFLinx startup. This is the error message:

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)

   at System.Collections.Generic.List`1.get_Item(Int32 index)

   at DOFLinx.MainForm.Set_Next_RGB_Colour()

   at DOFLinx.MainForm.RGBTimer_Tick(Object sender, EventArgs e)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4010.0 built by: NET48REL1LAST_B

----------------------------------------

DOFLinx

    Assembly Version: 1.0.0.0

    Win32 Version: 5.0.0.0

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 10.0.0.0

    Win32 Version: 14.8.3752.0 built by: NET48REL1

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

----------------------------------------

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

----------------------------------------

DirectOutput

    Assembly Version: 3.1.7011.27968

    Win32 Version: 3.1.7011.27968

----------------------------------------

Extensions

    Assembly Version: 3.1.7011.27968

    Win32 Version: 3.1.7011.27968

----------------------------------------

B2SBackglassServer

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

----------------------------------------

System.Web

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

And this is my .ini file:

 

####

# 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, Pinscape, Ultimate I/O 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=c:\DirectOutput\config\DOFLinx.ini

####

# The config file for DOFLinx to achieve B2S backglasses only with Pinball FX3

# 

# IMPORTANT - when used just for backglasses with FX3 and no output devices with toys, you must add this command line options for DOFLinx, DISABLEDOF=YES

#

 

 

# The location of the .FX3 game specific files included with the DOFLinx release package

# Ensure your path has a \ on the end of it

 

PATH_FX3=C:\DirectOutput\DOFLinx_FX3\

 

# The path to where you keep all of the .directb2s files that you've downloaded for use with FX3

# Ensure your path has a \ on the end of it

 

PATH_FX3_B2S=C:\DirectOutput\DOFLinx_FX3_B2S\

 

# This is the folder where B2SServer.exe can be found on your system

 

PATH_B2S_SERVER=C:\Visual Pinball\Tables\

 

# The list of processes that can activate DOFLinx, in this case, just Pinball FX3

 

PROCESSES=Pinball FX3

 

# An over-ride to the default setting given this is just being used with Pinball FX3, not FX2, FP or other systems that may require the default delay

 

PROCESS_TO_ACTIVE_TIME=1

# If you want to list the processes that will wake up DOFLinx, comment it out if you just want Pinball FX2

#PROCESSES=Pinball FX2,Pinball FX3,Future Pinball,VPinball_9_9_1,VPPhysMod5

 

# If you are using flag files, comment the line below out or set to 2000 as the default.

# If you need to use the Pinball FX2 grid to select games you will want this at around 30000 - I recommend not using the FX2 grid

PROCESS_TO_ACTIVE_TIME=1

JOY_PORT=3

JOY_X_OFFSET=32767

JOY_Y_OFFSET=32767

NUDGE_LEFT_POINT=-4000

NUDGE_RIGHT_POINT=4000

NUDGE_FORWARD_POINT=4000

NUDGE_LEFT_KEY=4C

NUDGE_RIGHT_KEY=52

NUDGE_FORWARD_KEY=46

#NUDGE_LEFT_INPUT=A2

#NUDGE_RIGHT_INPUT=A3

 

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

DEBUG=0

 

My startup shortcut for DOFLinx looks like this:

 

C:\DirectOutput\DOFLinx.exe PATH_INI=C:\DirectOutput\DOFLinx.ini DISABLEDOF=YES

 

Not sure if I have to change something in FX3 also...the b2s backglass shows up, but doesn't animate and that error comes up. Any help would be greatly appreciated!

[DDH69]

DIRECTOUTPUTCONFIG=c:\DirectOutput\config\DOFLinx.ini

This should be pointing to your DirectOutputConfig.INI not the DOFLinx.INI  Fixing this should sort out the ugly death you are seeing.

[captaincroutons]

Of course! I knew it was something stupid simple that I was overlooking. Years of coding in school has done me no good in practical use. Thank you! Will edit tomorrow when Im home from my shift and have slept.

EDIT: This did the trick! I actually couldnt find my config file for DOF, so I got one that you posted in another thread where someone was basically doing what Im doing and just setting up FX3. All is working now. Thank you!

Edited by captaincroutons, 01 October 2019 - 08:52 PM.

[xtrouble]

This is fantastic news. I'm adding mame games to my cab, only a few at the moment to re-live my youth, so this couldn't be better timing for me. Thanks for all that you do here !

[Mike DA Spike]

Will there be led strip support to for mame ?
I'm just into mame (have led strips and led display on my pinball cab), and would maybe cool to have a led display to work. Maybe mame name displayed and insert coun messages or something. Just some basic things

[DDH69]

Will there be led strip support to for mame ?

 

Yes.  The trick will be picking a suitable trigger.  I'm sure we can all have a fun journey building on this!