Open Roadblock62 opened 4 years ago
Thanks for creating the issue. Judging from your post at VPF, I'd say something's wrong with VPM 2.8+. For reference, quote:
My PinDMD1 works with Visual PinMAME 2.7 (Standalone DLL, PinDMD1) 2.7 I've tried VPinMame 2.8, 2.8b, 2.9, 3.0, 3.1, 3.2, 3.3 they either crash or they update the DMD slowly I've tried Freezy 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.7.1, 1.7.2, 1.8.0 they either crash or update DMD slowly Has anyone ever tested a PinDMD1 with Freezy and Attack from Mars (afm_113b) ? It seems when VPinMame started using an external dmddevice.dll the PinDMD1 got slower. I've had my cabinet for about a year and I noticed that some tables were slow like Williams and Bally but some others weren't so bad, like Stern and Data East. I kept hoping that the next version of Freezy or VPinMame would fix this.
Comparing the real PinDMD1 with a virtual DMD on the backglass at the same time, we can see that the real DMD can't keep up. It seems worst with Bally and Williams than Stern and Data East virtual pinball tables.
DmdDevice.log