490 replies to this topic

[psmiraglia]

here is a link to the folder with the logs:

 

https://mega.nz/#F!Mck02YZL!iQKEgosepGCB3CptziFzfQ

 

don't know what to tell you. Maybe I should stop testing and wait for others to validate... I have a 100% working system with the previous version of DOF: I just tried PBX, VP9, VPX, PinPro, FP, FX2, and FX3 (via doflinx) to be 100% sure.

[mjr]

here is a link to the folder with the logs:

 

https://mega.nz/#F!Mck02YZL!iQKEgosepGCB3CptziFzfQ

 

don't know what to tell you. Maybe I should stop testing and wait for others to validate... I have a 100% working system with the previous version of DOF: I just tried PBX, VP9, VPX, PinPro, FP, FX2, and FX3 (via doflinx) to be 100% sure.

 

If you look at your .bad file, you'll see that it's not even trying to load a cabinet.xml this time:

 

2018.02.16 22:56:00.869 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2018.02.16 22:56:00.869 Loading Pinball parts

2018.02.16 22:56:00.870 Loading cabinet

2018.02.16 22:56:00.870 No cabinet config file loaded. Will use AutoConfig.

 

So presumably your C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml file has no pointer to a Cabinet.xml.  When you're in "bad" mode, obviously - when you're in "good" mode you do have that link and that's why it's working.  That would be the place to look.

[psmiraglia]

config folders are an exact copy of each other... It is curious though that PBX *does* find the cabinet file, but vpx does not... 

 

2018.02.16 22:51:53.251 Global config loaded from: C:\DirectOutput\config\GlobalConfig_PinballX.xml

2018.02.16 22:51:53.251 Loading Pinball parts

2018.02.16 22:51:53.251 Loading cabinet

2018.02.16 22:51:53.252 Will load cabinet config file: C:\DirectOutput\Config\cabinet.xml

2018.02.16 22:51:53.541 1 output controller defnitions and 4 toy definitions loaded from cabinet config.

 

and GlobalConfig_PinballX.xml is an exact copy of GlobalConfig_B2SServer.xml

[mjr]

 

config folders are an exact copy of each other... It is curious though that PBX *does* find the cabinet file, but vpx does not... 

 

It's clear what the difference in the two scenarios is, right?

 

Cabinet.xml loaded:  2018.02.16 22:51:53.251 Global config loaded from: C:\DirectOutput\config\GlobalConfig_PinballX.xml

Cabinet.xml not loaded:  2018.02.16 22:56:00.869 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

 

Differences highlighted.  Presumably your GlobalConfig_PinballX.xml has a pointer to cabinet.xml  in it and your GlobalConfig_B2SServer.xml doesn't.  So let's test that out and see what's different about the two config files.  Here's a build with yet more added instrumentation that should dump the entire contents of the loaded global config file into the log:

 

http://mjrnet.org/pi...jr-20180217.zip

http://mjrnet.org/pi...jr-20180217.msi

 

Like you said earlier, there's probably something weird going on with shortcuts or something that's making the files loaded different from what they superficially appear to be, so this should help clarify by showing the actual contents of the files that DOF is reading.

[psmiraglia]

 

 

Like you said earlier, there's probably something weird going on with shortcuts or something that's making the files loaded different from what they superficially appear to be, so this should help clarify by showing the actual contents of the files that DOF is reading.

 

 

ok.i started from scratch: backed up my directoutput folder and used the original to upgrade dof and doflinx, and avoid link issues.

 

vp, doflinx work

pinpro works with the previous dofslave.exe, not the new one

pbf DOF fails to start. this is the plugin log:

 

18.02.17 03:20:39.083 DirectOutput PinballX Plugin, version 3.1.6622.21052, built 2018.02.17 11:41

18.02.17 03:20:39.093 DirectOutput PinballX Plugin, version 3.1.6622.21052, built 2018.02.17 11:41

18.02.17 03:20:43.360 DirectOutput PinballX Plugin, version 3.1.6622.21052, built 2018.02.17 11:41

18.02.17 03:23:05.180 DirectOutput PinballX Plugin, version 3.1.6622.21052, built 2018.02.17 11:41

18.02.17 03:23:05.182 Loading plugin config

18.02.17 03:23:05.267 Plugin config loaded

18.02.17 03:23:05.267 Initializing plugin

18.02.17 03:23:05.268 Loading PBX config data

18.02.17 03:23:05.277 PBX config data loaded

18.02.17 03:23:05.278 Initializing DOF

18.02.17 03:23:05.301 Init failed: Exception has been thrown by the target of an invocation.

18.02.17 03:23:05.302 . Stack:    at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)

   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)

   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)

   at PinballX.DOFManager.Init()

   at PinballX.Plugin.Initialize(IntPtr InfoPtr)

18.02.17 03:23:05.302 . Inner exception: Could not load type 'StringExtensions' from assembly 'DirectOutput, Version=3.1.6622.21052, Culture=neutral, PublicKeyToken=null'.

18.02.17 03:23:05.302 .. Stack: 

[mjr]

