Jump to content

New version: dmd-extensions with pin2dmd coloring plugin and pac file support !


Recommended Posts

Posted
15 minutes ago, Pine said:

I don't even have that DLL in my VPinMame folder either despite have latest Freezy and these updated files. 

.pac needs pin2color.dll

Posted
2 hours ago, Cliffy said:

Working ok for me. Here's my dmddevice.log attached. See if something in it stands out?

DmdDevice.log 2.61 kB · 4 downloads

 

Strange, our log files are doing different things...

 

Yours...

 

 [7] 2023/05/12 16:57:13.174  INFO | [vpm] Open(0) 
 [7] 2023/05/12 16:57:13.174  INFO | [vpm] Set_4_Colors_Palette(0,...) 
 [7] 2023/05/12 16:57:13.174  INFO | Setting palette to 4 colors... 
 [7] 2023/05/12 16:57:13.174  INFO | [vpm] PM_GameSettings(0, spagb_100, 1) 
 [7] 2023/05/12 16:57:13.174  INFO | Enabling game colorization 
 [7] 2023/05/12 16:57:13.174  INFO | Reloading config from E:\vpinball\VPinSPA\DmdDevice.ini. 
 [7] 2023/05/12 16:57:13.174  INFO | Setting game name: spagb_100 
 [7] 2023/05/12 16:57:13.174  INFO | Setting color: #FFFF5820 
 [7] 2023/05/12 16:57:13.174  INFO | Loading Pin2Color plugin ... 
 [7] 2023/05/12 16:57:13.275  INFO | Opening virtual display... 

 

 

Mine...

 

 [1] 2023/05/12 19:07:59.179  INFO | [vpm] Open(0) 
 [1] 2023/05/12 19:07:59.179  INFO | [vpm] Set_4_Colors_Palette(0,...) 
 [1] 2023/05/12 19:07:59.179  INFO | Setting palette to 4 colors... 
 [1] 2023/05/12 19:07:59.186  INFO | [vpm] PM_GameSettings(0, spagb_100, 1) 
 [1] 2023/05/12 19:07:59.186  INFO | Enabling game colorization 
 [1] 2023/05/12 19:07:59.186  INFO | Setting game name: spagb_100 
 [1] 2023/05/12 19:07:59.186  INFO | Setting color: #FFFF5820 
 [1] 2023/05/12 19:07:59.186  INFO | No palette file found at E:\vPinball\VisualPinball\VPinSPA\altcolor\spagb_100\pin2dmd.pal. 
 [1] 2023/05/12 19:07:59.186  INFO | Opening virtual display... 

 

I'm using a .PAC file which I thought was supported.

Posted
21 minutes ago, Pine said:

 

Strange, our log files are doing different things...

 

Yours...

 

 [7] 2023/05/12 16:57:13.174  INFO | [vpm] Open(0) 
 [7] 2023/05/12 16:57:13.174  INFO | [vpm] Set_4_Colors_Palette(0,...) 
 [7] 2023/05/12 16:57:13.174  INFO | Setting palette to 4 colors... 
 [7] 2023/05/12 16:57:13.174  INFO | [vpm] PM_GameSettings(0, spagb_100, 1) 
 [7] 2023/05/12 16:57:13.174  INFO | Enabling game colorization 
 [7] 2023/05/12 16:57:13.174  INFO | Reloading config from E:\vpinball\VPinSPA\DmdDevice.ini. 
 [7] 2023/05/12 16:57:13.174  INFO | Setting game name: spagb_100 
 [7] 2023/05/12 16:57:13.174  INFO | Setting color: #FFFF5820 
 [7] 2023/05/12 16:57:13.174  INFO | Loading Pin2Color plugin ... 
 [7] 2023/05/12 16:57:13.275  INFO | Opening virtual display... 

 

 

Mine...

 

 [1] 2023/05/12 19:07:59.179  INFO | [vpm] Open(0) 
 [1] 2023/05/12 19:07:59.179  INFO | [vpm] Set_4_Colors_Palette(0,...) 
 [1] 2023/05/12 19:07:59.179  INFO | Setting palette to 4 colors... 
 [1] 2023/05/12 19:07:59.186  INFO | [vpm] PM_GameSettings(0, spagb_100, 1) 
 [1] 2023/05/12 19:07:59.186  INFO | Enabling game colorization 
 [1] 2023/05/12 19:07:59.186  INFO | Setting game name: spagb_100 
 [1] 2023/05/12 19:07:59.186  INFO | Setting color: #FFFF5820 
 [1] 2023/05/12 19:07:59.186  INFO | No palette file found at E:\vPinball\VisualPinball\VPinSPA\altcolor\spagb_100\pin2dmd.pal. 
 [1] 2023/05/12 19:07:59.186  INFO | Opening virtual display... 

 

I'm using a .PAC file which I thought was supported.

