[UNRESOLVED] PBX very slow to exit "some" tables under 6.58

[TT11]

You will recall I raised this previously when I updated to 6.54.  When updating again to 6.58 it seemed much better.... BUT..... Again I am finding that some table exits are much slower than others.  It definitely seems related to the most recent PBX updates......  I had run 5.22 for a LONG time and it was great with speed.  Something has been introduced in the mean time to make the interface seem sluggish "at times".  Not all table exits, just some.  VPX 10.8 tables are the main culprit as most of VPX 10.7 and even the old VP9 tables are almost instant.... Only use DX and no Open GL.

[Draco1962]

Sorry you are running into continued issues.

Can you please attach copies of your Pinballx.ini and log.txt files (right after a slow exit) as we ask whenever you have an issue to report?

Also, some table names and VPX version(s) associated with each please.

Thank you.

[JimmyCoupe]

It might be worth explaining what sluggish\ slow is in actual seconds compared to what is normal for better understanding of the issue.  I can sometimes experience inconsistent exiting but its not related just to VPX.  I get it from PinballFX, M, Future Pinball etc as well.  Its nothing crazy, maybe 4-5 seconds hang on a black screen before returning to the menu.  Mostly my exits feel quick and consistent so from myside its nothing major.  I am running a AMD 5700G, 32gb, Windows 11.  I only run VPX 10.7.2 for info and it can happen from time to time.

[Mike_da_Spike]

When encountering this issue, please try saving your log file; it might help determine the cause of the slowness.

I've only observed slow performance with VPX 10.8 and haven't yet had the opportunity to investigate further.

[TT11]

PinballX.iniFetching info... log.txtFetching info...

For your advice.... Under 5.22 almost all tables would exit within 1 second maybe 2.  Since moving up to later releases this has become 4-5 seconds and sometimes up to 8-9 seconds to exit back to the wheel.PinballX.ini

I'm running Windows 10, Core i5 12400F, 16GB ram, RTX 3060 - Future Pinball, VP9, PM5, VPX6, VPX7 and VPX8 (Beta).  VPX8 is 64 bit DX - all others 32 bit DX.  No OpenGL versions.  2 Screen Cabinet only.

This table played was Cirqus Valtaire VP10 (VPX 10.7) and it seemed to take ages to return to the wheel when exiting.  From what I can read in the log.txt is 13 seconds correct?

[Tom Speirs]

Could you please provide a better sample, launching more than 1 table?

Thank you for your patience.

[TT11]

Is 13 seconds normal to close a VPX 10.7 table though?  I might go back to 6.22.....

[Draco1962]

  On 4/9/2025 at 1:33 PM, TT11 said:

Is 13 seconds normal to close a VPX 10.7 table though?  I might go back to 6.22.....

Expand  

Likely not normal, but hard to determine the cause. Please be aware that your level of support if you decide to downgrade to 6.22 will be diminished. Given that your circumstances do not mirror the majority of users, it may be that there is something missing within your configuration that will require some lengthy work to try to resolve. IMO, it may be best to stay the current course.

If you do, please provide additional examples as Tom has requested and attach the logs in reply. Thanks!

[Tom Speirs]

just one suggestion, try setting to run full screen windowed (rather than full screen exclusive). it looked to me like it was initializing the display that was slow rather than exiting the table.

[Tom Speirs]

ps: no its not normal.

Again, it looks like the delay is happening after the exit. That part is fine.

[Mike_da_Spike]

I noticed that indeed a slight performance increase between Full Exclusive mode and Full Screen Window (but get less FPS when switching to Windowed)
But I noticed that there was a big delay when turning of the Swisslixards DOF plugin.

