20 replies to this topic

[dramaone]

I've an earlier version of Doflinx installed which is running cool, with FX2, Future pinball etc

 

I've now downloaded FX3  since the new williams tables came out ( could not resist ) and are all working with

basic fb such as flipper solenoids, rgb

 

I know that all these new tables have not been scripted yet,however in readiness I want to update my Doflinx version.

 

Is there anything I need to consider before doing so, I don't want to do it and overwrite or mess up my previous config working with FX2.

I use an offline verison of FX2 that I cant and don't want to upgrade and am worried that a new doflinx version might mess this up.

 

Thoughts?

 

[DDH69]

If in doubt save your DOFLinx.exe and DOFLinx.ini files before you change anything, that way you can always go back. Even safer is to take a copy of the entire path that DOFLinx is in as that usually contains DOF as well.

A couple of things to consider ...
1. There is no update working with the Williams release as yet (I'm still lost in France)
2. The need for DOF R3++ may have come since the DOFLinx version you are using - check the DOFLinx update notes from your version to the current, it will be very clear when this requirement came into effect.
3. If you are using a really old DOFLinx version some INI file parameters have changed. If it has become unsupported or had new arguments added you should get a message of some sorts.

If you're looking to go straight to Williams supported DOFLinx perhaps wait jjntil its done then change once. Having said that, there is no issue with moving now and addressing any issues, FX2 wkll still work.

[dramaone]

thanks man, im running v5. updated with new files and get a microsoft net error could not load file or assembly ext v3.1.6

 

is that because i need dof r3++ ( sorry just seen thread below, i'll update to r3++ )

 

cheers

Edited by dramaone, 18 October 2018 - 06:29 AM.

[DDH69]

The .net error is 99% likely to be the need for R3++. If that doesn't fix it, post the error.

[Soolman]

Keep in mind that the newest version of pinballfx 3 will not yet work with 6.5. Because they released a new version somewhere this week, the version check fails so no table will work for now .

[dramaone]

Tried to update and still get .net framework error.  It was working briefly because I tried fishtales but then it crashed.

After that I get some lights on start of the game and then it crashes with the framework error.

 

I kept my old install folder and reverted back to that and all works fine.

 

 

 

 

 

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 DirectOutput.General.Generic.ExtList`1.get_Item(Int32 Index)
   at DOFLinx.MainForm.ProcFFButton(Int32 TheDev, Byte TheAct, Int32 TheIter, Int32 TheTime)
   at DOFLinx.MainForm.FPLinkTimer_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.6.1055.0 built by: NETFXREL2

----------------------------------------
DOFLinx
    Assembly Version: 1.0.0.0
    Win32 Version: 5.0.0.0

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.6.1055.0 built by: NETFXREL2

----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
DirectOutput
    Assembly Version: 3.1.6863.36690
    Win32 Version: 3.1.6863.36690

----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

----------------------------------------
Extensions
    Assembly Version: 3.1.6820.28072
    Win32 Version: 3.1.6863.36690

----------------------------------------
B2SBackglassServer
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0

----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1055.0 built by: NETFXREL2

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

************** 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.
 

Edited by dramaone, 12 November 2018 - 08:33 PM.

[DDH69]

This error is not the DOF framework.  A few questions for you ....

 

1. What FP game are you playing when this happens?

2. Does it happen with all FP games?

3. Any chance you can turn DEBUG=1 and reproduce then send a DOFLinx.LOG and your DOFLinx.INI ?

[dramaone]

It happens on all games ( ive tested ), fx games I get flasher lights lit and then it crashes on ball launch or flipper press ( cant recall ). FP games have no fb so I assume its crashing on launch.

 

Initially all was working, fx3 Williams had all fb but then crashed. At that time strangely even Pinballx was triggering flipper solenoids as I scrolled through the games.

 

I'll drop debug on.

 

As said reverted back to older doflinx setup and all is good.

[DDH69]

and your INI too

[dramaone]

Will do, I used my INI from older version though. 

 

When I looked at the new example INI's included I was a bit confused as they only detailed to look at directconfig.ini rather than directconfig20 and directconfig40 ( which I obviously download from the config tool, 20.ini for pacled64 and 40,ini for sainsmart.

Why do the example ini's only detail this? 

[DDH69]

The DIrectOutputConfigXX.ini has XX being different numbers dependant on the output device you have.  DOFLinx just gets the colours from the DirectOutputConfigXX.ini file.  This means you can point to any valid one you have.  Only point to one of them, do not add two lines and try to point to both.

[dramaone]

The DIrectOutputConfigXX.ini has XX being different numbers dependant on the output device you have.  DOFLinx just gets the colours from the DirectOutputConfigXX.ini file.  This means you can point to any valid one you have.  Only point to one of them, do not add two lines and try to point to both.

 Ok good that's what I thought but got confused and thought that with new updates something had changed as the sample.ini's don't detail XX or somebody's 20 or 40 etc.

I always point a one file so all is good.

I am going to try from fresh again tonight and if no luck I'll return with a log and ini.

 

Thanks for the timely help as usual. 

[dramaone]

Ok clean start and I followed this guide

 

http://mjrnet.org/pi...allInstructions

 

which helped me keep on track, no more error messages and all is well apart from when I exit Pinballfx2 or 3 games from PinballX is does not seem to stop DOFlinx

as flippers are still firing solenoids when scrolling through/selecting games.

Future pinball games exit and kills the feedback.

 

It doesn't stop selecting new games but just annoying solenoids firing on Pinballx game browsing.

 

I'm guessing you will still want a debug log of this ?

[DDH69]

Correct - DEBUG.LOG and current INI

 

Is it DOFLinx firing the solenoids or do you have a PinballX plugin loaded ?

Edited by DDH69, 14 November 2018 - 12:12 AM.

[dramaone]

I've never used the pinballx plugin.

With the solenoids only periodically firing on Pinballx as they only fire after exiting pinballfx2&3 exiting rather than FB I thought it was DOFlinx remaining on.

When I had a few issues I did tinker with a few bits in my spray and prey approach to problem solving so I'll check to see if I have the plugin activated.

 

Thanks

[DDH69]

I'm sure we can sort it out.  Sounds like you may have the PROCESSES= parameter or similar a bit off.

 

Back to the DEBUG.LOG and INI files.

[dramaone]

I disabled pinballx plugin and all is good. Setup is fully updated and working so thankyou for pointing me in that direction.

 

I built a mini pinball a year or so back, sold it and now have built a full sized one.

I'm now onto installing active backglasses which I never bothered with and then I'm tempted to venture into addressable Led's.

 

three questions;

 

1. I've only ever bothered with Pinballfx2/3 and FB and although I have VP installed have never got into that. I want to do more with that too but don't totally understand what its relationship with DOFlinx is.

I've obviously used the DOF config tool, so does VP use DOF and doesn't need DOFlinx?

 

 

2. When I open Fx3 scripts in notepad they are in code, but when I open FX2 scripts they read ok?

I've a solenoid that hits a bell and would love to link that to for eg the Jaws table

 

3. Active backglasses on FX3 williams show speaker and dmd grill how do I get rid of that? In active backglass menu I thought I'm I set it as disabled.

 

Thanks

Edited by dramaone, 14 November 2018 - 07:58 PM.

[DDH69]

1. Yes, VP uses DOF and does not require DOFLinx.  There are some very specific scenarios (ie old non DOF'ed tables in v9) that can have flipper solenoid functionality added for VP via DOFLinx, but generally not.

2. Correct FX3 files have encoded lines and unencoded headers.  You can add unencoded lines to the base of an FX3 file the same way as an FX2 file.

3. Turning off the grill for the Williams FX3 backglasses is a setting in the B2SServer.  From memory right click on the backglass and set the option to hide the grill.

[dramaone]

3. Turning off the grill for the Williams FX3 backglasses is a setting in the B2SServer.  From memory right click on the backglass and set the option to hide the grill.

Yeah I have to set to off, did it via a VP game because I couldn't access the backglass with a cursor in FX3.It has its in-game cursor which wont move off the playfield.

Does it have to be game specific or should the setting be universal for all games?

I don't have too many fx3 games but ET and JAWS are fine but the Williams collection all show grill and dmd but work fine other than that.

[DDH69]

The three FX3 Williams directb2s are the only ones in the FX3 series with grills.  The reason for this is that I've used the already existing great Williams backglass setup and artwork on this site as the basis, as such, you will not see the issue with any others like ET or Jaws.

 

Its definitely a B2S settings.  I seem to remember that B2SBackglassServer has a default and per table settings possible.  My suggestions:

 

1. Check your B2STableSettings.xml file.  if you've got an an entry for the Williams tables in question, check that <HideGrill> is 1

2. Because of FX3's capture of focus it is near impossible to right click during a game.  You can run DOFLinx with DEBUG=1, right click, and open the backglass in test mode.  At this point you can easily right click and hide the grill for each of the three backglasses (one at a time).