StackAndTile Forums › General › Support Help › Stacking does not work on newest PokerStars SCOOP tables
Post Reply

Post a New Reply
Reply to thread: Stacking does not work on newest PokerStars SCOOP tables
Username:
Please select the number: 6
1 2 3 4 5 6 7 8 9 10
Post Subject:
Your Message:
Smilies
Angel Angry Blush Confused
Dodgy Exclamation Heart Huh
Idea Sleepy Undecided Smile
Wink Cool Big Grin Tongue
Rolleyes Shy Sad  
Post Options:
Thread Subscription:
Specify the type of notification and thread subscription you'd like to have to this thread. (Registered users only)



Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)


Thread Review (Newest First)
Posted by DaradBur - 04-11-2021, 02:07 AM
2.99.13s worked perfectly, thanks!
Posted by DaradBur - 04-10-2021, 02:21 AM
(04-09-2021, 11:54 PM)SaT_Admin Wrote: Is the table background red/orange?

Are you using the PokerStarsAurora site inside SAT?

If so, try this version 2.99.13s and let me know if it works:

https://www.stackandtile.com/sat/tmp/Sta...29913s.exe

>Is the table background red/orange?

Yes

>Are you using the PokerStarsAurora site inside SAT?

Yes, I even removed and re-included the site.

>If so, try this version 2.99.13s and let me know if it works

Perfect, I'll let you know shortly!
Posted by SaT_Admin - 04-09-2021, 11:54 PM
Is the table background red/orange?

Are you using the PokerStarsAurora site inside SAT?

If so, try this version 2.99.13s and let me know if it works:

https://www.stackandtile.com/sat/tmp/Sta...29913s.exe
Posted by DaradBur - 04-09-2021, 05:57 PM
Hello,

There's been a PokerStars update yesterday (8 April 2021) which changed the SCOOP table theme. For some reason, I've been unable to stack those tables, they always come back to the grid, but I can move them in a different grid slot.

I did not find a way to disable special themes on PS (which can be done on Winamax for instance), doesn't seem to be a workaround right now.

Thanks!