Pin2Dmd Colorprism V4.0 Firmware

[lucky1]

I tested with MM colorization without a problem. Which colorization did you try to test ?

Please also try the 4.11 beta from here https://github.com/lucky01/PIN2DMD/tree/beta/firmware

with the beta dmddevice.dll

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

[bandicoot37]

8 hours ago, lucky1 said:

 

I could identify the problem and it can be fixed by adding the changes DJRobX made here in april 2020, which unfortunatelly did not make it into the current freezy code.

https://github.com/djrobx/dmd-extensions/blob/nopreloadpin2dmd/LibDmd/Output/Pin2Dmd/Pin2Dmd.cs

I attached a test build 

dmdext-1.9.0-PRELOAD-FIX-x86-Release.zip 28.66 MB · 2 downloads

Any luck to have this work whith a PIN2DMDXL ( excuse me i'm the only one who 's got this configuration  )

[lucky1]

3 minutes ago, bandicoot37 said:

Any luck to have this work whith a PIN2DMDXL ( excuse me i'm the only one who 's got this configuration  )

I don´t think so, but I think the devs have it already on the todo.

[DJMRSL]

20 hours ago, lucky1 said:

I tested with MM colorization without a problem. Which colorization did you try to test ?

Please also try the 4.11 beta from here https://github.com/lucky01/PIN2DMD/tree/beta/firmware

with the beta dmddevice.dll

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

@lucky1 Please see the enclosed pal file  used with the vPinSPA table pin2dmd.zip

 

I tried lots of different configs. some work with some table but not with others. When I try your dll, most colorizations work, but PuP no longer receives event triggers. When I try Freezy, as you said, the colorization doesn't work (and in fact, the PIN2DMD crashes, and will only come back when I powercycle) 

I am back to 3.20 now... as that FW version is stable with vPinSPA and Freezy so I can use PuP. 

 

With FW 4.10 I also tried the dmdext preload fix version you posted, but the issues are still  there... when I switch on colorization to enable use of alternate palette files and VNI files, the display also goes to black (E.g. Fish Tales)

 

Hoping now Freezy will integrate your sample code into his dll so I can continue to use PuP. 

 

Thanks for your help anyway... 

 

Cheers

[lucky1]

You can run both dlls parallel by renaming freezy dmddevice.dll to dmdscreen.dll and turn off pin2dmd support in freezys config. That way you can use freezy for pup.

 

I also made a test with the preload fix dll and fishtales and did not have a problem.

[DJMRSL]

1 hour ago, lucky1 said:

You can run both dlls parallel by renaming freezy dmddevice.dll to dmdscreen.dll and turn off pin2dmd support in freezys config. That way you can use freezy for pup.

 

I also made a test with the preload fix dll and fishtales and did not have a problem.

Thanks @Lucky1 , I will give this a try and let you know what I find...  cheers

[DJMRSL]

19 hours ago, DJMRSL said:

Thanks @Lucky1 , I will give this a try and let you know what I find...  cheers

@Lucky1 ... So confused as it's really weird what happens.... for some reason your dll still looks at the dmddevice.ini to enable to PIN2DMD... and behaves like it is still using the Freezy dll, though I have renamed/removed all instances. 

In the Popper menu I get proper colorization, the loading the vPinSPA table, all works fine on the DMD, but I do not receive any PuP event triggers. (Even after renaming dmddevice.dll to dmdscreen.dll like you suggested)  

None of the vPinMAME tables show anything on the DMD when I set PIN2DMD to false in the ini file, and only the non colorized versions run when setting PIN2DMD to 'true' in the ini file... all colorized tables crash the DMD

It's really like the freezy dll is still there..... 

 

 

[lucky1]

1 hour ago, DJMRSL said:

for some reason your dll still looks at the dmddevice.ini to enable to PIN2DMD

 

Impossible !! My dmddevice.dll from github does not even know about any ini file or are you refering to the modified freezy dmddevice.dll  from above ? 

My dmddevice.dll is only 100kbyte in size while freezy is about 12Mbyte.

I think it is better for you the way you suggested it, to stay on 3.20 until freezy is updated.

 

[DJMRSL]

1 hour ago, lucky1 said:

 

Impossible !! My dmddevice.dll from github does not even know about any ini file or are you refering to the modified freezy dmddevice.dll  from above ? 

My dmddevice.dll is only 100kbyte in size while freezy is about 12Mbyte.

I think it is better for you the way you suggested it, to stay on 3.20 until freezy is updated.

 

