I still have inconsistent behavior with my PINDMDv3 (3.05 32bit). At first boot, the DMD images and videos show well in PBX, about 75% of the time I exit a table, PBX just stops showing videos or images on it (stays blank). All vpin emulators I use (VP+VPinMAME, FX2/3+DMDext, FP+dmdintercept, etc.) have no problems with the DMD, even after its stops working in PBX.
It looks to me that there is either a race condition, or an incompatible dll that remains loaded, then PBX cannot load the version it likes.
When the DMD works, I can see a line in the PBX log stating that the external DMD has been started, when it does not, nothing is stated in the log.
I think a good starting point would be to understand the right combination of DLLS and ini files that should be in place for this DMD to operate properly in PBX. I have 3 or 4 different versions of most of the following files (from PBX, lucky, freezy, etc.). I believe I’ve tried pretty much every combination.
pindmd.dll
pindmd.ini
dmddevice.dll
dmddevice.ini
xdmd.dll
xdmddevice.dll
Can Tom, or someone that has pindmdv3 working flawlessly in PBX, share the list of files above they have in place (filename, date, size)? I’m still not clear on the role of each DLL in the context of pbx. Is xdmd supposed to call pindmd.dll or dmddevice.dll ? If the later, should pindmd.dll be removed ?
For the emulators, I use dmddevice/DMDext 1.7 from Freezy. It is worth noting that I also use freezy’s1.7 dmddevice.dll with xdmd/xdmddevice and UltraDMD, with no issues. If I try that combination of dlls PBX hangs when launching emulators.
I could provide logs and config files, but they don;t seem relevant at this time. Maybe a version of pbx with extra logging, would help ? Dmddevice.log and pindmd.log are not helpful.