search

freezy / dmd-extensions

A toolbox for virtual pinball dot matrix displays.
GNU General Public License v2.0
120 stars 52 forks source link

Blank DMD shows on BountyHunter #378

Open Ltek opened 1 year ago

Ltek commented 1 year ago

BountyHunter table is made to work with FlexDMD, and it does. The table script looks like it only calls FlexDMD (I'm new so not a script expert). A blank DMDext shows and I cannot find a way to turn it off. I don't get this problem with 38 other VP tables, just this one. The table author says he cannot repro, but at least one other user has posted saying they have the problem also.

BountyHunter

would love to have help fixing this... maybe a nice feature would be an option to 'disable for this table' in the right-click drop-down menu onscreen?

thx for the help

freezy commented 1 year ago

But FlexDMD also uses dmdext, no?

Anyway, if you want to disable the virtual display for any specific table, add this to DmdDevice.ini:

[game id]
virtualdmd enabled = false

For the game id, check the log, it's printed out.

wiesshund commented 1 year ago

looks related to the pup edited version of the table? as this does not happen with the author's release

Ltek commented 1 year ago

I dont know anything about how any of these DMDs work but I tried the setting, and it disabled both the blank and the FlexDMD. I also tried setting the INI size settings to 1 pix, and it shrank FlexDMD down also... thats a no go.

How do we isolate and resolve what is causing this? Looks like a bug since some people have the problem while most do not.

bOUNTYhUNTER_dmd

wiesshund commented 1 year ago

It isnt a bug with Freezy's DLL itself. It is only doing what it is told to be doing.

I dont have the PUP edited version of the table, so i cant look at the table script to see what might be calling up a 2nd virtual DMD window.

Have you reached out to the PUP Mod table author?

Tarzani's original version has nothing in it that would cause that

Ltek commented 1 year ago

I use the PUP from Mandalorian (cybrnautm) table. IMO the perfect compliment to Bounty Hunter (my favorite table) I'm far from an expert but don't see in the where to turn off the DMD in the PUP? Here's the SCREENS.PUP below. Thanks SOO much for the help. Really do appreciate it!

ScreenNum,ScreenDes,PlayList,PlayFile,Loopit,Active,Priority,CustomPos 0,Topper,,,0,ForceBack,, 2,Backglass,,,0,ForceBack,, 13,"PuP 13",,,0,ForcePopBack,,"2,0,0,100,100" 14,"PuP 14",,,0,ForcePopBack,,"0,0,0,100,100"

wiesshund commented 1 year ago

unfortunately i can tell you nothing of PUP as i do not use it but the above is not where i would be referring to, it would be something in the table's script, which would have had to have been modified for PUP.

But this should really move to which ever forum site hosts the table so the mod author can look at the issue.

I mean i know how to purposely instigate the issue you have, by creating two flexDMD objects and enabling virtual DMD on both of them, but i have no idea what is in the modded version of the table.

freezy commented 1 year ago

How do we isolate and resolve what is causing this?

Provide a log an your DmdDevice.ini.

Ltek commented 1 year ago

How do we isolate and resolve what is causing this?

Provide a log an your DmdDevice.ini

inserted Logs and INI attached. thx for the help! DmdDevice.zip

I mean i know how to purposely instigate the issue you have, by creating two flexDMD objects and enabling virtual DMD on both of them, but i have no idea what is in the modded version of the table.

its not a mod'd table. I simply renamed the folder "cybrnautm" (Mandolorian PuP Pack in PupVideos folder) to "starwarsbh" (Bounty Hunter's gamename)

If the Pack is causing it, we should be able to be removed/disabled with the Pup Editor I'd think?

DMD LOG