.pac needs pin2color.dll

Posted
1 hour ago, Cliffy said:

.pac needs pin2color.dll

yeah i put it in there, but it isnt doing anything, not using it, do I have to register it?

Posted
33 minutes ago, Pine said:

yeah i put it in there, but it isnt doing anything, not using it, do I have to register it?

Nope. I can't explain why yours is looking for a pallette file. You sure you have the files from the first page of this thread? Sorry I'm at a loss whats going on there :(

Posted
6 hours ago, Pine said:

Thanks. Seems the pin2color plug-in isn’t loading in my SPA setup. 

Did you update the dmddevice.dll from lucky in your vpinspa as well, or only update it for vpinmame directory ?

Posted
7 hours ago, MikeDASpike said:

Did you update the dmddevice.dll from lucky in your vpinspa as well, or only update it for vpinmame directory ?

Everything in vpinspa is a copy of the files in vpinmame where pac files and serum all work. I’ll start from scratch today, seems silly that one game takes more work than all the others lol. 

Posted

I upgraded my vpinmame folder with Lucky's latest release, and for some reason the serum files no longer work. If I take out the new  DmdDevice.dll and replace it with the prior one I was using (From March I believe) and serum started working again. I have copied x86 and x64 files into my vpinmame folder and overwritten everything except for my DmdDevice Config file. Thinking the DmDDevice.dll was corrupt I redownloaded the files again with same result. Should I be doing something different with the updated files?

Thanks to anyone for any assistance!

Posted
59 minutes ago, apinbalwiz said:

I upgraded my vpinmame folder with Lucky's latest release, and for some reason the serum files no longer work. If I take out the new  DmdDevice.dll and replace it with the prior one I was using (From March I believe) and serum started working again. I have copied x86 and x64 files into my vpinmame folder and overwritten everything except for my DmdDevice Config file. Thinking the DmDDevice.dll was corrupt I redownloaded the files again with same result. Should I be doing something different with the updated files?

Thanks to anyone for any assistance!

 

you rename/remove the serum and serum64 dlls?

 

Posted
9 minutes ago, apinbalwiz said:

Thanks for the reply!  The serum and serum64 dlls are in the vpinmame folder - should they be taken out?

Yes

Posted
10 minutes ago, outhere said:

Yes

Thank you sir.  I took the dlls out and put the new DmdDevice.dll back in, unfortunately serum still not working.  I can usually figure stuff out but this has me stumped.  Any other suggestions?

Posted
51 minutes ago, apinbalwiz said:

Thank you sir.  I took the dlls out and put the new DmdDevice.dll back in, unfortunately serum still not working.  I can usually figure stuff out but this has me stumped.  Any other suggestions?

I sincerely hope this doesn't sound trite but have you read back though this thread? :)  It does work and I'm sure you'll nail it, best of luck!

Posted (edited)
3 hours ago, apinbalwiz said:

I upgraded my vpinmame folder with Lucky's latest release, and for some reason the serum files no longer work. If I take out the new  DmdDevice.dll and replace it with the prior one I was using (From March I believe) and serum started working again. I have copied x86 and x64 files into my vpinmame folder and overwritten everything except for my DmdDevice Config file. Thinking the DmDDevice.dll was corrupt I redownloaded the files again with same result. Should I be doing something different with the updated files?

Thanks to anyone for any assistance!

Thats 2 of us, had this issue 2 wks ago ,tryed suggestions, didnt work, all good using the March dlls.

Edited by Oldschool4
Posted (edited)

I ran into an issue today after updating Freezy.  It looks like he updated the 2.1.1 on the repository and released 2.1.2 Hotfix.  Of course, I updated to the 2.1.2 Hotfix and all altcolor stopped working.  To figure out where the issue lay, I downloaded his 2.1.1 from github, which was also updated today, and altcolor still would not work.  I came back to this thread and downloaded the attached 2.1.1 and altcolor started working again.
 

I looked at the 2.1.1 dmddevice.dll from the github and the 2.1.1 dmddevice.dll from here and they are not the same.  The one attached here is older.  It looks like the pin2color.dll's need an update.  Is there a github repository to get the latest/greatest pin2color.dll's?

EDIT: Just read the thread from Freezy about 2.1.2.   He's working on porting Lucky's plugin, but he's not quite done yet.  He's hoping next release.

Edited by Smileslikejoker
Posted

Well, thanks to Cliffys confidence in me I did manage to finally nail it!   Hoping this might help you too Oldschool4.  Mine stopped working for two reasons - first was because I hadn't taken out or renamed the serum dlls in my vpinmame folder (thanks iwantpinball and outhere),  and the second reason was because I kept the previous color file in the folder (which was renamed) along with the newer version thinking that was okay.  Once I removed the older file leaving only the one in there fixed the problem with the other serum tables as well.  Hopefully this will help others having issues.

Cliffy I thought I read the entire thread, but knowing I lose brain cells by the second I either forgot some info I read or I missed reading some posts that would have helped me figure it out without having to bother you great folks. Will re-read and hope for the best!🙂

Posted

I am having a couple of issues with the latest drivers available here.  I only use a PIN2DMD with no virtual display in normal operation and have successfully installed the x64 upgrade.  I should note that everything was functioning fine but I think a windows update (.Net update?) may have caused the first issue identified below.

 

The first issue is that when starting Pinup Popper (or using a table with PUPDMDControl like Harry Potter) PUPDMDControl will crash when launching.  All other DMD functions seem to work great including VPX and FX3 (including colored roms in both).  The error in windows event viewer is:

Faulting application name: PUPDMD~1.EXE, version: 1.40.4.0, time stamp: 0x5d9ba3ec Faulting module name: clr.dll, version: 4.8.4614.0, time stamp: 0x63995f05 Exception code: 0xc00000fd Fault offset: 0x004c328a Faulting process id: 0x3968 Faulting application start time: 0x01d98b57672abd07 Faulting application path: C:\Pinball\VISUAL~1\VPinMAME\PUPDMD~1.EXE Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

 

The interesting bit is if I enable the virtual DMD with the PIN2DMD in my dmddevice.ini both the PIN2DMD and the virtual work as expected.  The virtual will also function perfectly if I disable the PIN2DMD.  I have also tried Freeze's 2.1.2 driver with the same results as identified above.

 

Things I have tried: Ran the .net repair tool, uninstalled and reinstalled .net (in windows features), reinstalled the C packages, uninstalled the windows updates that have installed recently, and updated my PINN2DMD firmware to 4.51 and none of these  has fixed it. Maybe I am missing something obvious,  that is certainly a possibility :)

 

