32 replies to this topic

[koadic]

Most table authors know that adding alpha ramps to a table incurs a performance penalty, and while just a couple here and there is usually no big deal, after adding many of them, another 12(ish) for the plunger animation just exacerbates the problem... which is where this new scripting comes in. Instead of the performance hit for adding 12 alpha ramps, it reduces the hit as if you were just adding 1 additional ramp...

The great thing is, this can be adapted to any lights or other animation that was created using alpha ramps, as it will reduce the performance hit to only the amount of ramps showing at any one time instead of all of the ramps included in the light/animation. As it is now, they are still drawn, only with a width of 0 to make them appear invisible, but they still causes a drop in performance.

This new method basically 'turns off' the alpha ramp, so when it isn't being used, it isn't seen and it isn't being drawn as an alpha ramp, so no additional drop in performance.

As you can see below, instead of setting .widthtop and .widthbottom to 0 to make it appear invisible, this turns the .alpha property on and off which also causes it to disappear and not be drawn when off. It is scripted below much like drop walls are, except with the necessary light refresh to update the animation.

New Alpha Ramp Plunger Code:
Plunger - Timer Enabled with Interval set at 40, and Enable Mechanical Plunger checked

CODE

Sub Table_KeyDown(ByVal keycode)
If keycode = PlungerKey Then Plunger.Pullback:Pcount = 0:PTime.Enabled = 1:Plunger.TimerEnabled=0
End Sub

Sub Table_KeyUp(ByVal keycode)
If keycode = PlungerKey Then
PTime.Enabled = 0:Pcount = 0:PTime2.Enabled = 1:Plunger.Fire:Plunger.TimerEnabled=1
If(BallinPlunger = 1) then 'the ball is in the plunger lane
PlaySound "Plunger2"
Else
PlaySound "Plunger"
End if
End If
End Sub

'***********************
'Koadic's NewStyle Alpha Ramp Plunger Scripting
'(based heavily on and modified from JP's work)
'***********************

Dim Plungers:Plungers = Array(p1, p2, p3, p4, p5, p6, p7, p8, p9, p10, p11, p12, p12)
Dim PlNewPos, PlOldPos, PCount, BallinPlunger
ResetPlungers

Sub swPlunger_Hit:BallinPlunger = 1:End Sub 'in this sub you may add a switch, for example Controller.Switch(14) = 1

Sub swPlunger_UnHit:BallinPlunger = 0:End Sub 'in this sub you may add a switch, for example Controller.Switch(14) = 0

Sub ResetPlungers
For x = 1 to 12:Plungers(x).alpha = 0:Next
Plungers(0).alpha = 1
Pcount = 0
PlNewPos = 0
PlOldPos = 0
PRefresh.state = ABS(PRefresh.state - 1)
End Sub

Sub PTime_Timer
If Pcount <12 Then
Plungers(Pcount).alpha = 0
Pcount = Pcount + 1
Plungers(Pcount).alpha = 1
PRefresh.state = ABS(PRefresh.state - 1)
End If
End Sub

Sub PTime2_Timer
Select Case Pcount
Case 0:ResetPlungers
Case 1:Plungers(0).alpha = 0:Plungers(2).alpha = 1:PRefresh.state = ABS(PRefresh.state - 1)
Case 2:ResetPlungers:Me.Enabled = 0
End Select
Pcount = Pcount + 1
End Sub

Sub Plunger_Timer()
Plungers(PlOldPos).alpha = 0
PlNewPos = INT(Plunger.Position/2)
If PlNewPos > 12 Then PlNewPos = 12
Plungers(PlNewPos).alpha = 1
PlOldPos = PlNewPos
PRefresh.state = ABS(PRefresh.state - 1)
End Sub

[fahq]

so the alpha = 0 makes the ramp not visible.
it would have been nice to have some documentation on the alpha ramps so we could have used this from the get go rather than now having to go back and update all the plungers and lights in our tables.

[unclewilly]

+1 on that.
this should be added to the vp9.12 users guid

[koadic]

I hear ya, all this has only come about because I looked at all the possible properties in the source code and started messing around with stuff