[1] 2023/06/10 13:34:23.937 INFO | Successfully loaded config from C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini. [1] 2023/06/10 13:34:23.937 INFO | Determined color path from assembly path: C:\vPinball\VisualPinball\VPinMAME\altcolor [1] 2023/06/10 13:34:23.947 INFO | Starting VPinMAME API 1.10.2 through VPinballX.exe. [1] 2023/06/10 13:34:23.947 INFO | Assembly located at C:\vPinball\VisualPinball\VPinMAME\dmddevice.dll [1] 2023/06/10 13:34:23.947 INFO | [vpm] Create(): New output id is 1 [12] 2023/06/10 13:34:23.947 INFO | PinDMDv1 device not found. [1] 2023/06/10 13:34:23.947 INFO | [vpm] Open(1) [1] 2023/06/10 13:34:23.947 INFO | [vpm] PM_GameSettings(1, starwarsbh_main, 0) [1] 2023/06/10 13:34:23.947 INFO | Disabling game colorization [1] 2023/06/10 13:34:23.947 INFO | Setting game name: starwarsbh_main [1] 2023/06/10 13:34:23.947 INFO | Setting color: #FFFF9658 [1] 2023/06/10 13:34:23.947 INFO | Opening virtual display... [12] 2023/06/10 13:34:23.947 INFO | PinDMDv2 device not found. [12] 2023/06/10 13:34:23.947 INFO | PinDMDv3 device not found. [12] 2023/06/10 13:34:23.967 INFO | Added VirtualDMD renderer. [12] 2023/06/10 13:34:23.967 INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False [12] 2023/06/10 13:34:23.967 INFO | Applying default color to render graphs (#FFFF4500). [12] 2023/06/10 13:34:23.967 INFO | Setting up 2-bit VPM Graph for 1 destination(s) [12] 2023/06/10 13:34:23.967 INFO | Connecting VPM 2-bit Source to Dmd (Gray2 => Gray2) [12] 2023/06/10 13:34:23.967 INFO | Setting up 4-bit VPM Graph for 1 destination(s) [12] 2023/06/10 13:34:23.967 INFO | Connecting VPM 4-bit Source to Dmd (Gray4 => Gray4) [12] 2023/06/10 13:34:23.967 INFO | Setting up RGB24-bit VPM Graph for 1 destination(s) [12] 2023/06/10 13:34:23.967 INFO | Connecting VPM RGB24 Source to Dmd (Rgb24 => Rgb24) [12] 2023/06/10 13:34:23.967 INFO | Setting up Alphanumeric VPM Graph for 1 destination(s) [13] 2023/06/10 13:34:23.985 INFO | PinDMDv1 device not found. [13] 2023/06/10 13:34:23.985 INFO | PinDMDv2 device not found. [13] 2023/06/10 13:34:23.985 INFO | PinDMDv3 device not found. [13] 2023/06/10 13:34:24.003 INFO | Added VirtualDMD renderer. [13] 2023/06/10 13:34:24.003 INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False [13] 2023/06/10 13:34:24.003 INFO | Applying default color to render graphs (#FFFF9658). [13] 2023/06/10 13:34:24.003 INFO | Setting up 2-bit VPM Graph for 1 destination(s) [13] 2023/06/10 13:34:24.003 INFO | Connecting VPM 2-bit Source to Dmd (Gray2 => Gray2) [13] 2023/06/10 13:34:24.003 INFO | Setting up 4-bit VPM Graph for 1 destination(s) [13] 2023/06/10 13:34:24.003 INFO | Connecting VPM 4-bit Source to Dmd (Gray4 => Gray4) [13] 2023/06/10 13:34:24.003 INFO | Setting up RGB24-bit VPM Graph for 1 destination(s) [13] 2023/06/10 13:34:24.003 INFO | Connecting VPM RGB24 Source to Dmd (Rgb24 => Rgb24) [13] 2023/06/10 13:34:24.003 INFO | Setting up Alphanumeric VPM Graph for 1 destination(s) [13] 2023/06/10 13:34:24.103 INFO | Creating FBOs for 128x32 [12] 2023/06/10 13:34:24.103 INFO | Creating FBOs for 128x32

FlexDMD Log

[1] 2023/06/10 13:34:23.883 ERROR | Failed to load dmdscreen.dll in C:\vPinball\VisualPinball\VPinMAME\dmdscreen.dll [1] 2023/06/10 13:34:24.149 ERROR | Failed to load dmdscreen.dll in C:\vPinball\VisualPinball\VPinMAME\dmdscreen.dll [11] 2023/06/10 13:34:24.154 WARN | Abnormally long elapsed time between frames of 0.2400568s (rendering lasted 240.0564ms, sleeping was 0ms), limiting to 66ms [11] 2023/06/10 13:34:24.210 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.218 ERROR | Missing resource 'blank.jpg' [11] 2023/06/10 13:34:24.230 ERROR | Unsupported animation in scene '': ZoomIn [11] 2023/06/10 13:34:24.341 WARN | Abnormally long elapsed time between frames of 0.1082323s (rendering lasted 108.2319ms, sleeping was 0ms), limiting to 66ms [11] 2023/06/10 13:34:30.753 ERROR | Unsupported animation in scene '': ZoomIn [11] 2023/06/10 13:34:33.269 ERROR | Unsupported animation in scene '': ZoomIn [11] 2023/06/10 13:34:39.578 WARN | Abnormally long elapsed time between frames of 0.1719251s (rendering lasted 171.9246ms, sleeping was 0ms), limiting to 66ms

wiesshund commented 1 year ago

Table would have to be modified Otherwise how would it know when to perform any PUP commands? It isnt a ROM table, so it has no ROM events to go by

Your log seems a bit odd?

