Pindmdv2 and Pinball Fx3 issues

[Aether2013]

Hi all,

Managed to get my Pindmdv2 working with pinball fx3, but noticed that the dmd does not display all shades like the virtual one does. I read the post on pindmdv2 dimmed, and tried the dmdext-pindmd2-force-2bit-v2.exe and the overall brightness increased but still missing some shades. Makes the DMD nearly impossible to read. Any ideas?

[Aether2013]

You can see from the image the detail missing in the pindmdv2

Shades work fine in VPX.

[freezy]

Are you using the legacy grabber or the memory grabber?

Could you take a screenshot with dmdext's virtual DMD on the screen as well, to be sure whether it's a grabbing issue or driver issue?

[Aether2013]

Hi Freezy,

Sorry for the late reply, just got back from a 2 week cruise.

Appreciate your reply email, I have attached the photos requested. Using both legacy and non legacy mode, there is a slight difference between the two as in I can see another shade, but still missing alot of data in the image.

The attached photos were taken using dmdext 1.7.3 from the link you gave me in the prior email.

Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: freezy notifications@github.com Date: 17/12/19 7:01 pm (GMT+10:00) To: freezy/dmd-extensions dmd-extensions@noreply.github.com Cc: Aether2013 soarer_rgv@hotmail.com, Author author@noreply.github.com Subject: Re: [freezy/dmd-extensions] Pindmdv2 and Pinball Fx3 issues (#203)

Are you using the legacy grabber or the memory grabber?

Could you take a screenshot with dmdext's virtual DMD on the screen as well, to be sure whether it's a grabbing issue or driver issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/freezy/dmd-extensions/issues/203?email_source=notifications&email_token=AN6BL25OGAY2QFPGX23JHATQZCBNTA5CNFSM4JUWHE3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHBQGXQ#issuecomment-566428510, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN6BL23G5HGTGXRZCEI2DQDQZCBNTANCNFSM4JUWHE3A.

[Jseph]

I was seeing the same things and was able to fix it with the changes I described in #205. Do you want the build? If so do you prefer 32 or 64 bit exe? If not I totally understand, not sure I would be comfortable running an exe from some random internet person either.

[freezy]

If you create a PR, it will build automatically :)

(sorry @Aether2013 for not getting back to you earlier)

[Aether2013]

If you don't mind sending me the builds, that would be appreciated, stranger or not, appreciate any help I can get with this. Is it possible to get both 32 and 64?

Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: Jseph notifications@github.com Date: 15/1/20 8:12 pm (GMT+10:00) To: freezy/dmd-extensions dmd-extensions@noreply.github.com Cc: Aether2013 soarer_rgv@hotmail.com, Author author@noreply.github.com Subject: Re: [freezy/dmd-extensions] Pindmdv2 and Pinball Fx3 issues (#203)

I was seeing the same things and was able to fix it with the changes I described in #205https://github.com/freezy/dmd-extensions/issues/205. Do you want the build? If so do you prefer 32 or 64 bit exe? If not I totally understand, not sure I would be comfortable running an exe from some random internet person either.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/freezy/dmd-extensions/issues/203?email_source=notifications&email_token=AN6BL2YWKBNGN4KHJOM4ZBLQ53HQRA5CNFSM4JUWHE3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI7S4AI#issuecomment-574565889, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN6BL22CC5M23KGIIFW2QBDQ53HQRANCNFSM4JUWHE3A.

[Aether2013]

That's cool Freezy, it was during the Xmas period anyways and understand people have commitments, appreciate the reply, just hoping I can get this sorted. 👍

[freezy]

So a fix was merged, thanks to @Jseph!

You can grab a build to test here (x86, x64), don't forget to adjust the DMD size in Pinball FX.

@Aether2013 let us know if it worked, then I'll close the issue (or feel free to close yourself).

[Aether2013]

Hi Freezy and Joseph, 

Thanks for your help so far, but the pindmdv2 still doesn't seem to be resembling the virtual one. 😕

Downloaded the x86 file, and overwrote the existing files in pinmame folder, ensuring that all files were unblocked, Windows defender turn off etc

Went to PBFX3 and confirmed screen res is 520x136.

Executed dmdext via command prompt as seen in the below screen capture.

Then ran PBFX3, went to aliens table. Virtual dmd on lcd screen, shows the below detail.

Whilst the pindmdv2 is still missing alot of data/shades, you can see the entire bar is missing at the bottom of the dmd.

Is there anything else you need me to provide in trying to resolve the issue?

Cheers,

[freezy]

Okay, so it doesn't seem to be a grabbing issue but rather a driver / downsampling issues with your PinDMD2. To be sure which, could you take a screenshot of the test image on your DMD with dmdext test -d pindmdv2?

In your first post you're talking about dmdext-pindmd2-force-2bit-v2.exe. What's that?

[Aether2013]

Hi Freezy, see below for dmdext test

dmdext-pindmd2-force-2bit-v2.exe I got from reading post #148.

Not sure if this is an issue, but with dmdext test it shows (Bitmap => Gray4), with mirror it comes up with (ColoredGray2=>Gray2).

[freezy]

Ah, okay, thanks. What's in dmdext-pindmd2-force-2bit-v2.exe was already merged, it's already in there. What this change did was send 4-bit frames when the source is actually 2 bit.

Your test image seems weird though, the lower left corner should be much lighter, and it looks like it's only displaying four shades instead of 16. Here's what it should look like:

How many shades can you distinguish in your test image?

[Aether2013]

Whoa, no where near 16 shades, tried to take a better photo.

I can only distinguish around 4 to 6 shades, but either way nowhere near what your photo shows.

For the usb drivers and using zadiag drivers, libusb-win32.

Thanks for your help champ.

[Aether2013]

Hey freezy, do you believe it is still an issue with the driver or downsampling? Is there a specific driver other than zadiag that I should try using?

[Aether2013]

Still not having any luck with this, is there any other way I can test the dmd/pindmdv2 to work out what the issue is? Just want to confirm that hardware is not the issue.

[russdx]

pinDMD2 100% supports 16 shades and should behave exactly like pinDMD3 when it comes to the packet structure. I will dig out the firmware source code and take a look.

[Aether2013]

Thanks Russ 👍

[rstoner-rgb]

Hello, anyone have an update on how to fix this issue? I've just recently gotten a pinDMD3 and I'm having this exact issue and it seems no matter what I try, my DMD looks just like Aether2013's photos while playing PinballFX3.

[russdx]

Looking at the source and playing with a pinDMD2 I dug out it does have 16 shades but they are not linear like the new led stuff and are very close together which makes it look like less.

[freezy]

@russdx I'll have a look at this later. There seems to be a general issue how 4-bit shades are generated.

[freezy]

@Aether2013 and @rstoner-rgb I've recently added a way to test more frame formats. Would it be possible to grab the latest build here and post screenshots for those two commands:

dmdext test --format=gray2
dmdext test --format=gray4

[Aether2013]

Hey freezy, using a pindmdv2 I get the two below outputs. Gray4 I can see more shades whilst with Gray 2 I can only see 4. Please tell me you can get the pindmdv2 running with 16 shades 🙏

dmdext test --format=gray2

dmdext test --format=gray4

Cheers,

[freezy]

Huh, this looks actually pretty good. @russdx this is what it's supposed to look like, right?

[russdx]

Yeah those images look very good, you will only see 4 shades on the 2grey as it’s 4 shade mode so this correct, it’s designed for older Williams style DMD games that only support 4 shades, pretty much just the stern stuff uses the 16 shades.

[freezy]

Okay, the driver seems to work, and grabbing is working too AFAIK.

@Aether2013 do you still have this issues with 1.8.0?

[freezy]

Closing, feel free to re-open if something's still not working.