321 replies to this topic

[poposchmatzer]

Then VPinMAME is limited to 4 shades. To get 16 shades support for sam roms, let's say I want make the DMD authentic as possible, I have to create a .pal file with an editor?

Edited by poposchmatzer, 05 March 2017 - 09:42 PM.

[Andypc]

So, if I have the .Pal file in the right place what could be causing my problems?

[Thalamus]

Then VPinMAME is limited to 4 shades. To get 16 shades support for sam roms, let's say I want make the DMD authentic as possible, I have to create a .pal file with an editor?

 

The archive with the patch contains the *.pal file you need. It just doesn't say anything about it in the readme.txt file.

You will not get pretty looking DMD with only 4 shades available. To be honest, I find that adjusting it to something different than the standard orange looks better than trying to go color on some of these. But, if you have 16 shades available. Then its a whole different ballgame.

Edited by Thalamus, 06 March 2017 - 12:03 AM.

[jocooter]

If pal file in right place, updated dmddevice.DLL and the newest Sam enabled DLL, start table hit f1 and check color. Then hit f3 to restart table

Sent from my A0001 using Tapatalk

[Thalamus]

If pal file in right place, updated dmddevice.DLL and the newest Sam enabled DLL, start table hit f1 and check color. Then hit f3 to restart table

Sent from my A0001 using Tapatalk

 

You forgot to say - check use external dll, it is that one that enables dmddevice.dll.

Edited by Thalamus, 06 March 2017 - 12:20 AM.

[jocooter]

If pal file in right place, updated dmddevice.DLL and the newest Sam enabled DLL, start table hit f1 and check color. Then hit f3 to restart table

Sent from my A0001 using Tapatalk

I stand corrected, need to check external DMD also


Sent from my A0001 using Tapatalk

[Andypc]

That is exactly what I have done. If I put the DMDdevice.dll in my VpinMame folder I get "No DMD device driver found". If I put the DMDdevice.dll in the SysWOW64 folder the table crashes as soon as I open it.

[Thalamus]

So, andy - you don't have any external dmd - only the virtual - right ? What about posting your dmddevice.ini

 

for congo as an example :

 

C:\Visual_Pinball\VPinMAME\altcolor\congo_21\pin2dmd.pal <- palette file

 

Where did you guys get your dmddevice.dll from btw ? Github ... or ??

[ViriiGuy]

I am still hammering out how to make this all work. But for some reason, changes to the INI file do not seem to do anything. When the color DMD does work and doesn't cause a crash, it is always on my playfield LCD, not my DMD monitor. Also, as my cab is Pin2K style, I need to be able to flip Y to mirror the DMD.. But I can't seem to get it to do that.

 

Any ideas what I could be doing wrong?

 

Scratch all of that.. I finally got all of that working. You have to fully exit Setup, to see any changes to the INI file.

However now.. it works perfectly in Test, but when I try to launch a game from VPX, it crashes.

Edited by ViriiGuy, 06 March 2017 - 11:11 PM.

[jocooter]

In .INI file turn virtual DMD to = false to remove from play field. Make sure you have what ever version dmd set to true. Start game, hit f1 check external DMD and color. Restart table. If it does not work update to newest files and try again.

Sent from my A0001 using Tapatalk

So, andy - you don't have any external dmd - only the virtual - right ? What about posting your dmddevice.ini
 
for congo as an example :
 
C:&#092;Visual_Pinball&#092;VPinMAME&#092;altcolor&#092;congo_21&#092;*******.pal <- palette file
 
Where did you guys get your dmddevice.dll from btw ? Github ... or ??

There's a newer version in thread dated mid February 2017 that has fixes


Sent from my A0001 using Tapatalk

That is exactly what I have done. If I put the DMDdevice.dll in my VpinMame folder I get "No DMD device driver found". If I put the DMDdevice.dll in the SysWOW64 folder the table crashes as soon as I open it.

Some versions looked for it in table folder


Sent from my A0001 using Tapatalk

I am still hammering out how to make this all work. But for some reason, changes to the INI file do not seem to do anything. When the color DMD does work and doesn't cause a crash, it is always on my playfield LCD, not my DMD monitor. Also, as my cab is Pin2K style, I need to be able to flip Y to mirror the DMD.. But I can't seem to get it to do that.
 
Any ideas what I could be doing wrong?

Wait, your using monitor not DMD?

