see in
FP when making a ramp let's start with one with a vuk at its end.
you click on that object in the editor line it up on the pf and let it go.
then you grab the vuk wireform end piece, line it up with the ramp you just dropped down and click to set it.
that's it you are done on to the next ramp.
In Vp you must shape that ramp so it matches the playfield and its intended upper level,
bending it as you go (by adding and adjusting the location of more points along its length)
if it must go around a corner or two. okay it's set, now for the vuk.
oh there is no vuk wireform so now you must find the half ring graphics and start to put them
(as decals on walls) under the actual ramp so it looks like the rings are holding up the ramp)
this is the only way to really build a vuk with the wires in front and behind the ball showing up properly
as the ball goes 'up' the ramp from the vuk. got all that? In
FP all those rings are included in the rendered image
now that is just the vuk how about the rest of that ugly ramp.
okay now we must import an other image for the ramp to show up properly too...
see how much more involved vp is just to make our pins look half as pretty as the ones in
FP?
so we take far longer to build a pin using vp than most of the ones made in fp with half the prettiness of them too!
but to have already built play field objects in vp would really be the icing on the cake,
only problem with using them is it does increase the size of the program.
Look at both
VP and
FP VP is around 1 meg,
FP sits at 13 megs I think
not a huge difference but it does matter when pushing your graphics card to the limit for
FP and all its pre-built toys