func_button can't be used multiple times. -solved-
Quote from Brainstone on February 23, 2012, 10:02 amThe outputs of my func_button:
OnPressed-->prop_dynamic-->SetAnimation-->start delay: 0
OnPressed--!self-->lock delay: 0
OnPressed-->prop_dynamic-->SetAnimation-->idle delay: 10
OnPressed--!self-->unlock delay: 10However, the prop_dynamic doesn't animate when I press the button the second time after 10 seconds.
Anybody knows why?
The outputs of my func_button:
OnPressed-->prop_dynamic-->SetAnimation-->start delay: 0
OnPressed--!self-->lock delay: 0
OnPressed-->prop_dynamic-->SetAnimation-->idle delay: 10
OnPressed--!self-->unlock delay: 10
However, the prop_dynamic doesn't animate when I press the button the second time after 10 seconds.
Anybody knows why?
Quote from josepezdj on February 23, 2012, 10:54 amBrainstone, this is what VDC specifically says about the func_button:
(https://developer.valvesoftware.com/wiki/Func_button)"Bug: Do not lock while pressed; it will not return when unlocked."
Could it simply be a bug?
What exactly are you setting this button for exactly? Anyway, I guess what you want is to prevent the interruption of the prop_dynamic animation, right? Well, 3 things:
1. Maybe the fact that the button itself is the one that fires its own outputs is causing a conflict... you could try introducing a couple of logic_relays mediating there, and use any settings as the following ones for example:
Func_button (set "Delay before Reset" to 10 secs):
OnPressed > Relay_1 > Trigger
OnOut > Relay_2 > TriggerRelay_1:
OnTrigger > Relay_2 > CancelPending / delay 0.00
OnTrigger > [prop_dynamic_name] > SetAnimation > [whatever] / delay 0.20Relay_2:
OnTrigger > Relay_1 > CancelPending / delay 0.00
OnTrigger > [prop_dynamic_name] > SetAnimation > [idle?] / delay 0.202. Also you can set the delay before reset to -1 (so it stays), and use an external logic_timer for the reset instead. Then, stop the logic_timer when you want the button to be unlock again.
3. Maybe you are using a bad output for the prop_dynamic: "Start"?? isn't it "Open" or "Close" or "whatever" instead?
Brainstone, this is what VDC specifically says about the func_button:
(https://developer.valvesoftware.com/wiki/Func_button)
"Bug: Do not lock while pressed; it will not return when unlocked."
Could it simply be a bug?
What exactly are you setting this button for exactly? Anyway, I guess what you want is to prevent the interruption of the prop_dynamic animation, right? Well, 3 things:
1. Maybe the fact that the button itself is the one that fires its own outputs is causing a conflict... you could try introducing a couple of logic_relays mediating there, and use any settings as the following ones for example:
Func_button (set "Delay before Reset" to 10 secs):
OnPressed > Relay_1 > Trigger
OnOut > Relay_2 > Trigger
Relay_1:
OnTrigger > Relay_2 > CancelPending / delay 0.00
OnTrigger > [prop_dynamic_name] > SetAnimation > [whatever] / delay 0.20
Relay_2:
OnTrigger > Relay_1 > CancelPending / delay 0.00
OnTrigger > [prop_dynamic_name] > SetAnimation > [idle?] / delay 0.20
2. Also you can set the delay before reset to -1 (so it stays), and use an external logic_timer for the reset instead. Then, stop the logic_timer when you want the button to be unlock again.
3. Maybe you are using a bad output for the prop_dynamic: "Start"?? isn't it "Open" or "Close" or "whatever" instead?
Quote from greykarel on February 23, 2012, 10:59 amVCD/ func_button article/ third line :
Bug: Do not lock while pressed; it will not return when unlocked.
EDIT: josepezdj has better reaction then me
VCD/ func_button article/ third line :
Bug: Do not lock while pressed; it will not return when unlocked.
EDIT: josepezdj has better reaction then me 
Quote from Brainstone on February 23, 2012, 11:34 am
Sorry guys, I looked in the VDC, but read over the line.
Sorry guys, I looked in the VDC, but read over the line.











