490 replies to this topic

[bellatrixzen]

Ok, I can install it ASAP. But, I dont really run VP. I run FP, PBA Arcooda, and FX3.

It is installed, but I dont really have any tables going.

 

I will report back after the house full of people have left.

 

Thanks again to everyone contributing!!

 

And Happy Thanksgiving to those who celebrate it!

[mjr]

Ok, I can install it ASAP. But, I dont really run VP.

 

Well, just use whatever you used to generate the last DOF log, then.

[zebulon]

The +GP has a gamepad button array (16 inputs) as well as the 16 outputs under the ledwiz vid and pid.  I found it strange that it would pop on the +GP but a regular ledwiz would be picked up.

 

Are you filtering by device name in the verification scans?  I'll fire up the +GP and have a look when I get to the shop tomorrow.

[zebulon]

Here's a descriptor dump mjr, should give you what you need.

 

 

Attached Files

•  DescriptorDump_LED-Wiz+GP_1.txt   2.27KB   13 downloads

[bellatrixzen]

Ok, so I installed the test build and for some very strange reason I get no logging at all now.

Not sure how I accomplished that, but yeah.....

 

Thanks mjr & zeb for your efforts, it is appreciated

[mjr]

Here's a descriptor dump mjr, should give you what you need.

 

Thanks... but wouldn't you know it, it's missing the one thing that DOF is looking for.  DOF wants to know about the parsed HID report structure, which your tool isn't drilling into, unfortunately.  If you have a chance to grab a log from the instrumented DOF I posted, that should have the information.

[zebulon]

No problem, I'll bring the GP home tonight so that I can get that info for you.  I don't need it but it might make life easier for those who are using them.

[bellatrixzen]

Corrected my problem by just installing a regular LedWiz as I didn't need the gamepad inputs on the +GP anyway.

Thanks for the help fellas!

[zebulon]

Sorry guys, been meaning to post this.

 

Here's the info you wanted mjr ...

2018.12.20 12:58:44.035 LedWiz-like device at VID=64250, PID=240, product string=LED-Wiz+GP 1, manufacturer string=GGG

 

 DirectOutput.zip   1.08KB   9 downloads

[mjr]

Sorry guys, been meaning to post this.

 

Here's the info you wanted mjr ...

DirectOutput.zip

 

Thanks!  That does indeed explain why it was getting filtered out.  I'll make the necessary changes in DOF and the replacement ledwiz.dll.

[zeenon]

Stumbled upon this thread by accident, but long story short my win7 cab crashed, but I have the entire data drive. (PBX, VP, VPX, FP and all the media/tables.)

Most likely going with win10 this time, and to be honest I havent messed with the cab since the early version of VPX came out. So now I have to relearn everything. I know I had DOF R2 running at the time, but looking at this thread there is a new version. I just need a little push in the right direction, after install win10, what is the order of installation? VPX, pinmame, then dof?

2 monitor setup with a pindmd/Vishay.

[Outhere]

New setup And more

https://www.vpforums...=40867&p=413287

All-in-one VPX, Some Games, then dof? --> yes

42. DOF Setup

http://mjrnet.org/pi...01602xx&sid=toc

[mjr]

 

Sorry guys, been meaning to post this.

 

Here's the info you wanted mjr ...

DirectOutput.zip

 

Thanks!  That does indeed explain why it was getting filtered out.  I'll make the necessary changes in DOF and the replacement ledwiz.dll.

 

Well, somehow I got distracted and didn't get around to actually releasing that update.  I just did - it's at the usual place:

 

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

 

Hopefully that'll fix the LedWiz+GP recognition issue.

[Phazer51]

 

 

Sorry guys, been meaning to post this.

 

Here's the info you wanted mjr ...

DirectOutput.zip

 

Thanks!  That does indeed explain why it was getting filtered out.  I'll make the necessary changes in DOF and the replacement ledwiz.dll.

 

Well, somehow I got distracted and didn't get around to actually releasing that update.  I just did - it's at the usual place:

 

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

 

Hopefully that'll fix the LedWiz+GP recognition issue.

 

 

EXCELLENT! A new DOF update just as I have to reinstall EVERYTHING on my cabinet after a hard drive failure.

 

Thank you, MJR.

[mjr]

EXCELLENT! A new DOF update just as I have to reinstall EVERYTHING on my cabinet after a hard drive failure.

 

See, there's always a silver lining.  

[scottacus]

HI Mike, I installed the latest version of the DOF R3 64 bit version and used the MSI.  I received the error from the installer that it couldn't set up the DirectOutput plugin for PinballX automatically and that I should refer to the R3 docs for details to manually install it. 

 

I just tried PinballX and DOF is working fine, I'm not sure what the error was about?

Edited by scottacus, 07 February 2019 - 12:06 AM.

[mjr]

HI Mike, I installed the latest version of the DOF R3 64 bit version and used the MSI.  I received the error from the installer that it couldn't set up the DirectOutput plugin for PinballX automatically and that I should refer to the R3 docs for details to manually install it. 

 

I just tried PinballX and DOF is working fine, I'm not sure what the error was about?

 

Did you happen to note the "Error details" section?  That has the technical information on where the process failed; it's hard for me to guess without that.

 

Given that it seems to be working for you, I'd probably just not worry about it.  If you want to try tracking it down,though, you could give it another run with a command line like this, to generate a full log file:

 

   DirectOutput-xxx.msi /l*v logfile.txt  

[scottacus]

Here is the error message for you 

[mjr]

Here is the error message for you [image]

 

Well, it's annoying that Setup cuts off the important part of the message at the end.  What it's trying to say is "Setup was unable to update the PinballX settings file", and then show you the system error message explaining why.   But of course we can't guess at what that error actually is since it's getting cut off.

 

If you run it with the command line parameters I mentioned earlier (that "/L*V" business), it should capture the full message to the log file. 

 

I'm guessing that you have PinballX set up in a read-only folder, or under a protected system folder like Program Files, or something like that - something that's blocking Setup from writing the .ini file.  But you probably don't actually need to update the .ini file in the first place.  What it's doing is adding the DOF plugin section.  You probably already have that in your .ini file.  That's why it's working despite the error.  But if you have the time to investigate further, it would be worth getting the full error message to double-check that there's not something more problematic going on with Setup.

[scottacus]

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"

 

I'm sure I messed up something here, I am not very facile at the command prompt...