Updated, Now I seem to have table exit delay and Puppacs stay open

[Spacegoogie]

I have updated to  Freezy's latest https://github.com/freezy/dmd-extensions/releases .

Now  when exiting a table (64-bit VPX) there is a 4-5 sec delay when closing the table, as before install it would be instant?

I'm going to rollback my Ver and make sure this is in fact the case.🍻

 

 

Edited November 10, 2024 by Spacegoogie

[Spacegoogie]

I reverted back to my previous  settings, and that was not it. I also updated vpinmame, b2s, and VPX to latest, did not fix.

Puppacks  are also remaining open after closing a tables.

 

This is so frustrating, every time there are updates something stops working or works worse then it did before.  

Just seems like it will never end, never ending updates. 

When is enough, enough? What point are we trying to get to? 

 

I was impressed with VPX almost what 20 years ago.

So many times I was setup with everything working 100%, but then I just have to get the newest update every time.

The next time my system is working 100% I will no longer update anything, Why when it already does more then most real pinball machines today.

I definitely don't need HD DMD's. What happen to reproducing the originality of a table? 

Seems like we always need to try and make something better when its not even necessary, when it was already was good and working.

Also thinking about cutting out all my puppacks and making that just one less problem to worry about. 

Like I said, Now I have more problems then I started with because I had to jump on the latest.

I'm done after this.

 

Would love to hear some of your thoughts.🍻

Edited November 10, 2024 by Spacegoogie

[BostonBuckeye]

Spacegoogle, I have the same issue and feel your pain. DMD tables won't close right away now in 10.8. Then once they do VPX either crashes or closes down.

I have been experimenting with VPX 10.8.1 as well and the same issue occurs with it so it could be a VpinMAME issue and not a DMD or VPX issue. I regularly update to the newest version of VpinMAME . I wouldn't even know how far to roll back in VpinMAME to see if that fixes the issue as they update it so often. I checked my back up copies of my vPinball folder on separate drives that aren't updated to dmd ext. 2.3.0 and they have the same issue as well. So that isn't the cause.

 

There are so many different parts to VPX that it is hard to figure out where the issue lies when trying to work through a problem. Every time I play a table I am just amazed at how well everything usually runs.

 

All of the people who work on the different areas of VPX like Freezy do a freaking amazing job and are computer geniuses. I can't thank them enough for creating this world of visual pinball. 

 

However, it is frustrating when things break when you update something after spending so many hours getting things set up and running smoothly. And yes I always make back ups but sometimes even then the problem still exists because you didn't notice it before you made a back up. I am so paranoid I have two back up folders saved on separate drives. My vPinball folder is around 380 GBs so I only have room to make two back ups.

 

Once you get things back up and running at 100% you are probably wise to stand pat if you are happy with everything. Happy pinballing brother!

 

 

 

 

 

 

 

 

 

 

 

[Spacegoogie]

I ran into all kinds of new issues along the way of  updating DMD, B2s, VPX, VPINMame, PinMame.

Updated the B2s to 2.5.x,

Started to get microsoft .net framework error when I would just let tables sit and run ( went back to B2s 2.1.2 from 2.5 to fix that issue).

I was not having it. Spent the last week getting things back to what I hope it use to be.

 

I have backups, clones (I'm finding it easier to just make a 1:1 clone). But I'm updating every-other day. I messed up the other day. I stared mistakingly changing and deleting files in my VPX backup thinking it was the folder I was working in!

I just about took myself out back to kick my own ass lol. So ya I think im back in bussness.

Running now:

VPX RC4

B2s 2.1.2

freezy 2.3.0

VPINMame , dont remember what Ver. im on, Im not at pinball table.

I thank all that contibute to this hobby!

All my extra time is spent here.

I ran into all kinds of new issues along the way of updating DMD, B2s, VPX, VPINMame, and PinMame.

Updated the B2s to 2.5.x,

Started to get Microsoft .NET Framework error when I would just let tables sit and run (went back to B2S 2.1.2 from 2.5 to fix that issue).

I was not having it lol. Spent the last week getting things back to what I hope it used to be.

 

I have backups and clones (I'm finding it easier to just make a 1:1 clone). I'm updating stuff every other day.

I messed up the other day. I stared, mistakenly changing and deleting files in my VPX backup, thinking it was the folder I was working in!

I just about took myself out back to kick my own ass lol. So yeah, I think I'm back in business.

Running now:

VPX RC4

B2s 2.1.2

freezy 2.3.0

VPINMame, don't remember what Ver. I'm not at the pinball table.

I thank all that contribute to this hobby!

All my extra time is spent here.🍻

 

 

[BostonBuckeye]

4 hours ago, Spacegoogie said:

I ran into all kinds of new issues along the way of  updating DMD, B2s, VPX, VPINMame, PinMame.

Updated the B2s to 2.5.x,

Started to get microsoft .net framework error when I would just let tables sit and run ( went back to B2s 2.1.2 from 2.5 to fix that issue).

I was not having it. Spent the last week getting things back to what I hope it use to be.

 

I have backups, clones (I'm finding it easier to just make a 1:1 clone). But I'm updating every-other day. I messed up the other day. I stared mistakingly changing and deleting files in my VPX backup thinking it was the folder I was working in!

I just about took myself out back to kick my own ass lol. So ya I think im back in bussness.

Running now:

VPX RC4

B2s 2.1.2

freezy 2.3.0

VPINMame , dont remember what Ver. im on, Im not at pinball table.

I thank all that contibute to this hobby!

All my extra time is spent here.

I ran into all kinds of new issues along the way of updating DMD, B2s, VPX, VPINMame, and PinMame.

Updated the B2s to 2.5.x,

Started to get Microsoft .NET Framework error when I would just let tables sit and run (went back to B2S 2.1.2 from 2.5 to fix that issue).

I was not having it lol. Spent the last week getting things back to what I hope it used to be.

 

I have backups and clones (I'm finding it easier to just make a 1:1 clone). I'm updating stuff every other day.

I messed up the other day. I stared, mistakenly changing and deleting files in my VPX backup, thinking it was the folder I was working in!

I just about took myself out back to kick my own ass lol. So yeah, I think I'm back in business.

Running now:

VPX RC4

B2s 2.1.2

freezy 2.3.0

VPINMame, don't remember what Ver. I'm not at the pinball table.

I thank all that contribute to this hobby!

All my extra time is spent here.🍻

 

 

Wow. So after all of this are DMD tables now shutting down properly for you?

 

I read through all of the recent bug reports for VPX in GitHub and someone placed a report two weeks ago #1989 regarding the same issue of tables not closing down properly in 10.8.1. The steps listed to reproduce are exactly the same and also occurs with the most recent updates in 10.8 and 10.7.4. So this is most likely a VPX issue and not a VpinMAME issue. Rolling back to VPX RC4 I imagine did fix the issue for you.

Edited November 15, 2024 by BostonBuckeye