dmddevice.log [1] 2023/06/10 17:38:29.628 INFO | Successfully loaded config from d:\pinball\vpx\VPinMAME\DmdDevice.ini. [1] 2023/06/10 17:38:29.628 INFO | Determined color path from assembly path: d:\pinball\vpx\VPinMAME\altcolor [1] 2023/06/10 17:38:30.680 INFO | Starting VPinMAME API 2.1.2 through VPinballX64.exe. [1] 2023/06/10 17:38:30.680 INFO | Assembly located at d:\pinball\vpx\VPinMAME\dmddevice64.dll [1] 2023/06/10 17:38:30.680 INFO | Running in D:\Pinball\VPX\Tables [1] 2023/06/10 17:38:30.680 INFO | [vpm] Create(): New output id is 1 [1] 2023/06/10 17:38:30.680 INFO | [vpm] Open(1) [1] 2023/06/10 17:38:30.680 INFO | [vpm] PM_GameSettings(1, BOUNTYHUNTER_main, 0) [1] 2023/06/10 17:38:30.680 INFO | Disabling game colorization [1] 2023/06/10 17:38:30.680 INFO | Setting game name: BOUNTYHUNTER_main [1] 2023/06/10 17:38:30.680 INFO | Setting color: #FFFF9658 [1] 2023/06/10 17:38:30.680 INFO | Opening virtual display... [17] 2023/06/10 17:38:30.699 INFO | Found B2S, moving behind DMD. [17] 2023/06/10 17:38:30.701 INFO | Added VirtualDMD renderer. [17] 2023/06/10 17:38:30.701 INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False [17] 2023/06/10 17:38:30.701 INFO | Applying default color to render graphs (#FFFF9658). [17] 2023/06/10 17:38:30.701 INFO | Setting up 2-bit VPM Graph for 1 destination(s) [17] 2023/06/10 17:38:30.701 INFO | Connecting VPM 2-bit Source to Virtual DMD (Gray2 => Gray2) [17] 2023/06/10 17:38:30.701 INFO | Setting up 4-bit VPM Graph for 1 destination(s) [17] 2023/06/10 17:38:30.701 INFO | Connecting VPM 4-bit Source to Virtual DMD (Gray4 => Gray4) [17] 2023/06/10 17:38:30.701 INFO | Setting up RGB24-bit VPM Graph for 1 destination(s) [17] 2023/06/10 17:38:30.701 INFO | Connecting VPM RGB24 Source to Virtual DMD (Rgb24 => Rgb24) [17] 2023/06/10 17:38:30.701 INFO | Setting up Alphanumeric VPM Graph for 1 destination(s) [17] 2023/06/10 17:38:30.768 INFO | Creating FBOs for 128x32 [1] 2023/06/10 17:39:19.456 INFO | [vpm] Close(1) [1] 2023/06/10 17:39:19.456 INFO | Closing up. [1] 2023/06/10 17:39:19.541 INFO | Source for 1 renderer(s) stopped. [1] 2023/06/10 17:39:19.541 INFO | Source for 1 renderer(s) stopped. [1] 2023/06/10 17:39:19.541 INFO | Source for 1 renderer(s) stopped. [1] 2023/06/10 17:39:19.541 INFO | Source for 0 renderer(s) stopped.

