Score points not always counted

[worldpeace-germany]

Hello,

mpf 0.80 is what I use. I have a problem that sometime points are not being awarded on hit.

I have a variable player

variable_player:
  s_pop_bumper_1_active: #yellow
    score: 100
  s_pop_bumper_2_active: #orange
    score: 200
  s_pop_bumper_3_active: #red
    score: 300
  s_slingshot_right_active: 
    score: 50
  s_slingshot_left_active: 
    score: 50

and sometimes - gut feeling 20-30% of the cases - when for example the slingshot is hit no points are scored - but the slingshot fires so the switch must have been active.

Anyone an idea or have seen the same issue?

Thanks!

[bernarma]

I don't have any ideas off the top of my head as I haven't dug into the correctness of scoring with my table but it may be helpful if you attach a log file with some commentary illustrating the problem.

[worldpeace-germany]

I could add a log file here, but the problem is in the case where no points are being counted there is nothing in the log. So the switch was even not considered as active from mpf. I really cannot say when it is considered as active and when not. I am use a Cobra board (in case that is somehow relevant). I press with the same force with a screwdriver against the rubber from the slingshot to simulate the situation, sometimes it counts the points, sometimes not. As if the auto-fire of the sling shot is somehow more sensitive than the part recognizing the switch close to fire the event that the switch is active.

I do have the impression (but not 100% certain) that this problem is only happening with auto-fire devices and not with normal switches. Maybe that give a hint.

I am happy to run any test and provide any log, I just don't any idea what to test or what other information to provide.

[atummons]

switches: - The Mission Pinball Frameworkmissionpinball.orgCheck that out, specifically the debounce setting. Might want to set it to quick. My hunch is that your ball is triggering the switch, but the slingshot is pushing the rubber off the switch too quick. It’s auto fire so hardware rules are activating the coil, not the computer. This means the switch is active, coil fires, and before the computer realizes it’s been 20ms and switch is still active (post switch hit), the switch is no longer active and that event never fires.That’s about the last code setting. Outside of that your switches are not adjusted correctly to trigger through the full motion and stay activated long enough with all forces to register as an event.Sent from my iPhoneOn Oct 4, 2024, at 9:19 AM, worldpeace-germany ***@***.***> wrote: I could add a log file here, but the problem is in the case where no points are being counted there is nothing in the log. So the switch was even not considered as active from mpf. I really cannot say when it is considered as active and when not. I am use a Cobra board (in case that is somehow relevant). I press with the same force with a screwdriver against the rubber from the slingshot to simulate the situation, sometimes it counts the points, sometimes not. As if the auto-fire of the sling shot is somehow more sensitive than the part recognizing the switch close to fire the event that the switch is active. I do have the impression (but not 100% certain) that this problem is only happening with auto-fire devices and not with normal switches. Maybe that give a hint. I am happy to run any test and provide any log, I just don't any idea what to test or what other information to provide. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[worldpeace-germany]

Thanks for the hint, but mpf has for autofire devices by default quick for the debounce setting. I nevertheless changed it, but no effect. I found for auto fire devices a delay parameter after setting that to 20ms it behaves as it should so problem solved.

Thanks everyone.