VPX-GL64 Newest Release 1/29/25

[Spacegoogie]

The one found here: https://github.com/vpinball/vpinball/releases

 

Has anyone been using? Any issues you notice or improvements?

My VR only setup is working great so I would rather not deal with any issues lol.

Should I update to this?

 

🍻

[Thalamus]

I don't have a VR setup. But, I can't see how you can go wrong. You can always, if you are that scared of breaking you etup. Just rename the VPinball_GLxxxx.exe to something. Then only replace the exe from the update and see if that breaks anything. If not, well, then you've got your answer. I advice you, make a zip bakup before doing anything. It is always smart having some way of retreat. Also make a backup from time to time of %appdata%\VisualPinball\VPinbllX.ini. (path might be slightly off, as it is taken from memory only).

 

[Spacegoogie]

While I appreciate the suggestion of renaming executables and backing up files (standard practice, really, like telling someone to wear a seatbelt while driving lol, I was hoping for something a bit more insightful. You know, like user experiences with this particular release. "I don't have a VR setup" isn't exactly the ringing endorsement I was looking for.

It would be like asking for restaurant recommendations and someone saying "I haven't eaten out in years, but I guess you could try the place down the street." Sure, you could, but is it any good? That's the million-dollar question my guy.

So, to reiterate: Has anyone with a VR setup actually used this specific release? Have you encountered any quirks, performance hits, or unexpected interactions with your VR hardware? Any improvements you've noticed? Or, conversely, any reasons to avoid this update like it's last week's fish? Real-world feedback from VR users would be greatly appreciated before I potentially introduce chaos into my perfectly functional setup. Because, let's be honest, "if it ain't broke, don't fix it" is a mantra I started living by, especially when it comes to VPX.🍻

[deadmanworking]

@Spacegoogie, that's quite a condescending reply to actually 100% solid advice: try it yourself while logging each step and making sure you can revert if something breaks..  It's not a big deal to try out if you have your backup routine down, so why expect others to do the work for you and throw around strange metaphors about seat belts and restaurants, it's a bit weird. 

[Spacegoogie]

@deadmanworkingIt's not about expecting others to "do the work for me." It's about leveraging the collective experience of the community.

Why reinvent the wheel, or in this case, spend hours troubleshooting, if someone else has already encountered and potentially solved the same issues? My "strange metaphors" were simply over the top illustrative of the fact that general advice, while well-meaning, doesn't address the specific information I'm looking for and again with your comment. 

My goal was to gather targeted feedback from VR users, and that is what I'm still hoping to receive respectively .

 

So, while I acknowledge the validity of the backup advice, it doesn't move the conversation any closer to actually answering my question.

I think if we are not actually going to answer the question at hand there is no point in even posting a response to it.

🍻

 

 

 

[deadmanworking]

@Spacegoogie, sure, it's a good idea to collect other users' experiences before upgrading, that's what these forums are for after all. But even if you'd be getting green light from 10 other VR users you could still break your individual setup with the update, so you need solid backups like Thalamus outlined any case to be able to instantly roll back in that case.

 

Why wait for answers that might never come instead of trying yourself and then maybe provide valuable experiences to others. 

 

Or never update at all, if you live by "if it ain't broke" that might be the better route for you, I think you'd be missing out though since for me updating VPX, VPinMAME and B2S last week fixed a few longstanding issues with some tables. I guess this kind of info is not interesting for you since I'm not a VR user, still think you shouldn't be brushing off others' advice in the manner you did, not very respectful. 

[Spacegoogie]

8 hours ago, deadmanworking said:

@Spacegoogie, sure, it's a good idea to collect other users' experiences before upgrading, that's what these forums are for after all. But even if you'd be getting green light from 10 other VR users you could still break your individual setup with the update, so you need solid backups like Thalamus outlined any case to be able to instantly roll back in that case.

 

Why wait for answers that might never come instead of trying yourself and then maybe provide valuable experiences to others. 

 

Or never update at all, if you live by "if it ain't broke" that might be the better route for you, I think you'd be missing out though since for me updating VPX, VPinMAME and B2S last week fixed a few longstanding issues with some tables. I guess this kind of info is not interesting for you since I'm not a VR user, still think you shouldn't be brushing off others' advice in the manner you did, not very respectful. 

Really man, because the first thing I said was "While I appreciate the suggestion", How is that disrespecting?

Yet here we are again with my  post being flooded with nothing useful or related to this question, that to me is disrespectful.

I have been working with VPX for over 20 years, if I need to ask about backup or anything related to it I would have included in this or another post.

 

And again, If you don't have any info related to the topic and it's irrelevant  to the post,  please  with extra sugar and a cherry on top,  find another post.

Good day.

 

[Thalamus]

@deadmanworking ... just ignore him. I will.