Any ideas what is wrong? (Finally resolved)

[DBrown67]

So I have been updating my cabinet after a long time away. So far I have installed:

 

Latest vpx 10.8.0 both 32 and 64 bits.

Visual C++ v14 both 32 and 64 bit.

VPinMame to 3.7.0-222

Freezy 2.5.0

FlexDMD which confirms 2.5.0 with all green tickboxes.

Checked my saved dmddevice.dll for "colorization=true".

 

Yet two very recently uploaded colorizations just will not work. These are Tron and Super Mario Bros. The first was updated on here just a few days ago. The latter on 30th June.

 

All other serum files have worked. All .pac work with the key I put in dmddevice.ini. Still testing on vpx 10.7.2 at the moment.

 

There must be something about these very recent uploaded files. It cannot be just a coincidence.

 

And yes, file names match rom names in correct altcolor folder.

 

I have yet to update b2sbackglass and pinupplayer. (I don't use Popper so only need new Pinup Player). I am taking it step by step. I cannot see those affecting Freezy 2.5.0 though?

 

The DMDs work but not coloured. Just basic 4 colour.

Edited July 20 by DBrown67

[deadmanworking]

Did you check that you don't have any stray serum*.* files hanging around in Vpinmame folder? 
If you correctly installed DMDext 2.5.0 it's included, but older Serum files will override so they need to be removed. 

Also did you unblock all installers after downloading (just to make sure)

[Cliffy]

8 hours ago, DBrown67 said:

So I have been updating my cabinet after a long time away. So far I have installed:

 

Latest vpx 10.8.0 both 32 and 64 bits.

Visual C++ v14 both 32 and 64 bit.

VPinMame to 3.7.0-222

Freezy 2.5.0

FlexDMD which confirms 2.5.0 with all green tickboxes.

Checked my saved dmddevice.dll for "colorization=true".

 

Yet two very recently uploaded colorizations just will not work. These are Tron and Super Mario Bros. The first was updated on here just a few days ago. The latter on 30th June.

 

All other serum files have worked. All .pac work with the key I put in dmddevice.ini. Still testing on vpx 10.7.2 at the moment.

 

There must be something about these very recent uploaded files. It cannot be just a coincidence.

 

And yes, file names match rom names in correct altcolor folder.

 

I have yet to update b2sbackglass and pinupplayer. (I don't use Popper so only need new Pinup Player). I am taking it step by step. I cannot see those affecting Freezy 2.5.0 though?

 

The DMDs work but not coloured. Just basic 4 colour.

does F1 show like below?

[DBrown67]

I never used serum files before. So I didn't have any old ones to delete. I used 7zip which automatically unblocks installers I'm lead to believe.
Yes my F1 box looks like that. Well, certainly the Use External DMD and Colorize DMD are both checked.

I have just updated B2S server and Pinup Player to 64 bit., and set DOF Config up for 32 and 64 bits. All working well, but those will be unrelated to this DMD issue I should think.

Edited July 17 by DBrown67

[PastorLUL]

post a dmddevice.log file, found in your root visual pinball folder. Be sure it's date is marked as today or whenever you last tried it. 

[DBrown67]

Here is the Dmddevice.log file after trying smb3 again.  There are some errors, but it might as well be written in Swahili for me.  😂

DmdDevice.log

[Cliffy]

32 minutes ago, DBrown67 said:

Here is the Dmddevice.log file after trying smb3 again.  There are some errors, but it might as well be written in Swahili for me.  😂

DmdDevice.log 768 B · 0 downloads

Google AI sez....

https://tinyurl.com/yes6bbac

 

[PastorLUL]

Weird, remove the color file and launch the game. Then post another dmddevice.log

[DBrown67]

A one line entry this time:  (I removed the smb3 folder from altcolor)

DmdDevice.log

Edited July 17 by DBrown67

[PastorLUL]

Yeah, so there seems to be something else going on with your setup not related to Serum then it seems. I have never seen this one. Maybe @freezy has any idea what this could mean.

[RepairDan57]

Can you post your DmdDevice.ini?  That might help

 

[DBrown67]

7 hours ago, RepairDan57 said:

Can you post your DmdDevice.ini?  That might help

 

Here it is

DmdDevice.ini

EDIT:  OK I had a look and I saw some errors. I have now disabled the [PINDMD1] etc. entries as I don't have real boards. I also deleted the doubled up [PINDMD2] entry.
But I am unsure about the plugin.0.paths. I don't have any pin2dmd.dll files so I have commented those lines out with a  ;

Edited July 18 by DBrown67

[deadmanworking]

1 hour ago, DBrown67 said:

Here it is

DmdDevice.ini

EDIT:  OK I had a look and I saw some errors. I have now disabled the [PINDMD1] etc. entries as I don't have real boards. I also deleted the doubled up [PINDMD2] entry.
But I am unsure about the plugin.0.paths. I don't have any pin2dmd.dll files so I have commented those lines out with a  ;

 

Are you sure your external DMD is even visible? 
; x-axis of the window position
left = 5590

Might be it's completely off screen and the orange-blue one is the table DMD?

[PastorLUL]

I suggest you regenerate the dmddevice.ini file. This one looks old as bricks.. Copy over the DMD settings at the bottom into your new ini file and start over. 

[DBrown67]

left = 5590   that is correct as my monitors go Playfield >> Backglass >> DMD in Windows, numbered 1, 3, 2 respectively.  DMDs all position good.
I did do an Alt/TAB to see if a new window was running. Nothing new there.

I took the dmddevice.ini file from the template folder in Freezy 2.5.0. I can see a lot of new stuff about rendering dots etc.
I added my co-ordinates and .pac key, but it has made no difference.

The only other thing I can think of is if the rom is mismatched, being as Gottlieb roms are "hard" to find. We might have the same rom name, but a checksum difference?
When I start SMB the rom gives info:  Premier Game #733  GPROM Checksum-5E86  (Gott press Q on keyboard to freeze DMD at right moment, as the checksum shows for only a second or so)

 

[RepairDan57]

1 hour ago, DBrown67 said:

left = 5590   that is correct as my monitors go Playfield >> Backglass >> DMD in Windows, numbered 1, 3, 2 respectively.  DMDs all position good.
I did do an Alt/TAB to see if a new window was running. Nothing new there.

I took the dmddevice.ini file from the template folder in Freezy 2.5.0. I can see a lot of new stuff about rendering dots etc.
I added my co-ordinates and .pac key, but it has made no difference.

The only other thing I can think of is if the rom is mismatched, being as Gottlieb roms are "hard" to find. We might have the same rom name, but a checksum difference?
When I start SMB the rom gives info:  Premier Game #733  GPROM Checksum-5E86  (Gott press Q on keyboard to freeze DMD at right moment, as the checksum shows for only a second or so)

 

What happens if you check the ROM from setup.exe or setup64.exe? Mine shows it has CRC and/or length errors  but still runs.

[DBrown67]

Just checked. I am running the exac same version of PinMame as you and my Game Info is identical for smb3 rom.

[RepairDan57]

3 minutes ago, DBrown67 said:

Just checked. I am running the exac same version of PinMame as you and my Game Info is identical for smb3 rom.

Did you start the ROM?

[DBrown67]

On 7/18/2026 at 2:11 PM, RepairDan57 said:

Did you start the ROM?

When I press start the DMD works but is just in 4 colour mode.  In VPinMame I have an "X" alongside the smb3 entry (as you do in your screenshot).
Does this mean there is an error?

[RepairDan57]

4 hours ago, DBrown67 said:

When I press start the DMD works but is just in 4 colour mode.  In VPinMame I have an "X" alongside the smb3 entry (as you do in your screenshot).
Does this mean there is an error?

I am sure this help fixed it but I have since found a different smb3.zip  rom that tests completely okay and updating  my VC_redist.x86.exe and  VC_redist.x64.exe has gotten this table working 100% for me.

 

I hope this helps

Edited July 20 by RepairDan57

[DBrown67]

I found an updated smb3 rom dating from September 2022 that was required for new (at the time) VPinMame 3.5.  But I now have VPinMame 3.7 and that updated ROM is what I am using. It doesn't colorize for me.

Is that the rom you are talking about that corrects the checksum for you? I get the first Actual checksum value you got when I run mine.

 

[RepairDan57]

9 minutes ago, DBrown67 said:

I found an updated smb3 rom dating from September 2022 that was required for new (at the time) VPinMame 3.5.  But I now have VPinMame 3.7 and that updated ROM is what I am using. It doesn't colorize for me.

Is that the rom you are talking about that corrects the checksum for you? I get the first Actual checksum value you got when I run mine.

 

This is the one I have that works. I am using VPinMame 3.7 also

[Cliffy]

1 hour ago, DBrown67 said:

I found an updated smb3 rom dating from September 2022 that was required for new (at the time) VPinMame 3.5.  But I now have VPinMame 3.7 and that updated ROM is what I am using. It doesn't colorize for me.

Is that the rom you are talking about that corrects the checksum for you? I get the first Actual checksum value you got when I run mine.

 

here's mine which was updated for pinmame 3.6

smb3.zip

[DBrown67]

Thanks Cliffy. Now that Rom does not give any checksum errors in latest 3.7 VPinMame.
But it still did not colorize. 

However... not to give in I went to the latest libserum github page and downloaded that version and stuck the serum64.dll into my VPinMame directory.
Bingo!   So what is embedded into 2.5.0 Freezy is not enough for this table.

EDIT:  Tron now works as well.  😍

Thank you everyone for your input.

 

Edited July 20 by DBrown67

[Cliffy]

It works for me without the serum dll's so something else is going on there