Ruenin Posted June 19, 2025 Posted June 19, 2025 I was browsing the top downloads and saw the T2 table. I recently installed Baller Installer on my laptop (Windows 11, 16GB RAM, RTX 3070). I got the files named appropriately and in their respective folders, but when I start the game in Virtual Pinball X, I get the following screen: Oddly (or not so, given the message), I can click Continue and it seems to work fine. I checked my .NET installation and I'm running the latest and greatest, as well as previous versions. Any idea what might be causing this?
actarus Posted June 20, 2025 Posted June 20, 2025 Hello, I have the same issue - with a much lower end configuration - so I am very interested in finding a resolution to this problem...
deadmanworking Posted June 20, 2025 Posted June 20, 2025 Hi guys, are you using the hauntfreaks backglass? I remember having this error so first try and check with a different backglass file to rule out an issue with table itself. Then check again if you are on the latest version of B2Sserver, VPinMAME, and Visual C runtimes, after my last round of updates this error disappeared for me.
actarus Posted July 2, 2025 Posted July 2, 2025 Thanks for your help, Well, I tried to update as many things as possible (indeed all but Windows itself) to the latest and greatest... (only .NET is restricted to 4.8 as I cannot update Windows easily, the pincab being in a no Internet area... but all Pinmame/VPX/.... components are at their latest version) and actually nothing improved. A puzzling thing is that when launched from VPX directly, table launches... PinUp pack, and works fine - applies to both versions of the table I use - but when launching from PinUpPopper, I end up with the B2S failing screen.... I have 2 versions of the table, one working fine, one exposing the error... Ended up disabling the failing one.
deadmanworking Posted July 3, 2025 Posted July 3, 2025 @actarus if this problem only occurs from Popper then you should that that Popper launches the correct and identical VPX version for that table, might be set to launch a different version that ends up crashing.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now