28 replies to this topic

[DDH69]

Once released available here.

 

A number of fixes for V6 as discussed here.  (plus a couple of more FX3 files)

 

MOST IMPORTANT - REPLACE ALL OF YOUR FX3 FILES WITH THE NEW ONES

 

The release notes are:

 

V6.01 23/12/17

- Drop the default test time on from 1000 to 100mS to stop solenoids being on too long by accident

- Removed the FX2 files from the distribution package, contact me direct if you need them

- Fix crash when B2S path was not set and no C:\VP\ path exists

- Fixed spelling of SonofZeus in the GAME_COLOUR= of the sample DOFLinx.INI - If you copied this, either manually fix it or recopy

- Rebuilt the TestB2S function

- Fixed a couple of instances where the FX2 B2S path was being used when it should have been the FX3 B2S path

- Added FX3 files for Wolverine and World War Hulk

 

[Tyson171]

Thanks for the update!

 

I noticed that the nudge flashers have changed how they were previously, now the two LEDS  fire on the right or left of your cab, but mine are firing opposite of each other.

 

So if I hit the right nudge, the lights on the left side of the cabinet go off, and vice versa.

 

It used to be three lights  (light 1, 3, and 5). 

 

Is there a way to set it back to the old way, or make the flashers fire on the proper side of the cabinet?

 

I tried pinball FX2, and that functions normally.

 

Thanks again for all the hard work!

[DDH69]

Thanks for the update!

 

I noticed that the nudge flashers have changed how they were previously, now the two LEDS  fire on the right or left of your cab, but mine are firing opposite of each other.

 

So if I hit the right nudge, the lights on the left side of the cabinet go off, and vice versa.

 

It used to be three lights  (light 1, 3, and 5). 

 

Is there a way to set it back to the old way, or make the flashers fire on the proper side of the cabinet?

 

I tried pinball FX2, and that functions normally.

 

Thanks again for all the hard work!

 

First thing, never dismiss the fact that I might have screwed up     Second thing, anything is possible.

 

I have setup 3 nudges in FX3, left, right and forward.  All three use an MX setup on the PF Back Effects MX device as setup in your favourite config tool.  You said "two LEDs" fire on the side of your cabinet, what sort of MX setup do you have?  The effect actually washes blocks across on an MX array.

 

The effects I am using are:

 

Left Nudge = Shift from Right to Left on Back MX

Right Nudge = Shift from Left to Right on Back MX

Forward Nudge = Shift Bottom To Top Back MX

[Tyson171]

I'm not actually using forward nudge, just left and right nudge (my key mappings don't really work out that great to have all three, so I just use my magna save buttons for left and right nudge). My cab is using analog nudge for visual pinball, never really designed it for FX2.

 

Anyways, I have something like this directly above my play field - http://shop.zebsboar...bar-640x480.png

 

So when I hit my right hand nudge, the two RGB Lights on the left go off, and vice versa.

 

Maybe I have my nudge mapped backwards, I didn't really think of that, I'll have to test it.

[DDH69]

OK, it looks like we're talking about flashers, not addressable LEDs - sorry I misunderstood.

 

