37 replies to this topic

[fichtenelch]

Hi, I am new to the virtual pinball hobby and first of all I want to say hi and thank you very much to the whole community and all the people who contributed to such to this fun hobby!

 

I am currently building my first virtual pinball and I am using MJR's Pinscape Build Guide as a reference for that. Things are going wekk, but I am having some problems getting my output controller to control more than 32 toys.

 

About the controller: The controller is a Pinscape compatible controller that I got from https://www.tindie.c...controller-kit/. It seems to be rather exotic, in retrospect I would have chosen a more common controller. But it is what it is for now and many things are already working very well.

 

About my software installation: I installed VPX 32 bitm B2S and DOF on a Windows 11 machine. I got B2S from the VPForums from https://www.vpforums...&showfile=12553. Regarding DOF I am using the MJR's version from http://mjrnet.org/pi...ll-updates.html. I can confirm that DOF works as B2S server plugin as described at http://mjrnet.org/pi...#VerifyDofSetup.

 

I use the DOF configuration as attached in DOF Configtool.pdf. I can control all toys using the Pinscape Config tool, including those with ports >32. When I start a table, e.g. the DOF test table, all toys up to port 32 are active, but the toys with ports >32 are not used.

 

As far as I understand DOF should detect the Pinscape controller and make use of more than 32 ports.  The DirectOutput.log (see below) shows that a Pinscape and an LEDWiz device are detected. The Cabinet Configuration frontend of DOF shows only 32 as "Output Count" (see also attachments). 

 

I suspect I have done something wrong with the DOF or Pinscape configuration.
Do you see any obvious points that seem suspicious in the config or logs?
Are you missing any important information to get further insights into possible causes for error?

 

Regards,

Florian


DirectOutput.log:
---------------------------------------------------------------------------------

DirectOutput Version 3.1.7776.42172, built 2021.04.16 23:25

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

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

2024.08.30 11:13:26.374 DirectOutput Logger initialized

2024.08.30 11:13:26.361 Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"

2024.08.30 11:13:26.374 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2024.08.30 11:13:26.375 Loading Pinball parts

2024.08.30 11:13:26.375 Loading cabinet

2024.08.30 11:13:26.375 No cabinet config file loaded. Will use AutoConfig.

2024.08.30 11:13:26.375 Cabinet auto configuration started

2024.08.30 11:13:26.627 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.628 Pinscape Controller USB error reading from device: Der angegebene Benutzerpuffer ist für den angeforderten Vorgang nicht zulässig (Win32 error 1784)

2024.08.30 11:13:26.637 Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01

2024.08.30 11:13:26.637 Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 32

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

2024.08.30 11:13:26.648 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.655 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.661 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.667 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.672 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.678 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2024.08.30 11:13:26.683 LedWiz-like device at VID=5218, PID=31893, product string=MYSTIC LIGHT , manufacturer string=MSI

2024.08.30 11:13:26.689 LedWiz-like device at VID=64250, PID=240, product string=Pinscape Controller, manufacturer string=mjrnet

2024.08.30 11:13:26.689 HID caps: usage page=1, usage=4, number of link collection nodes=1, output report byte length=9

2024.08.30 11:13:26.695 LedWiz-like device at VID=64250, PID=240, product string=Pinscape Controller, manufacturer string=mjrnet

2024.08.30 11:13:26.695 HID caps: usage page=12, usage=1, number of link collection nodes=1, output report byte length=0

2024.08.30 11:13:26.696 Opening 32-bit LedWiz driver...

2024.08.30 11:13:26.697 Detected and added LedWiz Nr. 1 with name LedWiz 01

2024.08.30 11:13:26.697 Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1

2024.08.30 11:13:26.699 Cabinet auto configuration finished

2024.08.30 11:13:26.699 Cabinet loaded

2024.08.30 11:13:26.699 Loading table config

2024.08.30 11:13:26.699 Warning: No table config file found. Will try to load config from LedControl file(s).

2024.08.30 11:13:26.699 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm_113b

2024.08.30 11:13:26.701 Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig51.ini

2024.08.30 11:13:26.706 Min DOF Version is 0.8 for file directoutputconfig51.ini

2024.08.30 11:13:26.706 Resolving Tables Variables

2024.08.30 11:13:26.707 Resolving Global Variables

2024.08.30 11:13:27.011 Failed: 117

2024.08.30 11:13:27.011 Warning: Cant parse the trigger part 117 of the ledcontrol table config setting 117.

2024.08.30 11:13:27.011 EXCEPTION: Could not parse setting 117 in column data E104/117.

2024.08.30 11:13:27.011 EXCEPTION: Thread: 

