490 replies to this topic

[fakingdeath]

Did you try to register the com object again (use admin rights)?

Verstuurd vanaf mijn SM-G930F met Tapatalk

 

 

Yeah, same results. If trying to register com object as user it throws an error. Running as admin shows successful. It shows up in regedit with the right information but still doesn't work.

[senseless]

Damn! I hoped this would have solved it. I will check at home. I vaguely remember I also copied some dll into the pinballx plugin directory to replace an existing one. It was months ago so not sure.... 

[coreduo0099]

Hi, just got back from spring break camping trip and my W10 fresh install lost it's digital license somehow...

So, I went back to my old dd disk backup, restored to SSD, and re-validated that no paths seem to matter except DirectOutput must be at C:\DirectOutput  spaces in paths to my E: drive paths all work.  I even tried shortcuts and symbolic links on C:\DirectOutput -> E:\path and no luck.  We must use C:\DirectOutput  for DOF location.

 

Also, a few other sidenotes:

-Updating to PinballX 2.6.5 fixed a FX2 D3D Launch issue I noticed came up after v2.5.?

-Updating to Jurrasic Park version of FX3 fixed the backglass not launching issue with DOF 6.22

 

All is good in my cabinet again!  (using my W10 upgrade from W7 original system)

[zebulon]

 

Thanks mjr,

I downloaded and ran the msi for 20180306, then rebooted and reran the checkpoint vpt - no change....  Then I pulled the usB connection on the Sainsmart and ran checkpoint using the keyboard - no shaker motor or selenoids.  1st log is with patch and sainsmart.  2nd log is with patch and keyboard only.

 

DirectOutput Version 3.1.6639.38700, built 2018.03.06 21:30

MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy

DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput

2018.03.07 13:40:33.530 DirectOutput Logger initialized

2018.03.07 13:40:33.497 Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"

2018.03.07 13:40:33.531 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2018.03.07 13:40:33.531 Loading Pinball parts

2018.03.07 13:40:33.533 Loading cabinet

2018.03.07 13:40:33.534 No cabinet config file loaded. Will use AutoConfig.

2018.03.07 13:40:33.534 Cabinet auto configuration started

2018.03.07 13:40:33.930 Detected and added PacLed64 Id 1 with name PacLed64 1

2018.03.07 13:40:33.931 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1

2018.03.07 13:40:33.932 PacDriveSingleton.PacUIOGetIdList: i=0, numdevices=1, DeviceType=PacLED64

2018.03.07 13:40:33.933 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)

2018.03.07 13:40:34.194 FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected Zeb's Plunger kit at index 0, name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLNGOP01; SKIPPING

2018.03.07 13:40:34.194 Cabinet auto configuration finished

2018.03.07 13:40:34.194 Cabinet loaded

2018.03.07 13:40:34.194 Loading table config

2018.03.07 13:40:34.195 Warning: No table config file found. Will try to load config from LedControl file(s).

2018.03.07 13:40:34.195 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName ckpt_a17

2018.03.07 13:40:34.197 Loading LedControl file C:\DirectOutput\Config\directoutputconfig20.ini

2018.03.07 13:40:34.209 Min DOF Version is 0.8 for file directoutputconfig20.ini

2018.03.07 13:40:34.663 1 directoutputconfig.ini or ledcontrol.ini files loaded.

2018.03.07 13:40:34.664 Config for RomName ckpt_a17 exists in LedControl data. Updating cabinet and config.

2018.03.07 13:40:34.686 Table config loading finished: romname=ckpt_a17, tablename=Checkpoint

2018.03.07 13:40:34.687 Pinball parts loaded

2018.03.07 13:40:34.687 Starting processes

2018.03.07 13:40:34.688 Initializing cabinet

2018.03.07 13:40:34.688 Debug: Initializing output controllers

2018.03.07 13:40:34.690 PacLed64 Id:1 initialized and updater thread started.

2018.03.07 13:40:34.690 Debug: Output controllers initialized

2018.03.07 13:40:34.694 Cabinet initialized

2018.03.07 13:40:34.698 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml

2018.03.07 13:40:34.797 Framework initialized.

