Well today I have done a lot of tests and nothing these:
1º-I have tested ckecking the option Tilt Sensibility to 1000 and nothing does the same only it moves the ball but not the table when I hit the cabinet.
2º-After I have tested with other KL25Z board because I bought two and nothing does the same both.
3º-Instead If I press for example the right buttom of nudge it moves the table a bit perfectly and gives tilt after of two o three hits tilt but using KL25Z board never gives tilt.
I don,t understand because worked a time fine and now doesn,t work.
Tilting and nudging in VP is rather complex. I'm not sure there's a good tutorial anywhere on how all of the different pieces work. I'll try to explain some of the elements, to help you understand the nuances of the effects you're seeing.
First, two definitions, because people use these terms inconsistently. Nudging is an acceleration input that affects the motion of the ball. Tilting is triggering the game's tilt switch.
On a real pinball, tilting occurs when you nudge the machine hard enough to make the tilt bob pendulum make electrical contact with the ring surrounding it. The game's software or hardware detects the electrical contact and triggers the TILT condition (which may result in a tilt penalty or just a warning).
On VP, things aren't nearly so simple. The goal with VP is to act like the real thing, but the actual mechanisms used to accomplish that are very different from the real thing.
For historical reasons, VP has two completely separate mechanisms for handling nudging and tilting: keyboard and accelerometer. This creates a lot of confusion because it's reasonable to think they'd be somehow related, but they're really not. I can see you're trying to compare their behavior and you're finding it weird that they're so inconsistent. Well, it's actually normal that they behave so differently, because they're really separate systems without much common ground. Let's look at how these two systems work so you can see what I mean.
Method #1 is keyboard input. Keyboard input is handled via four keys: center nudge, left nudge, right nudge, a "bang back". These are usually assigned to SPACE, Z, /, and T respectively.
What does VP do with these keys? Essentially nothing, as it turns out. All it does is read them from the keyboard and send KeyDown events to the table script. VP doesn't change the ball velocity, send a tilt switch to the ROM, or do anything else at all in response to these keys. All it does is send KeyDown events to the script. This means that the handling of these keys is entirely up to the table script, and so varies from table to table. Most tables use the same core scripts that handle these KeyDown events the same way, which is to first call back into VP to accelerate the ball(s) in the appropriate direction, and to then do some time-based arithmetic to see if there have been too many nudges in too short a time, in which case the script simulates triggering the tilt switch.
So the net effect here is that pressing nudge KEYS leads to accelerations on the ball and triggering the TILT condition (or not) according to logic embedded in the table script.
Method #2 is accelerometer nudging. The accelerometer is handled almost the opposite way from keyboard nudging, in that VP does most of the handling itself without getting the scripts involved. VP reads the amount of acceleration from the accelerometer and directly applies it to the motion of the ball(s) in real time. Scripts aren't notified of this at all; there are no events for it.
VP also feeds the accelerations into its own internal simulated tilt pendulum. Scripts aren't involved in the simulated pendulum either, until it actually triggers a tilt. That's what the "TILT SENSITIVITY" settings in the keyboard prefs dialog are all about. The sensitivity number basically determines how far the simulated pendulum can swing before it triggers a tilt event. Higher numbers = more sensitive = shorter pendulum excursions trigger tilt. When a pendulum tilt event occurs, it's finally time to get the table scripts involved. At this point, VP fires a KeyDown event for the "center nudge" key (the one that's usually assigned to SPACE).
Now you're back into those same KeyDown table scripts that were designed to handle keyboard nudging. All table scripts handle the virtual pendulum nudge key event exactly the same way they handle an actual keyboard SPACE key press, because they literally can't tell the difference between the two. Tables using the default core scripts will thus do what I described above: they'll accelerate the ball, do some timer arithmetic to see if fake nudges have been coming too quickly, and trigger a tilt switch closure if so.
The important thing in this case to realize is that the table scripts aren't involved in accelerometer nudging, but they do take over for accelerometer tilting. VP can't actually trigger a tilt per se; it can only fire the "center nudge" key event, and it's up to the table script to finish the job and generate the actual tilt switch signal.
Given that you can't get tables to tilt with the accelerometer, and assuming that nudging is working correctly for you (I think you said earlier that was the case), the problem has to be one of two things:
(1) the VP virtual tilt bob is never detecting a tilt and thus never firing a "center nudge" key event to the table script
(2) table scripts aren't triggering a TILT condition in response to the "center nudge" key
Here's something you can try to determine which it is.
Fire up the VP editor. Create a new table. Select menu Edit -> Script. Search for the part of the script that looks like this:
If keycode = CenterTiltKey Then
Nudge 0, 2
End If
Replace the line that says Nudge 0,2 with this:
MsgBox "Center nudge key"
Run the table. Nudge excessively. If you can eventually get the message box window to pop up, the problem is (2) above. If not, the problem is (1) above.
Edited by mjr, 06 December 2016 - 09:52 PM.
Top
are all trademarks of VPFORUMS.