Jump to content

Recommended Posts

Posted

Looking for anyone who has has seen this issue, or has an educated idea what it might be. I have tried a LOT (see below) and this was working fine for a long time (years). Nothing changed on the system that I know of... no windows updates since Nov 2025. Popper, VPX, etc al lthe same for a long time.

 

 

Issue: All PuPs (and B2Ss) load and run fine UNLESS they use Pup Capture. PuP Captures load the startup/attract overlays/videos but nont of the DMD changes send triggers to Popper, it seems.

I've been over everything I can think of (Freezy settings, etc). I created the Transformers PuP Pack (uses 100% DMD capture triggers) and I'm using that for my main testing but I have checked others, like StarWars Data East.

Tried...

  • Updating to Pinup 2 beta... did not help. (even a 1.5 reinstall all Popper files from backup did not help)
  • \VisualPinball\Tables\ Plugins and Plugins64 both have shortcuts for DirectOutput and PinUPPlayerB2SDriver
  • C:\vPinball\PinUPSystem\PinUPPlayerB2SDriver exists and files are there
  • DOF is working on all tables
  • B2Sserver (latest ver) process loads when a tables loads a .directb2s file
  • Freezy/DMDext (latest ver) installed, DMDs works fine (F1 shows the menu no issues, no errors)
  • DMDdevice.ini has pinup enabled = true
  • DMDext colorize is disabled



pinupDebugLog shows only a starting triggers...

20260606 08:04:55 Screen InitRoot tf_180og
20260606 08:04:55 Display Load Settings 12
20260606 08:04:55 Sending B2S D0 Event
20260606 08:04:55 PUP Connection Increased
20260606 08:04:55 PlayMedia 1 c:\vpinball\pinupsystem\pupvideos\tf_180og\dmd underlay\default dmd_ltek.mp4
20260606 08:04:55 VLC Sent Media 1 c:\vpinball\pinupsystem\pupvideos\tf_180og\dmd underlay\default dmd_ltek.mp4
20260606 08:04:55 B2S Event Fired  Default
20260606 08:04:56 PlayMedia 5 c:\vpinball\pinupsystem\pupvideos\tf_180og\attractmode\transformers g1 season 1 intro and outro (1984) [hq].mp4
20260606 08:04:56 VLC Sent Media 5 c:\vpinball\pinupsystem\pupvideos\tf_180og\attractmode\transformers g1 season 1 intro and outro (1984) [hq].mp4
20260606 08:04:56 B2S Event Fired  Attract - was D2


the Puplog.txt logs (see below) are odd - StarWars 'sees' the Captures but Transformers does not, yet neither work.

Transformers ... 

20260606 10:02:09 Open called
20260606 10:02:09 Set Game Name thread tf_180
20260606 10:02:10 Start Thread Matching
20260606 10:02:10 create PuPCap
20260606 10:02:10 Init Game name:tf_180
20260606 10:02:10 No PuPCapture found:  nothing to do

StarWars...

20260606 08:23:30 Init Game name:stwr_a14
20260606 08:23:30 Create Object Display
20260606 08:23:30 imagedir:C:\vPinball\PinUPSystem\PuPVideos\stwr_a14\PuPCapture
20260606 08:23:30 num images 90 


 

Posted

Are you absolutely certain that Windows hasn't stealth installed any updates? The issue sounds like a conflict between 32-Bit and 64-Bit DLLs, which is exactly what happened to me a week ago when Windows stealth installed the KB5089573 update and rebooted my machine while I was away. It broke EVERYTHING to do with PUP functionality and I estimate it took me over 40 hours to isolate and solve. If this is the case, run an elevated command prompt and use this code:

wusa /uninstall /kb:5089573


Just reboot and throw up a middle finger or two for Windows being Windows 🥂

Posted (edited)
1 hour ago, kiloNova said:

