490 replies to this topic

[mjr]

Hi Mike,  I put the msi file into the C drive, went in cmd, navigated to the c drive and entered c:\>DirectOutput-mjr-20190129.msi/l*v logfile.txt.,  I got "Error opening installation log file.  Verify that the specified log file exists and is writable"

 

Your C:\ folder is probably just write-protected - that's the usual way Windows sets things up.  If you specify a full path for logfile.txt that points to a writable folder, that should work.  Something like:

 

DirectOutput-mjr-20190129.msi  /l*v  C:\MyFolder\logfile.txt

[scottacus]

Here is the error log

 

I have no PinballX2 folder and when I look into the registry along that path there is no 53F4530D-802D-482A-86DD-F82D8EC5D615 for me to edit there.  The installer does make a PinballX2 folder and puts a plugins folder in it with DirectOutput PinballX Plugin.dll as the only file.

Attached Files

•  logfile.txt   200.22KB   5 downloads

Edited by scottacus, 08 February 2019 - 02:40 AM.

[mjr]

I have no PinballX2 folder and when I look into the registry along that path there is no 53F4530D-802D-482A-86DD-F82D8EC5D615 for me to edit there.  

 

Isn't Windows fun?  I'm going to make a wild guess that you're running 64-bit Windows, is that right?  If so, when you look with RegEdit, you need to look under this path:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

 

You could also just do a search (open RegEdit and press Ctrl+F) for 53F4530D - that'll turn it up.

 

What's going on is that Win64 sticks that extra Wow6432Node path element into certain keys that relate to 32-bit EXEs.  Win64 does that on the sly, so that programs like Setup don't see them.  That's why Setup reports the key without the \Wow6432Node\ element - Setup truly thinks it's looking at the key it lists in the log, but Windows is secretly changing the key behind Setup's back.  You see the true key when you use RegEdit.  I've spent many hours on wild goose chases thanks to this nefarious little trick.

 

If you want to learn more about the gory technical details, check out "Registry Redirector" in the Windows SDK docs:

 

https://docs.microso...stry-redirector

 

I suspect you just have some old registry cruft from a past install.  Is it possible that at some point in the past you might have renamed some folders, and didn't uninstall and reinstall all of your software when you did that?

Anyway, if you want to clear it up, your best bet is to probably go through a manual uninstall-reinstall cycle for PinballX to remove the old registry cruft.

 

- Run the "Add or remove programs" control panel

- Select PinballX

- Uninstall

- Download the PinballX installer

- Run it to do a fresh install

 

You might also be able to do a "Repair" operation from the "Add or remove programs" panel, if the PBX installer allows that.

Or you could just manually fix up the key so that it points to your current install folder.  I'd go that route myself, but it might not be the only thing screwed up there so you might want to check the related entries to make sure everything looks right.

[scottacus]

Fixed the registry keys and now it installs perfectly with no errors.  Man Mike you are a Windows genius!

[widget2k13]

hi, sorry to jump in on this post , i am having issues, and have had issues for months since building my cab with delays and non firing of my contractors and have never got to the bottom of it yet.

i have pincontrol 2 board and it seems to work fine in fx3, vp9, proc etc but vpx it randomly doesn't fire or delays and sometime can feel the contractors sticking on, 

i am not that clued up with the software side of things and most of the time it has been installed remotely by someone that knows his stuff and he said its all fine.

i am at a total loss as what to do and even thinking of pulling the pc2 board out and starting from scratch with a different controller, the maker of the board has tried to help me for a long time and now has tested a few of his own cabs with the same results. 

[mjr]

hi, sorry to jump in on this post , i am having issues, and have had issues for months since building my cab with delays and non firing of my contractors and have never got to the bottom of it yet.

i have pincontrol 2 board and it seems to work fine in fx3, vp9, proc etc but vpx it randomly doesn't fire or delays and sometime can feel the contractors sticking on, 

i am not that clued up with the software side of things and most of the time it has been installed remotely by someone that knows his stuff and he said its all fine.

i am at a total loss as what to do and even thinking of pulling the pc2 board out and starting from scratch with a different controller, the maker of the board has tried to help me for a long time and now has tested a few of his own cabs with the same results. 

 

If it's working well in other programs that don't use DOF, I think you're right to suspect the problem is on the DOF side.  

 

I'm afraid I don't have a pincontrol board myself, so I can't do anything in the way of testing or troubleshooting it.  Is anyone else using a pincontrol with DOF?  Are there any known DOF issues with it or anything special you have to do to get it working?

 

