1790 replies to this topic

[Thalamus]

https://www.dropbox....200405.avi?dl=0

 

I don't see any issues with lw3 ?? Not tried the others, but, I didn't see any issues with them before either so ... ?

 

- I'm just now curious now if Kiwi sees any changes for Baywatch.

Edited by Thalamus, 05 April 2020 - 11:22 AM.

[toxie]

Baywatch should be same as the last builds.

Apart from that: So far we're good it seems?! I desperately hope it stays that way. 

[Sheltemke]

We need 2 things i think:

 

-More testers

-Baywatch and Frankenstein for testing (lol just kidding).

 

Apollo 13 and Batman forever looks good for me. Animation will never as smooth/fast in sega DMD than Williams ones i think so i think its not bad now... Video mode in apollo13 works well.

 

Edit: Played Star wars and Lw3 too not found errors yet.

Edited by Sheltemke, 05 April 2020 - 11:36 AM.

[Thalamus]

I just tried the PM5 of Baywatch and the video mode at least is fast. No odd things happening while playing, but, must admit also - don't know that table very well so I'm really looking forward to the kiwi release. Personally, I think we should just release this version with a extra notice around the changes.

Edited by Thalamus, 05 April 2020 - 11:44 AM.

[kiwi]

I have been doing other things for two days,
I want to try the latest beta with Baywatch later.

[Sixtoed]

Apologies, time's been tight this weekend, I won't go through individuals but I tested all the usual suspects and everything seems to be working fine
Star Wars, Lethal Weapon 3 and Batman Forever specifically work fine.

[kiwi]

@Baywatch

I didn't have to wait long, second game,

 
the multiball stopped when there were 2 balls left in the game,
without any particular situation,
as if he had lost count of the balls in play.

[toxie]

But no such issues with VPM 3.2?

[Sixtoed]

What baywatch is that? the old vp9 one? I didn't find any particular errors with it, however the table did crash quite a few times whilst I attempted to test it (sound errors among other things).

 

I did some regression testing with the 3.2 release and like Batman Forever, Baywatch is a lot slower than how it is now (in the latest 3.3 beta), I'd be tempted to say that, like Star Wars, there might be some hack that's falling apart now it's running at its proper speed?

 

(just a guess)

Edited by Sixtoed, 05 April 2020 - 09:34 PM.

[toxie]

But with 3.2 you didn't get these crashes?

[Sheltemke]

@Baywatch

I didn't have to wait long, second game,

 
the multiball stopped when there were 2 balls left in the game,
without any particular situation,
as if he had lost count of the balls in play.

 

Surely you deleted nvram etc etc. You have tester(s) for your Baywatch wip? If yes they have the same problem while multiball running ? It's interesting becouse i played the VP9 version a lot (some time ago) and not remember multiball problem. The script is similar than vp9 version or not?

Just try to help sorry if some question sounds stupid.

[kiwi]

No balls problems with VPM3.2 or with previous versions, now I try again with the official VPM3.2 and let's see what happens.

 
The scripts haven't received any big changes lately, I just added ball rolling sounds and shadow.
I'll check the trough code again, it's the only place where the balls are destroyed.

[Sixtoed]

OK, I did some direct regression testing between 3.2 and 3.3 latest beta in Baywatch.

I got the same crash in both "Script Error Line: 1338 (null)" which is "BallXPos = Soundball.X" and it then comes up on the DMD as "1 Ball Missing"

This is using;

Baywatch_NightMod_Color_LoadedWeapon.vpt

 

Apart from that the most obvious things testing them back to back are obviously the speed being much better in 3.3 beta, and that I "think" the new 3.3 beta can have more call outs and animations played, or at least more reliably. (I'm assuming this is caused by animations lasting longer in 3.2, so I think it's catching things that the 3.2 didn't because it was still completing the previous animation?).

 

Also the kicker is unreliable in general.

 

I think it's a table problem.

 

*edit* I went back and tested with 3.2 again to make sure, and it crashed again, it's a table problem.

Edited by Sixtoed, 06 April 2020 - 09:36 AM.

[toxie]

@Baywatch

I didn't have to wait long, second game,

 
the multiball stopped when there were 2 balls left in the game,
without any particular situation,
as if he had lost count of the balls in play.

So this means with the newest beta we only have this (potential) regression so far?

[Sixtoed]

I got to baywatch normal multiball numerous times and never had that happen to me (just the crash I mentioned), but I'm not that good at it so didn't get that far past multiball...

 

I can't test it like Kiwi as he's building the new VPX version (which I now know having looked!) and I don't have that to test with so I can only go off the vp9 one, I also don't have the technical visuall pinball coding knowledge to be able to narrow it down further than this.

[toxie]

All good then. As Kiwi releases the new version we can all test that, and then let's see if there this problem is happening also on 3.2 or exclusively with the 3.3 beta.

 

In the meantime, thanks again to you all, and keep on testing. 

[kiwi]

I played for almost two hours with VPM3.2 without problems,

 
with the latest beta it is as if the trough loses the count of the balls in the multiball mode,

this can occur when balls go into the drain before all 5 balls are thrown into play.

 
But yes I can also release the table, more people can try the table.

[Sixtoed]

OK, I've played the Kiwi's new version of Baywatch on the latest beta from yesterday and got to multiball twice and not seen any problems? First time I didn't have anything drain, second time I purposely let the first ball down drain to see what happened and it still worked OK? It was pretty chaotic, but it seemed like everything was OK and I was still in multiball mode on the last 2 balls? (I think?).

 

Great update by the way Kiwi, it looks lovely and plays much better than the old one

Edited by Sixtoed, 06 April 2020 - 05:29 PM.

[hayhu1m]

As Sixtoed said i tested the same way last 2 balls still in multiball.

 

Absolutely stunning table Kiwi.

[Sheltemke]

Omg Kiwi what a beautiful table thank you so so much!

 

So i tested with last vpinmame from first post and first time when multiball running and 2 ball was on playfield when 1 ball went out the table registered as "last". So i couldn't play with the last ball.

After that 2 ball went to plunger same time.

 

After the game i deleted the nvram file(i played baywatch in vp9) and played 2 more with 2 multiball, it was no problem.

So i not sure if nvram were the problem or not but after i deleted it the next 2 game won't have error in multiball.

Unfortunately i have to go now so i can test it again tomorrow.