ZeDMD starts screensaver after returning from VPX to Frontend

[pjeantaud]

Hi Markus,

Thanks for this version 2.2.3.

Here’s my feedback, you can see it on the following video : http://pjeantaud.free.fr/Freezy/Freezy_2-3-3.mov

1. run PinballX, ZeDMD displays the DMD presentation video: OK.
2. lauch a VPX table, ZeDMD initialize, then display the DMD game: OK.
3. exit the game. Under PinballX, ZeDMD does not display anymore the presentation video: KO.
4. run another table, ZeDMD displays the DMD game as in step 2: OK.

So PinballX displays the presentation video on DMD only once. Thank you for you commitment.

Patrick

[mkalkbrenner]

The title should be "ZeDMD starts screensaver after returning from VPX to Frontend".

[mkalkbrenner]

The same has been reported for Pinball Y via discord.

@freezy so it looks like VPX doesn't cause a call to Dispose() if it is closed by the frontend. Or the Frontend doesn't call Init() again to get the connection to the DMD.

I don't think that this is a ZeDMD issue. The only difference between ZeDMD and others might be that a process could not open the connection if another process still "owns" the serial port.

[mkalkbrenner]

@zesinger just told me that people reported in forums that in dmddevice.log:

System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it

@freezy how is dmdext supposed to work with frontends and VPX both accessing DMD devices?

[pjeantaud]

Hello,

FYI, I made some extensive testing on my configuration:

• Windows 11 Pro
• VPX 10.7.3 final (32 bits)
• ZeDMD version 3.6.0
• PinballX 6.07 (64 bits)

The correct behavior is obtained with Freezy 2.2.1

Versions 2.2.2 and 2.2.3 present the problem described ahead. Thanks all for your commitment.

[mkalkbrenner]

https://github.com/freezy/dmd-extensions/pull/505

[mkalkbrenner]

should be fixed with the commit of #505.