2024.08.30 11:13:27.011 EXCEPTION: Message: Exception --> Cant parse the part 117 of the ledcontrol table config setting 117.

2024.08.30 11:13:27.111 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)

2024.08.30 11:13:27.111 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)

2024.08.30 11:13:27.111 EXCEPTION: Stacktrace:    bei DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)

2024.08.30 11:13:27.111 EXCEPTION: Targetsite: Void ParseSettingData(System.String)

2024.08.30 11:13:27.111 Warning: Previous exceptions occured in the line men_in_black,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,E101,E102/E123,E103,E104/117,0,E108 I16/E124 I16/E136 I16,E119,0,0,E110,E109,E107,E122 I60 of the ledcontrol file

2024.08.30 11:13:27.436 1 directoutputconfig.ini or ledcontrol.ini files loaded.

2024.08.30 11:13:27.437 Config for RomName afm_113b exists in LedControl data. Updating cabinet and config.

2024.08.30 11:13:27.540 Table config loading finished: romname=afm_113b, tablename=Attack From Mars (Bally 1995)

2024.08.30 11:13:27.541 Pinball parts loaded

2024.08.30 11:13:27.541 Starting processes

2024.08.30 11:13:27.541 Initializing cabinet

2024.08.30 11:13:27.541 Debug: Initializing output controllers

2024.08.30 11:13:27.542 Pinscape Pinscape Controller 01 intialized and updater thread started.

2024.08.30 11:13:27.543 Debug: Initializing LedWiz Nr. 01

2024.08.30 11:13:27.543 Pinscape Pinscape Controller 01 updater thread  started.

2024.08.30 11:13:27.543 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.

2024.08.30 11:13:27.544 LedWiz Nr. 01 initialized and updater thread initialized.

2024.08.30 11:13:27.544 Debug: Output controllers initialized

2024.08.30 11:13:27.544 Updater thread for LedWiz 01 started.

2024.08.30 11:13:27.546 Cabinet initialized

2024.08.30 11:13:27.549 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml

2024.08.30 11:13:27.608 Framework initialized.

2024.08.30 11:13:27.608 Have fun!

2024.08.30 11:16:42.148 Finishing framework

2024.08.30 11:16:42.149 Finishing cabinet

2024.08.30 11:16:42.150 Debug: Finishing output controllers

2024.08.30 11:16:42.152 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.

2024.08.30 11:16:42.154 Pinscape Pinscape Controller 01 finished and updater thread stopped.

2024.08.30 11:16:42.154 Debug: Finishing LedWiz Nr. 01

2024.08.30 11:16:42.154 Updater thread for LedWiz 01 terminated.

2024.08.30 11:16:42.156 LedWiz Nr. 01 finished and updater thread stopped.

2024.08.30 11:16:42.156 Debug: Output controllers finished

2024.08.30 11:16:42.156 Cabinet finished

2024.08.30 11:16:42.156 DirectOutput framework finished.

2024.08.30 11:16:42.156 Bye and thanks for using!

2024.08.30 11:18:56.441 Debug: Disposing LedWiz instance 01.

 

Attached Files

•  DOF Configtool.pdf   349.36KB   6 downloads
•  Screenshot 2024-08-30 114532.jpg   88.43KB   1 downloads

Edited by fichtenelch, 02 September 2024 - 12:10 PM.

[fhjui]

I have seen today that mjr has yesterday published a new firmware and dof version because of errors. I hope you have the old firmware 2021-12-22. I dont know the new one and its beta in the moment

yes, there are only 32 ports detected:

2024.08.30 11:13:26.637 Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 32

• at first you should fix the usb errors, the original message is ERROR_INVALID_USER_BUFFER, check the windows system and app. log for further errors
  I don't know how to fix this error but I doubt that is the cause. But the first presumption is to have an error-free system
• copy for the sake of order the default cabinet.xml from the example dir. to the dof config dir.
• I have downloaded the Pintronix config file and imported it to my pinscape. Then in the dof log the 46 defined outputs are recognized
  export your pinscape-config file with pinscape config tool, open the file using an editor and check if the 44 outputs you have defined are listed.
  that shows up like this:
  # 255[46] = outputs[46]:{port:{type:4,pin:7},flags:18,flipperLogic:240}

added:

First, the number of outputs defined on the KL25Z are read out. The rest of the DOF log is not so important at first

Edited by fhjui, 02 September 2024 - 03:52 PM.

[mjr]

It looks like you have the latest Pinscape firmware, which turned up a bug that was lurking in the DOF Pinscape driver (I wrote the DOF code in question - not trying to deflect blame!).  There should be two ways to solve it:

 