Okay, I think the start-from-scratch was a good idea - it looks like you're back to the original problem that we were trying to diagnose in the first place.  You've finally triggered the instrumentation that I added to try to see why the PBX plugin wasn't loading, and here we can see why - it looks like a DLL path issue.  There's an old DLL in the mix somewhere, as we can see from this message:

 

Could not load type 'StringExtensions' from assembly 'DirectOutput, Version=3.1.6622.21052, Culture=neutral, PublicKeyToken=null'.

 

So the code that's trying to load that is old - StringExtensions no longer exists in DirectOutput.dll but is in Extensions.dll now.  I think that's coming from the DirectOutputComObject. 

 

Did you do the MSI or ZIP install this time?  If you installed it manually from the ZIP you might need to re-register the COM object - I think that's where this error is coming from, which means the registered COM object is the old one.

[psmiraglia]

ok. last test for a while...

 

1 started from working setup

2 installed with MSI. this time around the installer askd me to reboot

3 after rebooting, tried a vpx table and did no work. looking at the log, again it could not find GlobalConfig_B2SServer.xml which in fact was gone. it was there before launching the MSI

4 restored a copy and now vpx works

 5 launched pbx and, after 10 or so seconds, dof kicked in. the same behavior was observed 3 or 4 times, a few times dof worked immediately after starting pbx

6 tested pinpro. new dofslave crashes, while old one works

7 doflinx 6.2 works (sort of) with FX3 and FP

 

for the scary part, after exiting fx3 dof started firing toys randomly for about 3 seconds then pbx crashed

 

i uploaded logs to the same mega folder

 

Now I wont be ale to test more for some time. txs

[mjr]

Some observations:

 

> 2 installed with MSI. this time around the installer askd me to reboot

 

This might explain some of the unstable behavior you've been seeing where you keep trying different installs and one thing starts working and another thing stops working, and a different mix the next time.  The reboot probably means that Setup couldn't copy a file due to a process holding a lock on the file.  So some of your problems might be coming from other programs that are running while you're trying to update files, and preventing some of the updates from taking place.

 

> 3 after rebooting, tried a vpx table and did no work. looking at the log, again it

> could not find GlobalConfig_B2SServer.xml which in fact was gone. it was there

> before launching the MSI

 

I don't think Setup has the ability to delete files randomly on its own, so my guess is that you probably installed into a newly created directory, and the new directory just didn't contain this file.

 

This probably is another part of the on-again/off-again this-works-now-but-this-doesn't behavior you've been having.  From all I can see, the new DLLs are working on your machine, because it looks like they've now worked at least once in each configuration (barring FX3, which is whole separate matter) - it looks to me like it's a matter of getting all of the .xml files in order each time.  Hopefully the more elaborate instrumentation showing what's in each XML file will help you debug that.

 

> 5 launched pbx and, after 10 or so seconds, dof kicked in.

 

This is new behavior, right?  Again, the DLLs are the same since we started this other than all the new instrumentation, so anything new you're seeing is most likely something that's changed on your system.  I don't have any guess about what could cause this; maybe a conflict with another program?

 

> for the scary part, after exiting fx3 dof started firing toys randomly for about

> 3 seconds then pbx crashed

 

That sounds like it might be related, but I don't have any guess about that either.

Edited by mjr, 17 February 2018 - 11:52 PM.

[Outhere]

Can the zip file be used as 1st time install or is it only for Upgrading..

The reason I ask is, The Zip did not have this file -- DirectOutputComObject.dll

Edited by Outhere, 18 February 2018 - 02:21 AM.

[mjr]

Can the zip file be used as 1st time install or is it only for Upgrading..

The reason I ask is, The Zip did not have this file -- DirectOutputComObject.dll

 

Sorry, no, that was unintentional - it should have been in there.  The ZIP and MSI should be equivalent.  I just missed it in the release script.  I've just added it and updated the ZIP file.

 

http://mjrnet.org/pi...ll-updates.html

[TerryRed]

To mjr and everyone involved in testing....thank you so much for the work put into this. I've been to busy testing PinUP Player (PuP) and PinUP Menu (PuM) that I haven't had time to test this out yet.

[psmiraglia]

@jesperpark were you able to test? the fix you shared with me (from DJrobx) helped with random toy fires that are now happening again me with this update... i was going to hold, but looks like ill be force to upgrade so i'd like to get parity with my current setup. at this time, for me, the random toy firing and dofslave.exe not working seem to be the only issues i have (i can work around the issues with the installer).

@mjr

 

> 3 after rebooting, tried a vpx table and did no work. looking at the log, again it

> could not find GlobalConfig_B2SServer.xml which in fact was gone. it was there

> before launching the MSI

 

I don't think Setup has the ability to delete files randomly on its own, so my guess is that you probably installed into a newly created directory, and the new directory just didn't contain this file.

 

>>> nope. it was an exact copy, that included doflinx and a bunch of other stuff. in fact, the pbx version of the ini was left untouched. 

 

 

> for the scary part, after exiting fx3 dof started firing toys randomly for about

> 3 seconds then pbx crashed

 

