Func_Button trouble Created 2 years ago2022-05-29 20:53:53 UTC by closed

Pretty simple, cannot interact with it when pressing E,

You check in Flags tab "Dont move". Read func_button . This happened also to me, but it solved when i added the Target because i forgoted to do that lol

It still doesnt work even when target and dont move is set

send the part of your map to me i can have a look

Check your other flags. If you have Touch Activates checked, then you have to walk into it, Quake 1 style. Otherwise, E should work.

Feel free to post a screenshot of your setup if you need help

https://drive.google.com/file/d/1Gf-ekUBl4--j9cnLYf99OKXDRIZO8GKB/view?usp=sharing that is the link to the jmf file, the button is a retinal scanner

I think i fixed it, i changed the texture from the trigger AA to solid blue , here's the link to the updated map

https://www.dropbox.com/s/wwjfx6geayx61e0/ithinkifixedit.jmf?dl=0

i think you cannot have a func_button with a trigger aa texture

i think it only works for trigger_once and trigger_multiple (you can use those as buttons) (triggers)

im here 8 months later and i found out it was because lip was blank instead of being set to 0, Pretty weird

Lip is always blank by default. That shouldn't break anything.

I don’t know... func_button that mysteriously stop working have been plaguing me ever since I started mapping. To this day I still do not know why. I’ll double check my lip and my textures...
I also once had a func_door_rotating that also stopped working, maybe it’s related...

I use button_target instead of func_button because for some reason func_button never works for me, i think its pretty bugged.

If func_button isn't firing its target when +USE'd you may check that its Touch Activates (256) flag isn't set and that the Health keyvalue is set to 0 (if greater than zero it needs to be "killed" before it fires its target). It shouldn't be necessary to tell anyone to check that the Target keyvalue actually points to a valid target, but just in case.

If it fires its target fine, but otherwise behaving in an unexpected way it'd be worth mentioning in what way it's behaving unexpectedly instead of saying "it's not working".

I use button_target instead of func_button because for some reason func_button never works for me, i think its pretty bugged.

Curious... I've literally never had issue with a func_button in over 20 years.

I use button_target instead of func_button because for some reason func_button never works for me, i think its pretty bugged.

I did too, problem is button_target fire when hit, which can makes things confusing for the player if the button activates because of say a nearby explosion.

Reviving this thread, as I still do not know how to make a func_button that is toggle-able. Does someone know?

The toggle flag should do that but depending on other keyvalues its behavior may change. Maybe create a small test map that illustrates what you're trying to do and what isn't working.

The toggle flag should do that but depending on other keyvalues its behavior may change. Maybe create a small test map that illustrates what you're trying to do and what isn't working.

My problem was that the button could only be used once with the Toggle flag checked. I tried fiddling with the lip and texture but it didn’t help.

I did find out the problem after more fiddling though: "Delay before reset" must be set to a value greater than or equal to 0. I was setting it to -1 as I was expecting it to work like other toggle entities like doors. I’ve added a note on the wiki about this behaviour, I don’t think I’m the only one who wasn’t aware of that.