sharkus,
I'm sorry. In particular, if one is just on the verge of achieving a good score.
I tested the table pretty often. I know that there are in rare situations problems with the ball count.
This also happens with the real machine.
It has to my own knowledge nothing to do with the remaining balls at the table.
As long as balls are not active on the playing field, they are not counted.
In the real machine, captured balls remain at the table. I've added a feature, however, that the remaining balls on the table can be cleared. With the key "c".
Noted only in passing.
Incidentally, it's pointed out in the added rules and notes file.
BTW: Whoever wants can view the 'ball in play' counter.
Editor -> backdrop view -> just move the black text box ( BACtext = balls active) into the viewing range.
I will do my best until the next update to find a solution. Since such an error happens very rarely it's difficult to eliminate these.
One solution can be to set the "TimerBAC" to a lower level. i.e. 10 or 5 ms.
Servus Walter
Sweet table! I never heard of it before. Discovering new tables is one of the reasons why
VP is so great.
I did have one problem that required an exit from
VP to fix. Please let me know if this is operator error (i.e. are you required to clear the table before a new game?)
Here's the sequence of events:
- 5 ball game
- previous game left balls locked in the volcano and tar pit
- during new game unlocked all balls and was playing 3-ball multi-ball
- lost all three balls in rapid succession
At that point things were stuck. The game would not put another ball in play. I tried all keys.
Thanks,
Sharkus