53 replies to this topic

[Outhere]

The download link takes you to 7.04

Edited by Outhere, 14 March 2020 - 11:40 PM.

[DDH69]

The link in post #1 leads to DOFLinx 7.04....

 

I uploaded V7.11 yesterday and deleted the broken V7.10.  For some reason the upload V7.11 isn't there, it all looked good, but ultimately its usually the human that stuffed it up (me).  Anyway, we're just checking out the fix for FP as well, so might wait until then rather than confuse things more.

 

Thanks for pointing it out, and thanks for the patience.

[DDH69]

OK, just uploaded the 7.12 package which will be available once OK'ed by admin.

 

This should resolve all the issues from V7.10.  Thanks everyone for your patience.

[fR33Styler]

Thx for fixing the Link (with 7.12).

 

Maybe there´s a little bug.. now (with 7.12) i have an LED animation on the right Playfield Leds which stays the most time (and was not there before).... kind of rainbow like.

 

Looks like this:

 

Best regards

[Outhere]

Thx for fixing the Link (with 7.12).

 

Maybe there´s a little bug.. now (with 7.12) i have an LED animation on the right Playfield Leds which stays the most time (and was not there before).... kind of rainbow like.

 

Looks like this:

 

Best regards

What emulator and what game?

If FP do you have a link to the game?
 

[newtopinball78]

I don't know if its an issue with my FP install but with 7.12 tested with Terry Red MOTU doflnx table and randomly lights are delayed or staying on as prev poster when launching ball. I also noticed sometimes doflinx not initiating when launching future pinball tables pbfx3 seems fine. Randomly get windows jit error when running doflinx

[DDH69]

I don't know if its an issue with my FP install but with 7.12 tested with Terry Red MOTU doflnx table and randomly lights are delayed or staying on as prev poster when launching ball. I also noticed sometimes doflinx not initiating when launching future pinball tables pbfx3 seems fine. Randomly get windows jit error when running doflinx

 

What version are you upgrading from?  Around 7.04 there was the need for a new DOFLinx.vbs in the FP\scripts folder.  Perhaps check you have the correct one of those.  If the problem persists, take a log file and start a new support thread with all the details.  It doesn't immediately sound related, but no matter what we'll sort it out with you.

[TerryRed]

Are any of you guys using the DOFLinxMsg HOLD_ACTIVATION command to pause FP when launching PinEvent tables possibly?

 

I was having crashing problems with DOFLinx prior when using it as part of my Launch Tables script.

 

 

 

This is an example for a FP launch script in Pinup Popper:

cd /d c:\directoutput
if "[custom3]"=="NO_DOFLINX" (DOFLinxMsg HOLD_ACTIVATION=1)
START "" "[DIREMU]\FutureDMD.exe" table="[GAMENAME]" close=1
START "" "[STARTDIR]Launch\VPXSTARTER.exe" 10 5 60 "BSP Software*"
START "" "[DIREMU]\FPLoader.exe" /open "[GAMEFULLNAME]" /play /exit /arcaderender /STAYINRAM

Then you add a command to your Close Script to allow DOFLinx to resume its normal operation. Here is an example for Popper:

"[STARTDIR]LAUNCH\PUPCLOSER.EXE" WINTIT "Future Pinball" 2 1
cd /d c:\directoutput
DOFLinxMsg HOLD_ACTIVATION=0

Then in Popper’s Game Manager, just add NO_DOFLINX to Custom Var #3 for any PinEvent tables.

 

This means that Popper will HOLD / PAUSE DOFLinx only for FP tables that have NO_DOFLINX in the Custom Var #3 field.

 

 

 

However, I haven't completely resolved my DOFLinx crashing problem when doing the above with FP.... so I just wondered if maybe others were getting crashes by doing the same.

Edited by TerryRed, 16 March 2020 - 11:41 AM.

[fR33Styler]

 

Thx for fixing the Link (with 7.12).

 

Maybe there´s a little bug.. now (with 7.12) i have an LED animation on the right Playfield Leds which stays the most time (and was not there before).... kind of rainbow like.

 

Looks like this:

 

 

Best regards

What emulator and what game?

If FP do you have a link to the game?
 

 

It´s Pinball FX3. And i found out... if i install 7.12 package (incl. DDLs etc.) and just change only 'DOFLinx.exe' (replace the 7.12 EXE file with 'DOFLinx V7.05 Beta 3' EXE) the Error is gone.

 

So must be related to DOFLinx.exe file in some way.

Edited by fR33Styler, 16 March 2020 - 07:35 PM.

[Outhere]

Are any of you guys using the DOFLinxMsg HOLD_ACTIVATION command to pause FP when launching PinEvent tables possibly?

I was having crashing problems with DOFLinx prior when using it as part of my Launch Tables script.

This is an example for a FP launch script in Pinup Popper:

cd /d c:\directoutput
if "[custom3]"=="NO_DOFLINX" (DOFLinxMsg HOLD_ACTIVATION=1)
START "" "[DIREMU]\FutureDMD.exe" table="[GAMENAME]" close=1
START "" "[STARTDIR]Launch\VPXSTARTER.exe" 10 5 60 "BSP Software*"
START "" "[DIREMU]\FPLoader.exe" /open "[GAMEFULLNAME]" /play /exit /arcaderender /STAYINRAM

Then you add a command to your Close Script to allow DOFLinx to resume its normal operation. Here is an example for Popper:

