118 replies to this topic

[koadic]

Seems to me that being able to adjust the Tilt Sensitivity would be a great option it sure gives more flexibility using the accelerometer.

If possible it would be great also to be able to use a separate tilt bob to get the table to trigger tilt warnings (more like in real life) however right now there is no key to map the tilt bob to.
I thought that was what the "mechanical tilt" key was supposed to do but I never got it to work.
So adding a key that would tell the table to send a tilt warning that we could wire to the tilt bob would also somehow be a solution to the problem.

Well, for that, all you have to do is assign it to a button identified in the VPMKeys file, such as "keyGameSpecific1 = 16 '(Q)" (or maybe add another key definition for tilt??) and add that key to the KeyDown and KeyUp Subs to trigger the tilt switch, and whenever the tiltbob triggers the switch, it will trigger a warning/tilt. Then you can turn the sensitivity down to 0 and rely only on the tiltbob.

[Shooby Doo]

This worked for me one day, but now I get really spotty results with nudging. Sometimes I start a table and the nudge doesn't work at all. Then I restart the table, not changing any settings, and it works but it's WAY too sensitive. No matter where I put the gain, it doesn't change anything.

[koadic]

This worked for me one day, but now I get really spotty results with nudging. Sometimes I start a table and the nudge doesn't work at all. Then I restart the table, not changing any settings, and it works but it's WAY too sensitive. No matter where I put the gain, it doesn't change anything.

I don't claim this is you're issue, only stating for clarity as it is easy to overlook in the first post... when adjusting the gain, if you have the table open when you adjust the gain values, the changes aren't noticeable until you either play the table, quit the table, and play the table again, or close the table and reopen it. To be 100% sure they take effect, you can always restart Visual Pinball.

But again, if they worked, then didn't, then too well, all without changing anything inbetween, then you probably have deeper issues.

[CPSNine]

Seems to me that being able to adjust the Tilt Sensitivity would be a great option it sure gives more flexibility using the accelerometer.

If possible it would be great also to be able to use a separate tilt bob to get the table to trigger tilt warnings (more like in real life) however right now there is no key to map the tilt bob to.
I thought that was what the "mechanical tilt" key was supposed to do but I never got it to work.
So adding a key that would tell the table to send a tilt warning that we could wire to the tilt bob would also somehow be a solution to the problem.

Well, for that, all you have to do is assign it to a button identified in the VPMKeys file, such as "keyGameSpecific1 = 16 '(Q)" (or maybe add another key definition for tilt??) and add that key to the KeyDown and KeyUp Subs to trigger the tilt switch, and whenever the tiltbob triggers the switch, it will trigger a warning/tilt. Then you can turn the sensitivity down to 0 and rely only on the tiltbob.

Thank you for the advice, and it seems pretty straight forward but unfortunately I think it is beyond my skills/knowledge (sorry)
From what I understand it is a code snipet I would like to insert in each table script to assign the (Q) key to send the tilt warning.
However I have no idea on how to do that.

[Shooby Doo]

This worked for me one day, but now I get really spotty results with nudging. Sometimes I start a table and the nudge doesn't work at all. Then I restart the table, not changing any settings, and it works but it's WAY too sensitive. No matter where I put the gain, it doesn't change anything.

I don't claim this is you're issue, only stating for clarity as it is easy to overlook in the first post... when adjusting the gain, if you have the table open when you adjust the gain values, the changes aren't noticeable until you either play the table, quit the table, and play the table again, or close the table and reopen it. To be 100% sure they take effect, you can always restart Visual Pinball.

But again, if they worked, then didn't, then too well, all without changing anything inbetween, then you probably have deeper issues.

You are correct sir! My mistake.

[koadic]

Thank you for the advice, and it seems pretty straight forward but unfortunately I think it is beyond my skills/knowledge (sorry)
From what I understand it is a code snipet I would like to insert in each table script to assign the (Q) key to send the tilt warning.
However I have no idea on how to do that.

It's not really all that hard, here is an example from 'TOM_vp91x_2.1.1FS' (Theater of Magic, added code in red) ...

CODE

'here you can grab the number for the tilt switch, which in this case is 14 (no need to add this line)

vpmNudge.TiltSwitch = 14
vpmNudge.Sensitivity = 1
vpmNudge.TiltObj = Array(Bumper1, Bumper2, Bumper3, LeftSlingshot, RightSlingshot)

....

Sub table1_KeyDown(ByVal Keycode)
If Keycode = KeyFront Then Controller.Switch(23) = 1
If Keycode = keyGameSpecific1 Then Controller.Switch(14) = 1
If keycode = PlungerKey Then PlungerIM.Pullback:Pcount = 0:PTime.Enabled = 1
If keycode = LeftTiltKey Then LeftNudge 80, 1.2, 20:PlaySound "nudge_left"
If keycode = RightTiltKey Then RightNudge 280, 1.2, 20:PlaySound "nudge_right"
If keycode = CenterTiltKey Then CenterNudge 0, 1.6, 25:PlaySound "nudge_forward"
'If keycode = KeyRules Then Rules
If vpmKeyDown(keycode) Then Exit Sub
End Sub

