New release: v2.3.0

[mbeckermn]

I took another pass at getting this to work with Serum files - reinstalling DMDExt, updating VPinMAME, installing Serum - but I'm getting the same results. I've also found an unexpected error in the logs when running Tommy, a bunch of repeated lines containing the following: 

 

[11] 2024/11/16 10:12:57.234  WARN | [vni] Tried to load animation but no animation file loaded. 
 

Logs are attached, as well as a screenshot of my VPinMAME folder showing that I've removed Serum.dll. I've also removed DMDdevice.dll and DMDdevice64.dll files from the following folders, and I'm getting the same results. 

 

PIND2DMD

PinDMD1

PinDMD2

PinDMD3

 

Any ideas? I'd really love to avoid doing a fresh install of Baller Installer, but if that's what it takes to get this working as expected now that I've been tinkering so much with these files, I may go that route just to get this working as expected. 

 

Thanks so much for all of the help. 

DmdDevice 4.log DmdDevice 5.log

[PastorLUL]

5 hours ago, mbeckermn said:

I took another pass at getting this to work with Serum files - reinstalling DMDExt, updating VPinMAME, installing Serum - but I'm getting the same results. I've also found an unexpected error in the logs when running Tommy, a bunch of repeated lines containing the following: 

 

[11] 2024/11/16 10:12:57.234  WARN | [vni] Tried to load animation but no animation file loaded. 
 

Logs are attached, as well as a screenshot of my VPinMAME folder showing that I've removed Serum.dll. I've also removed DMDdevice.dll and DMDdevice64.dll files from the following folders, and I'm getting the same results. 

 

PIND2DMD

PinDMD1

PinDMD2

PinDMD3

 

Any ideas? I'd really love to avoid doing a fresh install of Baller Installer, but if that's what it takes to get this working as expected now that I've been tinkering so much with these files, I may go that route just to get this working as expected. 

 

Thanks so much for all of the help. 

DmdDevice 4.log 4.87 kB · 1 download DmdDevice 5.log 25.85 kB · 1 download

 

by freezy In the first post at the bottom:

"EDIT: As usual, don't overwrite your DmdDevice.ini, but get rid of any serum.dll files you might added in the past. This release includes the latest Serum."

 

Especially the "This release includes the latest Serum."

-> remove ANY Serum file, I see that you still have serum_static.lib, serum_test, serum_test_s and serum64.lib

As said in the post, and in the description of the new Serum v2 colorizations I have been releasing: dmdext includes Serum from the get go. 

Edited November 16, 2024 by PastorLUL

[mbeckermn]

Thanks for the response. I was thinking it was just serum.dll files that needed to be removed so that's why I left the others. I deleted the others and I was still getting the same results. 

 

I searched for the error code and found this thread, once I installed the Visual C++ I'm in good shape. Thanks so much for all of the help while I've been navigating this as a newby. 

 

 

[Pookamoondo]

Ok, I managed to get VPINmame to generate DMDdevice.log files again.  

 

My dmddevice.ini includes this:

 

      ; the key to decrypt PAC files, in hex.
      vni.key = f0ad135937ffa111c60b24d88ebb2e59

 

When I open the Medieval Madness table with a full 64 colour DMD (containing coloured PAC/VNI files) it works great.

 

When I try and open a table that only contains a PAC file only (No VNI file), such as Twilight Zone, it does not work and only shows the basic 4 colours.

 

When I open the log file for Twilight Zone, it says "Error initializing colorizer: [vni] No PAC key found. Set it in DmdDevice.ini under vni.key. System.ArgumentException: [vni] No PAC key found. Set it in DmdDevice.ini under vni.key"

 

Can anyone see where I am going wrong please?

DmdDevice - TZ (Bad).log DmdDevice - MM (good).log DmdDevice.ini

Edited November 18, 2024 by Pookamoondo

[MikeDASpike]

5 hours ago, Pookamoondo said:

Ok, I managed to get VPINmame to generate DMDdevice.log files again.  

 

My dmddevice.ini includes this:

 

      ; the key to decrypt PAC files, in hex.
      vni.key = f0ad135937ffa111c60b24d88ebb2e59

 

When I open the Medieval Madness table with a full 64 colour DMD (containing coloured PAC/VNI files) it works great.

 

When I try and open a table that only contains a PAC file only (No VNI file), such as Twilight Zone, it does not work and only shows the basic 4 colours.

 

