Spork98765
Member
- Jul 3, 2015
- 363
- 0
The captive balls in R911 aren't skinned and they alternately turn blue/red when the sirens go off. The weird thing is instead of them being the same colour when it happens one is red then other is blue, and they they strobe back and forth.
TOTAN has a broken skillshot, still. If you tap while it is doing the zoom on the skillshot area intro doo-dah, that cannot be eliminated with event cam, then it freezes there until you lose your ball; or don't do it.
The pro mode in TO is fixed so ROM changes can be made, but now no end of game menu appears.
While navigating the coin door any presses on the clownishly huge buttons of the UX they are mounted on causes the playfield view to move around. This is a long standing bug. Either separate the playfield view controls from the coin door UI, or make it so the coin door UX zone doesn't have any other mapping so any touches/clicks in that are don't make the underlying view to move.
Should captive balls be changing skins when the play uses a custom ball? I seem to remember that it didn't happen then it did and was reported as a bug, then was fixed and it's now happening again. So, is it actually a bug, or is this now the way it will be from now on?
TOTAN has a broken skillshot, still. If you tap while it is doing the zoom on the skillshot area intro doo-dah, that cannot be eliminated with event cam, then it freezes there until you lose your ball; or don't do it.
The pro mode in TO is fixed so ROM changes can be made, but now no end of game menu appears.
While navigating the coin door any presses on the clownishly huge buttons of the UX they are mounted on causes the playfield view to move around. This is a long standing bug. Either separate the playfield view controls from the coin door UI, or make it so the coin door UX zone doesn't have any other mapping so any touches/clicks in that are don't make the underlying view to move.
Should captive balls be changing skins when the play uses a custom ball? I seem to remember that it didn't happen then it did and was reported as a bug, then was fixed and it's now happening again. So, is it actually a bug, or is this now the way it will be from now on?
Last edited: