Content Provider freneticamnesic Posted May 19, 2017 Content Provider Posted May 19, 2017 Trying not to be too annoyed by this... I never paid to get the colorprism fw so I'm still on the last open source build I was able to grab. I'm updating my cab so grabbed the newest vpm which seems to have modular dlls for the various DMD options. Using the pin2dmd dll it gives me an error that my firmware version is not supported and asks me to upgrade. Anyways what are my options here to get this to work? Use an old vpm? Pay up? Throw the damn thing away and go back to using an LCD? Or is there another way to get the DMD to work with the latest vpm
Content Provider CarnyPriest Posted May 19, 2017 Content Provider Posted May 19, 2017 PinDMD3? Ha!Sent from my iPad using Tapatalk
Content Provider freneticamnesic Posted May 19, 2017 Author Content Provider Posted May 19, 2017 Lol never
Content Provider UncleSash Posted May 19, 2017 Content Provider Posted May 19, 2017 Do you use the libusb or winusb driver?Try to install the libusb.
Content Provider freneticamnesic Posted May 19, 2017 Author Content Provider Posted May 19, 2017 Libusb that came with vpm didn't see a winusb
Content Provider freneticamnesic Posted May 19, 2017 Author Content Provider Posted May 19, 2017 Works with pindmd2 version of dmddevice.dll from the official vpm, flickers badly with the pindmd2 dll from the 2.9 beta
Content Provider lucky1 Posted May 19, 2017 Content Provider Posted May 19, 2017 You already found the way. Using the open source pindmd2 dmddevice.dll has exactly the same functionality as the old code with integrated drivers. Flickering is always a combination of using a newer version of vpinmame.dll and a older version of dmddevice.dll. Btw. members like you and Carny etc, who actively contribute to the vpin community and don´t want to donate, get a key for their device for free.
Content Provider freneticamnesic Posted May 19, 2017 Author Content Provider Posted May 19, 2017 I didn't think there was much change between 2.9 beta and 2.8 but I noticed something about updates if the files were included, so tried out 2.8 and sure enough that fixed it. Obviously, selecting the pin2dmd dll still gives the error but pindmd2 support worked at least. Still not ideal, and I see everyone having fun with the new palettes... sent you my device ID
Content Provider CarnyPriest Posted May 20, 2017 Content Provider Posted May 20, 2017 On 5/19/2017 at 0:10 AM, lucky1 said: You already found the way. Using the open source pindmd2 dmddevice.dll has exactly the same functionality as the old code with integrated drivers. Flickering is always a combination of using a newer version of vpinmame.dll and a older version of dmddevice.dll. Btw. members like you and Carny etc, who actively contribute to the vpin community and don´t want to donate, get a key for their device for free. Wow! Thank you! But I don't mind donating for a good cause: I've had my device in a storage box since before all this came about. Just need to dig it out at some point and fetch the machine ID.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.