yep, that’s what I meant…l realized I may have worded incorrectly…. It seems like despite renaming the freezy dlls they’re still in use…. I’ll do one last ditch effort to solve by cleaning house completely including any prefetch/temp files…. 
 

 

[lucky1]

I just uploaded a updated version 4.12 which avoids the crash with freezy.dll and allows to use the old versions if PAL STORAGE is set to RAM in the onscreen menu (https://pin2dmd.com/#3)

 

[DJMRSL]

8 hours ago, DJMRSL said:

yep, that’s what I meant…l realized I may have worded incorrectly…. It seems like despite renaming the freezy dlls they’re still in use…. I’ll do one last ditch effort to solve by cleaning house completely including any prefetch/temp files…. 
 

 

@Lucky1 I found the cause of my issue.... I had recently added an NVMe drive to my system and cloned my existing SSD to it. For some reason some files were still reading from the 'old' drive (Copy - paste error) When I disable the SSD in the diskmanager, VPX failed completely.... so good news and bad news... I found the issue, but now have to spend some time fixing... 

Thanks for your help!

 

 

update…. Yes! Got everything fixed. Your patched version of the Freezy dll did the trick along with FW 4.11 

it took some time to fix it all….but it’s up and running.

thanks again for your help 

[DJMRSL]

On 6/30/2021 at 8:52 PM, DJMRSL said:

@Lucky1 I found the cause of my issue.... I had recently added an NVMe drive to my system and cloned my existing SSD to it. For some reason some files were still reading from the 'old' drive (Copy - paste error) When I disable the SSD in the diskmanager, VPX failed completely.... so good news and bad news... I found the issue, but now have to spend some time fixing... 

Thanks for your help!

 

 

update…. Yes! Got everything fixed. Your patched version of the Freezy dll did the trick along with FW 4.11 

it took some time to fix it all….but it’s up and running.

thanks again for your help 

 

@Lucky1. I have been playing around with the patched freezy dll and FW4.11 over the weekend and found all tables to display on the DMD without the DMD crashing, but when trying to load 64 color palette tables, sometime colors display incorrectly.... so it sort of works but not quite the way it is supposed to work. I tried to capture what happens on Last Action Hero with dtatane colorization file 1.1.0

 

 

Some look worse... for example Terranigma's 64 color TNMT colorization, which I am happy to capture as reference as well, is very hard to read altogether. Kind of seems like the masking with multiple layers goes wrong... as in all black backgrounds seem to be colorized. 

 

 

Also... how set the PAL storage to RAM is unclear to me... I can access the config menu, cycle through settings to PAL storage, then it seems like I can select RAM or FLASH... but it's not clear what I selected when I exit the PAL storage setting and cycle to 'save config' ... nothing seems to have changed after I think I made a change in setting and moreover... every time I cycle through all settings and select PAL storage, the setting flips from the previous setting... so... first time I open the setting it says RAM, when I cycle around and come back to PAL storage it says FLASH... cycle again it says RAM again... etc, so what the setting is when I cycle to save settings, I would not know because I can't verify it. (If there's a way to include this setting in the Windows tool, that would make things more comprehensible) 

 

[lucky1]

- freezy currently does not support 64 colors no matter which firmware.

- a dot on the right side is displayed on the boot splash when set to RAM.

 

The problems you have are more freezy specific and not PIN2DMD firmware specific. So maybe better continue here or open a new thread 

 

[DJMRSL]

7 hours ago, lucky1 said:

- freezy currently does not support 64 colors no matter which firmware.

- a dot on the right side is displayed on the boot splash when set to RAM.

 

The problems you have are more freezy specific and not PIN2DMD firmware specific. So maybe better continue here or open a new thread 

 

 

@lucky1... finally got it working 100% now... using your dll and renamed the freeze to dmdscreen.dll.... like you suggested before (but this time it worked because I fixed my 2x disks issue)

Looks great!

 

Thanks again!

 

I'll now start my first attempt of colorizing Cactus Canyon

 

 

[Terranigma]

1 hour ago, DJMRSL said:

I'll now start my first attempt of colorizing Cactus Canyon

 

 

There was a project already started but the author stopped work on it. I have reached out to him regarding his project files but I have not had a response as of yet.

 

There were some dumps uploaded by user Senseless. You can find them here

 

Maybe that can help you get started.

 

Good luck!

[DJMRSL]

11 hours ago, Terranigma said:

 

There was a project already started but the author stopped work on it. I have reached out to him regarding his project files but I have not had a response as of yet.

 

There were some dumps uploaded by user Senseless. You can find them here

 

Maybe that can help you get started.

 

Good luck!

Thanks! I found the dump files and have loaded them into the editor…. Was struggling with Java at first before noticing I did not have the proper version installed, but all ok now.

 

Watching some tutorials as I’m getting started, any existing project files would be great to have.

 

thanks

[Terranigma]

I don't know of any public existing projects for Cactus Canyon but you can look at the previous attempt here.

Maybe give them a message and let them know you are going to continue it and see if they are willing to share it with you.

[movieguy]

Just made the jump to 4.12 to use with VPX and try some of the 64 color files.  On the 2.3 colorization update for Dracula I am running into issues.  When I launch the first ball the whole game crashes back to the desktop when the DMD transitions back to the score from the Dracula logo that shows when the ball is launched.  I see the same issue with the 16 color version as well.  If I remove all color files everything works as expected.  Also, if I use the test version of the freezy driver provided here the game doesn't crash with the 16 color version.

 

Anyone else seeing this?  It appears to also occur with previous versions of the colorization as well.  So far this is the only issue I have seen, but I just got up and running with  4.xx series.

[lucky1]

12 hours ago, movieguy said:

Just made the jump to 4.12 to use with VPX and try some of the 64 color files.  On the 2.3 colorization update for Dracula I am running into issues.  When I launch the first ball the whole game crashes back to the desktop when the DMD transitions back to the score from the Dracula logo that shows when the ball is launched.  I see the same issue with the 16 color version as well.  If I remove all color files everything works as expected.  Also, if I use the test version of the freezy driver provided here the game doesn't crash with the 16 color version.

 

Anyone else seeing this?  It appears to also occur with previous versions of the colorization as well.  So far this is the only issue I have seen, but I just got up and running with  4.xx series.

 

Any freezy logfile or pinmame dmd dumpfile for the crash moment you could share ?

[movieguy]

I can do that tonight when I get home from work.  Will these files be in my vpinmame folder or do I need to activate the logs first?  I think I know how to generate the freezy log, but I wouldn't expect that to help much because I am not seeing the crash with the freezy file. I haven't had to generate or look for the pinnmame log before.   

 

As another step I was going to try tonight was backing up to the 4.10 firmware and see if the problem goes away.  

[DJMRSL]

18 hours ago, movieguy said:

Just made the jump to 4.12 to use with VPX and try some of the 64 color files.  On the 2.3 colorization update for Dracula I am running into issues.  When I launch the first ball the whole game crashes back to the desktop when the DMD transitions back to the score from the Dracula logo that shows when the ball is launched.  I see the same issue with the 16 color version as well.  If I remove all color files everything works as expected.  Also, if I use the test version of the freezy driver provided here the game doesn't crash with the 16 color version.

 

Anyone else seeing this?  It appears to also occur with previous versions of the colorization as well.  So far this is the only issue I have seen, but I just got up and running with  4.xx series.

I see the same. STTNG also has a similar issue, vPinMAME just stops during the table start, when it kicks the balls around…

 

@lucky1I’ll get som log files…

[lucky1]

5 hours ago, movieguy said:

As another step I was going to try tonight was backing up to the 4.10 firmware and see if the problem goes away.  

 

No need to downgrade. Use 4.12

 

To activate the dmd dump feature of pinmame create a "dmddump" subfolder in pinmame and select Show DMD Window and External DMD in the pinmame settings.

[movieguy]

Lucky1,

 

   Here are the dump files.  Please let me know if you need anything else to help isolate the issue.  Thank you for your help!

 

 

drac_l1.raw drac_l1.txt

[lucky1]

10 hours ago, movieguy said:

Lucky1,

 

   Here are the dump files.  Please let me know if you need anything else to help isolate the issue.  Thank you for your help!

 

 

drac_l1.raw 356.43 kB · 1 download drac_l1.txt 966.05 kB · 1 download

 

I could reproduce the problem using your dumps ! Thanks !
New dll version is on my github.

[DJMRSL]

7 hours ago, lucky1 said:

 

I could reproduce the problem using your dumps ! Thanks !
New dll version is on my github.

Hi @Lucky1  Tested the new dll from Github. It worked perfectly fine for Dracula, but STTNG still crashes fairly quickly after launching the table. 

 

Enclosed are the dump files. 

 

Best

 

sttng_l7.raw sttng_l7.txt