490 replies to this topic

[Findusone]

Hi Mike,

i have got a stange missfireing with your new version.

The old R3Beta works fine for me.

Here are two videos, one with the old R3Beta and one with the Grander Unified R3++.

https://photos.app.goo.gl/z7esMjQSDV1BRANE3

Any ideas, what could be wrong?

BR, Jens

[psmiraglia]

@findyousone what controller do you have? I have a similar problem with a pacled.

[mjr]

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

 

Those DLL load errors usually come from one of two causes:

 

- Mismatched DLL versions - a mix of old and new DLL versions installed, and the wrong one is getting loaded

 

- "Blocked" DLLs

 

If you installed via the ZIP, you might try installing via the automated Setup version (the .MSI file) instead, since it handles all of the registry updates and unblocking automatically.  DOF has traditionally been such a PITA to set up because any tiny setup error or omission makes the whole thing not work.

i have got a stange missfireing with your new version.

The old R3Beta works fine for me.

 

If you're using PacLed, you're not the only one.  I added djrobx's fix that's supposed to help with that, but now I'm wondering if it's actually causing problems on some machines - maybe it's a whack-a-mole thing where the timing that works on one machine screws up another machine, and vice versa.

[Findusone]

@findyousone what controller do you have? I have a similar problem with a pacled.

I have got a Ledwiz for the output and a pinscape for the plunger and nudging.

[mjr]

 

@findyousone what controller do you have? I have a similar problem with a pacled.

I have got a Ledwiz for the output and a pinscape for the plunger and nudging.

 

For LedWiz, you might try adjusting the global timing parameters in the global config file.  Run the global config editor, load your B2S configuration, go to the Misc page, and set the "LedWiz Default Min Command Interval" to a higher value.  Save the config back to the original file.  Try maybe 10 or 20 ms and see if that helps.

psmiraglia - I built a copy with djrobx's changes rolled back, if you want to try that to see if the timing changes are the source of your random misfires.  It's also possible that you need his changes but need longer delays than he put in, so maybe we can try that next if this doesn't work.

 

http://mjrnet.org/pi...ed-rollback.zip

http://mjrnet.org/pi...ed-rollback.msi

[Findusone]

 
For LedWiz, you might try adjusting the global timing parameters in the global config file.  Run the global config editor, load your B2S configuration, go to the Misc page, and set the "LedWiz Default Min Command Interval" to a higher value.  Save the config back to the original file.  Try maybe 10 or 20 ms and see if that helps.

Thanks a lot, >=3ms seems to work for me 😊

[mjr]

 

For LedWiz, you might try adjusting the global timing parameters in the global config file.  Run the global config editor, load your B2S configuration, go to the Misc page, and set the "LedWiz Default Min Command Interval" to a higher value.  Save the config back to the original file.  Try maybe 10 or 20 ms and see if that helps.

 

Thanks a lot, >=3ms seems to work for me

 

Great!  Definitely the shorter the better.  If you haven't already tested it under PinballX (assuming you're using that), give it a try there too - for some reason PBX causes more problems with this than VP for me, and needs more time padding to make it reliable.  I'm not sure what PBX is up to, but something it does triggers the LedWiz timing issues pretty predictably.  (Which isn't really a PBX bug, as the real problem here is the LedWiz itself, but it would be nice to know why PBX triggers it.)

Edited by mjr, 24 February 2018 - 09:42 PM.

[coreduo0099]

 

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

 

Those DLL load errors usually come from one of two causes:

 

- Mismatched DLL versions - a mix of old and new DLL versions installed, and the wrong one is getting loaded

 

- "Blocked" DLLs

 

If you installed via the ZIP, you might try installing via the automated Setup version (the .MSI file) instead, since it handles all of the registry updates and unblocking automatically.  DOF has traditionally been such a PITA to set up because any tiny setup error or omission makes the whole thing not work.

 

Thanks.  started from scratch. used the msi, installed DOF 6.2, dof config files, and moved my cabinet xmls back over. Same issue.

I've searched for duplicates of dlls and can't find any.

with the fresh install, same thing fx2 is good, fx3 is good, future pinball good, pinballx menus are good, vp9 and vpx give the same message.

My W10 system is set up so that no files get blocked.  (Validated them as well)

 

Would you/someone please share the regedit values/exports on a working system and I can start hunting for what the heck is going on?

 

Any debug I can do/provide that might help?

Edited by coreduo0099, 24 February 2018 - 10:09 PM.

[mjr]

 

 

