1 reply to this topic

[CrimsonTurtle8]

Okay, so I've spent hours investigating a problem that me and at least 2 other people have had very recently that's basically unsolvable.

 

At any given moment in 10.8, all playfield_mesh objects across all or most tables can vanish. The collision is still there, but there is absolutely no way to restore the image. The only solution that somebody said worked (on reddit) is basically resetting your computer to square one once your files are backed up.

 

I've tried:

 

1. Replacing the playfield mesh with my own. This still has promise but every time I import a simple rectangle I made in Blender, it bogs the game down about 10 times slower for some reason. And I have no idea how to texture that properly yet. Also this bug is still a problem either way.

2. I've tried adjusting ALL video settings, accounting for graphics cards. I'm gonna stop you before you say "have you tried checking this box and unchecking this box--" etc. Yes, I tried that. 

3. Updating graphics cards.

4. Adjusting files in the VPX folder including trying to match them to 10.7 settings and setting all Visible =  to Visible 1.

5. Trying all image formats.

6. Trying to toggle on "visible" in the Live Objects part of the Live Editor.

7. Clean install of VPX with all new files.

8. Deleting/Uninstalling B2S. 

9. Creating a new Windows User and starting fresh.

10. Installing a graphics card command center and fiddling with priorities and power.

11. Ensuring there's only one screen VPX is displaying on.

12. A lot more I can't even remember. I asked ChatGPT and it gave me about 30 suggestions and fixes and none worked.

 

The problem is deep in the programming of VPX and Windows and how they're interacting because A) it stopped working in an instant with nothing to trigger it and B) Even downloading a fresh VPX 10.8 version onto a fresh user account with a "Completely Blank Table" makes an invisible playfield. "Full Example Table" works no matter what, perhaps because "playfield_mesh" is findable and editable within the software?

 

I have not yet tried resetting my computer and reinstalling windows, but that's what one guy on reddit said when it happened to him. He said it was the only solution. I'll have to spend about 3 hours backing up my files just in case.

 

Please look into this problem. It's likely to happen again to anyone at any time, and it's like a virus. It affects all your tables across the entire device, in perpetuity. 

 

EDIT: I'm getting the sense the mesh isn't necessarily part of it and that there's some ghostly collidable surface in this software that does most of the work. So when I import a new mesh named "playfield_mesh" it overrides that. This doesn't help me in any way though, if anything it makes it harder because I can't adjust this mysterious, ethereal playfield in any way.

Edited by CrimsonTurtle8, 22 January 2025 - 08:37 PM.

[jpsalas]

Actually there is a playfield mesh in all the tables, and it is called "playfield", and you can changes it's properties in the editor, in the window Table > Physics. There you can change its elasticity or friction. There aren't more properties than the ones there you can change.

 

On some tables the author has replaced this "playfield" with his own mesh, which must be called "playfield_mesh" fot it to replace the original playfield, and if you check the properies of this primitive you'll see that most of they are greyed out, because it is not the meaning to change those properties. You have simply replaced the default mesh with a new one, in case you needed some holes, which is mostly the only reason to change the playfield. But its properties will still be the same as in the Table > Physics.

Edited by jpsalas, 22 January 2025 - 08:54 PM.