MulletLife

FWIW, this is the issue I had with 6.20 as well. I tried a few earlier versions with the same issue. I've been running 6.07 without issues. I don't have a lot else to offer, just that whatever issue with long exits exist in 6.20, do NOT exist in 6.07.

Solved If you search in registry for the name of your dof64 folder, you will find an entry with the name Code Base. Simply point it to the correct spot and re-register.

Well yes, that would have been the first thing I tried. You helped create this plugin correct? Where does the app derive the info for the Direct Output path in the Plugin's Config window? I'm assuming its a registry key. If I know where the app is pulling the info from, then I know what keys to overwrite.

log.txtPinballX.iniNote this is from my test rig which is now on my desk and not hooked up to my vpin. But regardless, you can see that the DOF plugin can't initialize from the log.txt. My assumption is because its pointed to the x64 DOF folder.

Correct, my DOF works everywhere except in PBX. I believe the issue resulted as I accidently registered the the 64bit DOF hence the plugin is looking in the 64bit directory. I'm assuming it needs to point to the 32bit as its a 32bit application. That's the only difference between my 2 setups, 1 I accidently registered the 64bit DOF, no DOF in PBX on that build. I need to figure out how to change it back in the registry, or how to change the DOF path in the DOF Plugin (possibly the same answer).

When running PinballX Plugin Manager, then "Configuring' DirectOutput PinballX Plugin... My path shows: C:\DirectOutput-x64 I need it to point to c:\DirectOutput-x32. How do I accomplish this? Thanks

I think the issue is actually my playfield monitor. Changing setting regarding contrast etc seems to fix the issue though its odd the videos look different in VLC vs in PBX. Good enough for now. Thanks

PinballX.inilog.txt To my knowledge, the video codecs I installed initially were the above mentioned LAV filters. I also just reinstalled them and reverted to default settings with no change to the washed out videos. Again, the videos play fine stand alone, its through PBX they get washed out. Brightness in ini is set at 160. This issue has persisted through various PCs and screens. I'm fairly confident its not a hardware issue. Any help is appreciated. Thanks

Having this issue for years, finally doing something about it. I've tried altering the brightness from the PBX Display Settings options. I'm just looking to have the videos looks as they do when running from vlc/media player etc. What am I missing? Its like there is a white diffusion over the entire playfield. Thanks everyone

Lots to unpack there. My PC did do an update, not sure what update it did but last time I tried to do a rollout it bricked my PC and had to reinstall windows. But I guess that could be a variable the would be difficult to test. I can look to see what got updated though and report back. I am using MP4 and I did also install VLC (actually installed it vs it just existing in the pup folder). I did grab a link from a pinball source as I know you're supposed to use a specific one. That might be a variable. I can close PBX videos but I would assume that would be fairly similar to just running straight from VPX. I think I did that in the video but I would need to double check. It would certainly free up some resources, I just didn't think I was right on the edge of 120fps or 80fps because of an extra 10% of CPU usage. I can try with non-pups. I guess that would help narrow things down. I think I did and it was the same issue but I can certainly try again. No idea what WinActivate.exe is. I've been piggy backing and updating for 5 years, it may have been something that was there originally and just doesn't get used anymore.... no idea on that one.

Its just an LCD monitor. I do notice that the backglass and "topper" (ie my dmd overlay) is more delayed in shutting down. Especially if playing direct from VPX. VPX closes and topper/backglass hang for a few seconds. I can't recall now if that was since x64 or if that was when I upgraded from 5.47 to 5.80...