Sub table1_KeyUp(ByVal Keycode)
If Keycode = KeyFront Then Controller.Switch(23) = 0
If Keycode = keyGameSpecific1 Then Controller.Switch(14) = 0
If keycode = PlungerKey Then PlungerIM.Fire:PTime.Enabled = 0:Pcount = 0:PTime2.Enabled = 1
If vpmKeyUp(keycode) Then Exit Sub
End Sub

...

[koadic]

BUMP to update for build 6 - LINK

[CPSNine]

Thank you for the advice, and it seems pretty straight forward but unfortunately I think it is beyond my skills/knowledge (sorry)
From what I understand it is a code snipet I would like to insert in each table script to assign the (Q) key to send the tilt warning.
However I have no idea on how to do that.

It's not really all that hard, here is an example from 'TOM_vp91x_2.1.1FS' (Theater of Magic, added code in red) ...

CODE

'here you can grab the number for the tilt switch, which in this case is 14 (no need to add this line)

vpmNudge.TiltSwitch = 14
vpmNudge.Sensitivity = 1
vpmNudge.TiltObj = Array(Bumper1, Bumper2, Bumper3, LeftSlingshot, RightSlingshot)

....

Sub table1_KeyDown(ByVal Keycode)
If Keycode = KeyFront Then Controller.Switch(23) = 1
If Keycode = keyGameSpecific1 Then Controller.Switch(14) = 1
If keycode = PlungerKey Then PlungerIM.Pullback:Pcount = 0:PTime.Enabled = 1
If keycode = LeftTiltKey Then LeftNudge 80, 1.2, 20:PlaySound "nudge_left"
If keycode = RightTiltKey Then RightNudge 280, 1.2, 20:PlaySound "nudge_right"
If keycode = CenterTiltKey Then CenterNudge 0, 1.6, 25:PlaySound "nudge_forward"
'If keycode = KeyRules Then Rules
If vpmKeyDown(keycode) Then Exit Sub
End Sub

Sub table1_KeyUp(ByVal Keycode)
If Keycode = KeyFront Then Controller.Switch(23) = 0
If Keycode = keyGameSpecific1 Then Controller.Switch(14) = 0
If keycode = PlungerKey Then PlungerIM.Fire:PTime.Enabled = 0:Pcount = 0:PTime2.Enabled = 1
If vpmKeyUp(keycode) Then Exit Sub
End Sub

...

Depending on the table, it may take more to find which key is the one used for tilt, but the other stuff still applies. Otherwise, so long as your tiltbob is mapped to the Q key in this instance, it will trigger a tilt everytime the circuit closes.

[CPSNine]

Tried Build 6 but the tilt sensitivity does not seem to do anything.
Tested with default 400 then 800 and 1000 but haven't been able to get tilt warning.
Does the value works as you described in this post for the registry value - 0 never tilted / 1000 always tilted?

[koadic]

Tried Build 6 but the tilt sensitivity does not seem to do anything.
Tested with default 400 then 800 and 1000 but haven't been able to get tilt warning.
Does the value works as you described in this post for the registry value - 0 never tilted / 1000 always tilted?

If you haven't, you need to check the box to the left of where it says Tilt Sensitivity to enable it, as I left it disabled by default.

[CPSNine]

Tried Build 6 but the tilt sensitivity does not seem to do anything.
Tested with default 400 then 800 and 1000 but haven't been able to get tilt warning.
Does the value works as you described in this post for the registry value - 0 never tilted / 1000 always tilted?

If you haven't, you need to check the box to the left of where it says Tilt Sensitivity to enable it, as I left it disabled by default.

Yes I did check the box when I did my test.
I guess I'll wait for feedback from other users to see if it is an issue on my side.

[koadic]

Another issue is that it behaves like the gain values, and doesn't apply the first time you start the table (if opened already), you may need to restart VP after setting the value and hitting OK to get it to register properly (or at least close and reopen the table).

Otherwise, I know it works as I intended on my copy, if I set it to 900 or so, I can barely move the joystick before it starts tilting. Keep in mind though, this only effects how VP handles tilting (you will hear a solenoid type sound when it does), so if the table isn't set up properly to handle the tilt event, it may not actually tilt the table.

So, because of this, I'd like to ask what table you are testing on, to make sure it works like it does with the other tables I have tested it on.

Edited by koadic, 22 April 2012 - 09:08 PM.

[CPSNine]

