157 replies to this topic

[numiah]

I once again got the "object required" error during Monster Multiball @ version 1.4.3
When I drained the balls after that, the table was missing one ball and kept searching for it.

I wonder what could cause this error.

[jpsalas]

I can take a look at it, but I think that I'm out of ideas. In theory it is quite easy to use.

[numiah]

It's no biggie, but it's always sad when you get above 100 mill and need to restart the table
Perhaps if more people have this issue, we could narrow it down a bit to make it easier to locate.

[kiwi]

I changed the script line 1436
Dim currentball(3), ballStatus(3)

with
Dim currentball(4), ballStatus(4)

I tested the table and everything seems ok

Max

[jimmyfingers]

I changed the script line 1436
Dim currentball(3), ballStatus(3)

with
Dim currentball(4), ballStatus(4)

I tested the table and everything seems ok

Max

To be safe, on tables where I've added the B2B collision script / process, I've made this value one or two higher than the actual number of balls that could ever feasibly be in play / locked on the table. For this table, I would consider making it 5 for tnopb and, as always, match the Dim currentball(5), ballStatus(5) as sometimes there can be a timing thing between destroying a ball / ID and creating a new one.

I don't know this table that well, but it seems to that Monster Multi-ball is the test to see if the B2B is totally working but requires a ton of playing first or modifying the table to troubleshoot and get there quicker.

[jpsalas]

OK, last fix 1.4.4 for the ball collision is on its way up
I hope this time is the last update. Anyway, it is the last update it should work now

[numiah]

Works a charm now !
I had two monsterballs and all went perfect.

Thank you so much for your support JP, and thanks to kiwi for pointing things out.

[Arcade4]

Works a charm now !
I had two monsterballs and all went perfect.

Thank you so much for your support JP, and thanks to kiwi for pointing things out.

re

Great news.
Guess I will be getting the last version now.

[gStAv]

Thanks for your work JP!

[thewool]

I just wanted to add my thanks for the latest update JP

It was me that suggested the ball sounds in the first place, sorry for causing you such a pain in the arse

[Nick Warcholak]

I just wanted to add my thanks for the latest update JP

It was me that suggested the ball sounds in the first place, sorry for causing you such a pain in the arse

It adds a lot to the immersion factor IMO. I, for one, am glad you suggested it.

[cdf12345]

OK, last fix 1.4.4 for the ball collision is on its way up
I hope this time is the last update. Anyway, it is the last update it should work now

I was playing the B2S Scared Stiff, and ran into this problem with a ball missing in monster multiball, and the author said he was using your latest code.
I'm not sure if you were able to track it down but this is what I posted over there in case it can help you out at all:


I ran into a problem in the monster multiball.

One of the 4 balls is getting stuck somewhere between the coffin lock and the coffin kickout. I was able to get to monster multiball twice, and it happened both times. Shooting the coffin lock would "unstick the ball". Both times it happened, I was down to 2 balls left in the multiball, the stuck ball and the ball I was juggling. When I shot the lock (left loop) one ball was released out of the coffin and the other ball came back down the left loop onto the playfield (it may have been stuck around the lock gate?).

I have not had this problem with earlier versions of JP's Scared Stiff, I know he's been updating his code lately, so this may have been fixed in one of his recent updates. So this bug has more to do with what version of his code you based your B2S conversion on than anything the B2S code is effecting, but I thought you should be aware, in case JP has updated the table script and it needs to be updated in your conversion.

Edited by cdf12345, 24 September 2011 - 09:11 PM.

[gStAv]

Hi!

I don't know if that's the case in this table.
But when an updated version of a table comes out and you want to easily add the B2S code to it.

You can do this by comparing the differencies of the code from the same versions of the table. The one with the B2S code with the table without it,

Then add these lines B2S code to the new table in the right place of the script.

Very easy!

I've played with the free app WinMerge, download here

Ass seen of a screen dump below you can compare the two scripts side by side (not vp in pic), and any differences is shown marked yellow, and you can also
sot them quick by the column in the left.



So an updated table would be a few minutes for anyone to "MOD" back to B2S if needed!

Cheers!

Edited by gStAv, 25 September 2011 - 09:01 AM.

[DedRok_V]

I still get the invisible ball bug, dont know what causes it,



but today the invisible square ball turned into a white square ball then coloured in the ramps white.
Normally the ramps will have some stretched ball images down them when it goes invisible.

This is the only table out of 300 I have that does it. The GI8 and normal B2S tables do it too. All the last few versions.




Using an i7 and 2 GTS250's on XP

Please help

[DEFme]

Great table, but I'm having an issue with low audio. The flippers, bumpers, bullseye targets, and slingshots sounds play at perfect volume. My problem is that the DMD audio, game music, voice-overs these type of sounds play extremely quiet.
Is there a fix for this? Something I am doing incorrect?

In Visual Pinball --> Preferences --> Audio Options... both are at max volume.

Totally brand new to Virtual Pinball. Thanks for any help in advance.

[zocken23]

Try hitting 8,9 or 0 for in-game volume adjustment. if the dmd say "open coin door", try hitting end-key on your keyboard first.

[DEFme]

Try hitting 8,9 or 0 for in-game volume adjustment. if the dmd say "open coin door", try hitting end-key on your keyboard first.

8 & 9 did it! Thank you very much, zocken23.

[toolmaker]

Just had to share this...