Jump to content

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


lucky1

Recommended Posts

Sorry for a probably stupid question, but, if I have enabled VirtualDMD and in the table (e.g. an EM table) the pindmd window is set to hidden (.hidden=1), the virtual DMD nevertheless appears on my DMD screen.

Is this intentional or did I configure something wrong?

 

Thanks in advance!

 

Link to comment
Share on other sites

  • 2 weeks later...

Hello

 I have something strange that i cannot resolve

 

I'm using 2 screens and one Pin2DMD 

 

I play with only vpx and pinup popper

 

Everything was working well but i'd like to use .pac files for new colored Dmd

so i decide to update dmddevice.dll with your dll 

 

Using vpx everything working well (has i had to put "enable=native" in dmddevice.ini if i put "enable =true" it don't work)

 

but  no more visible dmd in pinup popper menu

 

When i put back my old dmddevice.dll evrything working well in pinup popper but no color dmd (pac files)

 

I decame crazy. My old dmddevice.dll is only 92ko and the new one is 12 mo

 

Do you have an idea please

how can i get some logs for this dll ?

thanks a lot

Link to comment
Share on other sites

  • Content Provider
2 hours ago, julian1976 said:

Hello

 I have something strange that i cannot resolve

 

I'm using 2 screens and one Pin2DMD 

 

I play with only vpx and pinup popper

 

Everything was working well but i'd like to use .pac files for new colored Dmd

so i decide to update dmddevice.dll with your dll 

 

Using vpx everything working well (has i had to put "enable=native" in dmddevice.ini if i put "enable =true" it don't work)

 

but  no more visible dmd in pinup popper menu

 

When i put back my old dmddevice.dll evrything working well in pinup popper but no color dmd (pac files)

 

I decame crazy. My old dmddevice.dll is only 92ko and the new one is 12 mo

 

Do you have an idea please

how can i get some logs for this dll ?

thanks a lot

 

From the size I think you use my dmddevice.dll for pin2dmd only instead of freezy dmddevice.dll. The latest version is available in the dmddevice.zip here 

https://github.com/lucky01/PIN2DMD/tree/master/integration/pinmame

 

No need for the pin2color.dll with that dmddevice.dll

Link to comment
Share on other sites

I'm still having trouble displaying the correct colors in my real dmd. Why do I see the colors correctly in the virtual one, while in the real one they are wrong? The sequence of colors when I turn on the dmd, is the same as the photo on your site (Lucky1). What can it be this time?

Link to comment
Share on other sites

Hello i found the solution for pinup popper

 

For vpx you have to put the lucky dll's in vpinball/vpinmame folder

for Pinup popper you have to put your working old dll in pinupsystem/pinupplayervpinmame folder and launch the "PUPDMDcontrol_regiter.bat

 

Everything work pretty well now

thanks a lot

Link to comment
Share on other sites

Hi all, I've been away for a while and have just found out about lucky1's new DMD extension.

I am still running freezys extension and the old .pal / .vni files

 

Question is if I use lucky1's version can I use the old .pal / .vni files and the new pac files or do I have to choose one or the other?

 

Link to comment
Share on other sites

  • 2 weeks later...
  • Content Provider

Maybe someone can help with this. 

 

7 hours ago, Rickmc said:

Kept getting error from vpu when trying to post this so hopefully it will get sent via message.

 

Playboys rom - playboy pup pack.  Triggers stopped working with lucky's dll.  If I switch back to Freezy dll, the pup pack triggers work fine.

 

This is in the puplog.txt when lucky1 dll is in place and I run the playboy (stern 2002) vpx file.

 

20230220 18:39:17 Open called
20230220 18:39:17 Set Game Name thread playboys
20230220 18:39:17 Start Thread Matching
20230220 18:39:17 create PuPCap
20230220 18:39:17 Init Game name:playboys
20230220 18:39:17 Create Object Display
20230220 18:39:17 imagedir:C:\vPinball\PinUPSystem\PuPVideos\playboys\PuPCapture
20230220 18:39:17 num images 56
20230220 18:39:32 ERROR sending b2sdata
20230220 18:39:32 ****Exception class name = EOleException
20230220 18:39:32 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:33 ERROR sending b2sdata
20230220 18:39:33 ****Exception class name = EOleException
20230220 18:39:33 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:34 ERROR sending b2sdata
20230220 18:39:34 ****Exception class name = EOleException
20230220 18:39:34 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:36 ERROR sending b2sdata
20230220 18:39:36 ****Exception class name = EOleException
20230220 18:39:36 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:38 ERROR sending b2sdata
20230220 18:39:38 ****Exception class name = EOleException
20230220 18:39:38 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:38 Free Object Display

 

This is what it says when I run the vpx with freezy dll

 

20230220 18:30:06 Open called
20230220 18:30:06 Set Game Name thread playboys
20230220 18:30:07 Start Thread Matching
20230220 18:30:07 create PuPCap
20230220 18:30:07 Init Game name:playboys
20230220 18:30:07 Create Object Display
20230220 18:30:07 imagedir:C:\vPinball\PinUPSystem\PuPVideos\playboys\PuPCapture
20230220 18:30:07 num images 56
20230220 18:37:53 Free Object Display

 

Thank you for any helpful suggestions.

Link to comment
Share on other sites

Hi Lucky1,

 

Turns out that I missed the last update of your dll and when I copied the latest into vpinmame, the problem went away so it's a problem you already solved.

 

Thanks

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Playboys rom - playboy pup pack.  Triggers stopped working with lucky's dll.  If I switch back to Freezy dll, the pup pack triggers work fine.

 

This is in the puplog.txt when lucky1 dll is in place and I run the playboy (stern 2002) vpx file.

 

20230220 18:39:17 Open called
20230220 18:39:17 Set Game Name thread playboys
20230220 18:39:17 Start Thread Matching
20230220 18:39:17 create PuPCap
20230220 18:39:17 Init Game name:playboys
20230220 18:39:17 Create Object Display
20230220 18:39:17 imagedir:C:\vPinball\PinUPSystem\PuPVideos\playboys\PuPCapture
20230220 18:39:17 num images 56
20230220 18:39:32 ERROR sending b2sdata
20230220 18:39:32 ****Exception class name = EOleException
20230220 18:39:32 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:33 ERROR sending b2sdata
20230220 18:39:33 ****Exception class name = EOleException
20230220 18:39:33 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:34 ERROR sending b2sdata
20230220 18:39:34 ****Exception class name = EOleException
20230220 18:39:34 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:36 ERROR sending b2sdata
20230220 18:39:36 ****Exception class name = EOleException
20230220 18:39:36 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:38 ERROR sending b2sdata
20230220 18:39:38 ****Exception class name = EOleException
20230220 18:39:38 ****Exception message = The application called an interface that was marshalled for a different thread
20230220 18:39:38 Free Object Display

 

This is what it says when I run the vpx with freezy dll

 

20230220 18:30:06 Open called
20230220 18:30:06 Set Game Name thread playboys
20230220 18:30:07 Start Thread Matching
20230220 18:30:07 create PuPCap
20230220 18:30:07 Init Game name:playboys
20230220 18:30:07 Create Object Display
20230220 18:30:07 imagedir:C:\vPinball\PinUPSystem\PuPVideos\playboys\PuPCapture
20230220 18:30:07 num images 56
20230220 18:37:53 Free Object Display

 

Thank you for any helpful suggestions.

Link to comment
Share on other sites

Hello,

 

First of all, thank you for your hard work.

 

I've a monochrome color issue with this DLL. When I use an older DLL (one that doesn't support PAC) I've a nice orange color for rom that a not colorized.
But with this one, I have a color that is way darker, more like an orange-red color. It was the same with Freezy DLL (it was the reason I kept your "original" DLL). It makes reading really hard.
Colorized rom render is great through.

 

Is there a parameter that I can try in the INI file for changing default rom color ? I didn't find anything.

 

Thank you for your help

Link to comment
Share on other sites

  • Content Provider
9 hours ago, adol said:

Hello,

 

First of all, thank you for your hard work.

 

I've a monochrome color issue with this DLL. When I use an older DLL (one that doesn't support PAC) I've a nice orange color for rom that a not colorized.
But with this one, I have a color that is way darker, more like an orange-red color. It was the same with Freezy DLL (it was the reason I kept your "original" DLL). It makes reading really hard.
Colorized rom render is great through.

 

