6 replies to this topic

[Skitso]

I'm having an odd issue activating Frankie multiball in Monster Bash: Frankie won't stand up no matter how many times I hit him. After enough hits, the multiball just starts with Frankie never getting up for me to shoot his ramp.

Table tests say "check switch 81, 82, 83 and 84" (the last two are FRANKIE TABLE UP/DOWN)

I use ROM "mb_106b" downloaded from here at VPforum

What I have tried:

-redownloaded table

-redownloaded rom

-factory reset
-deleted NVRAM -file
-cleared registry

Anyone else having the same issue? Could it be something that has broken with a new VPX version?

 

Thanks for help, friends!

Edited by Skitso, 05 September 2018 - 09:23 PM.

[tictox]

i played MB on VP 10.5 and have VPM 3.1 using mb_106b rom and got the frankie multiball a couple of times just a few days ago and had no issues with him standing up. Of coarse you didnt mention which build of the game you are using. Im using Monster-Bash-X-NZTT-1.3

[Skitso]

Yeah, I'm using the same table build. If anyone has any ideas, I would welcome them gladly.

[Draifet]

Maybe u tagged it as static by mistake? But strange if u already downloaded it again.

Edited by Draifet, 06 September 2018 - 05:33 AM.

[xenonph]

After hitting Frankie 5 times, an opening to ramp appears below him when the targets lower out of sight. He doesn’t stand until after you shoot the ramp, and right before the multi ball starts.
In pic1, he is standing after hitting ramp and during multiball.

 

 

If you hit F1 while table is running you can go into rom settings menu and skip pinball startup test as seen in pic2.

 

If that doesn’t help, try the nvram I added as attachment.
Place in your nvram folder.
 

Attached Files

•  mb_106b.nv   12.04KB   55 downloads

Edited by xenonph, 06 September 2018 - 06:24 AM.

[STAT]

Beside that, i hope you are using latest VPX 10.5 ?

[Skitso]

That Xenonph's nvram file fixed the issue! I can't understand how, however... because I had deleted it earlier so shouldn't the software create a new default one automatically? Oh well, at least it works now. Thanks everyone!