Jump to content
lucky1

SAM Build with modular DMD drivers for pindmd1,2,3 and PIN2DMD

Recommended Posts

1 hour ago, lucky1 said:

First of all if you don´t have any dmddevice.dll installed you should get

"No DMD device driver found" and definitely not "no pindmd found"

I thought you installed the PIN2DMD dmddevice.dll together with libusbk.dll in your pinmame directory ?

Then I asked you to install the pinDMD2 dmddevice.dll driver together with libusb0.dll  instead of PIN2DMD .

Now you are telling you already have pindmd2 drivers installed ? I´m a bit confused now.

 

Ok sorry for the confusion.

 

I do have PIN2DMD dmddevice.dll together with libusbk.dll in your pinmame directory - - no dmd screen when vp launch.. But does work if I run vpinmame in test mode.

If I remove dmddevice.dll from my vpin dir i do get "No DMD device driver found"

I just tried  pinDMD2 dmddevice.dll driver together with libusb0.dll  instead of PIN2DMD

It does work. So the issue is  specific to the Pin2dmd driver

 

Share this post


Link to post
Share on other sites
26 minutes ago, bent98 said:

 

Ok sorry for the confusion.

 

I do have PIN2DMD dmddevice.dll together with libusbk.dll in your pinmame directory - - no dmd screen when vp launch.. But does work if I run vpinmame in test mode.

If I remove dmddevice.dll from my vpin dir i do get "No DMD device driver found"

I just tried  pinDMD2 dmddevice.dll driver together with libusb0.dll  instead of PIN2DMD

It does work. So the issue is  specific to the Pin2dmd driver

 

OK ! Good thing to know. Could you please use zadig utility and change your pin2dmd driver to winusb and try again ?

Share this post


Link to post
Share on other sites

Oh crap it works.

 

Pin2dmd works now!

 

FYI the  pindmd2 driver doesnt work with the driver set to winusb.

I thought the driver needs to be set  to libusb via the Zadig util?

 

So moving forward with this driver we are supposed to have it set to winusb or are you going to fix the dll and I would need to revert back to the libusb setting?

 

 

Share this post


Link to post
Share on other sites

Ok ! It seems there is something wrong with libusbk then. Simply delete it from system32 and it should work again with winusb.

You can also try to copy it to your table folder. It is only needed for backwards compatibility to libusb32 

Share this post


Link to post
Share on other sites

Well, I deleted them from my system32. Now I can use the winusb32 driver but no matter what there are certain SAM tables that crash. Shrek, FG for instance.

 

Non SaM tables dont crash.

Share this post


Link to post
Share on other sites

Crash report
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:25CB0002
Attempt to read from 0x25CB0002
Thread ID: 0x12AC [4780]

Call stack
==========
25CB0002  (0x00000000 0x17C98348 0x000000C3 0x25cb0002)
261062C0 vpinmame.dll (0x00000000 0x26034B69 0x000026FC 0x00000000)
26034B69 vpinmame.dll (0x000004E0 0x264DA8D8 0x29D2FF88 0x00000001)
260478AC vpinmame.dll (0x17B05A88 0x00000000 0x75EC326B 0x00000000)
2604761D vpinmame.dll (0x29D2FFC4 0x76F33145 0x00DFA554 0xfffffffffffffffe)
76EEE394 ntdll.dll RtlInitUnicodeString + 0x164 (0x76EEE0E2 0x00000010 0x00000006 0x00000006)
76EEE394 ntdll.dll RtlInitUnicodeString + 0x164 (0x00000010 0x00000006 0x00000006 0x264334b0)
76EEE0E2 ntdll.dll RtlAllocateHeap + 0xAC (0x29D2FECC 0x26434738 0x00000000 0x29d2ff18)
261BC7DF vpinmame.dll DllUnregisterServer + 0x15E0F (0x00000004 0x264D6890 0x264D67F0 0x264342a0)
261B1A06 vpinmame.dll DllUnregisterServer + 0xB036 (0x00000000 0x1763A668 0x1763A668 0x264342a0)
261B1A06 vpinmame.dll DllUnregisterServer + 0xB036 (0x262E9444 0x1763A668 0x29D2FF88 0x00000000)
261B1A06 vpinmame.dll DllUnregisterServer + 0xB036 (0x00000000 0x17B05A88 0x75EC326B 0x2619ff5f)

Environment
===========
Date/time: 28/10/2016, 15:42:50:737
Number of CPUs: 4
Processor type: 586
System: Unknown Windows version - 6.1 (Service Pack 1)

Memory status
=============
Total Reserved: 155132K (151M) bytes
Total Commited: 1287876K (1257M) bytes
Total Free: 2751232K (2686M) bytes
Largest Free: 2096456K (2047M) bytes

Registers
=========
EAX=25CB0002 EBX=29D2FDD0 ECX=25CB0002 EDX=000000C3
ESI=17C98348 EDI=000026FC EBP=00000000 ESP=29D2FF50 EIP=261A7D03
FLG=00010216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B
 

Share this post


Link to post
Share on other sites

I have tested with all iterations of DMD.  the two most recent versions do not display on the DMD at all, ever for SAM tables.  The first of the two runs the tables and B2S without a DMD and the most recent crashes Virtual Pinball.  The current standard download of SAM PinMAME runs 100% without errors or crashes.  I experimented, with earlier versions, with at91jit and found that setting it to 0 on my configuration caused an echo of all sound, so I'm leaving it at 1.

Share this post


Link to post
Share on other sites

We should not mix things up here. There is  a lot of changes currently going on in VPM. Toxie is working at the sound, DJRobx at the sam emulation and me at the dmdinterface. So SAM crashes and stuttering is unfortunatelly not my business, Only DMD is.

Here is a new complete build of vpm + drivers for pindmd3. I think you are using a older version of vpm with newer drivers and that is why they don´t work.

 

-- see first post --

 

Share this post


Link to post
Share on other sites

Okay, this combination works 100%.  IT took everything I threw at it with NO crashes.  Most excellent!!!!

 

 

 

32 minutes ago, lucky1 said:

We should mix things up here. There is  a lot of changes currently going on in VPM. Toxie is working at the sound, DJRobx at the sam emulation and me at the dmdinterface. So SAM crashes and stuttering is unfortunatelly not my business, Only DMD is.

Here is a new complete build of vpm + drivers for pindmd3. I think you are using a older version of vpm with newer drivers and that is why they don´t work.

PinMame_pindmd3_dmddevice.zip

 

 

Share this post


Link to post
Share on other sites

I assume I should be using the version thats in the 1st page of this thread?

You didnt answer my question ,  The 64 bit dll's are for pinmame64 and not 64bit windows, correct?

Share this post


Link to post
Share on other sites
4 hours ago, lucky1 said:

That could be caused by Jit compiler which has most likely nothing to do with the changes I made.

Look here

Changing that reg entry fixed the issue on shrek and family guy. 

 

Share this post


Link to post
Share on other sites
4 hours ago, lucky1 said:

We should not mix things up here. There is  a lot of changes currently going on in VPM. Toxie is working at the sound, DJRobx at the sam emulation and me at the dmdinterface. So SAM crashes and stuttering is unfortunatelly not my business, Only DMD is.

Here is a new complete build of vpm + drivers for pindmd3. I think you are using a older version of vpm with newer drivers and that is why they don´t work.

PinMame_pindmd3_dmddevice.zip

Yep what he said.   Lots of good stuff going on all at once.

Just as a general PSA - color patch stern ROMS are not yet supported correctly.   Please use official stern ROMs until we get the bugs worked out for the color patch.   Color patch roms currently crash with at91jit=1, and only give us palette info about 5% of the time with at91jit=0, and you'll likely suffer with horrendous audio problems.   

Share this post


Link to post
Share on other sites

I have uploaded a new build based on the latest Carny repo with a new compile of all drivers.

Pindmd3 and 64bit pin2dmd driver is updated with the latest changes. Download please see first post.

Share this post


Link to post
Share on other sites

Okay, I have run this with all display varieties under VP 9.9 and 10.2.  Everything is displaying properly and VP has not crashed.  I experienced a ROM dump using the new VPX TSPP, but I suspect it to be an issue with the new table, since nothing else showed the slightest problem.  Four colors displayed properly on TSPP and JY.  Alpha display was crisp on BOP.  SAM tables showed excellent separation of shades and Fren's Star Trek LE looked fantastic.  As always, a pleasure to contribute to your project.

 

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now


×