New release: v2.3.0

[mbeckermn]

1 hour ago, Cliffy said:

edit the DmdDevice.log.config in your vpinmame folder with notepad++ or other xml editor and the two bottom lines change from warn to Trace and Info like this

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

Another dumb question, where do I find the log file? I have those values in my config but I'm not finding the actual log file. 

[Cliffy]

2 minutes ago, mbeckermn said:

Another dumb question, where do I find the log file? I have those values in my config but I'm not finding the actual log file. 

in your vpinball folder, or maybe you named it Visual Pinball. Wherever you have VPinballX.exe

[mbeckermn]

5 minutes ago, Cliffy said:

in your vpinball folder, or maybe you named it Visual Pinball. Wherever you have VPinballX.exe

Thanks, I was looking in VPinMAME. Log attached. Y'all really are the best - I appreciate the quick responses!

DmdDevice.log

[freezy]

5 minutes ago, mbeckermn said:

Thanks, I was looking in VPinMAME. Log attached. Y'all really are the best - I appreciate the quick responses!

DmdDevice.log 9.26 kB · 1 download

 

Hmm can you search your file system for serum64.dll and if there is one, which version is it?

[mbeckermn]

3 minutes ago, freezy said:

 

Hmm can you search your file system for serum64.dll and if there is one, which version is it?

Did a search and I'm not finding anything with that file name. 

[freezy]

3 minutes ago, mbeckermn said:

Did a search and I'm not finding anything with that file name. 

 

To be honest, I have no idea why it would not find any serum64.dll at all. You can try copying the latest from here to the same place where DmdDevice64.dll is located, but it's actually already packaged with DmdDevice64.dll.

[Cliffy]

24 minutes ago, mbeckermn said:

Did a search and I'm not finding anything with that file name. 

Are you sure you have freezys 2.3.00 dll's? Go to the vpinmame folder and hover the mouse over it. should look like attached.

Make certain no other dmddevice dll's exist in other folders (except vpinspa if you have that)

[Wolfanoz]

53 minutes ago, freezy said:

If you're debugging, try to reproduce it with a minimal setup. Start with VPM's setup.exe, check if colorizations work there. If okay, try it in VPX. If you throw everything at once at it, you'll have a hard time figuring out what's going on.

So yeah, just going through testing, color wasn't enabled oddly enough.  Thank you, amazing work as well. 

[mbeckermn]

8 minutes ago, Cliffy said:

Are you sure you have freezys 2.3.00 dll's? Go to the vpinmame folder and hover the mouse over it. should look like attached.

Make certain no other dmddevice dll's exist in other folders (except vpinspa if you have that)

Confirmed I'm getting that exact tooltip upon rollover. Also including a screenshot of a search for dmddevice - let me know if that looks as expected. Once again, thank you for your help!

[Cliffy]

and all files unblocked? Including the crz?

[mbeckermn]

1 hour ago, Cliffy said:

and all files unblocked? Including the crz?

Correct, I've verified everything is unblocked. 

[Cliffy]

I'm stumped then. Looking at your log I can't figure out why it's looking for a serum dll since it's already built into the dmddevice dll's.  Maybe try with a fresh dmddevice.ini? Back yours up first and make sure NO other dmddevice.ini exist in other folders

[mbeckermn]

4 hours ago, freezy said:

 

To be honest, I have no idea why it would not find any serum64.dll at all. You can try copying the latest from here to the same place where DmdDevice64.dll is located, but it's actually already packaged with DmdDevice64.dll.

I've downloaded the latest version of Serum you linked to and I get the same error. Log file attached, along with a screenshot of the serum files in the same directory as DmdDevice64.dll

 

I appreciate all of the attention to this question. 

DmdDevice.log

Edited November 13, 2024 by mbeckermn

[Pookamoondo]

I have coloured Roms working with  freezys 2.3.00 including PAC files that contain a .VNI file (Medieval Madness works great) , but i have a lot of Altcolour files that contain the PAC file only (no vni file) for example The Adams Family (TAF_L7).   I tried looking for the DMDDevice.log, but it does not appear to be generated when I run the tables, either in my Visual Pinball folder or my VPinmame folder.   Can anyone tell me how to make it generate the log so I can try and find out why my Pac files are not in colour please?

Edited November 14, 2024 by Pookamoondo

[mbeckermn]

I've reinstalled everything and I'm getting the same results. Not sure if it's relevant but I've found another location that has DmdDevice.dll and DmdDevice64.dll files: 

 