"[STARTDIR]LAUNCH\PUPCLOSER.EXE" WINTIT "Future Pinball" 2 1
cd /d c:\directoutput
DOFLinxMsg HOLD_ACTIVATION=0

Then in Popper’s Game Manager, just add NO_DOFLINX to Custom Var #3 for any PinEvent tables.

This means that Popper will HOLD / PAUSE DOFLinx only for FP tables that have NO_DOFLINX in the Custom Var #3 field.

However, I haven't completely resolved my DOFLinx crashing problem when doing the above with FP.... so I just wondered if maybe others were getting crashes by doing the same.

I have not experienced any crashes and I've Been using these settings since you posted them quite a while ago, But when I was doing my testing with DOFlinx It was outside of a front end
 

Edited by Outhere, 16 March 2020 - 08:00 PM.

[DDH69]

 

 

Thx for fixing the Link (with 7.12).

 

Maybe there´s a little bug.. now (with 7.12) i have an LED animation on the right Playfield Leds which stays the most time (and was not there before).... kind of rainbow like.

 

Looks like this:

 

 

Best regards

What emulator and what game?

If FP do you have a link to the game?
 

 

It´s Pinball FX3. And i found out... if i install 7.12 package (incl. DDLs etc.) and just change only 'DOFLinx.exe' (replace the 7.12 EXE file with 'DOFLinx V7.05 Beta 3' EXE) the Error is gone.

 

So must be related to DOFLinx.exe file in some way.

 

 

So, here we go .....

• I have not and cannot recreate artefacts staying on my display.  Also no other reports at this stage, but not doubting what you have
• Most MX effects used for FX3 games are time driven, very few stay on until turned off
• There is one notable exception to the above, its the launch lane effect which runs on MX Right Effect.  This stays on until ball launch or a flipper is pressed

So now we need more information ....

• A particular FX3 game or >=3 ?
• Is it right MX only, or other?
• Is it the same colour on different games  (I'm concentrating on the launch effect here)
• Does it turn off at some stage?  If so when (ie flipper press)

The ball launch effect is on the MX Right until the ball launches or a flipper is pressed.  If you get a ball saved by the game that goes to sit in the launch lane the launch ball trigger does not fire hence the effect stays until you press a flipper.  This was a historical situation that caused a symptom like you described, but it was fixed a fair while ago.  Just explaining in case you are seeing this effect and not knowing when it will turn off.

 

The other thing to do is test the various effects using the right-click ROM test routine so we can find out what effect is "sticking".  If we need to do this I'll post a game ROM name and the "E" codes to try.

 

DOFLinx only turns on / off effects through DOF for MS LEDs, its pretty unsophisticated.  None of this has changed recently, so I don't immediately have any suspect areas to look at.  The recent issue with MS LEDs not starting was just that, a complete failure to run the startup step, nothing about individual effects, run times or conditions.

 

I know you are an exacting individual, so I look forward to some great detail 

[Laurent0722]

hello,

looks like there is some troubles with FX3 but does anybody notice any wierd stuffs with VPX ???

 

Since i updated my cab to 7.12 (yesterday) i experiment some strange things with some table.

 

For exemple with the Flinstones, (amazing table btw) it looks like the blinking of the PF lights (in the game) triggers my contactors and the same goes with the ssf sounds !!! what a mess...

 

Any ideas ?

 

Thanks

 

Laurent (France)

[Outhere]

If you have any thing in this line to do with visual pinball remove it --> PROCESSES=Pinball FX3,Pinball FX2,Future Pinball

Otherwise try running visual pinball without this running in the background

[Laurent0722]

If you have any thing in this line to do with visual pinball remove it --> PROCESSES=Pinball FX3,Pinball FX2,Future Pinball

Otherwise try running visual pinball without this running in the background

First, thanks for your answer.

Simples ideas are often the best, indeed, i will try to stop DOFlinx and then run vpx so i would be able to check if there is a link between the update and the strange things that i'm facing.

 

But i should say that i don't understand what you mean by "If you have any thing in this line to do with visual pinball remove it --> PROCESSES=Pinball FX3,Pinball FX2,Future Pinball"

sorry english isn't my first language 

 

Thanks again for your help

 

Laurent (France)

[Outhere]

You should have A-line similar to this in your DOFlinx.ini file  - PROCESSES=Pinball FX3,Pinball FX2,Future Pinball
Post that line from your DOFlinx.ini
 

[Laurent0722]

this is the line:

 

PROCESSES=Pinball FX3,Pinball FX2,Future Pinball,mamelayplus

[Outhere]

this is the line:

 

PROCESSES=Pinball FX3,Pinball FX2,Future Pinball,mamelayplus

Looks good

[DDH69]

OK, some people cleverer than me (and I write the damn code!) have figured out that in V7.12 for FX3 the AUTO_MX=1 is causing addressable LEDs to do silly things.  Clearly its a bug, but also note, that unless you are using FP tables having AUTO_MX=0 is fine for FX3 as 100% of tables have FX3 files and the auto function is not needed.  So changing it to 0 is a short-term work-around, I'll sort this out in the next day or so.

[DDH69]

Think I've got it, a bit of testing tomorrow to confirm.

[Outhere]

AUTO_MX=1 -- If that's the case that explains why don't have Anything weird going on as I have not use that setting in quite a while

Edited by Outhere, 20 March 2020 - 11:27 AM.