2585 replies to this topic

[freneticamnesic]

using todays kingpin update? damnit

 

Fren,

Kingpin looks great! Plays really smooth too.

 

I did get a script error at Line 1509  Subscript out of range: 'b'

 

I was rocking along and shot it up the right ramp when it happened.

Don't know If it's something anyone else has seen. Using latest build 2012.

[Trinity]

Yes sir, I used the latest Kingpin. And latest beta.  Just downloaded it about 2 hours ago.

Like I said, ran smooth for awhile. Played it maybe 10 min. or so before it crashed.

[freneticamnesic]

thanks for the feedback..... back to the drawing board! sorry about that

[Trinity]

Nothing to be sorry about. It will be amazing in the end. No doubt here.

[ClarkKent]

With the first Kingpin table I got an error message in line 1555. Have to try the new one.

 

I would be happy to get a bigger ball (about size 53) or at least the variable to adjust the size by myself. And don't you think the flipper elasticity is too high? Ball is bouncing back heavily...

[freneticamnesic]

yep, i'd love feedback on the physics. i was telling the team i've played it too long like that, i no longer know what feels right lol...usually i think i'm pretty good with my physics but i have that all set up well before i start playing, not in this case though. i'll tweak the flippers a bit for the next update

 

With the first Kingpin table I got an error message in line 1555. Have to try the new one.

 

I would be happy to get a bigger ball (about size 53) or at least the variable to adjust the size by myself. And don't you think the flipper elasticity is too high? Ball is bouncing back heavily...

[ClarkKent]

Get the error message on line 1509 with the new version.

 

The physics on the flippers is really weird. Sometimes the ball accelerates while on the flippers, sometimes it suddenly stops when rolling down the inlane and reaching the flippers, sometimes it begins to jump on the flippers. As far as I remember JP mentioned something about this behavior earlier. His Nascar is really really well balanced and this never happens there - maybe he should have a look?

 

Nevertheless it's a GREAT port of the original game!

[robertms]

Bang up job  on Kingpin guys   Really enjoying it, however I do get the same errors as others.

 

 kingpin_beta_error.jpg   242.53KB   15 downloads

[freneticamnesic]

uploading a new version of kingpin, i missed a crazy obvious/not obvious setting. physics should be top notch now i adjusted rubber friction and force, adjusted flipper strength and friction, and playfield friction (this was the big one, I added an extra 0...)

 

it's the same link, new filename ends with a "-b" - let me know how these physics are, and hopefully the next update will fix the errors everyone is getting. in the meantime, i've commented out the ball rolling routine until i can fix it. disappointing! but that's why this is the table testing thread! 

Edited by freneticamnesic, 03 June 2015 - 06:22 AM.

[robertms]

Fren, updated physics play about a million times better. This really is a cool game. Thanks for all your hard work!

[hauntfreaks]

I've recently updated the graphics on Noah's Evel Knievel and made it FS for my cab... I made this known in the updated EK B2S thread

so I passed it to hmueck and with his lightning fast VPX conversion skills he passed it back to me...

I replaced lots of the walls with primitives all rubbers updated, hardware, plunger, wire triggers, non-legacy kicker (awesome swirl)... I've been testing in my cab and "I" think it plays really good...

 

Evel Knievel VPX

 

[ICPjuggla]

With the first Kingpin table I got an error message in line 1555. Have to try the new one.
 
I would be happy to get a bigger ball (about size 53) or at least the variable to adjust the size by myself. And don't you think the flipper elasticity is too high? Ball is bouncing back heavily...

Thx for the physics feedback as fren said we have all been playing it the way it is so its hard to tell what feels right.... :-)

About the ball size I've seen you menchaned this on many builds. To be honest I'm not really sure why, if the table is built using the right dimensions in the editor then the ball should be the correct size within VP. The Kingpin table has been built using the correct table dimensions so the ball should display properly within VP. Maybe this is something you should bring up in the VP10 beta thread and not to the authors. What I'm gathering is you think the ball is the wrong size within VP and it really has nothing to do with the people building the table.. Or maybe it's just your personal preference to have a bigger ball but either way that really has nothing to do with the authors if the correct dimensions are used when building the table..

[ClarkKent]

I only ask the authors to include a ballsize constant in the script - so everybody can choose the right size.

Edit: After discussing this thing with a friend we came to the conclusion that the ball looks smaller on my cab because I have only a 40 " monitor installed. On a 46 " monitor the ball looks slightly larger than a real one - on a 40 " display slightly smaller. So only using the ballsize constant would be the only solution to solve this problem for all display sizes. Of course, and I understand this, the ball would not be proportional to the rest of the table but I think it`s more important that the ball does not look like a small marble but a real size steel ball...

Edited by ClarkKent, 03 June 2015 - 03:10 PM.

[Trinity]

I've recently updated the graphics on Noah's Evel Knievel and made it FS for my cab... I made this known in the updated EK B2S thread

so I passed it to hmueck and with his lightning fast VPX conversion skills he passed it back to me...

I replaced lots of the walls with primitives all rubbers updated, hardware, plunger, wire triggers, non-legacy kicker (awesome swirl)... I've been testing in my cab and "I" think it plays really good...

 