- Either install the older Pinscape firmware (2021-12-22), as fhjui suggested...

 

- Or grab the latest DOF (2024-09-01), which fixes the DOF bug so that you can use the newest firmware

 

The new DOF release also has some other changes (mainly support for combined 32/64-bit installs), so it's actually a nice upgrade all by itself, but it's new enough that it hasn't had much testing yet.  If you're comfortable experimenting with a newer release, I'd recommend trying the new DOF - if it doesn't work property for you, you can just roll it back to an older version.  If you don't want to take a risk on a brand new release, the safest fix is to roll back to the older Pinscape firmware - that's a good stable release, and you can keep your existing stable DOF install.

Edited by mjr, 02 September 2024 - 06:41 PM.

[fhjui]

@mjr: many thanks for your hint.

I have installed the new firmware, and the usb errors occured as seen above, only 32 outputs were recognized.

After I installed the new versions dof and config tool, the errors are gone and pinscape recognizes all outputs again.

thanks

Edited by fhjui, 02 September 2024 - 06:33 PM.

[mjr]

Great - glad that fixed it.

 

The DOF problem was triggered because the new firmware changed the size of the HID report sent to the host, and DOF was (incorrectly) assuming a fixed size for that, so it got the USB errors you were seeing when it tried to read input from the device.  The new DOF fixes that by sensing the report size automatically, which is what it should have been doing all along, so that it can work with any past or future firmware version.

[fichtenelch]

Thank you so much for these clear directions!

 

I am happy with installing the new Firmware, Pinscape Config Tooland the updated DOF. I tried that just a moment ago. However, while the firmware update and and Config Tool update went through well, the DOF MSI installer Ends with an error - see also the attached Image.

 

@mjr: If you tell me what other information would be helpful for you to improve the installer, providing these Information would be the least I could do.

Attached Files

•  Screenshot 2024-09-02 215011.png   45.72KB   1 downloads

[mjr]

If you could run the installer again like this, it'll create a log.  

 

- Launch a CMD (DOS box) window

 

- CD to the folder containing the installer

 

- Type:   DirectOutput-mjr-x86-release-20240901.msi  /L*V setup.log

 

Or whichever .msi file is failing.  This should tell the installer to create a log file called setup.log in the current directory.  If you could shoot that to me (you can send it by private message here if you prefer), I'll take a look - hopefully it'll have the details on what went wrong.

[fichtenelch]

@mjr Got it. I just sent you a PM with the log file.

[mjr]

Thanks - I got the log.  The error is some internal error in Windows Setup trying to create a temporary file.  The strange thing is that this seems to be a known but in a NEWER version of the Setup build tool I use (a tool called WiX), and I know that because I ran into it myself after updating WiX.  The bug went away when I reverted back to the older WiX version, so I'm at a loss to understand why you're running into it now - the only explanation I can find of the error is "it's a bug in WiX, you have to use a different version", which I did.  I guess I'm going to have to dig into it deeper and find out what's really going on with the WiX bug; maybe it affects the older version too under some conditions.

[parallaxx]

Thanks - I got the log.  The error is some internal error in Windows Setup trying to create a temporary file.  The strange thing is that this seems to be a known but in a NEWER version of the Setup build tool I use (a tool called WiX), and I know that because I ran into it myself after updating WiX.  The bug went away when I reverted back to the older WiX version, so I'm at a loss to understand why you're running into it now - the only explanation I can find of the error is "it's a bug in WiX, you have to use a different version", which I did.  I guess I'm going to have to dig into it deeper and find out what's really going on with the WiX bug; maybe it affects the older version too under some conditions.

I have the same error during installation, probably due to Windows Defender. Will send you setup.log via PM

[mjr]

parallaxx - I think I see what's going on.  I accidentally left the link to the original DOF patch on the Pinscape Firwmare download page, but that patch was built with a newer version of WiX (the install builder tool I use) that has a known bug that makes the install fail.  I only discovered this after posting the patch.  The new full release on the DOF download page is built with a working version of WiX, so hopefully it'll install properly for you:

 

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