I didn't realize the log purges each game. The first time I tried was with AFM x64 and had the FPS issue. This log shows I changed PBX to run AFM in x32, still with FPS issue. That would lead me to believe its not the actual VPX install, its something else.... It (seems) to be a dmd issue but can't quite put my finger on the issue. It seems odd that the CPU is at 50% (though I don't know what it was before) and that freeing up the dmd resources changes it from 80fps to 120fps instantly. Hope the logs help. DmdDevice.ini log.txt PinballX.ini

Sounds good, will do. (I thought log.txt was maybe a wildcard for ANY log file)

Just so I don't miss anything and you need to ask again. Do you mind writing out the exact name of every log/ini you would like me to post? I can also try downgrading my vpx and see if that helps. There's also the option of going up to 10.8 to test as well. Thanks

Right, in terms of versions of dlls etc, I followed that tutorial to the letter. B2SBackglassServer-2.0.0-Release-win-x86 dmdext-v2.0.0-x64 dmdext-v2.0.0-x86 DOF-x64-2021-04-16 PinUPSystem_x64_drivers_v1_beta VPinballX-10.7.4-400-1965b7b-Release-win-x64 VPinballX-10.7.4-400-1965b7b-Release-win-x86 VPinMAME-sc-3.6-369-102e419-win-x64 VPinMAME-sc-3.6-369-102e419-win-x86 I can attach the files next time I'm on the VPin. FB doesn't seem to be much help other than to start fights over x64 vs x32. I just like to know what causes an issue and how to fix it. The more people that know how things work means the more people that can help when people have issues. But I'm almost at the point of pulling the shoot on this issue and going back to my old setup.

I do have my whole 32bit system backed up. I was just trying to be on the leading edge of the updates. I'm likely going to be going back to a full 32bit setup if the issue isn't resolved somewhat soon. I just finished making it 'perfect' so the next logical move was to break it

To preface, I don't think this is a PBX issue, I believe I have removed that as a variable. But if anyone is able to offer any help or suggestions it would be greatly appreciated. If there are any specific logs, version #s, etc. needed just let me know. I have a video linked to demonstrate the issue: https://mega.nz/file/tvYhhRIY#c7UbsmGZA-_K7__eMq_Mawcd-iEzx0pc7sFyRKGhhsY I believe the main culprit is the external DMD (possible a dmddevice.dll issue). Basically if I close that, all the issues go away, I'm locked in at 120fps but who wants to play without a dmd? Scutters suggested to change: The true to false, that didn't seem to work. [pinup] ; if enabled, send frames to PinUP. enabled = true Another user suggested not using altcolor, that didn't work. I've replaced the dmddevice64.dll with an older version (12mb vs 18mb), that didn't work. I'm on VPX 10.7.4 64 bit. I may try to go back to 10.7.2 or 10.7.3 and see if that makes a difference but I'm not hopeful on that one. Again, if anyone has any thoughts on what to try next, I'm all ears. Thanks very much in advance.

Bad and then good news (Only updating if this helps with bugs). Everything was fine with my WIN10 build. I tried to install FX3 and it needed to update my 2010 and 2015 redistributables (x86 and x64). This is what I think broke things as the ROM sounds once again stopped working. This is the bad news. Good news. I ran the Topper MP4s through TerryReds FFMPEG script (30fps no audio) and we're back and action. I'm going through and converting all my toppers now to mitigate this issue. To my knowledge, the toppers never had sound to begin with but maybe it was a muted/low audio channel?? I have back ups of the MP4s if anyone wants/needs to test it to fix the bug. Thanks for the help everyone.

Thanks very much for the reply, I wish I would have seen it before tinkering. Shark codecs KILLED my system. I ended up swapping hard drives so the issue is temporarily resolved. I'm now going to have to figure out how to undo what Shark did (its portable, didn't install anything, but the issues remain on deleting). Mainly, videos in PBX take noticably longer to load, and some backglasses even get stuck. What a mess. For Tom: Perhaps there is an update that happened in WIN11 that conflicts with some audio codec. I know 100% that it worked fine, likely did an win update of some sort, then certain topper videos cause the center channel rom sounds to stop working on anything other than 2.1 (in windows audio setup). PBX bug??? Maybe?? I think the root cause is elsewhere, but causes a conflict in PBX. This may pop as more people get on WIN11. Who knows. Hopefully there's enough info here to determine if there is something in PBX that is glitching and how to resolve it. Thanks everyone for their help. We'll call this resolved (for now). I'm sure FFMPEG conversions will likely do the trick be it an audio or maybe an alternate video codec used on some toppers.