That sounds like it might be related, but I don't have any guess about that either.

 

>>> i used to have this problem before and was fixed with a build that DJrobx mentioned before. it seems you have integrated the fix already, but the behavior remains

 

lastly, as doflinx 6.2 needs an update, ill probably be forced to upgrade dof... the other open item is dofslave, though it seems like the old version works. if more users verify this, maybe you can package the old version until freezy figures out if there is an issue with his new build?

[shadowshd]

Hi,

 

Just a quick feedback with MJR's DOF version : it seems to work fine on my cab.

 

I'm using Visual Pinball X and 9, Windows 10 1709 x64, PinballX and one Ledwiz, one Pinscape Controller, contactors, gear, shaker, 5 flashers, 2 strobes and a PinDMD.

 

I had a bug with the "historic" version of DOF R3 when using DOF PinballX Plugin : when I was exiting PinballX, I had a PinballX.exe process and as many VPinball.exe processes than times executed in Windows' task manager.

 

If I disabled DOF plugin everything returned to normal.

 

Now with MJR DOF I have no more residual processes of VP or PBX in task manager after exiting 

[tttttwii]

Hi,

 

Just a quick feedback with MJR's DOF version : it seems to work fine on my cab.

 

I'm using Visual Pinball X and 9, Windows 10 1709 x64, PinballX and one Ledwiz, one Pinscape Controller, contactors, gear, shaker, 5 flashers, 2 strobes and a PinDMD.

 

I had a bug with the "historic" version of DOF R3 when using DOF PinballX Plugin : when I was exiting PinballX, I had a PinballX.exe process and as many VPinball.exe processes than times executed in Windows' task manager.

 

If I disabled DOF plugin everything returned to normal.

 

Now with MJR DOF I have no more residual processes of VP or PBX in task manager after exiting 

Have you used the installer and just installed over your old installation or have you removed the old DOF folder and did a "new" install?

[psmiraglia]

I'm testing again and, though PBX, Doflinxand VP seem to work (PinPro does not), my toys fire randomly between games (I'm afraid coils will fry). This behavior was fixed a while back by DJRobX, and I believe the fix still needs to be build into DOF3, right ? I cannot risk damaging my toys with this build (and now I cannot use doflinx either, as the new version for FX3 requires DOF3).

 

thoughts ?

 

here is an example of what happens when I quit FX3: 

 

thanks, and let me know if there is anything specific you'd like me to test

[TerryRed]

I'm testing again and, though PBX, Doflinxand VP seem to work (PinPro does not), my toys fire randomly between games (I'm afraid coils will fry). This behavior was fixed a while back by DJRobX, and I believe the fix still needs to be build into DOF3, right ? I cannot risk damaging my toys with this build (and now I cannot use doflinx either, as the new version for FX3 requires DOF3).

 

thoughts ?

 

here is an example of what happens when I quit FX3: 

 

thanks, and let me know if there is anything specific you'd like me to test

 

Did you have a USB Sainsmart?  If so, can't help but think that is the result of the USB Sainsmart getting "reset" and they are known for cycling every output when being fired up for the first boot or reset....  ?

[psmiraglia]

no, it is a Pacled... this does not happen when the board starts either. DJRobx figured it out a while back and provided a patch.

[mjr]

I'm testing again and, though PBX, Doflinxand VP seem to work (PinPro does not), my toys fire randomly between games (I'm afraid coils will fry). This behavior was fixed a while back by DJRobX, and I believe the fix still needs to be build into DOF3, right ? 

 

I already merged the patch from djrobx - at least, I merged what he sent me.  Not sure if it's the same thing you're talking about, but it's his PacLed timing update.

 

https://github.com/m...bf05525946c4c56

I'm afraid I don't have a PacLed, so I can't test it myself or investigate further.  djrobx, if you're monitoring the thread, do you have any input?  Maybe further timing adjustments are needed?

[coreduo0099]

Hello,

I've got a slightly different variation.

Cab with 2 ledwiz working fine.

I'm testing fx3 so I upgraded to this unified version.

FX3 worked fine over the last week of intermittent table tweaking.

Tonight, came back to VPX and my tables were getting no DOF, yet DOF testers all show DOF is working fine itself.

I was testing with creature from black lagoon and once after F3 it started working.  quit and relaunched and no DOF.

I checked the backglass plugin and found this:

https://ibb.co/c1enTH

 

but the file is there.  I've re-installed too. 

swap back to my old DirectOutput directory (I had it backed up) and vpx is perfect.

swap back again to new DirectOutput directory and no luck

Any ideas?

 

[if the pic link is broken, the error is: The system cannot find the file specified.  File name: 'Extensions, Version=3.1.6623.21194, Culture=neutral, PublicKeyToken=null' at DirectOutput.Pinball.Setup(String GlobalConfigFilename, String TableFilename, String RomName) at ........

Edited by coreduo0099, 24 February 2018 - 08:06 AM.

[shadowshd]

Have you used the installer and just installed over your old installation or have you removed the old DOF folder and did a "new" install?

 

I did a backup of my existing DOF folder and unzipped MJR's version over my existing install