2018.03.07 13:40:34.797 Have fun!

2018.03.07 13:41:09.020 Finishing framework

2018.03.07 13:41:09.022 Finishing cabinet

2018.03.07 13:41:09.023 Debug: Finishing output controllers

2018.03.07 13:41:10.052 PacLed64 Id:1 finished and updater thread stopped.

2018.03.07 13:41:10.052 Debug: Output controllers finished

2018.03.07 13:41:10.052 Cabinet finished

2018.03.07 13:41:10.052 DirectOutput framework finished.

2018.03.07 13:41:10.052 Bye and thanks for using!

 

 

2nd log:

DirectOutput Version 3.1.6639.38700, built 2018.03.06 21:30

MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy

DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput

2018.03.07 13:51:49.524 DirectOutput Logger initialized

2018.03.07 13:51:49.499 Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"

2018.03.07 13:51:49.525 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2018.03.07 13:51:49.525 Loading Pinball parts

2018.03.07 13:51:49.532 Loading cabinet

2018.03.07 13:51:49.533 No cabinet config file loaded. Will use AutoConfig.

2018.03.07 13:51:49.533 Cabinet auto configuration started

2018.03.07 13:51:49.897 Detected and added PacLed64 Id 1 with name PacLed64 1

2018.03.07 13:51:49.897 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1

2018.03.07 13:51:49.899 PacDriveSingleton.PacUIOGetIdList: i=0, numdevices=1, DeviceType=PacLED64

2018.03.07 13:51:49.900 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)

2018.03.07 13:51:49.913 Cabinet auto configuration finished

2018.03.07 13:51:49.913 Cabinet loaded

2018.03.07 13:51:49.913 Loading table config

2018.03.07 13:51:49.914 Warning: No table config file found. Will try to load config from LedControl file(s).

2018.03.07 13:51:49.914 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName ckpt_a17

2018.03.07 13:51:49.916 Loading LedControl file C:\DirectOutput\Config\directoutputconfig20.ini

2018.03.07 13:51:49.925 Min DOF Version is 0.8 for file directoutputconfig20.ini

2018.03.07 13:51:50.331 1 directoutputconfig.ini or ledcontrol.ini files loaded.

2018.03.07 13:51:50.333 Config for RomName ckpt_a17 exists in LedControl data. Updating cabinet and config.

2018.03.07 13:51:50.353 Table config loading finished: romname=ckpt_a17, tablename=Checkpoint

2018.03.07 13:51:50.354 Pinball parts loaded

2018.03.07 13:51:50.354 Starting processes

2018.03.07 13:51:50.354 Initializing cabinet

2018.03.07 13:51:50.355 Debug: Initializing output controllers

2018.03.07 13:51:50.357 PacLed64 Id:1 initialized and updater thread started.

2018.03.07 13:51:50.357 Debug: Output controllers initialized

2018.03.07 13:51:50.360 Cabinet initialized

2018.03.07 13:51:50.364 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml

2018.03.07 13:51:50.460 Framework initialized.

2018.03.07 13:51:50.460 Have fun!

2018.03.07 13:53:22.680 Finishing framework

2018.03.07 13:53:22.682 Finishing cabinet

2018.03.07 13:53:22.683 Debug: Finishing output controllers

2018.03.07 13:53:23.705 PacLed64 Id:1 finished and updater thread stopped.

2018.03.07 13:53:23.705 Debug: Output controllers finished

2018.03.07 13:53:23.705 Cabinet finished

2018.03.07 13:53:23.705 DirectOutput framework finished.

2018.03.07 13:53:23.705 Bye and thanks for using!

 

 

 

Just a FYI, the Deluxe plunger kit does indeed have a FTDI chip on it running the output and ZB_Launch features.

 

 

 

 

 

<?xml version="1.0"?>

 

-<Cabinet xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 

<Name>zebsboards</Name>

 

 

-<OutputControllers>

 

 

-<FT245RBitbangController>

 

<Name>Zebsboards 1</Name>

 

<SerialNumber>ZBPLUNGE01</SerialNumber>

 

</FT245RBitbangController>

 

</OutputControllers>

 

 

