Content Provider CarnyPriest Posted December 7, 2024 Content Provider Posted December 7, 2024 The offline installer accesses the master branch of the game code repository. There is another branch that has native support for pin2dmd. You could try to download and replace the existing game code with the alternate code. From there, I don't know if support is automatic or if there is something else that needs to be done. I don't have the hardware, so I don't know. You might try contacting lucky1 about it. https://github.com/CarnyPriest/CCCforVP/tree/pin2dmd
KiwiBri Posted December 7, 2024 Posted December 7, 2024 41 minutes ago, CarnyPriest said: The offline installer accesses the master branch of the game code repository. There is another branch that has native support for pin2dmd. You could try to download and replace the existing game code with the alternate code. From there, I don't know if support is automatic or if there is something else that needs to be done. I don't have the hardware, so I don't know. You might try contacting lucky1 about it. https://github.com/CarnyPriest/CCCforVP/tree/pin2dmd Thanks I will look into this. When you read this thread, a couple years ago I fixed the issue I had on that install with the updated USB Driver. I was getting the error that CCC was crashing when being run. Right now I can't think why I am having the issue.... VPX 10.8 RC 5 (tried both 32/64 bit versions) Latest B2S Pin2DMD 4.52
KiwiBri Posted December 7, 2024 Posted December 7, 2024 57 minutes ago, CarnyPriest said: The offline installer accesses the master branch of the game code repository. There is another branch that has native support for pin2dmd. You could try to download and replace the existing game code with the alternate code. From there, I don't know if support is automatic or if there is something else that needs to be done. I don't have the hardware, so I don't know. You might try contacting lucky1 about it. https://github.com/CarnyPriest/CCCforVP/tree/pin2dmd I grabbed the ep_desktop_pygame.py file from that repo , and tried .. but got this error now:
Content Provider CarnyPriest Posted December 8, 2024 Content Provider Posted December 8, 2024 known issue with beta versions of VPX. There are some workarounds suggested here: https://github.com/vpinball/vpinball/issues/1578
KiwiBri Posted December 8, 2024 Posted December 8, 2024 7 minutes ago, CarnyPriest said: known issue with beta versions of VPX. There are some workarounds suggested here: https://github.com/vpinball/vpinball/issues/1578 Thanks, I’ll take a look at this. btw, I only replaced the one file from that repo, were you implying I should get all the code from that branch?
Content Provider CarnyPriest Posted December 8, 2024 Content Provider Posted December 8, 2024 34 minutes ago, KiwiBri said: Thanks, I’ll take a look at this. btw, I only replaced the one file from that repo, were you implying I should get all the code from that branch? That should be the only file you need from the master branch. That, and the presence of libusb for the hardware, but I assume you have that one already.
KiwiBri Posted December 8, 2024 Posted December 8, 2024 35 minutes ago, CarnyPriest said: That should be the only file you need from the master branch. That, and the presence of libusb for the hardware, but I assume you have that one already. yep. Got that. I have a system backup of the machine that once worked, I compared the files and they are the same in PROC and Python 2.7 so I’m just confused.🤔
Content Provider CarnyPriest Posted December 8, 2024 Content Provider Posted December 8, 2024 The workaround involves subbing out the core.vbs script with an older one. Plus, at least for me, I run p-roc tables with the x86 platform. I think this launcher program can automate this: I can't be much else with the specific workaround. My cab's been out of commission for months, so I haven't tested anything recently. Seems very doubtful that this will be addressed with the final 10.8 release. After all, this would be about getting pretty much one PITA table working. I've looked briefly at the core.vbs changes but nothing pops out to me. There have been a lot of changes this development cycle.
KiwiBri Posted December 8, 2024 Posted December 8, 2024 (edited) Thanks @CarnyPriest but all those things did not work for me. I have reinstalled the PROC and Python following the original instructions (using P-ROC_Offline_Installer-v3.4) and at the same point as @coincoin @julian1976 and @GrandlHuber all reported. At least I guess all that is consistent 🤷🏽♂️ I will restore my ep_desktop_pygame.py file to the original and go back to trying to use DMDEXT to stream the DMD to the Pin2DMD for now. Edited December 8, 2024 by KiwiBri
Content Provider CarnyPriest Posted December 8, 2024 Content Provider Posted December 8, 2024 Yeah, the offline installer is pointed to the master branch of the code (non-Pin2DMD). I would not expect that to work. The pin2dmd branch has the libusb on which lucky1 developed native support for the CCC DMD. It's old but maybe that one works. Could be new version is not backward compatible? I'm just guessing. You might follow up with lucky1.
KiwiBri Posted December 8, 2024 Posted December 8, 2024 Hi @lucky1 Not sure if you've seen the last few pages in this thread. It seems that the Pin2DMD implementation for CCC is not working.? (Also to add to this, it seems that the latest version of VPX 32/64 need to use a different core.vbs file to get the game working) We are able to get the game working with the virtual DMD showing, (after the core.vbs update/switch) but when we use the custom ep_desktop_pygame.py file to implement streaming to the Pin2DMD we are getting errors. Do you have any thoughts? thanks
Content Provider CarnyPriest Posted December 8, 2024 Content Provider Posted December 8, 2024 (edited) Checking to see if I inadvertently overwrite the file on a merge from master... No, looks like that code is still in the branch. Here's the commit notes: Here is a modified python script to send the display data directly to… … the pin2dmd without having to use dmdext. You need to install pyusb by executing "pip install pyusb" and copying the libusb-1,0.dll to the Python27 folder where the python.exe is located. Currently it is only tested with EVO128x32 and Nucleo based pin2dmd systems. [lucky1] Did you install the prerequisite pyusb and copy libusb to where your python.exe is located? Edited December 8, 2024 by CarnyPriest
KiwiBri Posted December 8, 2024 Posted December 8, 2024 3 hours ago, CarnyPriest said: Checking to see if I inadvertently overwrite the file on a merge from master... No, looks like that code is still in the branch. Here's the commit notes: Here is a modified python script to send the display data directly to… … the pin2dmd without having to use dmdext. You need to install pyusb by executing "pip install pyusb" and copying the libusb-1,0.dll to the Python27 folder where the python.exe is located. Currently it is only tested with EVO128x32 and Nucleo based pin2dmd systems. [lucky1] Did you install the prerequisite pyusb and copy libusb to where your python.exe is located? yes, I've become quite good at doing that pyusb install now..
Content Provider lucky1 Posted December 10, 2024 Content Provider Posted December 10, 2024 (edited) Do you also have libusbwin32 driver installed for pin2dmd using zadig and 32bit libusbk.dll in the same folder ? Any details about the errors you get ? Logfile ? Edited December 10, 2024 by lucky1
KiwiBri Posted December 10, 2024 Posted December 10, 2024 (edited) 1 hour ago, lucky1 said: Do you also have libusbwin32 driver installed for pin2dmd using zadig and 32bit libusbk.dll in the same folder ? Any details about the errors you get ? Logfile ? Here is the setup: VPX 10.8 RC 5 (tried both 32/64 bit versions) Latest B2S Pin2DMD 4.52 firware Which log (where?) should I get? Edited December 10, 2024 by KiwiBri
Content Provider lucky1 Posted December 11, 2024 Content Provider Posted December 11, 2024 (edited) Please try changing to libusb-win32 driver using zadig and place the libusbk.dll in the same folder ! Edited December 11, 2024 by lucky1
KiwiBri Posted December 11, 2024 Posted December 11, 2024 5 hours ago, lucky1 said: Please try changing to libusb-win32 driver using zadig and place the libusbk.dll in the same folder ! Hi, I had originally had version 1.0.24 of libusb-win32 set up, so went back to that and retried. I got the same errors as reported earlier. I then went and found the latest libusb-win32 v1.4.0.0 and put the DLL in Python27 folder, used Zadaig to install and still get the same issues. Note: I am using the Freezy dmddevice.dll, (didnt think this was an issue as doesnt the latest version of this include all your changes too?)
Content Provider lucky1 Posted December 11, 2024 Content Provider Posted December 11, 2024 Are you sure the issue is pin2dmd related at all ? Does the original py file work ?
KiwiBri Posted December 11, 2024 Posted December 11, 2024 (edited) 1 hour ago, lucky1 said: Are you sure the issue is pin2dmd related at all ? Does the original py file work ? Yeah, if I go back to the original py file, the game works, but of course the DMD is now the virtual one. DMDext will work to stream it from the virtual to the Pin2DMD . ps - Others have reported the same issue. I think I saw those posts on the the VPW CCC game comments thread. Same steps as I have done and same error. Edited December 11, 2024 by KiwiBri
Content Provider lucky1 Posted December 11, 2024 Content Provider Posted December 11, 2024 Could you try to comment out pygame.display.iconify() by adding a # in front
KiwiBri Posted December 11, 2024 Posted December 11, 2024 1 hour ago, lucky1 said: Could you try to comment out pygame.display.iconify() by adding a # in front commented it out but still getting this..
Content Provider lucky1 Posted December 12, 2024 Content Provider Posted December 12, 2024 Just to make sure it is caused by the USB please also comment out # self.dev = usb.core.find(idVendor=0x0314, idProduct=0xE457) # if self.dev is None: # raise ValueError('Device not found') and # self.dev.write(0x01,OutputPacketBuffer,1000)
KiwiBri Posted December 12, 2024 Posted December 12, 2024 10 hours ago, lucky1 said: Just to make sure it is caused by the USB please also comment out # self.dev = usb.core.find(idVendor=0x0314, idProduct=0xE457) # if self.dev is None: # raise ValueError('Device not found') and # self.dev.write(0x01,OutputPacketBuffer,1000) I commented out these lines and got the same error again. agh!! So.. ignoring the definition of the RGB/RBG stuff at the top the differences with the "original" working code and the "new DMD code" are as follows: Am I correct to Assume its all working for you @lucky1 ? If so, can I get a copy of Your P-ROC folder to compare to mine ?
Content Provider lucky1 Posted December 12, 2024 Content Provider Posted December 12, 2024 (edited) 1 hour ago, KiwiBri said: Am I correct to Assume its all working for you @lucky1 ? If so, can I get a copy of Your P-ROC folder to compare to mine ? I don´t have CCC installed. To me it seems that the original working code has been modified compared to the base used for the pin2dmd code. Try replacing the part between pygame.init() and pygame.mouse.setvisible(false) with the code from the original file. and also replace the two lines with self.screen. with self.dmd_display. Edited December 12, 2024 by lucky1
Content Provider lucky1 Posted December 12, 2024 Content Provider Posted December 12, 2024 I just saw that the changes have already been added to the PIN2DMD tree of Carnys github https://github.com/CarnyPriest/CCCforVP/blob/pin2dmd/ep/ep_desktop_pygame.py So checking out the pin2dmd tree should work
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now