C:\vPinball\VisualPinball\VPinMAME\DMDext

 

Should I remove just those files and leave the rest of the folder, delete the entire folder, or something else? New log file is attached. 

 

Thanks again for your help!

 

 

DmdDevice.log

Edited November 13, 2024 by mbeckermn

[BostonBuckeye]

I transferred over all of my DmdDevice.ini settings to the new file but all of my dmds need to be moved back into the correct position on the back glass. Is there no way to save individual table settings when upgrading?  

[Cliffy]

20 minutes ago, BostonBuckeye said:

I transferred over all of my DmdDevice.ini settings to the new file but all of my dmds need to be moved back into the correct position on the back glass. Is there no way to save individual table settings when upgrading?  

Sure. Copy all of the game settings en masse to the new ini. For example here's the start of the individual game settings in my ini (obviously a very few)

[5th_Element]
virtualdmd left = 1
virtualdmd top = 304
virtualdmd width = 516
virtualdmd height = 129

[abv106]
virtualdmd left = 9
virtualdmd top = 183
virtualdmd width = 520
virtualdmd height = 130

[acd_170h]
virtualdmd left = 0
virtualdmd top = 258
virtualdmd width = 461
virtualdmd height = 115.25

 

[BostonBuckeye]

5 minutes ago, Cliffy said:

Sure. Copy all of the game settings en masse to the new ini. For example here's the start of the individual game settings in my ini (obviously a very few)

[5th_Element]
virtualdmd left = 1
virtualdmd top = 304
virtualdmd width = 516
virtualdmd height = 129

[abv106]
virtualdmd left = 9
virtualdmd top = 183
virtualdmd width = 520
virtualdmd height = 130

[acd_170h]
virtualdmd left = 0
virtualdmd top = 258
virtualdmd width = 461
virtualdmd height = 115.25

 

Thanks Cliffy. Not at my computer right now. Would I find all of these individual game settings in my old ini file?

 

Also, before I submit a ticket on GitHub, whenever closing out of a table in the latest version of 10.8 the dmd takes a long time to close and causes VPX to crash or shutdown. Not sure if this is related to freezy’s update. Do you know what is causing this?

[Cliffy]

23 minutes ago, BostonBuckeye said:

Thanks Cliffy. Not at my computer right now. Would I find all of these individual game settings in my old ini file?

 

Also, before I submit a ticket on GitHub, whenever closing out of a table in the latest version of 10.8 the dmd takes a long time to close and causes VPX to crash or shutdown. Not sure if this is related to freezy’s update. Do you know what is causing this?

Yes sir. Thank goodness you made a backup, right?  As for the slow shutdown sorry it's not happening to me so no idea

[BostonBuckeye]

Just now, Cliffy said:

Yes sir. Thank goodness you made a backup, right?  As for the slow shutdown sorry it's not happening to me so no idea

Thanks Cliffy. I always make back ups! 🙂

[Pookamoondo]

Do PAC files need to have a corresponding VNI file with them to work with Freezy's 2.3.0?

[KRAKEN]

3 hours ago, Pookamoondo said:

Do PAC files need to have a corresponding VNI file with them to work with Freezy's 2.3.0?

PAC files work on their own

 

[KRAKEN]

12 hours ago, BostonBuckeye said:

Thanks Cliffy. Not at my computer right now. Would I find all of these individual game settings in my old ini file?

 

Also, before I submit a ticket on GitHub, whenever closing out of a table in the latest version of 10.8 the dmd takes a long time to close and causes VPX to crash or shutdown. Not sure if this is related to freezy’s update. Do you know what is causing this?

VPX crashing on shutdown is caused by more recent vPinMAME betas while using 64-bit DMDEXT.  https://github.com/vpinball/pinmame/issues/368  Roll back your vPinMAME to a previous version, like 1122.

[emiliotron]

Hola, instalada esta versión y funciona bien en vpx con todos los formatos, sin embargo en pinup popper no muestra DMD, que podrá ser?

Gracias

Edited November 15, 2024 by emiliotron

[BostonBuckeye]

6 hours ago, KRAKEN said:

VPX crashing on shutdown is caused by more recent vPinMAME betas while using 64-bit DMDEXT.  https://github.com/vpinball/pinmame/issues/368  Roll back your vPinMAME to a previous version, like 1122.

Thanks Kraken!