So I've tracked it down but don't have a resolution as of yet. 3 screen setup - backglass, topper (full screen), playfield. The PinballX Topper Media folder is the cause. Specifically, some of the files are fine, others will cause the issue. For EX, Bad Cats won't play sound. But its not an issue with that table, the issue is with the topper file. I remove the topper, sounds work. Put the topper back, no rom sounds. I've downloaded and installed VLC 2.2.8 thinking that may be the issue, its not. I'm thinking its a CODEC or audio driver that is present in WIN10 that isn't native to WIN11. That's my current guess. I have a LAV filter codec pack I install which I have reinstalled with no effect. I think there use to be a pack vpin people would install called Sharkey's, I'll have a look there as well. Another option is to put all the videos through ffmpeg and convert/strip sound or something so ALL files are the same audio/video codec and see if that works. That said, I'm sure there's a fix that doesn't involve that step. I'm thinking a win11 update (maybe realtek drivers) was the culprit. Now just need the cure. Thanks for all the help so far guys.

I can install 5.41, and will likely update once the issue is resolved. I'm at the point that I'm 100% confident the PBX version is not the issue. I'm close and I'll have an answer tomorrow.

Good news for those who are following along. I renamed my PinballX folder to Pinballx_. Installed 5.02 to PinballX and copied over my config and databases from the older folder. Everything works! I then copied over all the Folders (not the root dir files). It mentioned 172 files to overwrite. One of those 172 files must be the culprit as its now broken again. I feel the end is in sight. I will deleted, reinstall, and test folder by folder to see if I can find the issue. If I can find the singularity and it is a legit bug, I'm sure Tom will appreciate the info. If anyone feels like placing bets on the culprit.... Its somewhere in the folders but likely not the Config or Database folder. My guess is Media or Plugins. EDIT - Its the MEDIA folder. Need to track down which specific sub folder is the issue, but it is 100% in the media folder. If anyone has an educated guess as to a file or folder that may be the culprit.

Here's a copy of the INI I've also swapped out the external 7.1 soundcard with a completely different branded soundcard, no difference. So far my biggest clue is that Rom/music occurs when windows is set to 2.1, but not when set to 7.1. My 2 main tables that I'm testing (as that's helpful) are Attack From Mars and Bad Cats. One has puppaks, one doesn't. That doesn't seem to make a difference. ***FWIW - I did a fresh install on a new PC, same specs but WIndows10, PBX 5.02 Sam3.4, works perfectly fine. I'd love to not rip this PC out of a 100% finished cab if I could help it. PinballX copy.ini

It was running fine for a few weeks. I turned it on today and this was the issue. Hence why it may have been a windows update, or maybe a c++ that I installed in the interim that broke something. I'll see about grabbing the ini and pasting here. That reminds me I should grab the ini from a known working setup I have and seeing if an overwrite solves the problem. I feel like from my diagnostics its PBX related, but may be a PBX bug caused by windows drivers....

***UPDATE with moderate success**** I've done some additional testing if it helps with problem solving: This MAY have occurred after a C++Redist update... maybe - Downloaded news Sam build 3.5(beta??) and installed via setup and setup64. No change - Re-installed PBX 5.02 (from the newest) No change Have tested in VPX and get full sound under 2.1 settings and 7.1 settings. Tested with PBX launch with 2.1 sound (in VPX, not windows) and 7.1, no rom sounds. Tested with PBX with 2.1 sound (Windows), ROM sounds now exist. So is this a Windows issue, or is PBX somehow not picking up 7.1 sounds from Windows??? The saga continues....