In that case forget the above about MX patterns, lets talk flashers.  Left nudge lights up OL (outside left) and IL (inside left) red,  similarly right nudge lights up IR an OR, and for completeness (even though you're not using it) forward nudge lights up CN (centre).

 

It would be worth you checking what ports you've got assigned to LINK_FLOL, LINK_FLIL, LINK_FLIR, and LINK_OR.  You can test these from DOFLinx using the right click "Test RGB / Flasher" function.  Just identify what you've got setup in your INI then test those ports and you'll know if you've go the port assignments correct.

[Tyson171]

So i'm using the same .ini for both FX2 and FX3 tables.  It behaves different from FX2 to FX3 (I prefer the FX2 response I was getting).  Any thoughts? (IN FX2, 1,3,5 lite up regardless of what nudge function I used)

 

This actually just started in the 6.01 update today, 6.0 was fine.

 

I did play with the mapping of the nudge, it didn't matter at all.

 

I can create and upload a video to you-tube if you would like to see the behavior.

[DDH69]

The behaviour is certainly intended to be more advanced with FX3 over FX2.  In FX2 DOFLinx just recognised nudge, not which one.  When nudge was recognised in FX2, yes it lit up CN, OL and OR.  Now that the actual nudge can be recognised there are more specific effects.

 

Having said all of that, nothing says I've got it right.  I'll check when I fire my cabinet back up.

[TerryRed]

Just would like to say that DOF Config Tool now has the FX3 configs up...and I tried out FX3 on my cabinet.  DOF and MX Leds on the new tables look excellent DDH69. I really like these new original tables from Zen...especially Son of Zeus. They seemed to get everything just right on the table...music...visuals.. fun.

 

As far as the nudge effects for MX leds... they are firing...when I push nudge from my right side...I get a red effect from left to right as an example.

 

I also have an ongoing problem with FX3, in that it sometimes just won't close out properly for whatever reason and will just either freeze...or not completely return to PBX.

 

That said, the DOFLinx FX3 update came just in time for the holidays...nicely done!

[DDH69]

Thanks TerryRed.

 

Presents are always good.  Its our Summer Christmas in Oz (29oC today).  At 11:30 on Christmas day I've opened presents with my wife and (adult) children over fruit and champagne.  Now its my time for a while to work on pinball configs.  The good news ..... more presents over the Christmas -> New Year break while I'm on leave.  So far 6 new FX3 configs, some updated back glasses, 2 new MX setups and some more effects for FX3 across all tables.  I can feel it being a busy January!

 

So I've finished writing setups for the day, might go and test a few (OK play).  I did the FX3 setup for Might of the First Order this morning - I just want those 6 bumpers going again!

 

Have a good pinball holiday season 

[Jodannar]

Thanks DDH. Using my christmas afternoon to install DOFLinx for the first time and see how great it can be.

Thanks for all the work.

[rablack97]

upgraded to 6.01, any reason why my backglasses for would try to shop up on playfield and not the backglass?

[DDH69]

upgraded to 6.01, any reason why my backglasses for would try to shop up on playfield and not the backglass?

 

Not quite sure what you mean.

 

 

With regard to the left / right nudge question .... 

 

OK, checked today.  The Let nudge button is triggering the left nudge actions and they appear correct.

 

Perhaps run your setup with DEBUG on and check that when you press your left nudge key that the left nudge command triggers and which flasher comes on.  Happy to look at a DOFLinx.LOG if that would help you.

Edited by DDH69, 26 December 2017 - 10:08 AM.

[rablack97]

when using the b2s backglass for doflinx pbfx3 the backglass is showing up on the playfield and not on the backglass screen and crashes the game and i have to exit out.

 

When i remove the path to b2s in the ini, table loads fine just with no backglass.  This only happens when using the b2s backglass files for pbfx3.

[DDH69]

when using the b2s backglass for doflinx pbfx3 the backglass is showing up on the playfield and not on the backglass screen and crashes the game and i have to exit out.

 

When i remove the path to b2s in the ini, table loads fine just with no backglass.  This only happens when using the b2s backglass files for pbfx3.

 

Do you use B2S through VPX ?  DOFLinx just calls B2S it does not position it.  Where is your Screenres.txt file located?  Is it the same folders as B2SServer.EXE?  DO you have only one ScreenRes.txt on your machine?

 

It would be worth reading some of the back glass positioning threads on this site for further clues.

[rablack97]

b2s works fine for VPX, its positioned where it should be, only the b2s for fx3 are showing up on my playfield

 

yep same folder as b2s server, only one bs2 file on my system.

 

screenres.txt is setup correctly, when adding the b2s path back into the ini, the gamse crashes still, the dmd shows up on the playfied then it just crashes, i changed the screen number in the .txt file, the backglass did show on 3rd screen but the game still crashes.

 

26-Dec-17 21:18:13.470 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

26-Dec-17 21:18:13.501 - Starting up - version 6.01

26-Dec-17 21:18:13.533 - 0 Pinscape device(s) found

26-Dec-17 21:18:13.548 - 1 LEDWiz device(s) found

26-Dec-17 21:18:13.564 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0

26-Dec-17 21:18:13.580 - DOFLinx device:1 LEDWiz setup with 32 outputs

26-Dec-17 21:18:13.580 - 0 FTDI (Sainsmart) device(s) found

26-Dec-17 21:18:13.595 - Reading DOFLinx.INI startup config file details

26-Dec-17 21:18:13.611 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini

26-Dec-17 21:27:16.417 - Game name = ''

26-Dec-17 21:28:47.568 - Game name = ''

26-Dec-17 21:30:15.537 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

26-Dec-17 21:30:15.552 - Starting up - version 6.01

26-Dec-17 21:30:15.584 - 0 Pinscape device(s) found

26-Dec-17 21:30:15.602 - 1 LEDWiz device(s) found

26-Dec-17 21:30:15.606 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0

26-Dec-17 21:30:15.606 - DOFLinx device:1 LEDWiz setup with 32 outputs

26-Dec-17 21:30:15.622 - 0 FTDI (Sainsmart) device(s) found

26-Dec-17 21:30:15.622 - Reading DOFLinx.INI startup config file details

26-Dec-17 21:30:15.637 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini

26-Dec-17 21:30:53.718 - Game name = ''

26-Dec-17 21:31:40.824 - Game name = ''

Edited by rablack97, 27 December 2017 - 03:36 AM.

[DDH69]

 

b2s works fine for VPX, its positioned where it should be, only the b2s for fx3 are showing up on my playfield

 

yep same folder as b2s server, only one bs2 file on my system.

 

screenres.txt is setup correctly, when adding the b2s path back into the ini, the gamse crashes still, the dmd shows up on the playfied then it just crashes, i changed the screen number in the .txt file, the backglass did show on 3rd screen but the game still crashes.

 

 

I still don't have an answer for you. I do have more questions to help get you an answer.

1. You missed a question   - Do you only have one Screenres.txt file on your system?  (use search in Windows Exploroer, or at a command prompt type DIR \Screenres.exe /S then see if you only have one
2. Did you ever use B2S with FX2?  If so was it OK?
3. Can you please provide the crash message.
4. Do you have a \ on the end of your PATH_B2S_SERVER=  ?
5. You said "the dmd shows up on the playfied then it just crashes", do you mean dmd or B2S ?
6. Thanks for providing a copy of your DOFLinx.log, to get enough details to really help your need to temporarily set DEBUG=1 in your DOFLinx.INI file then reproduce the problem.

[rablack97]

Thank you for looking into this DDH96.

 

1.  Found a duplicate, had same values, removed it, game still crashes

2.  Nope never used FX2

3.  No message - photo of the freeze below

4.  Yes

5.  DMD show on top on the B2S on the playfield, example in photo

6.  In the spoiler

 

Spoiler

27-Dec-17 10:14:04.759 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
27-Dec-17 10:14:04.759 - Starting up - version 6.01
27-Dec-17 10:14:04.790 - 0 Pinscape device(s) found
27-Dec-17 10:14:04.790 - 1 LEDWiz device(s) found
27-Dec-17 10:14:04.812 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
27-Dec-17 10:14:04.828 - DOFLinx device:1 LEDWiz setup with 32 outputs
27-Dec-17 10:14:04.828 - 0 FTDI (Sainsmart) device(s) found
27-Dec-17 10:14:04.828 - Reading DOFLinx.INI startup config file details
27-Dec-17 10:14:04.843 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
27-Dec-17 10:14:06.707 - Found Teensy controller named 'TeensyStripController'
27-Dec-17 10:14:08.757 - 0 Pinscape device(s) found
27-Dec-17 10:14:08.772 - 1 LEDWiz device(s) found
27-Dec-17 10:14:08.804 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
27-Dec-17 10:14:08.804 - DOFLinx device:1 LEDWiz setup with 32 outputs
27-Dec-17 10:14:08.825 - 0 FTDI (Sainsmart) device(s) found
27-Dec-17 10:14:35.916 - Found valid process name of 'Pinball FX3'
27-Dec-17 10:14:35.932 - Setting FX3 process ID to :5376
27-Dec-17 10:14:37.943 - Activated by process name : 'Pinball FX3'
27-Dec-17 10:14:37.968 - Game name = ''
27-Dec-17 10:14:37.986 - Named process detected and startup commenced
27-Dec-17 10:14:38.000 - Process has administration rights
27-Dec-17 10:14:38.528 - FX3 EXE name=C:\Program Files (x86)\Steam\steamapps\common\Pinball FX3\Pinball FX3.exe Size=16109712 bytes, Dated 12/21/2017 9:03:44 PM
27-Dec-17 10:14:38.537 - Applying memory offsets for FX3 version circa 13/12/17
27-Dec-17 10:14:38.545 - FX3 full link active
27-Dec-17 10:14:38.554 - Using full colour palette
27-Dec-17 10:14:38.563 - Removing flasher from RGB list, device=1 port=17
27-Dec-17 10:14:38.571 - Removing flasher from RGB list, device=1 port=20
27-Dec-17 10:14:38.588 - Removing flasher from RGB list, device=1 port=23
27-Dec-17 10:14:38.596 - Removing flasher from RGB list, device=1 port=26
27-Dec-17 10:14:38.604 - Removing flasher from RGB list, device=1 port=29
27-Dec-17 10:14:44.550 - Loading FX3 configuration file c:\DirectOutput\FX3\SonOfZeus.FX3
27-Dec-17 10:14:46.380 - B2S Backglass loaded - SonOfZeus
27-Dec-17 10:14:46.435 - There are no OFF actions for GAMEMODE
27-Dec-17 10:14:47.935 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
27-Dec-17 10:14:47.948 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,100,PERU'
27-Dec-17 10:14:47.962 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,100,PERU'
27-Dec-17 10:14:47.971 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,100,PERU'
27-Dec-17 10:14:47.983 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,100,PERU'
27-Dec-17 10:14:47.993 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,100,PERU'
27-Dec-17 10:14:48.003 - GAMEMODE mode=1 action #6 of 'FF_DOF,E424,-1'
27-Dec-17 10:14:48.016 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
27-Dec-17 10:14:48.028 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
27-Dec-17 10:14:55.837 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
27-Dec-17 10:14:55.850 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
27-Dec-17 10:14:56.269 - There are no OFF actions for GAMEMODE
27-Dec-17 10:14:56.418 - Activating process disappeared so stopping things
27-Dec-17 10:14:56.492 - 0 Pinscape device(s) found
27-Dec-17 10:14:56.524 - 1 LEDWiz device(s) found
27-Dec-17 10:14:56.544 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
27-Dec-17 10:14:56.557 - DOFLinx device:1 LEDWiz setup with 32 outputs
27-Dec-17 10:14:56.569 - 0 FTDI (Sainsmart) device(s) found

 

Edited by rablack97, 27 December 2017 - 04:21 PM.

[DDH69]

OK then, lets determine if FX3 has a part to play in this.  We'll do that by testing DOFLinx running the B2S without FX3 running.

 

So from Windows, with FX3 not running;

• Start DOFLinx with DEBUG=1 so that you can see it on the screen
• Right click on the DOFLinx window to show the popup menu
• Select Test B2S
• B2S File name = SonOfZeus
• Command = B2SStartAnimation
• Parameters = TITLE    (case sensitive)

Does the B2S come up?  If so where?

[rablack97]

Yep, playfield

[senseless]

Thanks DDH69 for yet another great release! FX3 was just idling out on my pincab, waiting for a top notch release like this . Will be playing fx3 with DOF thanks to you!