flexDMD.log [1] 2023/06/10 17:38:16.806 INFO | FlexDMD version 1.9.0.0 [1] 2023/06/10 17:38:16.842 INFO | Render mode set to DMD_RGB [1] 2023/06/10 17:38:16.842 INFO | Game name set to BOUNTYHUNTER_main [1] 2023/06/10 17:38:16.842 INFO | Show DMD [1] 2023/06/10 17:38:16.842 INFO | Loaded dmddevice64.dll from d:\pinball\vpx\VPinMAME\dmddevice64.dll to create a virtual DMD [1] 2023/06/10 17:38:20.694 INFO | dmdscreen64.dll was not loaded since it is not available from d:\pinball\vpx\VPinMAME\dmdscreen64.dll [1] 2023/06/10 17:38:20.694 INFO | Starting render thread for game 'BOUNTYHUNTER_main' using render mode DMD_RGB [9] 2023/06/10 17:38:20.694 INFO | RenderThread start [1] 2023/06/10 17:38:20.720 INFO | Font added to cache:FlexDMD.Resources.udmd-f5by7.fnt&tint=FFA8A8A8&border_size=0&border_tint=FFFFFFFF [1] 2023/06/10 17:38:20.720 INFO | Font added to cache:FlexDMD.Resources.udmd-f6by12.fnt&tint=FFFFFFFF&border_size=0&border_tint=FFFFFFFF [1] 2023/06/10 17:38:20.720 INFO | Font added to cache:FlexDMD.Resources.udmd-f4by5.fnt&tint=FFA8A8A8&border_size=0&border_tint=FFFFFFFF [1] 2023/06/10 17:38:20.720 INFO | Hide DMD [9] 2023/06/10 17:38:20.883 WARN | Abnormally long elapsed time between frames of 0.1832047s (rendering lasted 183.2046ms, sleeping was 0ms), limiting to 66ms [1] 2023/06/10 17:38:21.162 INFO | Disposing DMD dynamic link library [1] 2023/06/10 17:38:21.162 INFO | Show DMD [9] 2023/06/10 17:38:21.162 WARN | Abnormally long elapsed time between frames of 0.2807287s (rendering lasted 280.7286ms, sleeping was 0ms), limiting to 66ms [1] 2023/06/10 17:38:21.162 INFO | Loaded dmddevice64.dll from d:\pinball\vpx\VPinMAME\dmddevice64.dll to create a virtual DMD [1] 2023/06/10 17:38:22.323 INFO | dmdscreen64.dll was not loaded since it is not available from d:\pinball\vpx\VPinMAME\dmdscreen64.dll [9] 2023/06/10 17:38:22.323 WARN | Abnormally long elapsed time between frames of 1.1597511s (rendering lasted 1159.751ms, sleeping was 0ms), limiting to 66ms [1] 2023/06/10 17:38:22.326 INFO | SetProjectFolder D:\Pinball\VPX\Tables\BountyHunterDMD [9] 2023/06/10 17:38:22.344 INFO | Font added to cache:FlexDMD.Resources.udmd-f5by7.fnt&tint=FF00FF37&border_size=1&border_tint=FF002207 [9] 2023/06/10 17:38:22.344 INFO | Font added to cache:FlexDMD.Resources.udmd-f6by12.fnt&tint=FF00440E&border_size=1&border_tint=FF00FF37 [9] 2023/06/10 17:38:22.344 INFO | Bitmap added to cache:blank.jpg [9] 2023/06/10 17:38:22.344 INFO | Font added to cache:FlexDMD.Resources.udmd-f5by7.fnt&tint=FF00FF37&border_size=1&border_tint=FF005512 [9] 2023/06/10 17:38:22.344 INFO | Font added to cache:FlexDMD.Resources.udmd-f6by12.fnt&tint=FF00440E&border_size=1&border_tint=FF005512 [9] 2023/06/10 17:38:22.344 INFO | Font added to cache:FlexDMD.Resources.udmd-f14by26.fnt&tint=FF00FF37&border_size=1&border_tint=FF005512 [9] 2023/06/10 17:38:22.356 INFO | Font added to cache:FlexDMD.Resources.udmd-f14by26.fnt&tint=FF002207&border_size=1&border_tint=FF00DD2F [9] 2023/06/10 17:38:22.356 INFO | Font added to cache:FlexDMD.Resources.udmd-f12by24.fnt&tint=FF002207&border_size=1&border_tint=FF00DD2F [9] 2023/06/10 17:38:22.356 INFO | Font added to cache:FlexDMD.Resources.udmd-f7by13.fnt&tint=FF002207&border_size=1&border_tint=FF00DD2F [9] 2023/06/10 17:38:22.356 ERROR | Unsupported animation in scene '': ZoomIn [9] 2023/06/10 17:38:23.105 INFO | Attaching to Visual Pinball Player window lifecycle [9] 2023/06/10 17:38:28.832 ERROR | Unsupported animation in scene '': ZoomIn [1] 2023/06/10 17:38:29.538 INFO | Hide DMD [1] 2023/06/10 17:38:29.631 INFO | Disposing DMD dynamic link library [9] 2023/06/10 17:38:29.631 WARN | Abnormally long elapsed time between frames of 0.0816643s (rendering lasted 81.6643ms, sleeping was 0ms), limiting to 66ms [1] 2023/06/10 17:38:29.631 INFO | Show DMD [1] 2023/06/10 17:38:29.631 INFO | Loaded dmddevice64.dll from d:\pinball\vpx\VPinMAME\dmddevice64.dll to create a virtual DMD [1] 2023/06/10 17:38:30.791 INFO | dmdscreen64.dll was not loaded since it is not available from d:\pinball\vpx\VPinMAME\dmdscreen64.dll [9] 2023/06/10 17:38:30.791 WARN | Abnormally long elapsed time between frames of 1.1590473s (rendering lasted 1159.0472ms, sleeping was 0ms), limiting to 66ms [9] 2023/06/10 17:38:30.791 INFO | Font added to cache:FlexDMD.Resources.udmd-f5by7.fnt&tint=FFFF9658&border_size=1&border_tint=FF331E11 [9] 2023/06/10 17:38:30.791 INFO | Font added to cache:FlexDMD.Resources.udmd-f6by12.fnt&tint=FFFF9658&border_size=1&border_tint=FF331E11 [9] 2023/06/10 17:38:30.791 INFO | Bitmap added to cache:Door_1.jpg [9] 2023/06/10 17:38:30.809 INFO | Font added to cache:FlexDMD.Resources.udmd-f5by7.fnt&tint=FF000000&border_size=1&border_tint=FFCC7846 [9] 2023/06/10 17:38:30.810 INFO | Font added to cache:FlexDMD.Resources.udmd-f6by12.fnt&tint=FFFF9658&border_size=1&border_tint=FF110A05 [9] 2023/06/10 17:38:30.810 INFO | Bitmap added to cache:mando1.jpg [9] 2023/06/10 17:38:32.490 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (1 videos are currently opened) [9] 2023/06/10 17:38:34.198 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (0 remaining videos are currently opened) [9] 2023/06/10 17:38:34.238 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\theway2.wmv size=128x32 length=2.266s (1 videos are currently opened) [9] 2023/06/10 17:38:35.969 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\theway2.wmv size=128x32 length=2.266s (0 remaining videos are currently opened) [9] 2023/06/10 17:38:40.702 INFO | Bitmap added to cache:Door_2.jpg [9] 2023/06/10 17:38:40.850 INFO | Bitmap added to cache:Door_3.jpg [9] 2023/06/10 17:38:41.001 INFO | Bitmap added to cache:Door_4.jpg [9] 2023/06/10 17:38:41.149 INFO | Bitmap added to cache:Door_5.jpg [9] 2023/06/10 17:38:41.297 INFO | Bitmap added to cache:Door_6.jpg [9] 2023/06/10 17:38:41.447 INFO | Bitmap added to cache:Door_7.jpg [9] 2023/06/10 17:38:45.150 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\greenlight.wmv size=128x32 length=2.7s (1 videos are currently opened) [9] 2023/06/10 17:38:46.871 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\greenlight.wmv size=128x32 length=2.7s (0 remaining videos are currently opened) [9] 2023/06/10 17:38:46.875 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\ramp21.wmv size=128x32 length=1.733s (1 videos are currently opened) [9] 2023/06/10 17:38:48.574 INFO | End of stream [9] 2023/06/10 17:38:48.610 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\ramp21.wmv size=128x32 length=1.733s (0 remaining videos are currently opened) [9] 2023/06/10 17:38:57.184 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\bluestars.wmv size=128x32 length=10.3s (1 videos are currently opened) [9] 2023/06/10 17:39:06.144 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\bluestars.wmv size=128x32 length=10.3s (0 remaining videos are currently opened) [9] 2023/06/10 17:39:10.669 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (1 videos are currently opened) [9] 2023/06/10 17:39:12.438 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (0 remaining videos are currently opened) [9] 2023/06/10 17:39:15.161 INFO | Video opened: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (1 videos are currently opened) [9] 2023/06/10 17:39:16.926 INFO | Video closed: D:\Pinball\VPX\Tables\BountyHunterDMD\circle1.wmv size=128x32 length=3.466s (0 remaining videos are currently opened) [1] 2023/06/10 17:39:19.453 INFO | Stopping render thread [9] 2023/06/10 17:39:19.453 INFO | RenderThread end [1] 2023/06/10 17:39:19.453 INFO | Hide DMD [1] 2023/06/10 17:39:19.546 INFO | Disposing DMD dynamic link library