[unclewilly]

appreciate you looking at that.
the source makes no sence to me.

now maybe i can make freddy playable for everyone

[jpsalas]

Nice found! This can also be used with many of the flasher effects made with alpha ramps.

Edited by jpsalas, 06 July 2012 - 06:52 PM.

[Wizards_Hat]

+1 on that.
this should be added to the vp9.12 users guid

If anyone wants to write a paragraph explaining this & let me know where in the guide you think this should go, please do - if it fits, I'll include it in the next update of the guide.

Currently the guide purely documents all of the available settings, options, codes, objects & properties - it makes no comment on how any of these can be used.
My only concern about including "work arounds" or "tricks" in the guide is where do you stop with that?
e.g. if you include a description of this way of using alpha ramps, do you then also include a description of how balls can be used for animation etc, etc, etc...

Not trying to be negative here - just trying to keep the user guide concise yet useful - suggestions welcome.
(for anyone that's never seen it the guide is here: http://www.vpforums....d_Help_v1.0.pdf)

Regards,
Dan.

[koadic]

Nice found! This can also be used with many of the flasher effects made with alpha ramps.

As well as flipper decals like such that are used in Haunted House... anything using ramps that need to made visible/invisible.

This also lends itself to batch replacement in current scripts as I described in the first post, all instances of .widthtop/.widthbottom can be replaced with either .alpha = 1 or 0, and you will get the performance improvements without any additional table editing trying to implement a new method.

Edit: LOL I don't even know if this property was meant to be used in this manner, or if this is just a side effect/bug. Either way though, it appears a better method than shrinking alpha ramps to a width of 0. I just don't know if there are any downfalls that I haven't come across yet, which is why I am sharing this so it can be field tested.

Edited by koadic, 06 July 2012 - 07:35 PM.

[destruk]

Probably include the property in the guide, as that's what the guide is to cover, and then someone could make a 'tricks and techniques guide' for general usage/efficiency routines?

[rob046]

I was about to come on here & say that koadic helped me optimize CFTBL mod with this trick, & I hope all authors catch wind of this & also see the other uses for this. Yes this is a great find for optimization of tables that run a little rough. Thanks to him for deciding to experiment & find this on something I was working on. Sweet!

Edited by rob046, 06 July 2012 - 09:12 PM.

[rob046]

Probably include the property in the guide, as that's what the guide is to cover, and then someone could make a 'tricks and techniques guide' for general usage/efficiency routines?

Not a bad idea. Again with cftbl mod, I had to learn some optimization. If I had just made all clear plastics into alpha ramps, the table would be an absolute hog & unplayable for many. I'm sure guys like JP already know many of the tricks but there are some tables out there not optimized. I know I had to just figure out some things on my own, trial & error. & all I know is just a couple basic things in regards to alpha ramps. Such as for better performance, limit the number of control points, but don't use too few or else they will look like ass for those needing to keep the slider all the way left. Find a good compromise there. Then of course there is setting alpha's to solid in whatever areas you can, such as ramp borders or maybe areas where the ball doesn't pass under. However, 1 downside to this is that for some reason the alpha's appear darker when doing this. Also when doing this, draw these ramps to front or else some funky things can happen.
So as far as building in the editor there is a few things, then of course from a coding perspective we now have this idea from koadic.

Edited by rob046, 06 July 2012 - 09:32 PM.

[koadic]

However, 1 downside to this is that for some reason the alpha's appear darker when doing this.

This is because it doesn't use the alpha channel when doing it this way, so the image is completely opaque instead of translucent.

[rob046]

However, 1 downside to this is that for some reason the alpha's appear darker when doing this.

This is because it doesn't use the alpha channel when doing it this way, so the image is completely opaque instead of translucent.

Yeah I figured the reason had something to do with that. Something I was going to try out was using more transparent textures for solid ramps like that, to compensate for the darker appearance. Actually I think I did briefly try it & the results weren't what I wanted, but I'll revisit it.

[jimmyfingers]

This is a HUGE find! I just applied some basic changes to my BSD MOD for the alpha lighting and the frame rate increased by about 30-40%. Really useful for improving performance where we can now and getting more tables even smoother (or simply playable for some people).

Thanks for all your work on this

[koadic]

This is a HUGE find! I just applied some basic changes to my BSD MOD for the alpha lighting and the frame rate increased by about 30-40%. Really useful for improving performance where we can now and getting more tables even smoother (or simply playable for some people).

Thanks for all your work on this

My pleasure and the greatest thing about this is there is very little to change to achieve the results, just some basic scripting replacements..

Next thing I am attempting to work on is a companion to your flipper mod, to allow for tap passes from when the flipper is at a rest position, instead of needing a flipper in a downward swing to get a softer touch, I'm just trying to iron out a few wrinkles before grabbing a larger base of testers.

[jimmyfingers]

Hey Koadic, would you be able to post the script for this enhancement on the Alpha Ramp plunger but also with the "either or" approach to the PBWplunger or a key being pressed. You had one earlier that drew correctly regardless of whether or not the analog plunger was used vs. the key being pressed. Hope this rings a bell as I'd like to use this script verbatim (I have a motion sensor but not a plunger which throws it off as it detects the "PBW" even though I don't have a plunger and use a key assignment).