When I open the log file for Twilight Zone, it says "Error initializing colorizer: [vni] No PAC key found. Set it in DmdDevice.ini under vni.key. System.ArgumentException: [vni] No PAC key found. Set it in DmdDevice.ini under vni.key"

 

Can anyone see where I am going wrong please?

DmdDevice - TZ (Bad).log 4.71 kB · 1 download DmdDevice - MM (good).log 6.53 kB · 0 downloads DmdDevice.ini 29.8 kB · 1 download

Try disabling/removing the plugins in your dmddevice.ini 

plugin.0.path = 
plugin.0.path64 = 
plugin.0.passthrough = false

Edit :You pasted your vni.key under the [virtual dmd], but it should be under global section

Edited November 18, 2024 by MikeDASpike

[Pookamoondo]

17 hours ago, MikeDASpike said:

Try disabling/removing the plugins in your dmddevice.ini 

plugin.0.path = 
plugin.0.path64 = 
plugin.0.passthrough = false

Edit :You pasted your vni.key under the [virtual dmd], but it should be under global section

 

Bingo, you are correct and its now working....  Thank you!  

[MikeDASpike]

3 hours ago, Pookamoondo said:

 

Bingo, you are correct and its now working....  Thank you!  

Good to hear.enjoy !

[Turnbull]

On 11/8/2024 at 8:57 PM, Tikimaster said:

This is, how a key looks like.

 

; the key to decrypt PAC files, in hex.
vni.key =f0ad135937ffa111c60b24d88ebb2e59

 

No key - no Pac files. I took my key from the old ini in my backup.

I have compared my old ini file with the new one in a text editor. The new ini contains some changes and new entries. So I thought it was safer to just copy my old styles and table-settings into the new ini. Afterwards I was careful to compare the old settings with the new ones. I set all settings I use in the new one. There weren't many, but it took some time, at the end everything works for me now. Serum, Pac files, medieval madness, vni-pal, I have not yet found a colorization that does not work properly.

 

 

 

weird, in my DmdDevice.ini the vni.key was never set, but PAC files work anyway.

[LEXUS_RCF]

hello,

i do update but some DMD in one color (original) are bugged. for example Rescue911, it seems one color is missing.

Any idea ?

THX

[halen]

I installed the three new Pinball FX tables (Black Knight, Banzai and Earthshaker). The dmd extensions 2.30 is not working (black screen). I went back to 2.22 and the dmd is working again.

[Johngreve]

Edit: solution to this was installing MS C++ 

 

Good morning,

I just updated to dmdext 2.3 from 2.2 this morning and haven’t been able to get serum colorized tables to display on my pin3dmd in color when launching the tables in 10.8. 64 bit.Color displays properly when launching the table in 10.7 as well as 10.8 32 bit. Even the serum2 colorizations look great when the table is launched in 10.7 or 10.8 32 bit.

I’ve attached the DmdDevicelog which says it’s looking for a serum64.dll. I understand that that is now built in. When hovering over Dmddevice64.dll you can see that it is version 2.3.0 however the date is over two years old.The example shown earlier in this thread displays a date of 11/7/24. I’m only guessing that this .dll is my problem. Can anyone here help me figure this issue out. 
All .pac and .vni/.pal tables still seem to display color properly when launched in 10.8

I read through this whole thread a couple of times and couldn’t quite get my answer to my problem.

Thanks !

Edited December 17, 2024 by Johngreve
Found solution

[emanoel299]

HI guys

After install DMD extensions 2.3.0 some tables doesn´t start. The VPX close before start the game. Only BackGlass still on screen without DMD. I roll back to old version 2.2.2 and now is fine.

[yid4lyf]

Hi Guys I have done everything you have said and my .pac files still dont work i literally dont know what to do any more. I have entered the vni key into my dmddevice.ini and still nothing. All my programs are up to date. If anyone could help that would be great. Thanks guys

[yid4lyf]

14 minutes ago, yid4lyf said:

Hi Guys I have done everything you have said and my .pac files still dont work i literally dont know what to do any more. I have entered the vni key into my dmddevice.ini and still nothing. All my programs are up to date. If anyone could help that would be great. Thanks guys

I just found that if i use Lucky1's DLL files the pac files work put then my tables that run .cRZ files crash. Once i put Freezy's DLL files back my .cRZ tables work but then my pac files stop working.