In your DMDDevice log, i see it opening 2 render windows. Last 2 lines of the log

Not that it directly matters, but the gamename is different in your logs. I got table directly from the authors upload, so it seems your version of the table is modified? If you run this table, using Tartzani's upload https://www.vpforums.org/index.php?app=downloads&showfile=15528 do you have same issue?

I am using freezys stock dmddevice.ini out of the 2.1.2 zip by the way

wiesshund commented 1 year ago

ps, you seem to be missing blank.jpg from you table dmd folder just make a 128x32 black jpg and name it blank.jpg as that is all that it is

Ltek commented 1 year ago

Only table I've ever used is Tartazni's 3.02, starting in Jan. A week ago copied over a new/fresh VPX. Only thing I set in script was turn on Flex...

FlexDMD= 1 ' 1=on 0=off : See instructions over for FLEX and Freezy MiddleDisplay= 1 ' 1=on 0=off ( 2=FlexDMD on Playfield: Will override FlexDMD setting ) ForceBackScreen= 0 ' 1=on 0=off : dB2S

... interestingly, when using ForceBackScreen= 1 it forces the 'blank dmd' to behind the Overlay. but, it will not let me save the location, so I can trick it into a location that would be covered by the overlay. I think DMDext is controlling/rendering that blank dmd so why doesnt it allow me to disable it or save the location?

I dont know why it would have different game names... dmddevice.log ... game name: BOUNTYHUNTER_main table script ... cGameName = "starwarsbh"

blank.jpg is not in the 3.02 download. There is not one in the zip in the "BountyHunterDMD" folder. I just made one - thx!

I dont know what version of Freezys', whatever Pinup Popper installs. I only have this issue on this table/pack.

wiesshund commented 1 year ago

I just re-downloaded and unzipped the table and loaded in editor cgamename says BOUNTYHUNTER not starwarsbh and blank.jpg was 100% in the DMD folder in the zip So not sure where you are getting your table from or whatnot?

Run FLexDMDUI.exe, you will see what version of freezys you have I have no idea what comes with popper, i dont use popper

Ltek commented 1 year ago

maybe you have an older version. I just DL'd again 2 mins ago, v3.02 from... https://vpuniverse.com/files/file/6450-starwars-bountyhunter/ Capture

wiesshund commented 1 year ago

https://i.imgur.com/LwYoAJO.jpg

Ltek commented 1 year ago

https://i.imgur.com/LwYoAJO.jpg Take a screenshot of the same section I did above... there is no way we are DLing the same file set if yours shows something different.

wiesshund commented 1 year ago

image

image

Ltek commented 1 year ago

WOW... I just DL'd from https://vpuniverse.com/files/file/6450-starwars-bountyhunter/

the zip says 3.02 but after copying (and overwriting all) I opened VPx, and Viewed script...

"Star Wars BountyHunter 3.0 (2021-22) by tartzani"

Wha?''

Can you please ZIP just the script text and upload here... I'll overwrite what I have and see what happens. Thanks for all the help... I dont get what is going on

Ltek commented 1 year ago

@wiesshund the plot thickens...

image

wiesshund commented 1 year ago

Try this? bountyhunter.srec.txt

Ltek commented 1 year ago