If I enabled the DOF plugin it takes around 16 seconds when closing VPX and get back to PBX (and VPX doesn't get closed correctly, so it needed to be killed ?) :

07:28:44.04  10-4-2025:  Exit System Control Pressed
07:28:44.63  10-4-2025:  Found Visual Pinball editor window
07:28:52.85  10-4-2025:  Killing process
07:28:52.85  10-4-2025:  Process Closed
07:28:57.40  10-4-2025:  Getting high score
07:28:57.50  10-4-2025:  Writing high score
07:29:02.73  10-4-2025:  Created DirectX BackGlass Window
07:29:02.76  10-4-2025:  Created DirectX Topper Window

When turning off the plugin, it takes around 4 seconds to close VPX and return to PBX (process doesn't need to be killed):
 

06:42:48.82  10-4-2025:  Exit System Control Pressed
06:42:50.14  10-4-2025:  Found Visual Pinball editor window
06:42:51.38  10-4-2025:  Process Closed
06:42:52.45  10-4-2025:  Getting high score
06:42:52.57  10-4-2025:  Writing high score
06:42:52.74  10-4-2025:  Created DirectX BackGlass Window
06:42:52.76  10-4-2025:  Created DirectX Topper Window

The one thing 1 noticed @Tom Speirs 
When DOF plugin is enabled, I launch a table and check the Taskmanager. I see that Vpinball64.exe is runing.
When pressing the quit button, the screen becomes black, Vpinball64.exe  is running, but become in not responding. But closes in a few seconds.
But it takes another 6 seconds, before PinballX is showing something.
This is the log from that when pressing ESC :
 

08:05:38.27  10-4-2025:  Exit System Control Pressed
08:05:40.45  10-4-2025:  Found Visual Pinball editor window
08:05:48.72  10-4-2025:  Killing process
08:05:48.72  10-4-2025:  Process Closed
08:05:53.50  10-4-2025:  Getting high score
08:05:53.61  10-4-2025:  Writing high score
08:05:58.82  10-4-2025:  Created DirectX BackGlass Window
08:05:58.84  10-4-2025:  Created DirectX Topper Window

Not sure what is happening between 8:05:53 and 8:05:58, but it looks like it is doing nothing.
but is I said, only happening when the DOF plugin is enabled.



 

[Mike_da_Spike]

@TT11are you using DOF with the dof plugin as well ?

Maybe I have another issue than you have

[TT11]

Absolutely no DOF in my setup.  A very standard iPAC for buttons, nudging and ball shooter - Basic to say the least.

One thing I did was go back to 6.22 and I have to say.... Exits are quicker.

I will make changes to 'full screen windowed' but will this stop me being able to Q a game to go back to the editor and make changes and then F5 to restart a table OK?  I do that SO OFTEN for changing ball rolling volumes, reduce bloom fx etc.

[Tom Speirs]

this is full screen windowed in pinballx not visual pinball.

[TT11]

Will this stop me being able to 'Q' a game to go back into the editor and make changes and then F5 to restart a table OK?  I do that SO OFTEN for changing ball rolling volumes, reduce bloom fx etc?

[Tom Speirs]

nope, completely unrelated and don't think it applies to 6.22 anyway.

Im thick enough skinned but probably hard to help you with anything. sorry.

i will look into it though. Mike is helping.

[Tom Speirs]

ill just try and work with Mike when I can get to it. he says he can duplicate some stuff and he wants to help.

As i think i said though, the issue seems to occur when reinitializing the display etc not exiting the table, although i realise that looks like slow exit. it could be xdmd, it could be directx, or it could be the ini file

i provide old versions for the purpose of fixing new versions. it can indicate where things went wrong.

There are other things that come up that make me do new versions. Your just not experiencing those issues because i fixed them  People update other software too such as Visual Pinball and Windows which required updates. i do my best in the face of adversity

it seems like pinballx is quite stable right now and works so i don't consider this a priority.

[Tom Speirs]

I am not motivated to work on this over other work right now. Its working and stable so not a priority. i will hopefully get to it at a later date. Marking this as unresolved and closing.

The issue is noted but on the back burner for now.