[Rappelbox]

2 hours ago, yid4lyf said:

I just found that if i use Lucky1's DLL files the pac files work put then my tables that run .cRZ files crash. Once i put Freezy's DLL files back my .cRZ tables work but then my pac files stop working.

remove the serum(64) and pin2dmd(64).dlls from your vpinmame directory

[yid4lyf]

4 hours ago, Rappelbox said:

remove the serum(64) and pin2dmd(64).dlls from your vpinmame directory

I have done that and its still not working

[Jewer]

Like a lot of the posts above I have the same problem with pac files no longer working, but pal/vni and crz do.

 

I have the vni key in the correct location in the dmddevice.ini, I have none of the old serum or pin2dmd files lurking around that should not be there and C++ is all up to date.

 

I have also experienced that rolling freezy back to a previous version will make pac work, but break one of the other formats.

The weird thing is that all altcolor formats worked previously on the previous freezy versions, so I wonder if some other updated component is the culprit?

 

Just my 2 cents to keep this post alive

[PastorLUL]

post your dmddevice.log or it didn't happen! (as freezy would say)

[Jewer]

4 hours ago, PastorLUL said:

post your dmddevice.log or it didn't happen! (as freezy would say)

Absolutely!

 

I have just looked at it and was puzzled. My dmddevice.log shows in the Finder that it was updated in 2023. Shouldn't it be updated today if I just ran a table? And when I look in it, it says it is starting DmdDevice API 2.2.0, but I am running 2.3.0 (according to FlexDMDUI.exe).

 

Here, you can have a look

DmdDevice.log

[PastorLUL]

2 hours ago, Jewer said:

Absolutely!

 

I have just looked at it and was puzzled. My dmddevice.log shows in the Finder that it was updated in 2023. Shouldn't it be updated today if I just ran a table? And when I look in it, it says it is starting DmdDevice API 2.2.0, but I am running 2.3.0 (according to FlexDMDUI.exe).

 

Here, you can have a look

DmdDevice.log 2.71 kB · 2 downloads

Make sure it's the one generated in your Visual Pinball folder.

[Jewer]

1 hour ago, PastorLUL said:

Make sure it's the one generated in your Visual Pinball folder.

That just shows how much I need the help - I pulled one from the Vpinmame folder

 

This is the correct one.

DmdDevice.log

[PastorLUL]

 

11 minutes ago, Jewer said:

That just shows how much I need the help - I pulled one from the Vpinmame folder

 

This is the correct one.

DmdDevice.log 4.99 kB · 0 downloads

 

Try renaming it to "pin2dmd.pac", so remove the _

[Jewer]

10 hours ago, PastorLUL said:

 

 

Try renaming it to "pin2dmd.pac", so remove the _

That was it, sort of

 

Your find (good catch) puzzled me since this table was just an example. All .pac files are affected and I could not recall any of them being named incorrectly.

 

But in every altcolor containing pac was a hidden file with the naming that you mentioned, and that got triggered before the actual pac file. So now I have deleted all these and pac is back up and running.

 

What made these hidden files, I have no idea.

 

Huge thank you.

Edited December 23, 2024 by Jewer

[Jewer]

1 hour ago, Jewer said:

That was it, sort of

 

Your find (good catch) puzzled me since this table was just an example. All .pac files are affected and I could not recall any of them being named incorrectly.

 

But in every altcolor containing pac was a hidden file with the naming that you mentioned, and that got triggered before the actual pac file. So now I have deleted all these and pac is back up and running.

 

What made these hidden files, I have no idea.

 

Huge thank you.

Also... I went through all altcolor folders and every one had hidden ._pin2dmd files, no matter if the extension was pac, crz, pal or vni. How they got there I have no idea, but only pac colorizations where affected and would not work, so it seems like this is the only format that is very particular about other files in the folder.

I don't know if this is important information but just an observation

[LynnInDenver]

2 hours ago, Jewer said:

Also... I went through all altcolor folders and every one had hidden ._pin2dmd files, no matter if the extension was pac, crz, pal or vni. How they got there I have no idea, but only pac colorizations where affected and would not work, so it seems like this is the only format that is very particular about other files in the folder.

I don't know if this is important information but just an observation

Did you uncompress them on a Macintosh? Because those are typically "meta" files that a Macintosh always writes.