If pal file in right place, updated dmddevice.DLL and the newest Sam enabled DLL, start table hit f1 and check color. Then hit f3 to restart table

Sent from my A0001 using Tapatalk

I stand corrected, need to check external DMD also


Sent from my A0001 using Tapatalk

Sent from my A0001 using Tapatalk

[ViriiGuy]

Yes, I have it working on my monitor properly now in test. But when I launch the table from VPX, it just crashes.

Sent from my A0001 using Tapatalk

I am still hammering out how to make this all work. But for some reason, changes to the INI file do not seem to do anything. When the color DMD does work and doesn't cause a crash, it is always on my playfield LCD, not my DMD monitor. Also, as my cab is Pin2K style, I need to be able to flip Y to mirror the DMD.. But I can't seem to get it to do that.
 
Any ideas what I could be doing wrong?

Wait, your using monitor not DMD?

 

 

[freezy]

When it crashes, can you guys post a log file so I get an idea about the source of the problem and what priorities I should set?

 

If you have copied the DLL to the SysWOW64 folder, then you'll need to copy DmdDevice.log.config as well and change "fileName" at line 27 to somewhere your user has write permissions without having to be Administrator (i.e. not at SysWOW64). Paste the content of that file if you have crashes please.

[jocooter]

Yes, I have it working on my monitor properly now in test. But when I launch the table from VPX, it just crashes.


Sent from my A0001 using Tapatalk

I am still hammering out how to make this all work. But for some reason, changes to the INI file do not seem to do anything. When the color DMD does work and doesn't cause a crash, it is always on my playfield LCD, not my DMD monitor. Also, as my cab is Pin2K style, I need to be able to flip Y to mirror the DMD.. But I can't seem to get it to do that.
 
Any ideas what I could be doing wrong?

Wait, your using monitor not DMD?

 
 

Try copying to tables folder


Sent from my A0001 using Tapatalk

[ViriiGuy]

moving it all to the tables folder made no difference.

 

So to get the log to output, I would change this line..

<target xsi:type="File" name="file" filename"DmdDevice.log"

to this?

<target xsi:type="File" name="file" c:\temp"DmdDevice.log"

Edited by ViriiGuy, 06 March 2017 - 11:39 PM.

[freezy]

No, it's an XML. By "fileName" I mean the value of "filename".

<target xsi:type="File" name="file" fileName="c:\temp\DmdDevice.log"

Edited by freezy, 07 March 2017 - 12:02 AM.

[ViriiGuy]

well, it makes no sense what so ever... but I edited that config for the log, now it all works!

Edited by ViriiGuy, 07 March 2017 - 09:57 AM.

[freezy]

Huh, really.

 

@sliderpoint, @shadowshd, @OzBlackKnight, does that happen with you as well?

[sliderpoint]

Nope, editing the file does nothing to help my problem. I've tried a variety of them on my laptop and cab (both installs are the same configuration).  This is the log from met17LE using Carny's latest build of VPM

 [1] 2017/03/07 12:39:00.221  INFO | Determined color path from assembly path: D:\VP\altcolor 
 [1] 2017/03/07 12:39:00.239  INFO | [vpm] Open() 
 [1] 2017/03/07 12:39:00.239  INFO | [vpm] Set_4_Colors_Palette() 
 [1] 2017/03/07 12:39:00.239  INFO | Setting palette to 4 colors... 
 [1] 2017/03/07 12:39:00.239  INFO | [vpm] PM_GameSettings(1) 
 [1] 2017/03/07 12:39:00.239  INFO | Enabling game colorization 
 [1] 2017/03/07 12:39:00.239  INFO | Setting game name: mtl_170hc 
 [1] 2017/03/07 12:39:00.239  INFO | Setting color: #FFFF5820 
 [1] 2017/03/07 12:39:00.257 ERROR | System.BadImageFormatException: Could not load file or assembly 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'dmdext, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null'
   at PinMameDevice.DmdExt.Init()
   at PinMameDevice.DmdDevice.GameSettings(String gameName, UInt64 hardwareGeneration, IntPtr options)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

-Mike

[Thalamus]

Try disable at91jit in registry for that rom ... might be it

 

\\hkcu\software\freeware\mtl_170c\at91jit - set it to 0

[robwaade]

why cant the color roms be easy like the original roms to get them working why so many steps to go through i cant figure it out