-<Toys>

 

 

-<LedWizEquivalent>

 

<Name>ZebsboardsLWEQ 1</Name>

 

<LedWizNumber>40</LedWizNumber>

 

 

-<Outputs>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.01</OutputName>

 

<LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.02</OutputName>

 

<LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.03</OutputName>

 

<LedWizEquivalentOutputNumber>3</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.04</OutputName>

 

<LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.05</OutputName>

 

<LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.06</OutputName>

 

<LedWizEquivalentOutputNumber>6</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.07</OutputName>

 

<LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

-<LedWizEquivalentOutput>

 

<OutputName>Zebsboards 1.08</OutputName>

 

<LedWizEquivalentOutputNumber>8</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

</Outputs>

 

</LedWizEquivalent>

 

</Toys>

 

<Colors/>

 

<Curves/>

 

<AutoConfigEnabled>true</AutoConfigEnabled>

 

</Cabinet>

 

[mjr]

 

Just a FYI, the Deluxe plunger kit does indeed have a FTDI chip on it running the output and ZB_Launch features.

 

 

Ah, okay...  Does that mean it should be auto-configured as though it's a SainSmart, or does it need its own special handling?  If it's the former, I'll just take out that bit I added that skips it in the auto-config and return it to the default handling.

[zebulon]

Shouldn't need any special handling, from what I could see in the previous logfile posted it looked to be loading properly by the autoconfig for Sainsmart. 

 

Thanks for looking at that.

[mjr]

Shouldn't need any special handling, from what I could see in the previous logfile posted it looked to be loading properly by the autoconfig for Sainsmart. 

 

Perfect - I'll just take out the special case.

 

[Edit]

Just posted the update (23 Mar 2018 edition) to the usual place:

 

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

Edited by mjr, 23 March 2018 - 07:03 PM.

[coreduo0099]

Hi,

 

Now that I've been happily playing for Weeks, I just found that my .xml dof files are no longer working in VP9 or VP10 but DOF seems to work fine in VP9, VP10, FX2, FX3, etc..

 

Any suggestions on what might be wrong?  I've tried going back to older VPX builds and back to 6.11 and 5.2 DOF but no luck.

 

Is there something I'm missing to have vpx leverage the .xml dof files for tables not using DOF?    I can't think of what I've changed that would have broken this behavior on the 20 or so older tables I set up with custom .xml files.

 

Thanks

[mjr]

Now that I've been happily playing for Weeks, I just found that my .xml dof files are no longer working in VP9 or VP10 but DOF seems to work fine in VP9, VP10, FX2, FX3, etc..

 

Any suggestions on what might be wrong?  I've tried going back to older VPX builds and back to 6.11 and 5.2 DOF but no luck.

 

Is there something I'm missing to have vpx leverage the .xml dof files for tables not using DOF?    I can't think of what I've changed that would have broken this behavior on the 20 or so older tables I set up with custom .xml files.

 

Nothing I can think of - I don't think anything in that area changed in DOF between the old R3 beta and this point, either, but there might be some subtle side-effect bug in there somewhere.  Did you move any files around to new paths?  Have you looked at the DOF logs to see if there are any hints in there?

[coreduo0099]

Excellent.. Log didn't have answer but gave me an idea..

 

When I did all my rebuild experimenting several weeks back, I switched from my cabinet.xml config to autoconfig my cabinet.

 

I swapped back in my cabinet.xml I hand built and now my DOF effects are back.

 

So, it appears that a autoconfig cabinet.xml does not work with table.xml DOF files.

[wrd1972]

Just used the new installer. Many thanks for this! The previous way of installing DOF was painful.

 

I am having one issue now. DOF seems to not work when I load VP10 and start the first table...DOF is dead. But exiting and starting the table a second time and so on...DOF seems to work pefectly. Just not that initial start after after VP loads.

 

I am running  2 Sainsmart 8-relay boards and a Zebs deluxe plunger. I just recently added the Zebs plunger but prior to that, I had the Virtuapin V2 plunger and DOF R2, and never this issue.

 

Any ideas?

[mjr]