Is there a parameter that I can try in the INI file for changing default rom color ? I didn't find anything.

 

Thank you for your help

 

Did you try to adjust the color in pinmame ?

Link to comment
Share on other sites

I could use some help since I've tried on and off over the last few months and still can't get the pac versions to work.  I've downloaded and replaced the latest files in the Jan 23 release and with them installed, none of my DMDs show up, not even the non-colorized ones.  If I revert back to the original dmddevice.dll file, the DMDs work fine, even the pal/vni but I still can't figure out what I'm doing wrong to keep the pacs from working or why that dmddevice.dll kills the dmd on all my tables.

FWIW, I'm on a 3-screen cabinet running, vpx 10.7.3, PInmame32 3.5, and b2s server 1.3.1.1

Link to comment
Share on other sites

5 hours ago, Protomech said:

I could use some help since I've tried on and off over the last few months and still can't get the pac versions to work.  I've downloaded and replaced the latest files in the Jan 23 release and with them installed, none of my DMDs show up, not even the non-colorized ones.  If I revert back to the original dmddevice.dll file, the DMDs work fine, even the pal/vni but I still can't figure out what I'm doing wrong to keep the pacs from working or why that dmddevice.dll kills the dmd on all my tables.

FWIW, I'm on a 3-screen cabinet running, vpx 10.7.3, PInmame32 3.5, and b2s server 1.3.1.1

SEE > For NEW Pac Files   + PAL / VNI Files
https://vpuniverse.com/forums/topic/3370-attack-from-mars-colorization/page/3/?tab=comments#comment-42753

 

Link to comment
Share on other sites

3 hours ago, outhere said:

I too could use some help here, with a kind of similar situation.

 

VPinMAME is updated to 3.5 and got Freezy up and running. Colored roms with PAL and FSQ are working fine, but PAC will not run - it just keep showing the old brown DMD.

 

I have tried adding the recommended files that makes PAC files work, but nothing changes. Is there some kind of setup that I should tinker with, or an old registry that need changes?

 

Just a quick note: a couple of days ago I started getting the colored roms to work, and without really knowing what I did, I got both PAL/FSQ and PAC to work, but only on two tables. After that new PAC files would not work. I then put an old working VPinMAME-folder back in, to start over, and here we are.

 

Could something interfere from that old run?

 

Every kind of help is greatly appreciated.

Link to comment
Share on other sites

On 2/24/2023 at 8:15 PM, lucky1 said:

 

Did you try to adjust the color in pinmame ?

 

Hello,

 

Thank you for your answer.

 

I just did and it, indeed, change the color. The default color is (255,88,32). Is there a color that would be better, more orange and less red ?

If not, I'll make some tests.

 

Is it normal that the color change between your older DLL and this one, or is it just my setup ?

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