(I've also updated the link on the Pinscape Firmware page to point to the newer version, so anyone trying the patch link should get the newer version now.)

[fhjui]

@mjr:

I have installed the new DOF version on my dev-pc running win10 and MS-defender sucessfully. The installer couldn't find the b2ssettings.xml, but thats normal on all my PCs and is not important.

Only in the log are some msi errors "MSI © (50:44) [21:41:22:451]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1707"
 

yesterday I have it installed  an a win-11 PC with bitdefender, also with success.

If necessary I can send you the log from the above inst.

 

would it be a good idea that you create a new thread for this update issue ?

[fichtenelch]

I can confirm that the installers are working also on my machine, DOF and VPX are working as expected now. Thanks a lot!

[mjr]

That's great!

 

If anyone else runs into an install problem with the DOF patch, hopefully the latest release from the DOF updates page will fix it, but let me know if you run into any new problems with that.

Edited by mjr, 03 September 2024 - 08:32 PM.

[parallaxx]

Thanks, it works now. Where should I put directoutputconfig.ini file from DOF configtool for this new version?

 

C:\DirectOutput ?

C:\DirectOutput\X64 ?

 

Thanks

 

parallaxx - I think I see what's going on.  I accidentally left the link to the original DOF patch on the Pinscape Firwmare download page, but that patch was built with a newer version of WiX (the install builder tool I use) that has a known bug that makes the install fail.  I only discovered this after posting the patch.  The new full release on the DOF download page is built with a working version of WiX, so hopefully it'll install properly for you:

 

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

(I've also updated the link on the Pinscape Firmware page to point to the newer version, so anyone trying the patch link should get the newer version now.)

[mjr]

The config files all go in the usual places in the C:\DirectOutput main install folder.  Just use all of the traditional file locations, pretending that the x86 and x64 folders aren't there at all and that everything is in C:\DirectOutput.

So, for example, your Global Config files go in C:\DirectOutput\Config.

The various .ini files can go in the main install folder (C:\DirectOutput) or in the Config folder.

Edited by mjr, 04 September 2024 - 06:25 PM.

[DDH69]

@mjr thanks for the new combined version.  I'm just working through it with DOFLinx and a number of configurations.

 

I think there may be an issue with the new version and predefined shapes and letters for addressable LEDs not displaying.  Anything with SHPLetter? , flshmulo , strblft , etc - the items in the [Variables DOF] section of the directoutputXX.ini

 

I have a couple of folders setup, old and new.  Old works, new doesn't. 

 

If I copy just the new Directoutput.dll from \Directoutput\x64 to my old working folder then all addressable LED effects except those in the section I mention above work.

 

Happy to be guided or provide information required.

[mjr]

DDH69 - if you could look through the logs and see if you can find mentions of the affected files, that might pinpoint it.  It sounds like the new file searching rules (to look in the root install folder rather than the DLL folder) are missing some of those files.  It should just be a matter of identifying the specific files that it's missing and applying the new search rule.  DOF is about 99.5% constructed from the time-honored engineering practice known as "copy and paste", so any time you want to change something like this, you have to change it in a LOT of places in the code.

The log messages (if you can find them) are often helpful because they can serve as a good search key to look for the exact point in the code where it's going wrong.

[DDH69]

DDH69 - if you could look through the logs and see if you can find mentions of the affected files, that might pinpoint it.  It sounds like the new file searching rules (to look in the root install folder rather than the DLL folder) are missing some of those files.  It should just be a matter of identifying the specific files that it's missing and applying the new search rule.  DOF is about 99.5% constructed from the time-honored engineering practice known as "copy and paste", so any time you want to change something like this, you have to change it in a LOT of places in the code.

The log messages (if you can find them) are often helpful because they can serve as a good search key to look for the exact point in the code where it's going wrong.

 

Nothing erroneous in the directoutput.log .

 

I played around a bit more when you talked about the paths and found that copying DirectOutputShapes.xml and .png into the \DirectOutput\config folder resolved the issue.  From not working to working, the DirectOutput.Log is identical.

 

Not sure of the best fix here, really over to you.  My thoughts:

1. The lack of a log error message is likely problematic when fault finding going forward

2. Should the new installers place the two DirectOutputShapes files in the \DirectOutput\config folder instead of \DirectOutput

3. Should the search path when loading DirectOutputShapes.* be updated to include looking in \DirectOutput ?

[mjr]

The shapes stuff is a part I never use myself, so your input on how it's supposed to work is definitely helpful.  Given that the DirectOutputShapes.* files have always been installed in the main folder, I'd say we should keep the install as-is and fix the part of the code that searches for them.  If it's just the DirectOutputShapes.* files, it should be fairly easy to find all the places in the code where they're loaded.  I'll definitely add some logging while I'm at it - my guess is that DOF considers those files "optional", so it doesn't consider it worthy of a warning if they're not found.  But that's the wrong idea since it's not helpful for troubleshooting if you wanted them to be found.  My attitude on logging in DOF is the more the merrier, since it's so hard to debug something with no UI running in the background.