The ball is wild -- possible it was just not sitting cleanly in the catapult, which is why we said our goal was 90%. On my game, which I unboxed a couple of weeks ago, have yet to see a miss (have original power supply).
At some point when this happens, if you don't mind, immediately power off the machine, so as to keep minimize stuff flowing in to the logs, then boot up and pull the logs and send to me.
can't say I did a lot of testing on a five ball game, I'll look into it.
Quoted from kdecgp:
I followed the wires from the api stage display and they go to a connector with a label wca 0020-60 and the white connector and area near the connector on the board look brown.
Not seeing what you think is brown and there is no high voltage on that board (which is what can toast a connector) Possible the 'brown' is the marking so you know which plug goes where? There are no wires going to that board that would be tied to the mini-display, so guessing your got your wires crossed at some point. There is a wire to that board that connects with the servos in the stage. Open a ticket with Barry, via out website, and he can help you troubleshoot the issue.
As others have mentioned, there is a setting for this, but thought it defaults to off. It is obviously a good feature for locations so a game is not left standing with a ball in the shooter lane. We use it on our lobby game so the receptionist is not stuck listening to the main track all day because someone walked away mid game.
When I do the 'official' release, which unless something major comes up, should be later this week. In the meantime, those playing with the test version get to find the changes are their own, at least a couple have been mentioned here (or maybe they were in PMs)