World Poker Tour (Stern 2006)

Great table RobbyKingPin, this is one of my favorite tables! but I ran into something odd with this table, if I play for awhile like 3 or 4 games in a row the ball will begin to shutter and the longer you play the more the shutting until it just is too much and you just have to quit. I have no other table that does this and I have another version of this table and you can play it all day long with no shutter ever.
My system is up to date and is over kill for VPX, my frame rate is around 260fps and monitor is at 144Hz so frame pacing is spot on. It just seems like there may be a possibility that a routine in your script that maybe is causing this? not sure it's just odd. Thanks again for all your work! 

Thanks Robby for your help, I did some more testing today and found it is in your version somewhere as both of these versions use the same rom and do not have any ball shutter at all:

World Poker Tour (Stern 2006)_Bigus(MOD) 4.0 and JP's World Joker Tour 5.5.0, I can play these for 15 games in a row with no issues, just 3 games in your version and the ball shutter starts. I also turn off everything  I could in your menu to bare bones and still have the same issue. I like your version the best, it plays and looks great. I'm going to figure out what's going on one way or another. Thanks Again.

It's not about performance, it's about play-ability for me. Just got done playing only one game that I was doing quite well on and playing for awhile but the shutter got so bad the ball was like under a strobe light, just not playable causes a lot of lag.

Like I said above I reduced EVERYTHING in the menu to bare bones and no change at all, I'm not sure if very many people are using 144Hz monitor are experiencing this but maybe someone will chime in and I can determine if it just my system or something else.

Anyhow I'm not disappointed in the table you have done awesome work here and appreciate it! I'm just trying to figure this out. The other WPT tables I use are fine tables they are no where as good as yours but they have zero lag/shutter and hold a 144fps and play just fine.

One more thing I used F11 to monitor the frame rate, you can see it go from a steady 144fps and then slowly drop to 120 and lower, this is where the ball shutter really kicks in, just food for thought.

Something seems broken in the latest update. 

I don't exclude it is my setup and not the game but none of the playfield inserts are responsive.

When I launch the game, the playfield inserts start flashing for a few seconds into the attract mode but then stop and they are not responsive during gameplay. They just aren't triggered while the game plays as normal.
I am using the latest stable 10.8 VPX and latest stable Vpinmame (above 3.6).

All was fine in the previous version/ update.

SOLVED:

You have to update to the latest B2s Server (v2.13 ) on Github in order for it to work:

https://github.com/vpinball/b2s-backglass

A simple copy paste over the existing files works (backup those files first)
How to update described here:

https://github.com/vpinball/b2s-backglass/wiki/Update
 

Edit : I just realised updating to B2s Server to v.2.13 is actually stated in the table description.
I did this months ago but I had to redo it in order for it to work.

Thanks for the update. 

On 7/28/2025 at 7:16 AM, RobbyKingPin said:

I bet performance can be weird sometimes. Probably mine costs the most performance out of the gate so maybe it will happen sooner on mine then compared to others. This does have a lot more bells and whistles compared to what you tried to compare. The difference in quality is not something that can be compared to any other version out there. I do believe this is not in my control since we even got AI used for performance gains  (+30 FPS as a result) So the choice is really simple, accept this performance on this table and just don't play 5 games after each other or try to reduce performance with the options provided in the menu. And just pray to the gods just like me that VPinMame gets even more stable in the future. I mean a reset after a game over is like a minor thing to do and takes very little time as well

@RobbyKingPin and @MachWon There are several errors when I attempt to lock the table and it runs an audit. Some of the errors at the top specifically mention potential stuttering related to timers.

Table audit:
. Warning: Ball uses legacy 'spherical mapping', it will be rendered like a 2D object and therefore will look bad in VR, stereo or headtracking
. Warning: Part 'DT' uses a timer with a very short period of 5ms, below a 60FPS framerate. This will likely cause stutters and the table will not support 'frame pacing'.
. Warning: Part 'PinMameTimer' uses a timer with a very short period of 1ms, below a 60FPS framerate. This will likely cause stutters and the table will not support 'frame pacing'.
. Warning: Part 'RLS' uses a timer with a very short period of 10ms, below a 60FPS framerate. This will likely cause stutters and the table will not support 'frame pacing'.
. Warning: Part 'PrimT' uses a timer with a very short period of 0ms, below a 60FPS framerate. This will likely cause stutters and the table will not support 'frame pacing'.
. Warning: Part 'CorTimer' uses a timer with a very short period of 10ms, below a 60FPS framerate. This will likely cause stutters and the table will not support 'frame pacing'.
. Warning: Primitive 'PinCab_Backbox' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn1' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn2' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn3' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn4' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn5' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn6' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'CabLightOn7' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'bumperscrews1' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'bumperscrews2' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Warning: Primitive 'bumperscrews3' uses translucency (lighting from below) while it is fully opaque. Translucency will be discarded.
. Total sound size: 25MiB
. Total image size: 211MiB in VPX file, at least 1512MiB in GPU memory when played
. Total number of faces used in primitives: 747461, needing 30MiB in GPU memory when played
 

@RobbyKingPin Apophis gave me a tip to hopefully further banish the remaining traces of the drunken blur and creeping black ink effects on some areas of the table during certain lighting events in VR.

Try setting the Playfield reflections render probe roughness to 1 instead of 0.

During a 5 minute gameplay test this seems to have 99% fixed the issue except on one occasion when I pressed pause, I was unable to replicate the issue on subsequent pauses though.

If anyone wants to DIY this fix before the next update, just go to the editor menu Table/Render Probe Manager/Playfield Reflections/ Set the roughness slide level to "1" instead of "0".

I think there may be a FPS cost to this fix though, but I'm not sure.

doesnt work properly in the newest VpinballX GL64 3d mode (after several seconds screen changes into grey & white pixel mosaic)

Runtime error
-------------
Line: 1777
Subscript out of range: 'chgLamp(...)'
 need someones help please

Thanks for this great update. I have a problem with the Card DMD on the table. I can see the WPT people picture and the cards letter are on the left and not on the middle of the DMD.

Please help

coolball

Thanks, looks perfect now.

Great update.

This looks amazing! But i have a lg 3d tv and the image is flooting. Any suggestions on solving this?

On 12/20/2025 at 9:23 PM, kilazz said:

doesnt work properly in the newest VpinballX GL64 3d mode (after several seconds screen changes into grey & white pixel mosaic)

Yes i have the exact same thing. Hope there will be a fix

Thanks RobbyKingPin, this is looking really good but I found the ball to be slow and hard to get up in the ramps so I changed the Playfield Friction to 0.1 and increased the flipper strength to 2200 and it plays much better to me. If anyone wants to try these changes I attached the .vpp that you can import to test this out. Thanks again for your work.

Edit: I updated this .vpp to RobbyKingPin Suggested settings.

World Poker Tour (Stern 2006) v.2.4.vpp

I understand where you are coming from but changing the playfield friction and a bit more flipper strength isn't going blow out the nFozzy or anything, the ball moves sluggish compared to the original table. Maybe you have another suggestion for this? 

Also I found the ball getting stuck at left & right side of the bottom bumper at Wall100-Wall101, you can nudge it but this will fix it. now I can play without thinking about it.