User Tools

Site Tools


Upgrading PinUP/vPinMAME to use the newer Freezy (DMDExt) 1.9

Location of releases:

Grab x86 (32bit) versions of ZIP (no need to use installer when upgrading)

unblock zip file and then unzip into a temp folder somewhere.

read install update/notes as each one may have certain items. Like v1.9 has some future pinball files/updates within zip.

Warning: the zip file contains a dmddevice.ini file with default settings that will overwrite your existing settings so do NOT copy/paste dmddevice.ini file from upgrade zips.

Baller installer default location is : c:\vPinball\VisualPinball\vPinMAME

(backup all files from that folder before overwriting incase you have to rollback!)

Copy files from zip (excluding dmddevice.ini and any .config files from zip) and overwrite them into your vpinmame folder.

example: (v1.9 zipfile contents)

ensure the remainder of items below are correct!! escpecially the .config files logging is correct.

note: v1.9 has new future pinball features: read here if setting up dmdext for FP:

NOTE: When you make changes in The DMDdevice.INI file you must restart VP In order for the changes to take Effect

For VPX, you need to Verify/Change the dmddevice.ini

The [video] section should now be disabled (it was enabled for ver early versions of PinUP before). It should look like this:

; if enabled, writes frames to an .avi file
enabled =false
; path to folder or .avi file. if folder, gamename.avi is used.

Now you add a new section for Pinup Player's PuPCapture:


Also, if you have a DmdDevice.log.config file, you need to edit that file and make sure that if the <rules> section looks like this:

<logger name="" minlevel="Trace" writeTo="console" />
<logger name="" minlevel="Trace" writeTo="file" />

…it needs to be changed to:

<logger name="" minlevel="warn" writeTo="console" />
<logger name="" minlevel="warn" writeTo="file" />

Same with the dmdextlog.config. The <rules> section should look like:

<logger name="*" minlevel=""warn" writeTo="console" />

This is to disable logging for when colouring is being used. Apparently it can cause performance issues for some people. It's only needed for those who are colouri modding DMDs and are troubleshooting.

Also if you are Using FlexDMD
Same with the FlexDMD.log.config. The <rules> section should look like:

    <logger name="*" minlevel="warn" writeTo="console" />
    <logger name="*" minlevel="warn" writeTo="file" />
upgrade_freezy.txt · Last modified: 2022/04/07 11:26 by outhere