started from scratch. used the msi, installed DOF 6.2, dof config files, and moved my cabinet xmls back over. Same issue.

I've searched for duplicates of dlls and can't find any.

with the fresh install, same thing fx2 is good, fx3 is good, future pinball good, pinballx menus are good, vp9 and vpx give the same message.

 

The difference between VP and everything else is that VP loads DOF through B2S (is it any wonder this is such a huge pain to set up? ).   So the B2S setup is the place to look for the problem, I think.

 

You wouldn't believe the number of times a DOF problem turns out to be multiple copies of B2S installed, so you might start there as a sanity check.  The MSI installer should eliminate that whole issue, because it looks up the active registered B2S DLL, but there might be some other case I didn't think of.

 

If you only have one copy of B2S installed, it should presumably be in your Visual Pinball\Tables folder.  Check what's in the Plugins folder under that.  There should probably just be a single file called DirectOutput (no spaces) that's a shortcut to your DirectOutput install folder.

 

Finally, do you have any SPACE characters anywhere in the path names involved in the Visual Pinball, B2S, or DirectOutput installations?  I've had one report that space characters in the path names can make these secondary DLL loads fail. 

[coreduo0099]

 

 

 

started from scratch. used the msi, installed DOF 6.2, dof config files, and moved my cabinet xmls back over. Same issue.

I've searched for duplicates of dlls and can't find any.

with the fresh install, same thing fx2 is good, fx3 is good, future pinball good, pinballx menus are good, vp9 and vpx give the same message.

 

The difference between VP and everything else is that VP loads DOF through B2S (is it any wonder this is such a huge pain to set up? ).   So the B2S setup is the place to look for the problem, I think.

 

You wouldn't believe the number of times a DOF problem turns out to be multiple copies of B2S installed, so you might start there as a sanity check.  The MSI installer should eliminate that whole issue, because it looks up the active registered B2S DLL, but there might be some other case I didn't think of.

 

If you only have one copy of B2S installed, it should presumably be in your Visual Pinball\Tables folder.  Check what's in the Plugins folder under that.  There should probably just be a single file called DirectOutput (no spaces) that's a shortcut to your DirectOutput install folder.

 

Finally, do you have any SPACE characters anywhere in the path names involved in the Visual Pinball, B2S, or DirectOutput installations?  I've had one report that space characters in the path names can make these secondary DLL loads fail. 

 

One copy of B2S in my \Tables

I also have a plug in for PUP videos

I do have a space, which has never caused issues, but maybe that explains the intermittent (mostly fail) for the new Extension.dll

scraping my registry for all occurances of the old path and replacing the space with _

....back soon after a reboot and test I hope...

[coreduo0099]

scraping my registry for all occurances of the old path and replacing the space with _

....back soon after a reboot and test I hope...

 

 

Well 6 hours later of editing registry values, startup tasks, scripts, etc. exactly the same behavior.  6.11 works fine with old framework with VPinball, R3++ not working 99% of the time with Visual pinball on my rig.. 

[mjr]

 

scraping my registry for all occurances of the old path and replacing the space with _

....back soon after a reboot and test I hope...

 

 

Well 6 hours later of editing registry values, startup tasks, scripts, etc. exactly the same behavior.  6.11 works fine with old framework with VPinball, R3++ not working 99% of the time with Visual pinball on my rig.. 

 

Sorry that was a wild goose chase...  did you try a fresh install of the MSI now that all of the paths are fixed up?

 

And you said "99% of the time"???  Meaning it does work some of the time?  I'm really at a loss to know how that could be - seems like something's really screwy if it works some of the time and not other times with no configuration changes.  Configuration problems don't tend to come and go like that.  Maybe the problem has nothing to do with configuration and is something resource-related, like you're running out of memory, having file locking conflicts, something like that.

[psmiraglia]

[quote name="mjr" post="400965" timestamp="1519500266"][quote name="Findusone" post="400963" timestamp="1519499493"]
[quote name="psmiraglia" post="400960" timestamp="1519496261"]
 

http://mjrnet.org/pi...ed-rollback.zip
http://mjrnet.org/pi...ed-rollback.msi[/quote]

Same results. Random fires within PBX. Probably within VP too, but I cannot tell for sure.

[coreduo0099]

Sorry that was a wild goose chase...  did you try a fresh install of the MSI now that all of the paths are fixed up?

 

And you said "99% of the time"???  Meaning it does work some of the time?  I'm really at a loss to know how that could be - seems like something's really screwy if it works some of the time and not other times with no configuration changes.  Configuration problems don't tend to come and go like that.  Maybe the problem has nothing to do with configuration and is something resource-related, like you're running out of memory, having file locking conflicts, something like that.

 

