NailBuster Posted March 2 Author Posted March 2 12 hours ago, Dicentim said: I also posted my issue on your Facebook group. lets start with process of elimination. if you set useDMD=false in popper (disabling realdmd/pindmd interface in popper). do you still have the problem of blinking? Also, for others. BETA18 is up on the wiki (first post link in this thread). it has a pinupEvent utility that will log system/pup events to help troubleshoot. Seems like it hleped find the reason for stuarts (above) issue with crashing on startup being a MSI sound utility overlay... still investigating.
Stuart Posted March 2 Posted March 2 It turned out to be the Nahimic service fdrom ASUS. It's sound studio app. I think I installed it to get 7.1 working for SSF. Disableing it got rid of the black screen and except for the quieter scrolling through the game wheel which I am good with, it seems to be workiong properly now with 2.0. Not sure I see any difference but I guess it has benifits Appreciate NailBusters help to decipher the issue. Stuart
Dicentim Posted March 3 Posted March 3 11 hours ago, NailBuster said: lets start with process of elimination. if you set useDMD=false in popper (disabling realdmd/pindmd interface in popper). do you still have the problem of blinking? Also, for others. BETA18 is up on the wiki (first post link in this thread). it has a pinupEvent utility that will log system/pup events to help troubleshoot. Seems like it hleped find the reason for stuarts (above) issue with crashing on startup being a MSI sound utility overlay... still investigating. Hi, First I installed beta 1.8. SSF issue is fixed, thanks. Still have this "double DMD" (Pin2DMD + VirtualDMD on backglass) issue. Good news is now when exiting a table and returning to Pinup Home Menu the playfield is displaying after about 1 second. The difference between this new PinupdisplayX version and the 1.5 is that during this second I can see the Desktop menu instead of the back screen during transition. Of course black screen is better. Here is the log of PinUP Event Viewer : Then I tried to see for this double DMD issue. When turning usedmd=false in Pinup Script, the Pin2DMD disappeared in Menu but the virtual DMD was still present. Then I tried to completely turn DMD on "None" : But there was still a solid black virtual DMD, displaying nothing during the menu screens. Finally I turned the DMD on Off in this menu : And there's no DMD display at all. But it didn't fixed the 1 second desktop display issue when exiting a table. Cheers.
NailBuster Posted March 3 Author Posted March 3 11 hours ago, Dicentim said: Hi, Here is the log of PinUP Event Viewer : can you try a couple more items. can you see if DOF is slowing your exit? if you useDOF=false does that speed up your return? as far as two dmd. you can in popper theme set your BG to forceON to be ontop of the small mirror-dmd. on a side note: not a pinup thing, but why is that swUSB.exe constantly coming up with those messages/ do you have a weird USB device that is reconnecting/disconnecting or something? swusb.exe is a system event.
Dicentim Posted March 4 Posted March 4 I've tried to set useDOF=false and the return toHomeMenu is taking the same time (about 1 second). Please note that returning to HomeMenu is taking the same time using PinupDisplayX 1.5 but the difference is that there's a black screen during the transition so that's Ok. With new version there's no black screen during return so I can see Windows desktop and that looks odd. About the USB messages, I really don't know I have no physical disconnections.
Cliffy Posted March 4 Posted March 4 1 hour ago, Dicentim said: About the USB messages, I really don't know I have no physical disconnections. From google ai; swusb.exe (Switch USB) is a legitimate but often problematic background process, usually installed by Realtek or ASUS USB wireless drivers (e.g., USB-N53, USB-AC56) to manage USB 2.0/3.0 switching. It is known to cause memory leaks, high RAM usage, system crashes, and prevent clean shutdowns.
embryodead Posted March 5 Posted March 5 Hi, Running lastest Pinup beta18 and wanted to report a strange bug. On Space Cadet Galactic edition the backglass PUP is not showing on screen 2 only a black screen. If you click on the screen with the mousse the backglass show up. It seems to be hidden behond some kind of blackscreen. Try to change setting in the pup and it is always the sae behavior even in force show on. Best
NailBuster Posted March 5 Author Posted March 5 (edited) 3 hours ago, embryodead said: Hi, Try to change setting in the pup and it is always the sae behavior even in force show on. Best not a v2.0 bug it's just some pup-layouts need some minor corrections to their setup, this packs two-screen setup is missing a D0 trigger for bg with overlapping pups. Easy workaround is to just set that puppack to stay on v1.5. (see beta wiki page on how to do that, takes 2 seconds to set). Edited March 5 by NailBuster
embryodead Posted March 5 Posted March 5 2 hours ago, NailBuster said: not a v2.0 bug it's just some pup-layouts need some minor corrections to their setup, this packs two-screen setup is missing a D0 trigger for bg with overlapping pups. Easy workaround is to just set that puppack to stay on v1.5. (see beta wiki page on how to do that, takes 2 seconds to set). Thank for your fast reply, i noticed the lack of a D0 trigger and try to correct it myself, but after numerous try i didnt find any way to get make it show a the start of the table( full dmd was working fine) It is not the only pup whith this behavior as i check many of them. Thank you fot un input on the use of the usePuPDriver.ini i will use it for all the problematic pup i discovered Just one quick question, are the performance better using pinup 2.0 on legacy pup or only future pup can benefit form it ? As i ve monitored cpu ang gpu usage using both 1.5 and 2.0 and didnt notice any difference is % usage or performance.
fourbanks Posted March 9 Posted March 9 i have all my pup packs working as expected, except the moon walking dead only, i believe this is nothing to do with the PinUP Player v2.0 beta files.
ktmspark Posted March 10 Posted March 10 On 3/5/2026 at 3:38 PM, NailBuster said: not a v2.0 bug it's just some pup-layouts need some minor corrections to their setup, this packs two-screen setup is missing a D0 trigger for bg with overlapping pups. Easy workaround is to just set that puppack to stay on v1.5. (see beta wiki page on how to do that, takes 2 seconds to set). hi , after much searching , im struggling to find the easy workaround details to set puppacks to stay on v1.5, please do u have a link . TIA
Tikimaster Posted March 10 Posted March 10 (edited) Rename the 1.5 Version to PinUPDisplayX15.exe Move it into your Pinupsystem folder beside PinUPDisplayX.exe Open a text editor. Type: [PINUP] Driver=PinUPDisplayX15.exe save it and rename it to usePuPDriver.ini If you put this file into a pupvideo folder - Version 1.5 will run. Edited March 10 by Tikimaster
ktmspark Posted March 10 Posted March 10 5 hours ago, Tikimaster said: Rename the 1.5 Version to PinUPDisplayX15.exe Move it into your Pinupsystem folder beside PinUPDisplayX.exe Open a text editor. Type: [PINUP] Driver=PinUPDisplayX15.exe save it and rename it to usePuPDriver.ini If you put this file into a pupvideo folder - Version 1.5 will run. thanks much appreciated
ktmspark Posted March 10 Posted March 10 (edited) so , just tried the latest beta :PinUPPlayer_v20_x64_beta20 these are the anomalies im seeing and solving: 1: had the slim pup dmd show as solid black box when running popper - disappeared when running a table - solved this by going into pinup menu screen and turning dmd to off (thanks @Dicentim) 2: i have backglass , playfield and full dmd , when paging thru tables in popper , all 3 screens are ghosting the previous screens so it looks like faded version of prev screens shown? - solved this issue by updating to latest nvidia drivers 3 : popper is def louder when paging thru tables with std buttons or the mag save buttons: not solved but not a big deal Im using VPinballX_GL-10.8.0-2074 and VPinMAME-sc-3.7.0-47, Nvidia RTX 3070 on 4k playfield so far i have only tried batman 66 and GOTG and both seem ok so far TIA Edited March 10 by ktmspark
Content Provider TerryRed Posted March 10 Content Provider Posted March 10 OK, so just to get everyone up to speed... ================================================================= PUP v2.0 beta 20+ Everyone should only be using the newest beta 20 (or higher) for pup v2.0. It will update everything correctly. Overwrite all files, and do NOT rename any exes. Use the exact names and files in the latest beta as they are! PinUpDisplay.exe = pup 1.4 (all older pup based tables and rom based pup-packs) PinUpDisplayX.exe = pup 1.5 (newer pup based tables that have usePuPDriver.ini in their pup-pack folder, and it specifies Driver=PinUPDisplayX.exe) PinUpDisplayX2.exe = pup v2.0 (newer pup based tables that have usePuPDriver.ini in their pup-pack folder, and it specifies Driver=PinUPDisplayX2.exe) ================================================================= Compatibility All older tables and pup-packs should work the same as they did before (as long as they weren't changed), as they are not using any of pup v2.0's files. Only Pinup Popper was updated to use pup v2.0. PUP 1.4 Tables and PuP-Packs Rom based pup-packs or older pup 1.4 based tables can't use pup v2.0 files as they are not compatible! If the table's pup-pack folder does not have a usePuPDriver.ini file, then it's a pup 1.4 table / pup-pack! These tables and pup-packs should run exactly the same as they did before. PUP 1.5 Tables and PuP-Packs If a table has a pup-pack that came with a usePuPDriver.ini file in their pup-pack folder, and it specifies Driver=PinUPDisplayX.exe, then it is a table that supports pup 1.5 features. Some newer VPX tables are pup 1.5 based tables. On FP, MOTU CE 1.3 also is a pup 1.5 based table. You "can" change Driver=PinUPDisplayX.exe to Driver=PinUPDisplayX2.exe to try to make the table use pup 2.0 instead.... but it's possible there may be unforeseen issues. I'd recommend staying with Driver=PinUPDisplayX.exe for these tables for now, and wait for table updates that will properly use pup v2.0. As an example, MOTU CE 1.3 can work with Driver=PinUPDisplayX2.exe mostly fine, but some videos won't play correctly due to some changes in functions, and the SSF / Ball Rolling may sound wrong. A new MOTU CE 1.4 update to both the table and pup-pack is coming that will work correctly with pup v2.0 and use its newer features and it's new PUP SSF engine. All other PinEvent tables are pup 1.4 based tables for now. ================================================================= PUP SSF - Pinball FX 3 SSF pup-packs, FP PinEvent tables, and some other FP tables all support PUP SSF - this legacy sound engine is still used for these tables and functions PUP v2.0 now has a new SSF sound engine! - pup v2.0 SSF uses bass.dll, and allows for ball rolling tracking and up to 30 sound channels! - this means that FP tables updated to support pup SSF v2.0 can now have 10 balls tracked with their own positions and sounds - we can now change each ball's material sounds for when they roll on ramps or different materials (10 wood, 10 plastic, 10 metal) - pup v2.0 SSF is NOT used with FX 3 SSF pup-packs or the current FP tables that support PUP SSF - pup v2.0 SSF is only used by Popper v2.0 and new FP tables that support pup v2.0 (MOTU CE 1.4 will support this) ================================================================= PUP SSF settings in PinupPlayer.ini By default, there are no SSF settings in the PinupPlayer.ini file in (PinupSystem folder) These settings can be added (only IF needed) in the SYSTEM section SoundDeviceIndex SoundDeviceIndex64 SSFAdjustVolume Example: [SYSTEM] SoundDeviceIndex=3 SoundDeviceIndex64=12 SSFAdjustVolume=100 Use the Default Audio Device (in Windows) for PUP SSF - if there are any lines with SoundDeviceIndex or SoundDeviceIndex64, remove them Use one Audio Device for game audio and SSF - if there are any lines with SoundDeviceIndex or SoundDeviceIndex64, remove them Use a Second Audio Device for SSF - set the Device ID for both SoundDeviceIndex and SoundDeviceIndex64 - SoundDeviceIndex and SoundDeviceIndex64 may require a different Device ID for the same Audio device (they each use a different PUP SSF engine) How to know it a FP table uses PUP SSF or PUP SSF v2.0? - if a table with PUP SSF does not have a usePuPDriver.ini file in its pup-pack folder, it uses the older PUP SSF sound engine. This uses SoundDeviceIndex - if a table with PUP SSF has a usePuPDriver.ini file in its pup-pack folder and it specifies Driver = PinUPDisplayX2.exe, it uses PUP SSF v2.0. This uses SoundDeviceIndex64 SoundDeviceIndex - sets ID of audio device used for older PUP SSF (FX3, FP tables with PUP SSF) - run the FP table that has PUP SSF. If there is no SSF heard where you want it, then change SoundDeviceIndex to a different number until you hear SSF on your preferred audio device SoundDeviceIndex64 - sets ID of audio device used for PUP SSF v2.0 (Popper, FP tables with PUP SSF v2.0) - run Popper or a FP table that has PUP SSF v2.0. If there is no SSF heard where you want it, then change SoundDeviceIndex64 to a different number until you hear SSF on your preferred audio device After running a pup v2.0 table or Popper, you can check “pupSoundIndex.txt” in PinupSystem folder to see a list of your audio device IDs. Note: these IDs only apply to SoundDeviceIndex64 SSFAdjustVolume - adjust main volume for all SSF and Ball Rolling sounds - 100 is max volume - this is only used with Popper and FP tables that support PUP v2.0 SSF ================================================================= Hope that helps clear some things up! Look out for Masters of the Universe - Collector's Edition 1.4 update coming soon for Future Pinball-BAM. It will support pup v2.0 and use lots of new features such as pixel shaders, lots of new alpha videos, and all new ball rolling functions and sounds!
Tikimaster Posted March 10 Posted March 10 (edited) Thanks, @TerryRed. That's a very neat structure and logic. Edited March 10 by Tikimaster
ktmspark Posted March 17 Posted March 17 On 3/10/2026 at 6:28 PM, ktmspark said: so , just tried the latest beta :PinUPPlayer_v20_x64_beta20 these are the anomalies im seeing and solving: 1: had the slim pup dmd show as solid black box when running popper - disappeared when running a table - solved this by going into pinup menu screen and turning dmd to off (thanks @Dicentim) 2: i have backglass , playfield and full dmd , when paging thru tables in popper , all 3 screens are ghosting the previous screens so it looks like faded version of prev screens shown? 3 : popper is def louder when paging thru tables with std buttons or the mag save buttons: not solved but not a big deal Im using VPinballX_GL-10.8.0-2074 and VPinMAME-sc-3.7.0-47, Nvidia RTX 3070 on 4k playfield so far i have only tried batman 66 and GOTG and both seem ok so far TIA Hi , just to update , i thought the nvidia gpu driver update fixed the ghosted overlaying videos when paging thru popper , but it seems it hasnt , on first boot paging thru tables seems ok , its when coming back out of table into popper , the 3 screens all get ghosted and overlayed . this doesnt affect the functionality as when i go back into a table everything is fine , it just makes popper look messy when paging thru tables. (I can post video if required) . On the plus side , table with pup packs seem to run much better than on the prev popper. I am happy to keep as is until the issue is sorted or someone finds a fix , I have tried replacing my default vpx popper playlist as prev ones were 60fps , the new ones at 30fps ( diff video entirely) does not fix screens ghosting. (im on Windows 10 if relevant)
NailBuster Posted March 17 Author Posted March 17 4 hours ago, ktmspark said: Hi , just to update , i thought the nvidia gpu driver update fixed the ghosted overlaying videos when paging thru popper , but it seems it hasnt , on first boot paging thru tables seems ok , its when coming back out of table into popper , the 3 screens all get ghosted and overlayed . this doesnt affect the functionality as when i go back into a table everything is fine , it just makes popper look messy when paging thru tables. (I can post video if required) . On the plus side , table with pup packs seem to run much better than on the prev popper. I am happy to keep as is until the issue is sorted or someone finds a fix , I have tried replacing my default vpx popper playlist as prev ones were 60fps , the new ones at 30fps ( diff video entirely) does not fix screens ghosting. (im on Windows 10 if relevant) the issue with ghosting is media related, it happens on the same mp4 (during the fade in/out transition). You can re-record those files or use media-manager to convert to 'Popper Standard Format' will make the mp4 work with alpha blending. Something with alpha blending shaders and some strange-mp4 encoding frames are causing the ghosting. If i disable the nice-shader-transition effect theres no issues, but i really like the transition effects
ktmspark Posted March 17 Posted March 17 2 hours ago, NailBuster said: the issue with ghosting is media related, it happens on the same mp4 (during the fade in/out transition). You can re-record those files or use media-manager to convert to 'Popper Standard Format' will make the mp4 work with alpha blending. Something with alpha blending shaders and some strange-mp4 encoding frames are causing the ghosting. If i disable the nice-shader-transition effect theres no issues, but i really like the transition effects Thanks for that info , is there an option to disable the transition effects in popper options, or is it a dev thing only ? All the table videos are recordered thru popper so i presume they are correct format , Is there a batch way to convert playlist vids to the standard format or must they be done on individual basis ? Help much appreciated , I love how the new popper seems to leave much more resources to FP/VPX, I recently played some tables with pup packs that used to crash out after varying times with no crashes at all .
outhere Posted March 22 Posted March 22 After updating to 2.0 I get this Error All files are unblocked
puerto Posted March 22 Posted March 22 Hi all, testing out the latest beta :PinUPPlayer_v20_x64_beta20. Transitions are quicker than before, everything running pretty smooth. I have many emulators set up and all videos (3 screen set-up) are running fine except for 2 Weird glitches noted: Pinball FX3 only : all playfield videos are reversed (only playfield , full dmd and backglass ok) Pinball FX only: ghosted overlaying videos on some, but not all games listed (happens on all 3 screens, )
drady Posted March 23 Posted March 23 Really enjoying 2.0. Have a weird effect that the full DMD preview/ screen capture on no particular table gets stuck eg. One table full DMD preview image won't change when going through game Catalog. When launching a game it still stuck though game DMD show etc. Tables like guardians show the pup full DMD but on exit the stuck image is still there. PC is GPU 3060, Ryzen 5
NailBuster Posted March 27 Author Posted March 27 FYI. Beta22 is now available on WIKI page or PinUPDater. Should help with visual glitching that some are having, and more, see README or WIKI for full info.
Tikimaster Posted March 27 Posted March 27 Sounds great: One Question Then if all is well after install you can then in Popper Config/Global Settings/first tab set your Video Acceleration Driver. Choose DirectX (recommended) to start and if you have any issues, try out OpenGL afterwards. In Popper Config, you can now set the transition/fade speed between videos in Popper, you can even disable if you choose. In Popper Config/Global Settings/Wheelbar. Higher the number the faster the effect, 30-80 is decent range How can I set these things with player only?
fourbanks Posted March 28 Posted March 28 7 hours ago, NailBuster said: FYI. Beta22 is now available on WIKI page or PinUPDater. Should help with visual glitching that some are having, and more, see README or WIKI for full info. all good David on windows 10 and 11 thank you
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now