[Resolved] Can't Exit VPX

[MrGrynch]

Well this is new.  Added a bunch of VPX tables today and suddenly I cannot reliably exit them via PinballX.  Sometimes it works, other times not.  This wasn't a problem until now.  I do not have ESC disabled in VPX.  I have exit emulator tied to a button on my cab.

I appreciate any help!

 

log.txt PinballX.ini

[MrGrynch]

I tried mapping the same exit button to Quit in VPX, and that works a bit better but I can see the “quit to editor” dialog and sometimes have to hit it twice.

still this is new behavior and I didn’t have to change this mapping previously

[Mike_da_Spike]

Do you have visuapinball.exe run as admin ?

There should be no need to have the same button mapped in vp and pbx to exit emulator. The frontend should take care of it

[MrGrynch]

I do not have VPX running as admin.  It’s all very strange.  It was working beautifully until I added the new tables.  

[Mike_da_Spike]

I cannot think of a solution.
Maybe a stupid question.
Do you momentarily press the exit button, or you keep it pressed ?

I just tested once that when I pressed my exit button, that PinballX would not respond to it at all. And end up with a crash of PinballX.
 But wasn't able to reproduce this anymore.
sorry, Out of options to help you 

[MrGrynch]

I just press once.  I know it’s a software issue since it work is fine navigating PinballX and MAME otherwise, and it does sometimes work for VPX

Thanks for trying Mike!

[MrGrynch]

Tinkering around a bit more:

- Run PBX as admin, same problem

- Run PBX with new config, same problem

if I sit there and repeatedly push the exit button, it will eventually work.

I’ve been noticing a long delay displaying backglass images.  Wonder if something is hogging my resources.  Strange though that I can use the VPX exit/quit buttons and it will exit just fine and then PBX merrily takes over.  Does PBX end the VPX process?  How does it exit the emulator?

[MrGrynch]

If I had to guess, a recent Windows 10 update is interfering with the method PBX uses to exit VPX.  The joystick buttons are working fine for everything else.  Not even the keyboard keys are working for PBX/VPX.  The latest symptom?  I press the exit button, and almost two minutes later, it exits

[Mike_da_Spike]

I had a w10 update yesterday as well. 

I will check in a few hours. You not using teamviewer ,  right ? This causes a huge delay wit visual pinball 10.7

Not sure how pbx ends the process. But think it just kills the process of visual pinball. 

[Mike_da_Spike]

Even after my Windows update, al is working as expected

This is my Visual pinball layout.
I have disabled ESC key and set override default button layout.

Don't have mapped a Joy button for exit :

What I do have is set Force exclusive mode :


I noticed that you don't have that setup in Pinballx :

Maybe that will help if you put it to yes ?

[MrGrynch]

@Mike_da_SpikeThanks for this info!  I have a new motherboard coming today.  Once I have it all back up and running, I will check these out.  I appreciate your help.

[Mike_da_Spike]

27 minutes ago, MrGrynch said:

@Mike_da_SpikeThanks for this info!  I have a new motherboard coming today.  Once I have it all back up and running, I will check these out.  I appreciate your help.

Thats a drastic fix. Replacing your mb for not exiting pbx 

An Easter present for you !

[MrGrynch]

Going with the nuclear option!

[Mike_da_Spike]

[MrGrynch]

New motherboard arrived, but the new CPU was not compatible.. Guess I should have read the specs more closely.  Waiting on new CPU.

[Mike_da_Spike]

Well amd doesnt fit on an intel socket ...

[MrGrynch]

Figure I’ll upgrade to a 1TB M.2 NVMe while I’m waiting.  You would laugh if I told you the original specs for this computer

[Mike_da_Spike]

Sounds like a beast. Rtx 3080 with core i9 ?

[MrGrynch]

Only a beast in comparison to what I had.. Original config:
Gigabyte H110-DS2V DDS3 motherboard
Intel Celeron G3930,
Kingston 4GB DDR3
GT 730K GPU
450W PSU, 240GB SATA SSD
Windows 7

New computer cobbled together online from used parts ($400 invested):
MSI B365M Mortar MB
Corsair 32GB DDR4 3200MHZ
Intel i5-9400 GPU (in transit)
NVidia GTX 970 GPU
Samsung EVO 970 Plus 1TB (in transit)
750-watt PowerSpec Bronze PSU
Windows 10

That was the best I could do an still keep the cost down.  I'll continue to upgrade over time as I find decent deals.  Buddy of mine scored an RTX 3080 from a local shop of $360!!! 

[MrGrynch]

I don't want to jinx myself, but the upgraded hardware SEEMS to have solved the problem.  I've gone through all the tables and they are exiting without any problem.  I just got everything put back together, so its late.  I'll really put it through its paces tomorrow.

 

[Mike_da_Spike]

Good to hear mate. Maybe it was hardware related

[MrGrynch]

On 4/21/2022 at 12:22 AM, Mike_da_Spike said:

Good to hear mate. Maybe it was hardware related

It's just so bizarre.  When I only had a handful of tables, it was fine.  I mean ROCK SOLID.  I added about a dozen more and the problems started.  Since each table runs in isolation, the number I have shouldn't matter.  I am happy upgrading the hardware seems to have fixed it, but it really bugs me why it was a problem in the first place.

Thanks for all of your help @Mike_da_Spike.  I really appreciate it!

 

[Mike_da_Spike]

We are here to help each other. Not sure what minimum specs should be to run a frontend,  but maybe it run out of memory. Just a guess

[Draco1962]

I found switching from Win 7 to 10 brought with it better memory management. Could be part of the equation.