not fresh, but re-installed the msi

by 99% i was referring to my F3 comment... On a few games, I hit F3 a few times and a few times I got lucky and the DOF kicked in when the backglass re-loaded.

[mjr]

not fresh, but re-installed the msi

 

 

by 99% i was referring to my F3 comment... On a few games, I hit F3 a few times and a few times I got lucky and the DOF kicked in when the backglass re-loaded.

 

 

That's just weird, but it does point in a different direction, like I said.  Think about this:  if it were a missing file, would it EVER work, even .00001% of the time?  Is there any way that missing file would randomly pop into existence .00001% of the time when you press F3?  Same question for a path wrong in the registry, corrupted file, or wrong file version.  Seems to rule out all of the things we've been trying to chase down.

 

The thing that does come and go, sometimes without an apparent pattern, is resource errors:  out of memory conditions, file locks, that kind of thing.

 

But unfortunately that doesn't give me any ideas for what's going wrong - this doesn't look like any of the usual DOF problems.  Do you have any other software running in your system that could be somehow locking out DOF?  I can't think of anything that would that effect, but this is so weird I'm just throwing out random ideas.  You said the new DOF was working for a while when you first installed it a while back, and then stopped, right?  Did anything else in your system change around that same time, even something seemingly unrelated to DOF?

[coreduo0099]

 

not fresh, but re-installed the msi

 

by 99% i was referring to my F3 comment... On a few games, I hit F3 a few times and a few times I got lucky and the DOF kicked in when the backglass re-loaded.

 

 

That's just weird, but it does point in a different direction, like I said.  Think about this:  if it were a missing file, would it EVER work, even .00001% of the time?  Is there any way that missing file would randomly pop into existence .00001% of the time when you press F3?  Same question for a path wrong in the registry, corrupted file, or wrong file version.  Seems to rule out all of the things we've been trying to chase down.

 

The thing that does come and go, sometimes without an apparent pattern, is resource errors:  out of memory conditions, file locks, that kind of thing.

 

But unfortunately that doesn't give me any ideas for what's going wrong - this doesn't look like any of the usual DOF problems.  Do you have any other software running in your system that could be somehow locking out DOF?  I can't think of anything that would that effect, but this is so weird I'm just throwing out random ideas.  You said the new DOF was working for a while when you first installed it a while back, and then stopped, right?  Did anything else in your system change around that same time, even something seemingly unrelated to DOF?

 

Yeah, I agree, for a dedicated cabinet that was working damn well, this is very bizzarre.  Now to add to it, in PinballX, If i try to run a table multiple times.. FX2 gives a D3D error and VPX (for example I picked Old Coney Island) tells me to check the rom path.  But if I don't use PinballX all is fine.  I have a cloned boot drive and backups of DOF.  I may go back to it if I don't have a breakthrough soon.  The only change was installing the new DOF3++/DOF6.20 and FX3.

 

Oh, at one point last night, I'd run a table and DOF thought my flippers were being held down and started firing the flipper solenoids.. rebooting solved that one..  Just darn bizzarre.

 

Oh and when the F3 made the backglass work, coincidently the DMD position settings got hosed in the registry and defaulted back to my playfield screen....

Edited by coreduo0099, 25 February 2018 - 10:01 PM.

[TerryRed]

Finally got around to updating both DOF R3++ and DOFLinx 6.22.

 