Evel Knievel VPX

 

Whoo Hooo!  Awesome job on this! Looks and plays fantastic!

[lodger]

I've recently updated the graphics on Noah's Evel Knievel and made it FS for my cab... I made this known in the updated EK B2S thread

so I passed it to hmueck and with his lightning fast VPX conversion skills he passed it back to me...

I replaced lots of the walls with primitives all rubbers updated, hardware, plunger, wire triggers, non-legacy kicker (awesome swirl)... I've been testing in my cab and "I" think it plays really good...

 

Evel Knievel VPX

 

Wishing I were home to try this... this looks fantastic

[hmueck]

Wishing I were home to try this... this looks fantastic

You mean by the look of the unavailable flickr picture?

 

[freneticamnesic]

 

Wishing I were home to try this... this looks fantastic

You mean by the look of the unavailable flickr picture?

 

 

pebkac, looks great from here

[ninuzzu]

Sorry for the long post.
After some investigation maybe I found the problem in KingPin ballrolling crash.
First thing first I enabled JP's Rolling Sounds again,so copy this code at the end of the script
(it's slightly different from the original, difference on line 1505)

'*****************************************

'      JP's VP10 Rolling Sounds

'*****************************************



Const tnob = 5 ' total number of balls

ReDim rolling(tnob)

InitRolling



Sub InitRolling

    Dim i

    For i = 0 to tnob

        rolling(i) = False

    Next

End Sub



Sub RollingTimer_Timer()

    Dim BOT, b

    BOT = GetBalls



    ' stop the sound of deleted balls

    For b = UBound(BOT) + 1 to tnob

        rolling(b) = False

        StopSound("fx_ballrolling" & b)

    Next



    ' exit the sub if no balls on the table

    If UBound(BOT) = -1 Then Exit Sub



    ' play the rolling sound for each ball

    For b = 0 to UBound(BOT)

        If BallVel(BOT(b) ) > 1 AND BOT(b).z < 30 Then

            rolling(b) = True

            PlaySound("fx_ballrolling" & b), -1, Vol(BOT(b) ), Pan(BOT(b) ), 0, Pitch(BOT(b) ), 1, 0

        Else

            If rolling(b) = True Then

                StopSound("fx_ballrolling" & b)

                rolling(b) = False

            End If

        End If

    Next

End Sub

I was hearing some looping sound during game play so I disabled the game sound.
To do that just go ingame and press 7, then press 1 and , using the flippers, tune down the volume to zero and press 7 to exit.
Then the funny things start to happen: try to hit the Hotel Lex VUK multiple times and you get multiple looping rolling sounds;
the 4th time you hit it the game crashes with the error on line 1556
If you try to change tnob to 6 (line 1529) it will crash the 5th time you hit it , if you change to 7 the 6th time and so on....
A ramp could help you to get the vuk,like in this photo

http://oi62.tinypic.com/b87kpg.jpg
So I guess the problem could be in the script used to manage the vuk,since in the table I'm working on this doesn't happen.
It seems to be fixed in this way:
1) comment line 581 and 582 like this

'Sub sw51a_Hit:sw51.Enabled = 1:End Sub

'Sub sw51_Hit:bsVUK.AddBall Me:sw51.Enabled = 0:End Sub

2)copy this code at line 583

Dim aBall, aZpos



Sub sw51_Hit

Set aBall = ActiveBall

aZpos = 50

Me.TimerInterval = 2

Me.TimerEnabled = 1

End Sub



Sub sw51_Timer

aBall.Z = aZpos

aZpos = aZpos-2

If aZpos <40 Then

Me.TimerEnabled = 0

Me.DestroyBall

bsVUK.AddBall me

End If

End Sub

3) Now , at line 164, make this change

bsVUK.InitKick sw51,173,28

4) in the editor delete or move sw51b and sw51a out of the table
5) select sw51 kicker and, in state and physics, enable it and disable fall through; the same goes for sw44 kicker
6) finally, on line 1546 of the script, change tnob to 6.

I have tested this for hours, no crash; so it seems there's a problem with the method used to manage the VUK, or with VP itself.
With the old method it works. Hope this helps

Edited by ninuzzu, 03 June 2015 - 04:36 PM.

[freneticamnesic]

Clever work. I'll try it out tonight thank you

[ICPjuggla]

I only ask the authors to include a ballsize constant in the script - so everybody can choose the right size.
Edit: After discussing this thing with a friend we came to the conclusion that the ball looks smaller on my cab because I have only a 40 " monitor installed. On a 46 " monitor the ball looks slightly larger than a real one - on a 40 " display slightly smaller. So only using the ballsize constant would be the only solution to solve this problem for all display sizes. Of course, and I understand this, the ball would not be proportional to the rest of the table but I think it`s more important that the ball does not look like a small marble but a real size steel ball...

I also use a 40" TV in my cab and to me when a table is built with the proper dimensions the ball looks perfict and the proportion looks spot on. Actually a wile back there was a thread that compared TV sizes and ball sizes within VP with a table built to the propor dimensions and the consciences was that a 40" or a 42" TV was almost the perfic size to display the ball in proportion to a real pinball table ie the ball.. Now only if I could find that thread it's here somewhere! lol :-)