I am having one issue now. DOF seems to not work when I load VP10 and start the first table...DOF is dead. But exiting and starting the table a second time and so on...DOF seems to work pefectly. Just not that initial start after after VP loads.

 

There are some messages from coreduo0099 earlier in this thread about a similar issue, where DOF wouldn't work on the first attempt for a VP session, but would work if rebooted the ROM in VPM by pressing F3.  That's not exactly the same thing, though, so it might be unrelated. 

 

The thing that seemed to fix it for him was to move everything in the VP ecosystem (VP itself, VPinMAME, B2S, and DirectOutput) to folders on the C: drive, and to put DirectOutput in C:\DirectOutput (that exact name, with no spaces or any other changes in the path name). 

 

Caveat:  I'm not entirely convinced that a C: path actually matters, because (a) I can't find anything in the DOF code itself that should make C: any different from other drives, and (b) my own testing setup has DOF in a D: folder, and that seems to work fine.  So it's possible that what fixed coreduo0099's issue had nothing to do with the path location.  He said he did a full resinstall of EVERYTHING at the same time he moved it all to C:, so I think there's a good chance that what actually happened was that he had some unsolved config issue in the old setup that got cleared up when he did the full reinstall.  But it might be worth a try given that you're seeing similar flaky behavior.

 

If that doesn't help, have you tried looking at your DOF log files?  There should be a file called DirectOutput.log in your Visual Pinball\Tables folder.  Try this:

 

- Find DirectOutput.log

- Delete it

- Reboot your machine or whatever is needed to get to that starting condition where DOF won't work properly

- Run VP

- Exit

 

Now look at DirectOutput.log and see what it contains.  For starters, verify that it exists, and that the timestamps match the time of the test you just ran.  Also check that the DOF version listed at the top is the R3++ version.  Then look to see if any errors are reported, and if the table config was loaded.  DOF is pretty indiscriminate about what it writes to the log file, so it can take some patience to look through all of the details, but hopefully it'll have some clue about what's going wrong.

 

If there's no log file at all, start over (with the reboot if necessary to get back to the problematic starting condition), run VP, and then right-click on the backglass to bring up the B2S status box.  Look at the Plugins section to see if DOF is getting loaded, and if so, check to see if there's an exception listed in the Plugins info box.  If the problem is getting the DOF DLL to load, that might have some information about why that's failing.

[coreduo0099]

 

I am having one issue now. DOF seems to not work when I load VP10 and start the first table...DOF is dead. But exiting and starting the table a second time and so on...DOF seems to work pefectly. Just not that initial start after after VP loads.

 

There are some messages from coreduo0099 earlier in this thread about a similar issue, where DOF wouldn't work on the first attempt for a VP session, but would work if rebooted the ROM in VPM by pressing F3.  That's not exactly the same thing, though, so it might be unrelated. 

 

The thing that seemed to fix it for him was to move everything in the VP ecosystem (VP itself, VPinMAME, B2S, and DirectOutput) to folders on the C: drive, and to put DirectOutput in C:\DirectOutput (that exact name, with no spaces or any other changes in the path name). 

 

Caveat:  I'm not entirely convinced that a C: path actually matters, because (a) I can't find anything in the DOF code itself that should make C: any different from other drives, and (b) my own testing setup has DOF in a D: folder, and that seems to work fine.  So it's possible that what fixed coreduo0099's issue had nothing to do with the path location.  He said he did a full resinstall of EVERYTHING at the same time he moved it all to C:, so I think there's a good chance that what actually happened was that he had some unsolved config issue in the old setup that got cleared up when he did the full reinstall.  But it might be worth a try given that you're seeing similar flaky behavior.

Sounds similiar to my issue.  If you go to  your backglass and check plugins, you'll see on first launch it wont load. then after it does, at least it did on ACDC for me.

 

To fix it correclty the fix is to uninstall and reinstall doflinx and DOF R3++ to C:\DirectOutput

NO other paths matter.  I had mine on an E:\path and tried both shortcuts and symbolic links from C:\DirectOutput to the E drive and it did not fix it.  Only installing natively to C:\DirectOutput fixed it.  I can't explain why, other than I tried everything for about a month and wasted 60-80 hours tearing my hair out.

