Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

Recommended Posts

Posted

Okay, i thought of something.

Here is something that will fix it for everyone assuming the player window closes.

It will read this setting in 6.87 and beyond.

[VisualPinball]
WaitForEditorClose=

It defaults to 400 so set it above that. Its milliseconds.

Note: Don't set it above 9500 or so otherwise it will time out and kill the process.

  • Like 1
Posted
2 hours ago, Tom Speirs said:

Okay, i thought of something.

Here is something that will fix it for everyone assuming the player window closes.

It will read this setting in 6.87 and beyond.

[VisualPinball]
WaitForEditorClose=

It defaults to 400 so set it above that. Its milliseconds.

Note: Don't set it above 9500 or so otherwise it will time out and kill the process.

Thanks Tom. v6.87 still closing process well for me with 10.7 & 10.8

I didn't need to add or tweak the new ini key value, but just to be clear..   

  1. The new WaitForEditorClose key currently has to be added to the ini manually (i.e. not via Setttings)?
  2. When/if it is added, does it affect all Visual Pinball systems (i.e. those under 'custom systems' set to type 'Visual Pinball' as well as the standard inbuild Visual Pinball system)?
Posted
1 minute ago, scutters said:

Thanks Tom. v6.87 still closing process well for me with 10.7 & 10.8

I didn't need to add or tweak the new ini key value, but just to be clear..   

  1. The new WaitForEditorClose key currently has to be added to the ini manually (i.e. not via Setttings)?
  2. When/if it is added, does it affect all Visual Pinball systems (i.e. those under 'custom systems' set to type 'Visual Pinball' as well as the standard inbuild Visual Pinball system)?

Yes to both...

  • Thanks 1
Posted

So with the latest version, Blood Machines PUP DMD continues to break on launch for unknown reasons, only launching the overlay.  I actually tried it as the first table launched on system startup and it did work, that time only.  Immediately after, Batman '66 exhibited the same issue (legacy problem).  I restarted Batman and that time it worked.  All closed easily at default settings, however, including BM.

So to test the idea that it was related to not closing properly, I checked task manager, and no PUP process remained between runs, to no avail.  I then killed PBX and observed a few oddities...

1. After having it fail in PBX, going directly through GL version continued to fail
2. Launching in in DX version, however, cleared the problem...
3. ...which led to trying again with GL, where it remained fixed
4. Then I brought back up PBX, which is using GL...  and it again messed up on start.

I'll experiment more later tonight.  Intending to check if it is happening and persisting if first load is on GL without PBX, and also seeing if the same issue exists if that table is set to DX in PBX.

log.txt

Posted

So after messing with it further...  as to BM, specifically, it looks like it's an issue with that table and all current versions of VPX.  Seems to be coin-toss as to when the PUP loads correctly right now on GL or DX.

So as to PBX issues, it closes properly like all the others at this point...  Cautiously optimistic this bug is resolved, but I'll keep an eye on it.  Thanks!

  • Like 1
  • Draco1962 changed the title to [RESOLVED] Exiting Does Not Close PUP Packs
  • Draco1962 locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...