Another issue is that it behaves like the gain values, and doesn't apply the first time you start the table (if opened already), you may need to restart VP after setting the value and hitting OK to get it to register properly (or at least close and reopen the table).

Otherwise, I know it works as I intended on my copy, if I set it to 900 or so, I can barely move the joystick before it starts tilting. Keep in mind though, this only effects how VP handles tilting (you will hear a solenoid type sound when it does), so if the table isn't set up properly to handle the tilt event, it may not actually tilt the table.

So, because of this, I'd like to ask what table you are testing on, to make sure it works like it does with the other tables I have tested it on.

Koadik to the rescue once again.
It was my mistake indeed. I was changing settings and relaunching the table without closing it.
Restarted VP and then it worked like a charm.
thanks again so much

Update:
In all my testing to try to find out why the table was not sending the tilt warnings, I remember that I re-downloaded the original core.vbs because I was using Blur's modified version.
And from what I can see on my machine the table will not Tilt with analog nudging with this version of the core.vbs.
So people having issues make sure you have the official version of core.vbs

Edited by CPSNine, 25 April 2012 - 12:53 AM.

[Knome]

The plunger works nice, with the tables that support it well. There is something wrong with the nudging though. With keys or a joystick the ball does not snap back like it should but instead acts with the control as a ball in hand. Could you force a return to center reading a few milliseconds after a nudge even if the stick is not actually back yet?

[blur]

Another issue is that it behaves like the gain values, and doesn't apply the first time you start the table (if opened already), you may need to restart VP after setting the value and hitting OK to get it to register properly (or at least close and reopen the table).

Otherwise, I know it works as I intended on my copy, if I set it to 900 or so, I can barely move the joystick before it starts tilting. Keep in mind though, this only effects how VP handles tilting (you will hear a solenoid type sound when it does), so if the table isn't set up properly to handle the tilt event, it may not actually tilt the table.

So, because of this, I'd like to ask what table you are testing on, to make sure it works like it does with the other tables I have tested it on.

Koadik to the rescue once again.
It was my mistake indeed. I was changing settings and relaunching the table without closing it.
Restarted VP and then it worked like a charm.
thanks again so much

Update:
In all my testing to try to find out why the table was not sending the tilt warnings, I remember that I re-downloaded the original core.vbs because I was using Blur's modified version.
And from what I can see on my machine the table will not Tilt with analog nudging with this version of the core.vbs.
So people having issues make sure you have the official version of core.vbs

just tested with my core.vbs - it (tilt ) works fine - don't know what you have tested

The plunger works nice, with the tables that support it well. There is something wrong with the nudging though. With keys or a joystick the ball does not snap back like it should but instead acts with the control as a ball in hand. Could you force a return to center reading a few milliseconds after a nudge even if the stick is not actually back yet?

that doesn't make sense - stick is manual accelerometer - if you put some weight on it it will measure acceleration of your cab just like accelerometers measure it

and if you attach it to your cab - stick will get back very quickly - the only way it would not get back is if your cab is accelerating constantly with big speed - but then your cab will probably end up in space very soon

so for normal situations accelerometer is never on the end point for long time, instead it hangs back and forth and so the ball will also go back and forth (giving you counter force immediately)
if you push your stick manually all the way to the end and keep it there you are cheating cause you will never be able to do that with gamepad attached to cab

Edited by blur, 25 April 2012 - 06:21 AM.

[Knome]

I did not know that joysticks were used to measure nudge on a cabinet, but I knew that if they were this problem would not occur there. I was just talking about using a joystick for the desktop computer. However, just using this for the plunger is a big plus. The keys are the same way though, and I doubt that cabinet users use a keyboard. I noticed a release of a alternative .vbs file that promises to fix the issue, so the issue seems to be already addressed, if not solved.

[blur]

nope, that alternate vbs file is my core.vbs 3.33 and it gives you counter force only for digital nudge (with buttons), not for analog nudge

[CPSNine]

just tested with my core.vbs - it (tilt ) works fine - don't know what you have tested

Yep sorry about that.
Downloaded a fresh copy of your core.vbs 3.33 (from the link in your sig) and it does tilt.
Don't know what version I had in my machine when it was not tilting.
Sorry again sure did not want to discredit your amazing work. (updated my original post).

Koadic, could it be possible that some tables would be more sensitive to tilting than other? (due to script difference may be)
Harlem Globe trotters on Tour seems more sensitive than diner for exemple.

Edited by CPSNine, 25 April 2012 - 12:54 AM.

[blur]

yup there is a tilt sensitivity in every table - it goes from 0 to 10, 5 is default (middle), 10 is very sensitive table (tilts easy)

Edited by blur, 25 April 2012 - 09:51 AM.

[yukiko1701d]

Nice work!!! @Koadic

Reputation of your program the best in Japan.

Banzai!!!@Your project.