Second issue - serum files do not seem to color with the latest version of the drivers.  I do not have serum.dlls in my vpinmame folder with the drivers.  If I use Freeze's 2.1.2 driver it works as expected with serum color but then I dont have PAC color files.  I used DMDEXT's colored rom function with Championship Pub to confirm the issue occurs with both DMDEXT or the dmddevice.dll driver.

 

Any help or suggestions would be greatly appreciated.  I've spent several hours on this, and Im out of ideas - at least for the first issue.

Posted
1 hour ago, movieguy said:

I am having a couple of issues with the latest drivers available here.  I only use a PIN2DMD with no virtual display in normal operation and have successfully installed the x64 upgrade.  I should note that everything was functioning fine but I think a windows update (.Net update?) may have caused the first issue identified below.

 

The first issue is that when starting Pinup Popper (or using a table with PUPDMDControl like Harry Potter) PUPDMDControl will crash when launching.  All other DMD functions seem to work great including VPX and FX3 (including colored roms in both).  The error in windows event viewer is:

Faulting application name: PUPDMD~1.EXE, version: 1.40.4.0, time stamp: 0x5d9ba3ec Faulting module name: clr.dll, version: 4.8.4614.0, time stamp: 0x63995f05 Exception code: 0xc00000fd Fault offset: 0x004c328a Faulting process id: 0x3968 Faulting application start time: 0x01d98b57672abd07 Faulting application path: C:\Pinball\VISUAL~1\VPinMAME\PUPDMD~1.EXE Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

 

The interesting bit is if I enable the virtual DMD with the PIN2DMD in my dmddevice.ini both the PIN2DMD and the virtual work as expected.  The virtual will also function perfectly if I disable the PIN2DMD.  I have also tried Freeze's 2.1.2 driver with the same results as identified above.

 

Things I have tried: Ran the .net repair tool, uninstalled and reinstalled .net (in windows features), reinstalled the C packages, uninstalled the windows updates that have installed recently, and updated my PINN2DMD firmware to 4.51 and none of these  has fixed it. Maybe I am missing something obvious,  that is certainly a possibility :)

 

Second issue - serum files do not seem to color with the latest version of the drivers.  I do not have serum.dlls in my vpinmame folder with the drivers.  If I use Freeze's 2.1.2 driver it works as expected with serum color but then I dont have PAC color files.  I used DMDEXT's colored rom function with Championship Pub to confirm the issue occurs with both DMDEXT or the dmddevice.dll driver.

 

Any help or suggestions would be greatly appreciated.  I've spent several hours on this, and Im out of ideas - at least for the first issue.

what does your puplog.txt show? Dmddevice.log in vpinball folder show anything? 

Posted
1 hour ago, Cliffy said:

what does your puplog.txt show? Dmddevice.log in vpinball folder show anything? 

 

The dmddevice.log in the vpinball folder doent update when loading pinup popper (and I assume PUPDMDControl), but the dmddevice.log in my vpinmame folder does.  I have attached that and the puplog here.

DmdDevice.log PUPLOG.txt

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
×
  • Create New...