Try this? bountyhunter.srec.txt

Sorry was on holiday. I tried it, same issue. I'm going to install the latest DMDext and see if it help. This is crazy frustrating since I have added 6 tables since we started this thread and they all work fine - so I have over 50 tables without this issue, just this one does.

@freezy... I see in the latest version you are exposing registry settings in the UI, this is great - thank you. I hope you will consider removing all the registry settings completely and use text file stores like json, csv - anything really. A large part of the difficulty with VPx, Popper, etc is that settings are all over the place (registry, text files in multiple folders, etc)... and some settings can overlap/conflict. If they are all text format, in a single folder like \visual pinball\config, then we'd all have a far easier time doing setup and troubleshooting.

wiesshund commented 1 year ago

it already stores all the settings in dmddevice.ini

you dont have to use any registry settings, unless you want freezys to adopt vpm's window position data which vpn stores in registry.

Nothing, empty, see? Nothing saved in registry at all

image

Ltek commented 11 months ago

FYI - I installed the latest DMDext and that empty/black DMD is gone. I didnt change anything settings, script, etc. Only installed the newest DMDext build. This leads me to think there was a bug in the prior DMDext. I'll report back if I see anything else in the next few days as I play some more tables.

freezy commented 11 months ago

When you say latest, which build are you referring to?

Ltek commented 11 months ago

@freezy I finally got around to installing 2.2.0 beta and did a bunch more testing and think I found something!

After the BountyHunter FlexDMD is loaded that blank DMD persists across ALL other tables loaded after it. The only way to get rid of it is to close VPx entirely.

I've added screenshots where after closing BountyHunter... you can see no table running at all... and the blank DMD is there, I loaded Volkan - its there, then loaded Mortal Kombat -- the blank DMD is there still!

I dont see a process in Task Manager for B2S but maybe B2Sserver is starting a process and not releasing it... and its something specifically that the FlexDMD from BountyHunter is causing? This ONLY happens when FlexDMD from BountyHunter is loaded first.

20230731_194004 20230731_192958 20230731_193043 20230731_193750

Ltek commented 11 months ago

@freezy any ideas, this must be a rare bug I get that but it always happens on my system and only on this table... and now for all 3 versions of DMDext I've installed.

Ltek commented 11 months ago

hello?

freezy commented 11 months ago

Sorry, I didn't follow up. Can you post how to reproduce, step by step, along with a log, please?

Ltek commented 11 months ago

Sorry, I didn't follow up. Can you post how to reproduce, step by step, along with a log, please?

It happens every time. I have no specific steps. Just load/run the table in VPX 10.7.4

I see no mention of logging in the Wiki and my mind-reading skills are rusty with age so are you asking me to set LogPath setting in B2STableSettings.xml? (I looked around and found that file - that setting is empty)

Also, the XML (I didnt know it stored table settings) has the tables settings as...

  <starwarsbh>
    <HideGrill>1</HideGrill>
    <HideB2SDMD>0</HideB2SDMD>
    <HideDMD>1</HideDMD>
    <LampsSkipFrames>1</LampsSkipFrames>
    <SolenoidsSkipFrames>3</SolenoidsSkipFrames>
    <GIStringsSkipFrames>3</GIStringsSkipFrames>
    <LEDsSkipFrames>0</LEDsSkipFrames>
    <UsedLEDType>2</UsedLEDType>
    <IsGlowBulbOn>0</IsGlowBulbOn>
    <GlowIndex>-1</GlowIndex>
    <StartAsEXE>1</StartAsEXE>
    <StartBackground>0</StartBackground>
    <FormToFront>0</FormToFront>
    <FormToBack>1</FormToBack>
    <FormNoFocus>0</FormNoFocus>
    <Animations />
  </starwarsbh>
freezy commented 11 months ago

https://github.com/freezy/dmd-extensions#reporting-bugs

If I can't repro, I can't help. I can't mind read neither. I won't spend time trying to guess what's going on, specially on a problem reported by a single user.

Ltek commented 11 months ago

Apologies, my fault I didnt see that and thought the Wiki would have the info. The other thing that confused me is that I was looking for B2Sserver logging, not DMDdevice -- I did not associate that with DMDext or B2Sserver (vpin is confusing with multiple similarly named and interacting parts - example, until I posted here, I had no idea FlexDMD was DMDext)

I DO appreciate your help, and work on the DMD... I get the level of effort, my career has been in the software and hardware industry for 35 years.

Oddly I have different DmdDevice.log files... \vPinball\VisualPinball *no DmdDevice.log.config file here \vPinball\VisualPinball\VPinMAME ***DmdDevice.log.config is here

DmdDevice.log in vPinMame did not get updated, last updated 2 days ago.

I turned on Trace and opened the BountyHunter table...