I imagine I could analyze the two and work it out so no big deal if you can't just thought it might save some time for others in the same boat or who want the same functionality but might not be as into script modification / splicing.

[thewool]

Great work chaps!

I've tried, but I won't pretend to understand the coding aspects... but really appreciate the + effect it will have on how tables run.

Cheers! :drinks

[unclewilly]

hey jimmy just open the script and do edit replace
search and replace all .widthtop and .widthbottom with .alpha
then change the numbers 0 stays as 0 and any widths say 200 change those to 1

you can use the pinwizard code from bbb.
i just did this for freddy and it makes a world of difference

[koadic]

Hey Koadic, would you be able to post the script for this enhancement on the Alpha Ramp plunger but also with the "either or" approach to the PBWplunger or a key being pressed. You had one earlier that drew correctly regardless of whether or not the analog plunger was used vs. the key being pressed. Hope this rings a bell as I'd like to use this script verbatim (I have a motion sensor but not a plunger which throws it off as it detects the "PBW" even though I don't have a plunger and use a key assignment).

I imagine I could analyze the two and work it out so no big deal if you can't just thought it might save some time for others in the same boat or who want the same functionality but might not be as into script modification / splicing.

You can use the script verbatim, as this is what I included above... You enable the Plunger timer by default with an interval of 40, then use the KeyDown and KeyUp parts for the plungerkey included above, that way whenever the plunger button is pushed, the timer is disabled, then reenabled when it is released. That way the animation works correctly regardless.

[jimmyfingers]

hey jimmy just open the script and do edit replace
search and replace all .widthtop and .widthbottom with .alpha
then change the numbers 0 stays as 0 and any widths say 200 change those to 1

you can use the pinwizard code from bbb.
i just did this for freddy and it makes a world of difference

Thanks UW, but I got that part and actually have been up most of the night editing / enjoying some tables that I hadn't played as much because of stutter. It's real easy to replace and I've been re-writing some alpha ramp routines on some tables as they had some nuances / uniqueness to get the full performance boost (LW3 now runs super smooth and I more than doubled the FPS but it had some extra quirks to really get smooth - had to change how the refresh was happening as well).

What I was looking for was this new plunger code but also with the addition of the logic that had something like when the plunger key is pressed, the PBW or PBW plunger animation portion is disabled so that one can use either the key or the analog plunger and the animation still works.

In general and so far while editing / assessing some tables for this performance improvement, I noticed that if the ramps are set smaller / narrower in the editor than what they'll be when they are "expanded" as part ot the alpha ramp routine, then those will need to be fixed and set to the width in the editor that they have as parameters for the routine calls or I've been writing a routine to initialize the size (widthtop / widthbottom) that runs in the script so that I don't have to go around all the editor and find the ramps and for which I can copy and paste the current alpha ramp routine calls with the sizes in them, re-format / replace, and place back in as init calls at the top of the table.

This find is massive for performance improvement and the magnitude for which it can help, thanks again Koadic!