28 replies to this topic

[calrissian]

 

Adding a note in case it can help other people out there who have DOF issues on just a few original and EM tables and who have been pulling their hair like me...
Despite applying fix mentioned above, I still had a few original tables and EM tables where my DOF contactors / toys would not work with VPx 10.8 yet would work when opened with old versions (10.7.3)

It's most certainly a consequence of upgrading everything to 64bit and registering directoutputcomobject from the directoutput_x64 folder on top of the x86, which you shouldn't do and which has really weird side effects.
My understanding is that depending on how the "controller" script of a table is written, VPX may be fetching dof settings from registry keys of old VPX versions and ignoring the software settings.

So, on top of fixing the link to the correct folder in regedit, I also looked for the DOF version number and found out I still had 2 versions around : 3.1.7698.40088 and 3.1.8440.34790 .

I replaced all the keys with the latter version number and now it all works again.

 

Yes some people may be using old versions of DOF (32 bit).

 

I've always installed the latest DOF R3++ from mjr's site. For some people who had problems (while also updating to 64 bit DOF)... installing that version fixed their 32 bit DOF issues.

 

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

I'm suspicious that I may have registered 64-bit, or have a registry problem, but I'm not sure, and not sure how to fix.  Solenoids work on some of the Pinevent tables but not all.  Solenoids work on most VPX tables, but not on some of the newer original tables (so Big Bang Bar works fine, but not Die Hard or Futurama), running the latest 10.8 64-bit beta.  The trick is I'm never throwing the errors described above, so I never see those version numbers to hunt down in the registry.  Not sure then how to see if I have the 64-bit registered.

 

I have reinstalled 32-bit Dof from MJR just to be sure I didn't have an old version running.  Any ideas on things I should chase on this?

[TerryRed]

 

 

Adding a note in case it can help other people out there who have DOF issues on just a few original and EM tables and who have been pulling their hair like me...
Despite applying fix mentioned above, I still had a few original tables and EM tables where my DOF contactors / toys would not work with VPx 10.8 yet would work when opened with old versions (10.7.3)

It's most certainly a consequence of upgrading everything to 64bit and registering directoutputcomobject from the directoutput_x64 folder on top of the x86, which you shouldn't do and which has really weird side effects.
My understanding is that depending on how the "controller" script of a table is written, VPX may be fetching dof settings from registry keys of old VPX versions and ignoring the software settings.

So, on top of fixing the link to the correct folder in regedit, I also looked for the DOF version number and found out I still had 2 versions around : 3.1.7698.40088 and 3.1.8440.34790 .

I replaced all the keys with the latter version number and now it all works again.

 

Yes some people may be using old versions of DOF (32 bit).

 

I've always installed the latest DOF R3++ from mjr's site. For some people who had problems (while also updating to 64 bit DOF)... installing that version fixed their 32 bit DOF issues.

 

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

I'm suspicious that I may have registered 64-bit, or have a registry problem, but I'm not sure, and not sure how to fix.  Solenoids work on some of the Pinevent tables but not all.  Solenoids work on most VPX tables, but not on some of the newer original tables (so Big Bang Bar works fine, but not Die Hard or Futurama), running the latest 10.8 64-bit beta.  The trick is I'm never throwing the errors described above, so I never see those version numbers to hunt down in the registry.  Not sure then how to see if I have the 64-bit registered.

 

I have reinstalled 32-bit Dof from MJR just to be sure I didn't have an old version running.  Any ideas on things I should chase on this?

 

 

 

If you have DOFLinx installed and running, be sure it is not running at all when running FP PinEvent tables.

 

The way DOF is added to all PinEvent tables is the same (directly... same as Popper. No b2s server or doflinx used). So if one PinEvent table is working they should all work. However, PinEvent LITE tables will only have "basic" dof added. Solenoids, and minimal lighting.

[digitalarts]

Calrissian,
About your problem with the newer vpx tables: did you updated your dof config files ?

[calrissian]

Thanks to you both.  I do shut off Doflinx when running Pinevent tables, and I did update the Dof Config files.  I'm going to try loading a version of 10.7 and see if any of the "non-working Dof" tables work on them this weekend, and see if I'm actually replicating firebrand007's error above.  I thought, too of uninstalling Dof (both 32-bit and 64-bit) and reinstalling, but don't see how that would solve a registry problem if I created one.

 

That, or just enjoy the tables without the solenoids for awhile, right?!

[sus]

OMG first thank you Terry Red for such nice games but please add this note to your setup as this drove me nuts. Just mention about the 64bit reg. I am up and running because of this post.

[TerryRed]

OMG first thank you Terry Red for such nice games but please add this note to your setup as this drove me nuts. Just mention about the 64bit reg. I am up and running because of this post.

 

This issue is not a "FP issue"... its the result of a VPX 64 bit / DOF update done incorrectly.

 

 

That said, I included this problem and this solution in my "FAQ and Help Guide" in my FP and BAM Essentials AIO package update (2.2 just released), which everyone should be installing. (and everyone should be reading that guide if having problems)

Edited by TerryRed, 07 February 2024 - 06:24 PM.

[WadeZ]

Adding a note in case it can help other people out there who have DOF issues on just a few original and EM tables and who have been pulling their hair like me...
Despite applying fix mentioned above, I still had a few original tables and EM tables where my DOF contactors / toys would not work with VPx 10.8 yet would work when opened with old versions (10.7.3)

It's most certainly a consequence of upgrading everything to 64bit and registering directoutputcomobject from the directoutput_x64 folder on top of the x86, which you shouldn't do and which has really weird side effects.
My understanding is that depending on how the "controller" script of a table is written, VPX may be fetching dof settings from registry keys of old VPX versions and ignoring the software settings.

So, on top of fixing the link to the correct folder in regedit, I also looked for the DOF version number and found out I still had 2 versions around : 3.1.7698.40088 and 3.1.8440.34790 .

I replaced all the keys with the latter version number and now it all works again.

 

Can you please tell me what this means:" I replaced all the keys with the latter version number". I think I have the same problem and I get fixing the link to the correct folder in regedit but I don't know what "replacing the keys" means. Thank you.

[fhjui]

So, on top of fixing the link to the correct folder in regedit, I also looked for the DOF version number and found out I still had 2 versions around : 3.1.7698.40088 and 3.1.8440.34790 .

I replaced all the keys with the latter version number and now it all works again.

 

Can you please tell me what this means:" I replaced all the keys with the latter version number". I think I have the same problem and I get fixing the link to the correct folder in regedit but I don't know what "replacing the keys" means. Thank you.

 

These DOF programs numbers don't need to be the same versions, because they are separate programs, my vpin 32bit-DOF has 3.1.7698 und 64bit-DOF has 3.1.8440.34788, and that works without problems.

 

 

[LarryJ]

I'll add my own note to this thread as the registry search helped fix my problem with DOF not working with Popper.

 

I have both 32 and 64 bit DOF installed and there was only one registry entry pointing at the 32 bit version, but the file it was pointing at (DirectOutputComObject.dll) was missing.

 

I may have been able to do a re-install to fix, but I tracked down a 32 bit version of the dll and copied it to the DirectOutput directory and I now have DOF working in VPX and Popper.

Edited by LarryJ, 16 March 2024 - 06:19 PM.