[10] 2023/08/07 11:46:07.440  INFO | Added VirtualDMD renderer. 
[10] 2023/08/07 11:46:07.440  INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False 
[10] 2023/08/07 11:46:07.440  INFO | Applying default color to render graphs (#FFFF4500). 
[10] 2023/08/07 11:46:07.440  INFO | Setting up 2-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[10] 2023/08/07 11:46:07.440  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 => Gray2) 
[10] 2023/08/07 11:46:07.440  INFO | Setting up 4-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[10] 2023/08/07 11:46:07.440  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 => Gray4) 
[10] 2023/08/07 11:46:07.440  INFO | Setting up RGB24 Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[10] 2023/08/07 11:46:07.440  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 => Rgb24) 
[10] 2023/08/07 11:46:07.440  INFO | Setting up Alphanumeric Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[10] 2023/08/07 11:46:07.440 DEBUG | DMD position: No registry because it's ignored. 
[10] 2023/08/07 11:46:07.548  INFO | Creating FBOs for 128x32 
 [1] 2023/08/07 11:46:08.506  INFO | Starting VPinMAME API 2.2.0-BETA2 (x86) through VPinballX.exe. 
 [1] 2023/08/07 11:46:08.506  INFO | Assembly located at C:\vPinball\VisualPinball\VPinMAME\dmddevice.dll 
 [1] 2023/08/07 11:46:08.506  INFO | Running in C:\vPinball\VisualPinball\Tables 
 [1] 2023/08/07 11:46:08.506  INFO | [dll] Create(): New output id is 1 
 [1] 2023/08/07 11:46:08.506  INFO | [dll] Open(1) 
 [1] 2023/08/07 11:46:08.506  INFO | [dll] PM_GameSettings(1, BOUNTYHUNTER_main, 0) 
 [1] 2023/08/07 11:46:08.506  INFO | Disabling game colorization 
 [1] 2023/08/07 11:46:08.506  INFO | Setting game name: BOUNTYHUNTER_main 
 [1] 2023/08/07 11:46:08.506  INFO | Setting color: #FFFF9658 
 [1] 2023/08/07 11:46:08.506  INFO | Opening virtual display... 
[19] 2023/08/07 11:46:08.506  INFO | Added VirtualDMD renderer. 
[19] 2023/08/07 11:46:08.506  INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False 
[19] 2023/08/07 11:46:08.506  INFO | Applying default color to render graphs (#FFFF9658). 
[19] 2023/08/07 11:46:08.506  INFO | Setting up 2-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[19] 2023/08/07 11:46:08.506  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 => Gray2) 
[19] 2023/08/07 11:46:08.506  INFO | Setting up 4-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[19] 2023/08/07 11:46:08.506  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 => Gray4) 
[19] 2023/08/07 11:46:08.506  INFO | Setting up RGB24 Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[19] 2023/08/07 11:46:08.506  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 => Rgb24) 
[19] 2023/08/07 11:46:08.506  INFO | Setting up Alphanumeric Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[19] 2023/08/07 11:46:08.506 DEBUG | DMD position: No registry because it's ignored. 
[19] 2023/08/07 11:46:08.548  INFO | Creating FBOs for 128x32 
 [1] 2023/08/07 11:46:44.248  INFO | [dll] Close(1) 
 [1] 2023/08/07 11:46:44.248  INFO | Closing up. 
 [1] 2023/08/07 11:46:44.387 DEBUG | Disposing 2-bit Passthrough Graph... 
 [1] 2023/08/07 11:46:44.387  INFO | Source for 1 renderer(s) stopped. 
 [1] 2023/08/07 11:46:44.387 DEBUG | Disposing 4-bit Passthrough Graph... 
 [1] 2023/08/07 11:46:44.387  INFO | Source for 1 renderer(s) stopped. 
 [1] 2023/08/07 11:46:44.387 DEBUG | Disposing RGB24 Passthrough Graph... 
 [1] 2023/08/07 11:46:44.387  INFO | Source for 1 renderer(s) stopped. 
 [1] 2023/08/07 11:46:44.387 DEBUG | Disposing Alphanumeric Passthrough Graph... 
 [1] 2023/08/07 11:46:44.387  INFO | Source for 0 renderer(s) stopped.
freezy commented 11 months ago

When I say step-by-step, I mean something like that:

  1. Download table from VPU
  2. Open script, set FlexDMD=1
  3. Run table - 2 DMDs open, one black and one with content
  4. Play some - the content one updates, the other stays black
  5. Exit table - the content DMD closes, the black one stays.

Log:

 [1] 2023/08/07 20:35:35.785  INFO | Starting DmdDevice API 2.2.0-SNAPSHOT (x86) through VPinballX.exe. 
 [1] 2023/08/07 20:35:35.785  INFO | Assembly located at L:\Visual Pinball\VPinMAME\dmddevice.dll 
 [1] 2023/08/07 20:35:35.785  INFO | Running in L:\Visual Pinball\Tables 
 [1] 2023/08/07 20:35:35.785  INFO | Successfully loaded config from L:\Visual Pinball\VPinMAME\DmdDevice.ini. 
 [1] 2023/08/07 20:35:35.785  INFO | [serum] Determined altcolor path from assembly path: L:\Visual Pinball\VPinMAME\altcolor 
