Riddle me this

[Hoop22]

I can't for the life of me solve this.  I have VPX installed into a folder.  All the regular stuff is inside, table folder, vpinmame, etc..

Things were running fine, including my audio (SSF).  I downloaded one of the VPX betas.  I usually extract the beta into a temp folder and am able to run the exe from that same folder.  It pics up my table locations, ultradmds, etc.. from the regular install folder.  If things seem to run fine, I usually just drop the VpinballX.exe file from the beta into my normal install folder.

 

This is where things go fishy.  When I run VPinballX.exe from my regular installed folder, my audio is gone.  Game runs, just no audio.  If I run that same exe file from the temporary extracted beta folder, things run normal and the audio functions as it should.  Audio continues to run normal from the popper front end, but audio disappears once popper loads a game.

 

I've tried deleting a table nvram, cfg, and registry rom entry and still no audio.  Yet if I run that exe file from the temporary beta folder.....everything is back to normal.  I've even copied all of the beta contents into my install folder.  Same thing.

 

Any ideas?

 

Thanks in advance.

 

 

[Solters]

Start the table. Press alt and tab. I think you have win 11 or 10. go to audio mixer under settings. I think the sound is turned down. Windows has done a few times with me 

[gezortenplotz]

I would like to recommend Ear Trumpet for easier handling of the modern win mixer via tray.

[Hoop22]

Thanks for the suggestions.  The tray volume seems to be connected.  I think what is happening is that Pinvol seems to freak out after running vpx from the temporary location.  Then, when reverting back to running it from the original install folder, it quits doing its job.  I'm wondering if pinvol has a setting somewhere that controls where it is expecting VPinballX.exe to run from.  I can't seem to find antything in the pinvol ini files and assume it might pickup vpx from the task monitor, but that doesn't exactly help my theory.  I did unistall a windows update from 8/21, but I don't see much change and I didn't have this problem when that update happened.  It didn't really happen until I tested a beta vpx version out of a temporary folder.