Did a fresh install (but didnt change registry...don't know how) of DOF R3++ using mjr's installer..  Just created new GlobalConfig for DOF R3++, and copied over my cabinet.xml files, and updated with DOF Config Tool. Installed DOFLinx 6.22 and copied over my DOFLinx.ini (and my own SUP files), and that was it!

 

FP, VPX, FX3, Pinball X all updated and working beautifully as is PinUP Player with DOFLinx.  New FX3 table look great with feedback and lighting....  again, thanks for your hard work guys!

 

I have one Led-Wiz, and a Teensy.

 

 

The only thing you are missing mjr, are my updates to the following file:

 

DirectOutputShapes.xml

 

...for addressable leds.

 

 

I updated that file to now include "shapes" for letters, numbers and other characters. Arngrim added these into DOF Config Tool as well (to use the new variables I made to work with these updates), and he includes the new updated files (DirectOutputShapes.xml, DirectOutputShapes,png) whenever you generate new config files.  It would be good to include the updated file with your installer and zip. You can just use the version Arngrim includes with DOF Config Tool.

 

Thanks again.

Edited by TerryRed, 26 February 2018 - 12:37 AM.

[coreduo0099]

 

 

not fresh, but re-installed the msi

 

by 99% i was referring to my F3 comment... On a few games, I hit F3 a few times and a few times I got lucky and the DOF kicked in when the backglass re-loaded.

 

 

That's just weird, but it does point in a different direction, like I said.  Think about this:  if it were a missing file, would it EVER work, even .00001% of the time?  Is there any way that missing file would randomly pop into existence .00001% of the time when you press F3?  Same question for a path wrong in the registry, corrupted file, or wrong file version.  Seems to rule out all of the things we've been trying to chase down.

 

The thing that does come and go, sometimes without an apparent pattern, is resource errors:  out of memory conditions, file locks, that kind of thing.

 

But unfortunately that doesn't give me any ideas for what's going wrong - this doesn't look like any of the usual DOF problems.  Do you have any other software running in your system that could be somehow locking out DOF?  I can't think of anything that would that effect, but this is so weird I'm just throwing out random ideas.  You said the new DOF was working for a while when you first installed it a while back, and then stopped, right?  Did anything else in your system change around that same time, even something seemingly unrelated to DOF?

 

Yeah, I agree, for a dedicated cabinet that was working damn well, this is very bizzarre.  Now to add to it, in PinballX, If i try to run a table multiple times.. FX2 gives a D3D error and VPX (for example I picked Old Coney Island) tells me to check the rom path.  But if I don't use PinballX all is fine.  I have a cloned boot drive and backups of DOF.  I may go back to it if I don't have a breakthrough soon.  The only change was installing the new DOF3++/DOF6.20 and FX3.

 

Oh, at one point last night, I'd run a table and DOF thought my flippers were being held down and started firing the flipper solenoids.. rebooting solved that one..  Just darn bizzarre.

 

Oh and when the F3 made the backglass work, coincidently the DMD position settings got hosed in the registry and defaulted back to my playfield screen....

 

Looks like i missed 6.22 was out.. I'll try that too.

I re-scanned my registry, uninstalled/reinstalled some things and found that going back to pinballx 2.50 eliminated the issues of programs not launching a 2nd time. (I forgot I updated pinballx to current)

Which pinballx ver are you guys using?

I also found this when testing an ultradmd table (americas most haunted).. UDMD startup logo would display with backglass, then this...

https://ibb.co/jLW2Vx

[DDH69]

@coreduo0099

 

I am following your saga, just don't have much of value to add.  If anything comes to mind as I read your journey I will post.  In the meantime, in answer to your versions question.

 

Latest PinballX

DOF R3++ initial release

Win 10 current updates

DOFLinx 6.22 (shouldn't make any difference from 6.20)

2 x LEDWiz, 1 x Pinscape in native mode, 1 x Teensy

[coreduo0099]

@coreduo0099

 

I am following your saga, just don't have much of value to add.  If anything comes to mind as I read your journey I will post.  In the meantime, in answer to your versions question.

 

Latest PinballX (went back to 2.50)

DOF R3++ initial release

Win 10 current updates (windows7pro upgreade system)

DOFLinx 6.22 (shouldn't make any difference from 6.20)

2 x LEDWiz, 1 x Pinscape in native mode

Thanks.. edits above

 

After lots of frustration, I swapped back to my 6.11 DirectOutput folder by simply renaming both (swapping the active one) .. All works great (my PROC tables too).  Figuring all MUST be fixed, I just did another clean DOFLinx/DOF R3++/DOFConfig as Terry did.

Still that same error about Extensions.dll not loading with Vpinball.  Super Bizarre.

 

I'm thinking there is some dependency for Extensions.dll that my system has a problem with. (e.g. some .Net version or something I need as a Pre-requisite?) The file is installed by your msi, so it must be correct.  Is Vpinball the only setup that leverages Extensions.dll or do FX2 and FX2 backglasses do as well?

 

If you can think of anything, I'll check back Thursday or Friday when i can tinker again.

 

Since I get the error with just launching VpinballX and any DOF table, I don't see how PinballX can be part of the issue.

(BTW, I un-installed and reinstalled PinballX, VPinball, fresh DOFOutput fully configured folder, PUP during all of this where 6.11 works fine.)

 

BTW, I noticed the readme mentioned a 6.12 but I can't find the file anywhere.. I figured I'd update it in case that is as far as I can go for a while....

Edited by coreduo0099, 26 February 2018 - 08:10 AM.