Are you absolutely certain that Windows hasn't stealth installed any updates? The issue sounds like a conflict between 32-Bit and 64-Bit DLLs, which is exactly what happened to me a week ago when Windows stealth installed the KB5089573 update and rebooted my machine while I was away. It broke EVERYTHING to do with PUP functionality and I estimate it took me over 40 hours to isolate and solve. If this is the case, run an elevated command prompt and use this code:
 

wusa /uninstall /kb:5089573


Just reboot and throw up a middle finger or two for Windows being Windows 🥂

Windows update does not show any updates since Nov 2025.

image.png.68b3fabfec0cbb48e6286ef345767721.png

My PuPs do run. For example, in my Tron Neon table I use PuPevents to trigger screens, and that works... but in Transformers PuP, I used PuPcaptures.... which is not working for me.

Edited by LTek
Posted

looks like b2splugin/table script is using "tf_180og",  but freezy/pupcapture is using "tf_180".     so freezy is expecting pupvideos\tf_180\pupcaptures folder.

 

 

 

 

Posted (edited)

Thank you!  after a while staring a logs, etc 2 little letters make your eyes trick your brain.

BUT other pup capture packs (which I did not mess with the game names) have blank backglasses. (I've tested Batman Dark Knight, Tron Legacy and Star Wars Data East). All the same prob, and they are all PuPCaptures. 
Backglasses work on all the other tables B2S, Pups, etc


If I test these packs in the PuP editor, the backglasses work fine. It seems that something is not seeing the triggers?

 

20260606 19:42:56 Open called
20260606 19:42:56 Set Game Name thread bdk_294
20260606 19:42:58 Start Thread Matching
20260606 19:42:58 create PuPCap
20260606 19:42:58 Init Game name:bdk_294
20260606 19:42:58 Create Object Display
20260606 19:42:58 imagedir:C:\vPinball\PinUPSystem\PuPVideos\bdk_294\PuPCapture
20260606 19:42:58 num images 111
20260606 19:44:55 Free Object Display

all of them are also seen my dmddevice...

 [6] 2026/06/06 19:58:44.185  INFO | Reloading config from C:\vPinball\VisualPinball\VPinMAME\DMD Extensions\DmdDevice.ini. 
 [6] 2026/06/06 19:58:44.185  INFO | Setting game name: trn_174h 
 [6] 2026/06/06 19:58:44.185  INFO | Setting color: #FFFF5820 
 [6] 2026/06/06 19:58:44.185  INFO | Opening virtual display... 
 [4] 2026/06/06 19:58:44.209  INFO | Added VirtualDMD renderer. 
 [4] 2026/06/06 19:58:44.209  INFO | [pinup] Starting trn_174h... 
 [4] 2026/06/06 19:58:44.218  INFO | Added PinUP renderer. 

Edited by LTek
Posted

i assume you're testing outside of any frontend, running directly from vpx.

 

  if you see 'black' backglass,  if you alt-tab,  is there a b2sform that is all-black and covering the pup?  other than that I don't know what it could be.  does alt-tab see the pup on a different monitor or behind playfield.

Posted (edited)

@NailBuster  I found the issue (dont know how to fix)... there is a problem with PinupDisplay not running/loading. If you have any ideas why this is happening,  maybe something is not registered in Windows, etc... I'd appreciate it. I'm considering running Baller installer and then restoring the database to see if that fixes it. I suspect its not something huge since the rest of Pinup works perfectly.

Test method 1:  Launching through VPX -- PinupDisplay never loads 
Test method 2:  add table script (code below) to force it, everything works perfectly even when launching only through VPX
Test method 3:  Launching through PinUp Menu -- PinupDisplay loads into memory, but is not working properly. You can see how there are two instances, and only 1 has a PNG showing, the other should be a video and it is not there.

Seem the comms to load PinupDisplay is not happening or getting lost? 

image.thumb.png.0859ac032fd9ff92544e572810f1f638.png

Are B2Sdrivers (your page on it), shortcuts in the Plugins / Plugins64 or the DLLs themselves?  I have tried both, currently have the files themselves.

📁 B2SServer (or \Tables if your DLL is there)
   └── 📄 B2SBackglassServer.dll
   └── 📁 Plugins
        └── 📁 PinUPPlayerB2SDriver
             └── 📄 B2SServerPluginInterface.dll
             └── 📄 PinUpPlayerB2SDriver.dll

 

' ---------- PINUP PLAYER: STARTUP & CONTROL SECTION ----------
Dim PuPlayer: Dim PUPStatus: PUPStatus=false ' dont edit this line!!!  


Sub PuPStart(cGameName)
    If PUPStatus=true then Exit Sub
    If usePUP=true then
        Set PuPlayer = CreateObject("PinUpPlayer.PinDisplay")
        If PuPlayer is Nothing Then
            usePUP=false
            PUPStatus=false
        Else
            PuPlayer.B2SInit "",cGameName  'start the Pup-Pack
            PUPStatus=true
        End If
    End If
End Sub

' ---------- Placed at end of Table Init ----------

PuPStart(cGameName) 






 

Edited by LTek
Posted (edited)

@NailBuster any idea on where the comms issue is?

is this an accurate flow for PuPcapture packs? when the packs load, the only process in memeory is PinupPlayer... not PUPDMDControl, PupCapture or any PinupDisplay
VPX
 ↓
VPinMAME
 ↓
External DMD enabled
 ↓
dmddevice.dll
 ↓
Frames sent to PinUP
 ↓
PUPDMDControl.exe
 ↓
PinUpPlayer.exe
 ↓
PuPCapture image matching
 ↓
Trigger videos/playlists
 ↓
PinUpDisplay.exe

Edited by LTek
Posted

sounds like you maybe upgraded b2s manually??   and maybe even moved it out of tables? 

 

if you can run something like stranger things table via popper (that table doesn't use b2s) and it works,  then its your b2s setup that's the prob.

 

need to figure out your b2s/plugins/com stuff.  May also need to rollback if you're on latest nightlies of b2s or vpinmame or dmdext.  PinUpdater has the most stable files, but not nightlies.

 

if you have a backup/image of your cab from when all was working I'd do that.   pup v2 upgrade is file based update only (didn't change any file settings) so you can rollback the exes is all that's needed.

 

theres also pinupregister.bat files in pinupsystem that you can run as admin to reregister pup.   also b2server has its own re-register exes as well that you need to use if you do stuff manually.

 

 

Posted

B2Sserver triggers PUPDMDControl.exe to start the Pupcapture processing?

Everything works (B2S tables, regular PuP Pack tables, etc) except if the PuP Pack uses PupCapture.  As I mentioned, if I manually ad the code to force Popper to load, it does and the PuPcapture Packs work.

Over the past 3 days I reinstalled B2Sserver, Pinup Popper 1.5 & 2.0, and DMDext -- multiple times -- reregistering multiple times. 

B2Sserver files always in the Tables folder
DMDext files always in VpinMame folder

 

Posted

pupdmdcontrol.exe is not used for dmdext.   (that is for realdmd and popper driver)

 

dmddevice.dll -->  dmddevicepup.dll   is where the frame matching/events happen.  (xxx64.dll for 64 bit dmdext)

 

so just having external dll checked is all that is needed for dmdext to startup framematching/pup if enabled.

 

Posted (edited)

OK, thought dmddevice.dll controlled it so I'm baffled -- I used your Popper Updater and also tried manually downloading the latest version from github... same issue.  the Plugins folders have the DLLs, the DMDext has 'external' checked, I've tried changing the dmddevice.ini settings colorize true/false and more. I've made/published 2 Pupcapture pups (Transformers and Batman Dark Knight), its not like I'm 'new' 😉

and since the pups work when i add table script to force the launch, it does seem clear that whtever triggers Popper to start up, is not triggering poppe

PuPlayer.B2SInit "",cPuPPack


 

Edited by LTek
Posted

pup v2.0 is stable (over 2K users now).  So i'd stick with that version,  because it also has more debug info as well.

 

update v2.0 and run pupeventviewer.exe BEFORE anything else and see if that helps you out.

Posted (edited)
20 minutes ago, NailBuster said:

pup v2.0 is stable (over 2K users now).  So i'd stick with that version,  because it also has more debug info as well.

 

update v2.0 and run pupeventviewer.exe BEFORE anything else and see if that helps you out.

installed Popper 2

also, in case you did not see my edit above: when I  force popper to launch via table script, Pupcapture packs play fine. Using ... PuPlayer.B2SInit "",cPuPPack



EventvViewer...
 

=====    PuPEvent Viewer    2026/06/09 16:41:39    PinUP Event Viewer Active: 2026/06/09 16:41:39
2364    *svchost.exe    2026/06/09 16:41:40    Stopped: svchost.exe (PID: 2364) closed. Exit Code: 0
14192    *dllhost.exe    2026/06/09 16:41:44    Stopped: dllhost.exe (PID: 14192) closed. Exit Code: 0
9060    *VPinballX.exe    2026/06/09 16:41:45    Windows Started: VPinballX.exe (PID: 9060)
5240    *DataExchangeHost.exe    2026/06/09 16:41:56    Windows Started: DataExchangeHost.exe (PID: 5240)
7504    <Process Not Found or Access Denied>    2026/06/09 16:42:00    [0609/164200.797:ERROR:third_party\webrtc\modules\desktop_capture\win\dxgi_output_duplicator.cc:209] Failed to capture frame: HRESULT: 0x887A0026, Message: The keyed mutex was abandoned.

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:00    [0609/164200.816:ERROR:third_party\webrtc\modules\desktop_capture\win\screen_capturer_win_directx.cc:166] DxgiDuplicatorController failed to capture desktop, error code Duplication failed

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:01    [0609/164201.004:WARNING:third_party\webrtc\modules\desktop_capture\win\dxgi_adapter_duplicator.cc:116] Cannot initialize any DxgiOutputDuplicator instance.

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:01    [0609/164201.004:WARNING:third_party\webrtc\modules\desktop_capture\win\dxgi_duplicator_controller.cc:286] Failed to initialize DxgiAdapterDuplicator on adapter 1

9340    *PinUpPlayer.exe    2026/06/09 16:42:11    Windows Started: PinUpPlayer.exe (PID: 9340)
9340    PinUpPlayer.exe    2026/06/09 16:42:17    PUPLAYER:  HANDLE LAST RELEASE PinUpDisplayMain
9340    PinUpPlayer.exe    2026/06/09 16:42:17    PUPLAYER:  Killing server title PUPMENU
9340    *PinUpPlayer.exe    2026/06/09 16:42:17    Stopped: PinUpPlayer.exe (PID: 9340) closed. Exit Code: 0
7504    <Process Not Found or Access Denied>    2026/06/09 16:42:18    [0609/164218.197:ERROR:third_party\webrtc\modules\desktop_capture\win\dxgi_output_duplicator.cc:209] Failed to capture frame: HRESULT: 0x887A0026, Message: The keyed mutex was abandoned.

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:18    [0609/164218.227:ERROR:third_party\webrtc\modules\desktop_capture\win\screen_capturer_win_directx.cc:166] DxgiDuplicatorController failed to capture desktop, error code Duplication failed

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:18    [0609/164218.397:WARNING:third_party\webrtc\modules\desktop_capture\win\dxgi_adapter_duplicator.cc:116] Cannot initialize any DxgiOutputDuplicator instance.

7504    <Process Not Found or Access Denied>    2026/06/09 16:42:18    [0609/164218.397:WARNING:third_party\webrtc\modules\desktop_capture\win\dxgi_duplicator_controller.cc:286] Failed to initialize DxgiAdapterDuplicator on adapter 1

5240    *DataExchangeHost.exe    2026/06/09 16:42:27    Stopped: DataExchangeHost.exe (PID: 5240) closed. Exit Code: 0
6592    *backgroundTaskHost.exe    2026/06/09 16:42:32    Windows Started: backgroundTaskHost.exe (PID: 6592)



Also, the DMDdevice Log shows its all loading...

 

[6] 2026/06/09 16:42:04.453  INFO | Starting DmdDevice API 2.3.1 (x64) through VPinballX.exe. 
 [6] 2026/06/09 16:42:04.488  INFO | Assembly located at C:\vPinball\VisualPinball\VPinMAME\DmdDevice64.dll 
 [6] 2026/06/09 16:42:04.488  INFO | Running in C:\vPinball\visualpinball\Tables 
 [6] 2026/06/09 16:42:04.511  INFO | Successfully loaded config from C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini. 
 [6] 2026/06/09 16:42:04.573  INFO | [serum] Determined altcolor path from assembly path: C:\vPinball\VisualPinball\VPinMAME\altcolor 
 [6] 2026/06/09 16:42:05.688  INFO | [dll] Open(0) 
 [6] 2026/06/09 16:42:05.688  INFO | [dll] Set_4_Colors_Palette(device: 0, 0%: #000000, 33%:#0600D6, 66%:#E10FC1, 100%:#FF5820) 
 [6] 2026/06/09 16:42:05.688  INFO | [dll] PM_GameSettings(0, bdk_294, 1) 
 [6] 2026/06/09 16:42:05.688  INFO | Enabling game colorization 
 [6] 2026/06/09 16:42:05.688  INFO | Setting game name: bdk_294 
 [6] 2026/06/09 16:42:05.688  INFO | Setting color: #FFFF5820 
 [6] 2026/06/09 16:42:05.688  INFO | Opening virtual display... 
[16] 2026/06/09 16:42:05.772  INFO | Added VirtualDMD renderer. 
[16] 2026/06/09 16:42:05.779  INFO | [pinup] Starting bdk_294... 
[16] 2026/06/09 16:42:05.779  INFO | Added PinUP renderer. 
[16] 2026/06/09 16:42:05.779  INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | Applying palette to render graphs. 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.794  INFO | [RenderGraph] SetColor(0%: #FF000000, 33%:#FF551700, 66%:#FFAA2E00, 100%:#FFFF4500) 
[16] 2026/06/09 16:42:05.818  INFO | Setting up 2-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[16] 2026/06/09 16:42:05.828  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 -> Gray2) - deduped 
[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice 2-bit Source to PinUP Writer (Gray2 -> Gray2) - not deduped 
[16] 2026/06/09 16:42:05.840  INFO | Setting up 4-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 -> Gray4) - deduped 
[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice 4-bit Source to PinUP Writer (Gray4 -> Gray4) - not deduped 
[16] 2026/06/09 16:42:05.840  INFO | Setting up RGB24 Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 -> Rgb24) 
[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice RGB24 Source to PinUP Writer (Rgb24 -> Gray4) 
[16] 2026/06/09 16:42:05.840  INFO | Setting up Alphanumeric Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[16] 2026/06/09 16:42:05.840 DEBUG | DMD position: No registry because it's ignored. 
[16] 2026/06/09 16:42:06.179  INFO | Creating FBOs for 128x32 
 [6] 2026/06/09 16:42:17.334  INFO | [dll] Close(0) 
 [6] 2026/06/09 16:42:17.334  INFO | Closing up. 
 [6] 2026/06/09 16:42:17.350 DEBUG | Disposing 2-bit Passthrough Graph... 
 [6] 2026/06/09 16:42:17.350  INFO | Source for 2 renderer(s) stopped. 
 [6] 2026/06/09 16:42:17.570 DEBUG | Disposing 4-bit Passthrough Graph... 
 [6] 2026/06/09 16:42:17.570  INFO | Source for 2 renderer(s) stopped. 
 [6] 2026/06/09 16:42:17.570 DEBUG | Disposing RGB24 Passthrough Graph... 
 [6] 2026/06/09 16:42:17.570  INFO | Source for 2 renderer(s) stopped. 
 [6] 2026/06/09 16:42:17.570 DEBUG | Disposing Alphanumeric Passthrough Graph... 

 

Edited by LTek
Posted (edited)

i have no idea why b2s/dmdext wouldn't start your pup.  Either one will start the pup.   I'd try dmdext v2.3.0 and b2s v2.1.2 as thats the default in baller.  Maybe try non-color roms too.

 

"[16] 2026/06/09 16:42:05.840  INFO |   -> Connecting DmdDevice RGB24 Source to PinUP Writer (Rgb24 -> Gray4) "    this might be something as older dmdext didn't down convert to gray4 ?  

older dmdext had this in log

[10] 2025/01/17 11:14:36.048  INFO | Connecting VPM RGB24 Source to PinUP Writer (Rgb24 => Bitmap) 

 

maybe nothing, but dont know why dmdext sends gray4 instead of bitmap now?  maybe they are same thing, need to ask dmdext devs.

 

also,  what is that 3rd party events/errors trying to screen grab/capture your desktop during vpx?  were you recording something?

Edited by NailBuster
Posted (edited)

Since B2S and/or DMDext will start the PuP, whatever should be  'listening' or registered in Windows (?) is not... or are they making a specific call to something? I can try to trace it. Since forcing via script makes it work perfectly, it must be something simple in the Windows registry, or some sort of process that is failing Id think?  Unfortunately the Event viewer does not capture anything helpful for troubleshooting this. It shows B2Sserver loading, that's all.

The COM object looks like it is registered fine

HKEY_CLASSES_ROOT\PinUpPlayer.PinDisplay
    (Default)    REG_SZ    PinUP Player Com Object

HKEY_CLASSES_ROOT\PinUpPlayer.PinDisplay\Clsid
    (Default)    REG_SZ    {88919FAC-00B2-4AA8-B1C7-52AD65C476D3}



ROMs have not changed, same ones I've used since day one. All of this was working perfectly until about a two weeks ago. It has been a month or so since I played prior to that. 

I had all the newer B2S & DMDext running/working before (I installed them long ago)... Today I re-installed popper v1.5 (for I think the 3rd time in 2 days) with the updater and that looks like it installed older versions of B2S & DMDext.  So those are the versions I'm still using. Then you suggested updating to popper v2, which I just did before my last post.  So... with the Gray4 thing, that is happening using the version popper updater installs.

I ran multiple tables, with both the DMDext that comes with Popper Updater, and the latest 2.4.0 (github)... they both never show a conversion to Bitmap.
here's one example...
 

[23] 2026/06/09 20:21:01.995  INFO | Setting up 2-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 2-bit Source to Virtual DMD (Gray2 -> Gray2) - deduped 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 2-bit Source to PinUP Writer (Gray2 -> Gray2) - not deduped 
[23] 2026/06/09 20:21:01.995  INFO | Setting up 4-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 4-bit Source to Virtual DMD (Gray4 -> Gray4) - deduped 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 4-bit Source to PinUP Writer (Gray4 -> Gray4) - not deduped 
[23] 2026/06/09 20:21:01.995  INFO | Setting up 8-bit Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 8-bit Source to Virtual DMD (Gray8 -> Gray8) 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice 8-bit Source to PinUP Writer (Gray8 -> Gray4) 
[23] 2026/06/09 20:21:01.995  INFO | Setting up RGB24 Passthrough Graph for 2 destination(s) [ Virtual DMD, PinUP Writer ] 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice RGB24 Source to Virtual DMD (Rgb24 -> Rgb24) 
[23] 2026/06/09 20:21:01.995  INFO |   -> Connecting DmdDevice RGB24 Source to PinUP Writer (Rgb24 -> Gray4) 



Those 3rd party events are known common errors when switching in/out of Full Screen Exclusive - the GPU looses connection for a moment. When VPX loads/unloads the table. I've always (3+ yrs) used FS Exclusive.  As a test, I ran Windowed, no 3rd party errors, but also, did not fix the issue of course. 

Edited by LTek
Posted

Solved... the PinUpPlayerB2SDriver.dll was an old version, and it was not working properly. How that got there is beyond me... but I knew it was something simple. So if you see it again, you know that PupCaptures Packs will not launch with an older version of that driver -- at least with Popper 1.5 and 2.0

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