5 replies to this topic

[allknowing2012]

Having a problem with a set of drop down targets. When I hit the last target, they are reset by the rom *but* the ball is still in the target spot so it drops down again. Of course you shouldnt have it down again but worse thing is it is not registered as down - so you can not hit the bank down again. Is this a coding issue or something that should be handled by the primitive target scripts?

I was thinking perhaps to put in a timer for the _hit of the target so it gives the ball a chance to get out of the way (vertical bank of targets so the ball is there for a good split second). 

Perhaps the rom switch pulse is too soon/too quick? In reality the pulse shouldnt happen until the target has dropped out of the way. I wonder if it is being replicated and pulsed as soon as the target is hit?

Thoughts?

Anyone else face this?

Edited by allknowing2012, 01 January 2016 - 02:10 AM.

[kiwi]

I have the same problem with VP9, with a timer that delays the fall of the target I have almost solved the problem, but in multiball mode is inevitable that sometimes two targets are hit simultaneously.

 
Yesterday I tried the VPX targets and noticed the same as you said above, then VPX crashed and I have not tried again.
It's interesting to me to know if there is an alternative code, Instead of the code used commonly, that solves this problem.

 

Max

[allknowing2012]

This is turning out to be a big pain .. what happens is the targets are getting the reset from the rom, but the drop targets are still under the control of the timer going down. So it stays down.

It also appears that a dt.hit command makes the target quickly go up and then back down .. so the primitive actions are not needed??

What  I did was put a msgbox on the _hit event to show the target was up during the hit event, then i added a target timer with another msgbox command to show where things were at the timer expiration and then fired the hit command. So the target is up. msgbox, target falls, msgbox *then* it goes up & down again with the dt.hit event - real quickly.

It will stay down if the others are being sent a  reset during a full target reset.

[gtxjoe]

Try adding a slight delay to the drop target bank reset. I.e.When the drop target reset solenoid fires start A 500 Msec timer. In the timer routine reset the target bank

[allknowing2012]

Thanks .. my initial attempts were to add timers to delay the hit until the target dropped. I have tried your suggestion but it seems to have messed up something.

It wont kick out the ball after a drain - almost like the rom doesnt think the targets are reset.

[update] Commenting out the msgbox seems to have corrected the issue - perhaps that pause was messing up the rom timings.

 

I used code from google..

SolCallback(15)= "SolRaiseDrop"

Sub SolRaiseDrop(enabled)
   If enabled Then
      'msgbox "Reset Targets"
      TargetResetT.interval=500
      TargetResetT.enabled=True
   End if
End Sub


Sub TargetResetT_Timer()
  TargetResetT.enabled=False
  dtR.DropSol_On
End Sub

Edited by allknowing2012, 03 January 2016 - 12:47 AM.

[allknowing2012]

Case closed .. creating the timer as above for the reset has fixed (or worked around) the issue of the targets staying down after a quick reset.

Thanks for the suggestion gtxjoe.