You might try experimenting with different DOF versions to see if that makes any difference.  I'd try maybe the official DOF R2 release, one of the DOF R3 betas, and my two follow-on releases (R3+ and R3++).  Looking at the commit history for the pincontrol code specifically, it's only had a couple of superficial changes since the original code in R2, so I'm not too hopeful that you'll find different behavior across the versions.  But other parts of DOF have changed more substantially across those versions, so there's an outside chance that there's some bad interaction with some seemingly unrelated change elsewhere in DOF.

[widget2k13]

thanks mjr 

i have tried other older dof versions with no difference to the outcome

think ive hit a brick wall with this now 

[mjr]

thanks mjr 

i have tried other older dof versions with no difference to the outcome

think ive hit a brick wall with this now 

 

Okay, good that you tried, anyway - I thought it would be worth checking in case something got broken accidentally by an unrelated change.  But like I said, the code that's actually specific to that device is pretty much the original code from 2014, so I wasn't expecting any differences.

 

I can't think of what else to try.  I assume you've looked over the DOF logs to see if there are any errors reported?  Probably not given that you're only seeing sporadic problems, but it might be worth checking if you haven't already done so.

[widget2k13]

i haven't checked any logs as i never knew there was any, i think what the problem is the contractors are taking too long to release after they have fired because i can see them staying on meaning that they are not ready in time to fire again when the next bumper/target etc is hit but i know nothing about any of this so im just really guessing 

[mjr]

i haven't checked any logs as i never knew there was any, i think what the problem is the contractors are taking too long to release after they have fired because i can see them staying on meaning that they are not ready in time to fire again when the next bumper/target etc is hit but i know nothing about any of this so im just really guessing 

 

That's plausible.  DOF is faster than the legacy interfaces because it doesn't block the client program on USB I/O.  Contactors definitely have a relatively long minimum cycle time because of the physical motion involved.  If you want to test this idea, you could temporarily replace your contactors with LEDs and see if they suffer from the same problem.  LEDs can respond pretty much instantaneously (at least on the time scales we're talking about here), so if they show the same laggy behavior, it would rule out the contactors as the issue.

[widget2k13]

good suggestion mate , i may swap a couple of ports around and try that to rule it out

[widget2k13]

ok small update, tried with leds and there is no delay that i can see, i also tried the contractors direct and there seems to be very little to no delay when doing them direct to power, its almost as if something is telling them to stay on longer or is not turning them off quick enough ?

[STV]

Even tho they seem to work fine in vp9 I'm curious what model # contactors you're using.    I'm using something like this:  SIEMENS CONTACTOR 3RH1140-1AK60

[widget2k13]

mine ar siemens contractors also 3ra1120-igc24-0bb4

[widget2k13]

mjr do you sell pinscape boards and expansion boards etc ? i tried to pm you but it said i was not allowed 

[Phazer51]

mjr do you sell pinscape boards and expansion boards etc ? i tried to pm you but it said i was not allowed

You need the FRDM-KL25Z board and then use mjr's instructions to flash it as a "Pinscape Controller."

NXP SEMICONDUCTOR FRDM-KL25Z Freedom Development Platform, Kinetis L MCU, KL25, 48MHz, 128KB Flash - 1 item(s) https://www.amazon.c...i_qJiCCb9TECH6B

[widget2k13]

thanks, its the expansion boards and components needed for them im stuck on 

[djrino]

Hi im new on this so sorry if was already explained..

i use future pinball so i have downloaded tron legacy table ant i need to install the DOFLinx ..

 

on explanation file i see that i need to have this situation 

 

----------------------------------------------------------------------------

Installation

1) Find the folder on your system containing DOF, ie C:\DirectOutput. It will be the folder with

DirectOutput.dll, ledwiz.dll, ftd2xx.dll, pacdrive.dll in it.

2) Unpack the DOFLinx Vx.x.zip into this folder.

3) Edit the supplied DOFLinx.INI or create your own for your setup.

 

----------------------------------------------------------------------

 

on my system i not have the folder mentioned on installation guide and i have searched the dll and not have it.. i'm using win10 on my cabinet..

So what i need to to to install it???

im a littel confused any help is apreciated Tnx

[mjr]

Try here:

 

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

 

See the DOF section - use "DOF Windows Setup Installer (MSI)".  Ignore the LEDWIZ.DLL section.

[widget2k13]

ok installed pinscape with mosfet boards and all i can say is that im blown away with the dof now, i thought it was good but man this is awesome with pinscape no delays no misfires nothing just perfect.

thank you so much mjr for all your work.

 

only small problem i have is the launch button on my cab will not launch the ball in fx3 for some reason, its set as enter key and works as an enter key no problem when selecting etc in fx3 but just will not launch the ball, if i press enter on the keyboard it works fine, if i change the launch key in fx3 to my start button for example it works fine, its got me puzzled to say the least.