Jump to content

Recommended Posts

Posted (edited)

I am currently in the process of updating my cabinet from 10.7.2 to 10.8.0 and all the appropriate supporting programs, such as DMDext.


The problem came updating DMDext.  The video I was following explicity stated not to copy the dmddevice.ini file across. But now the latest version places that file into a DMDext folder that sits within VPinMame.
So now I have inadvertantly copied this file. And all my DMDs have moved.

I did have a backup folder of my whole VPinball folder before I started. So no problem I thought, just copy back the old DMDext folder. No dice... the dmds have not gone back to original placement. So something has changed I cannot seem to fix.

I am finding updating this section very complex. Different videos saying to copy different stuff over. Things in different locations to what is in the video.

Can anyone offer any help?  My original dmd.exe version is 1.10.2 if that helps any.

EDIT:  Managed to get back where I was as I forgot to put back the dmddevice.dll, dmddevice64.dll and dmdext.exe from backup folder. I only moved the original dmdext folder. Now I have all my dmds back where they were.
But I am still confused as to how to go about updating this without breaking stuff.  

 

Edited by DBrown67
Posted
3 hours ago, DBrown67 said:

I am currently in the process of updating my cabinet from 10.7.2 to 10.8.0 and all the appropriate supporting programs, such as DMDext.


The problem came updating DMDext.  The video I was following explicity stated not to copy the dmddevice.ini file across. But now the latest version places that file into a DMDext folder that sits within VPinMame.
So now I have inadvertantly copied this file. And all my DMDs have moved.

I did have a backup folder of my whole VPinball folder before I started. So no problem I thought, just copy back the old DMDext folder. No dice... the dmds have not gone back to original placement. So something has changed I cannot seem to fix.

I am finding updating this section very complex. Different videos saying to copy different stuff over. Things in different locations to what is in the video.

Can anyone offer any help?  My original dmd.exe version is 1.10.2 if that helps any.

EDIT:  Managed to get back where I was as I forgot to put back the dmddevice.dll, dmddevice64.dll and dmdext.exe from backup folder. I only moved the original dmdext folder. Now I have all my dmds back where they were.
But I am still confused as to how to go about updating this without breaking stuff.  

 

 

dmdext subfolder is not the correct place for these files, that folder only contains a "textures" folder. So Dmddevice* files go into VPinMame folder. 
The reason you shouldn't overwrite Dmddevice.ini is that it holds all your custom positions as you just had the experience with. 
In the same folder run FlexDMD.exe and check that you get green light across the board. 

Next time you want to update, look into the zip files of the update to see which files are replaced, zip up those files as a backup and upgrade. 
Not a problem but keep updates to 1 at a time and create copies / zips of all files of your working setup

2026-07-12 18_27_47-Screenshot.png

Posted

OK thanks for that. So in my new updated VPinMame folder (after pressing install buttons for new 32 and 64 bit versions) I still need to bring across my old dmddevice.ini file? And put it into VPinMame directory, with the other new .dll files?  (Do NOT put them into DMDext folder)

I was still struggling with the editing of certain files. Adding that key for certain .PAC files and there was another file to edit, which I could not open into a text editor at all. (DmdDevice.log.config)

Posted

Yes if you want to keep your DMD positions and settings, you would always need preserve Dmddevice.ini, simply do not extract / overwrite it. Also, back up. 
If you had the vmi key for the PAC files in there and did not lose that file, no need to edit/add that again. 
I've never heard of editing DmdDevice.log.config tbh!

Posted

This is the video I was following, and at 10:10 is where he goes to the Nailbuster wiki and edits the dmddevice.ini and the DmdDevide.log.config files.
As I said I can't even open the latter file in a text editor.
 

 

Posted
38 minutes ago, DBrown67 said:

This is the video I was following, and at 10:10 is where he goes to the Nailbuster wiki and edits the dmddevice.ini and the DmdDevide.log.config files.
As I said I can't even open the latter file in a text editor.
 

 

DmdDevice.log.config is an xml file. Get notepad ++, it's free and easily edits just about anything. The config file determines the logging detail level of the dmddevice.dll's that you see in the dmddevice.log it generates

Posted (edited)

Thank you again. One issue I have (and it's not massive just something to clear up) is that with the new up to date Freezy my DMDs are smaller and have moved slightly. I was under the impression there is only one place where registry values are stored for each rom.
Does Freezy or VPinMame interpret this data differently to old versions?

I don't mind moving/resizing all my DMDs as the vast majority are globally set. But a few are repositioning.
I am currently upgrading my install but still using 10.7.2 to see what differences there are. And this is one of them. Just trying to understand why it is different.

When trying the up to date VPinMame I am installing using the button on the console for both 32 and 64 bits. Dunno if that causes anything new regards DMD placement.

Edited by DBrown67
Posted
On 7/13/2026 at 3:35 AM, DBrown67 said:

Thank you again. One issue I have (and it's not massive just something to clear up) is that with the new up to date Freezy my DMDs are smaller and have moved slightly. I was under the impression there is only one place where registry values are stored for each rom.
Does Freezy or VPinMame interpret this data differently to old versions?

I don't mind moving/resizing all my DMDs as the vast majority are globally set. But a few are repositioning.
I am currently upgrading my install but still using 10.7.2 to see what differences there are. And this is one of them. Just trying to understand why it is different.

When trying the up to date VPinMame I am installing using the button on the console for both 32 and 64 bits. Dunno if that causes anything new regards DMD placement.

 

In your old DmdDevice.ini file that you backed up, there should be a whole bunch of entries at the bottom that look like below.  Each section begins with [romname] then the following rows are the coordinates and size of your virtual DMD.  Do you have these table settings at the bottom of your new DmdDevice.ini after updating? 

image.png.b935b3ec56a2d183340402edcaf876ea.png

 

Also check this setting in the same ini file.  Having this parameter set to true will make the virtual DMD appear in the same spot as the PinMame DVD, not your defined coordinates in the file.

image.png.6b28f351f1e24ec2b8061f54ae57e57c.png

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...