All of my other pinball cab stuff is in E:\Emulator\Pinball emu\ other than PROC.  It also worked best on C at C:\PROC

 

 

The temporary workaround that will likely bite you in the ass later is to make a copy of Extensions.dll and put it in your vpinball.exe directory.  That also resolved it, but I could see that I'd one day forget and get the two versions out of sync.

 

Hope it helps.

 

Question, what is your DirectOutput directory path?

[wrd1972]

Thanks for the replies guys.

 

Regarding:

"The thing that seemed to fix it for him was to move everything in the VP ecosystem (VP itself, VPinMAME, B2S, and DirectOutput) to folders on the C: drive, and to put DirectOutput in C:\DirectOutput (that exact name, with no spaces or any other changes in the path name)".

I already have the folders configured like this.

 

I will look at the logs maybe this weekend and see if it reveals anything of value. Will also try a DOF reinstall and possibly the extensions trick...for troubleshooting only.

 

I have all of my DOF in c:/Directoutput/...

[mjr]

Thanks for the replies guys.

 

Regarding:

"The thing that seemed to fix it for him was to move everything in the VP ecosystem (VP itself, VPinMAME, B2S, and DirectOutput) to folders on the C: drive, and to put DirectOutput in C:\DirectOutput (that exact name, with no spaces or any other changes in the path name)".

I already have the folders configured like this.

 

I will look at the logs maybe this weekend and see if it reveals anything of value. Will also try a DOF reinstall and possibly the extensions trick...for troubleshooting only.

I have all of my DOF in c:/Directoutput/...

 

The thing to check first is probably grabbing "before and after" logs - one in the initial boot-up state where it doesn't work, and one after it starts working.  Then compare them to see what's different.  Hopefully the differences between the two will point to what's wrong in the non-working one.

[wrd1972]

MJR,

Where can I find the log file?

 

I dont see it in the Directoutput folder.

Edited by wrd1972, 21 April 2018 - 03:07 AM.

[psmiraglia]

For about 2 months I have been running DOF3++ and Doflinx 6.2x for Pinball FX3 only, and DOF3 and Doflinx 6.11 for VP, FX2, FP, PRO and PBX. (you may recall there were a couple of issues I was facing with my pacled, among them a rapid fire of my ports within PBX, something that was fixed before the branches merger). All systems to their latest release (inc VP10.5b) except for PBX, which I'm running v2.75 (I have lag issues with anything newer than that).
 
I have just grabbed the latest ZIP and upgraded Doflinx to 6.25 and all systems seem to be functioning properly, with two very small exceptions: a)when I launch a table, a single fire of my chime1 can be heard. I have not looked into the DOF config for PBX to determine if this is new or not, but it does not bother me and, b) I have to use the old version of dofslave for pinball pro (from doflinx 6.11). I will test further this week, and will keep PBX in attract mode in the meantime. I'm not sure which version of the PBX dof plugin and associated DLLs I have in place but, whatever they are, they seem fine. Lastly note that I don't run doflinx in the background, as that used to make the problem worse when returning to PBX, and I don't see a need to change that: launching/killing before/after FP, FX2, FX3 and PRO does the trick.
 
so far so good for both my PacLed and teensy toys.
[update] it seems like DOF3++ and Doflinx 6.25 are both stable for my setup now. Many thanks!!

Edited by psmiraglia, 26 April 2018 - 11:32 PM.

[mjr]

MJR,

Where can I find the log file?

 

I dont see it in the Directoutput folder.

 

The location is set in the global config file - the default is "the current folder", wherever that happens to be for whatever program you're running.  For PinballX, it's usually the PinballX program folder, and for VP it's usually the Visual Pinball\Tables folder.  If all else fails, you can always go to the Windows search box and search for DirectOutput.log across your whole set of local disks.

[wrd1972]

Wow...its not inn the directoutput directory. And it does not even come up during a system wide search. Figures...thats my luck

Now what do I need to do?

[Outhere]

In order for me to get my log to work, I had to put the direct path to where the log should be..

In the GlobalConfig_B2SServer.xml