[12] 2023/08/07 20:35:35.810  INFO | Added VirtualDMD renderer. 
[12] 2023/08/07 20:35:35.810  WARN | Error opening PinUP output: ROM name must not be null. 
[12] 2023/08/07 20:35:35.810  INFO | Transformation  options: Resize=Fit, HFlip=False, VFlip=False 
[12] 2023/08/07 20:35:35.810  INFO | Applying default color to render graphs (#FFFF4500). 
[12] 2023/08/07 20:35:35.810  INFO | Setting up 2-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[12] 2023/08/07 20:35:35.810  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 => Gray2) 
[12] 2023/08/07 20:35:35.810  INFO | Setting up 4-bit Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[12] 2023/08/07 20:35:35.810  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 => Gray4) 
[12] 2023/08/07 20:35:35.810  INFO | Setting up RGB24 Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[12] 2023/08/07 20:35:35.810  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 => Rgb24) 
[12] 2023/08/07 20:35:35.811  INFO | Setting up Alphanumeric Passthrough Graph for 1 destination(s) [ Virtual DMD ] 
[12] 2023/08/07 20:35:35.939  INFO | Creating FBOs for 128x32 
 [1] 2023/08/07 20:35:36.885  INFO | [dll] Create(): New output id is 1 
 [1] 2023/08/07 20:35:36.885  INFO | [dll] Open(1) 
 [1] 2023/08/07 20:35:36.885  INFO | [dll] PM_GameSettings(1, starwarsbh_main, 0) 
 [1] 2023/08/07 20:35:36.885  INFO | Disabling game colorization 
 [1] 2023/08/07 20:35:36.885  INFO | Setting game name: starwarsbh_main 
 [1] 2023/08/07 20:35:36.891  INFO | Setting color: #FFFF9658 
 [1] 2023/08/07 20:35:36.891  INFO | Opening virtual display... 
[25] 2023/08/07 20:35:36.911  INFO | Added VirtualDMD renderer. 
[25] 2023/08/07 20:35:36.911  INFO | [pinup] Starting starwarsbh_main... 
[25] 2023/08/07 20:35:36.911  INFO | Added PinUP renderer. 
[25] 2023/08/07 20:35:36.911  INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False 
[25] 2023/08/07 20:35:36.911  INFO | Applying default color to render graphs (#FFFF9658). 
[25] 2023/08/07 20:35:36.911  INFO | Setting up 2-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 => Gray2) 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice 2-bit Source to PinUP Writer (Gray2 => Gray2) 
[25] 2023/08/07 20:35:36.911  INFO | Setting up 4-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 => Gray4) 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice 4-bit Source to PinUP Writer (Gray4 => Gray4) 
[25] 2023/08/07 20:35:36.911  INFO | Setting up RGB24 Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 => Rgb24) 
[25] 2023/08/07 20:35:36.911  INFO |   -> Connecting DmdDevice RGB24 Source to PinUP Writer (Rgb24 => Gray4) 
[25] 2023/08/07 20:35:36.911  INFO | Setting up Alphanumeric Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[25] 2023/08/07 20:35:36.965  INFO | Creating FBOs for 128x32 
 [1] 2023/08/07 20:35:47.248  INFO | [dll] Close(1) 
 [1] 2023/08/07 20:35:47.248  INFO | Closing up. 
 [1] 2023/08/07 20:35:47.253  INFO | Source for 2 renderer(s) stopped. 
 [1] 2023/08/07 20:35:47.253  INFO | Source for 2 renderer(s) stopped. 
 [1] 2023/08/07 20:35:47.253  INFO | Source for 2 renderer(s) stopped. 
 [1] 2023/08/07 20:35:47.253  INFO | Source for 0 renderer(s) stopped.

On the bright side, I was able to reproduce. Will look into it, but not a priority. Probably a bug how FlexDMD is used, but will need to confirm.

Note that the game name in my log is starwarsbh_main while yours is BOUNTYHUNTER_main, which makes me think that you're using another table?

Ltek commented 11 months ago

"starwarsbh" is correct. I was testing (and forgot to revert) Wiesshund's script (discussion is above) . cGameName = "starwarsbh" was confirmed by table author Tartzani in his table thread https://vpuniverse.com/files/file/6450-starwars-bountyhunter/?do=findComment&comment=45968

wiesshund commented 11 months ago

On the bright side, I was able to reproduce. Will look into it, but not a priority. Probably a bug how FlexDMD is used, but will need to confirm.

How did you reproduce it? I couldn't make it happen at all?

freezy commented 11 months ago

See my description above. I'll post more details when I know more.

Ltek commented 9 months ago

@freezy just checking to see if there is an ETA for a fix? thx

Ltek commented 9 months ago

@freezy I think I found another that does this... the latest release of Fathom. It will not remove that DMD box no matter wht I try... with F1 menu if I disable either box, it still stays. 20231001_141843

wiesshund commented 9 months ago

you sure you do not have use external DLL enabled in vpm or being forced in table script or something?

cause not only do you have the virtual DMD showing, you have also picked a color, because it is orange by default

freezy commented 9 months ago

@freezy just checking to see if there is an ETA for a fix? thx

Sorry, but my focus is on other projects right now. I will revisit this eventually, but asking for ETAs will not make this progress more quickly.