Button code is still f*cked up...
 

Ok, here's the deal; there are 2 things I noticed:
1) Yesterday I played around with the waypoints in cs_iraq to see if I could fix them up - especially at the doors to the hostage rooms. Now as Pierre-Marie had told, I made the connections through the doors veeeery long (this time far beyond the highest apmd setting, approx. 300-350 units !!) and tried it out, and it didn't work. I tried two different WP layouts, and both failed.
2) On cs_siege2k (nice remake, 100% bot-compatible this time, WP available from me on request :D (but please in a new thread in WP forum, ok?)), I saw bots getting stuck exactly on the threshold of an open door and play that annoying "push the imaginary button" game again - until round end. The problem is that there are no buttons, and the doors open fine. I found out that the connections through these doors also had to be veeeeery long in order to work at all, although there's no button there.

Ok, so it seems that the suggested solution to make very long connections works as long as there are no buttons. Thus, problem 2) is avoidable and doesn't need to be fixed in the code.
If there are buttons, however, it fails miserably (see screenshots in ZIP). The bots try to reach the button on the other side of the wall and get stuck forever. Check the button flags on both screenies - the first shows the way I think this ought to be waypointed, the second one is an experiment, which would actually have worked, hadn't it been for the buggy button code.

If I understood you coders correctly, this is what bots do: If a path through a door is blocked by an entity like func_door or whatever the mapper used, the bot will check for a button nearby and push it before continuing. As soon as the obstacle is removed (i.e. the door is opened), the bots will leave the button alone because no obstacle is detected. If the button needs to be pushed every single time (auto-closing doors like in cs_iraq), a WP with button flag can be inserted near the button, preferably in a way that enforces that bots pass the button prior to attempting to go through the door.
BUT: In the "search for button" routine, do bots check if access to a button is blocked by a solid brush or anything else that blocks their path? Because I think that's the problem... they "see" a button on the other side of a wall and try to push it - which doesn't work in most cases.
Besides, they stray from waypointed navigation when going to buttons - thus, in cs_arabstreets, when I close the door, bots will bump into it, begin to search for a button, turn in the direction of the button and push into thin air, getting stuck forever again. I'd rather have them follow waypoint connections to get near that button. That would force waypointers to set nodes right next to buttons, but it would ensure that bots choose an appropriate approach angle to reach the button instead of walking towards it in a straight line, disregarding all obstacles (like protruding door frames) and getting stuck.

Re: Button code is still f*cked up...
 

I wanted report this problem with buttons, too. Maybe I didn't want so sharp words title...;)
I tryied about 5 times different configurations of WP near this garage's door (cs_arabstreets) to force bots to open it - still without success (but I was thinking I'm too bad waypointer). But if T Wrecks can't do this the same like me - something must be wrong in this button code. I tryied with and without "use_button" flag , I looked to the de_prodigy , but there is different situation - the door is not so big, so button near by doesn't need "use_button" flag. But what about cs_arabstreet - this garage door need or not this flag? How to force bots to open it?
BTW - now You have good ocassion to see if this garage door kills bots , too (during opening, exactly the same like these sliding doors at first floor).;)
Maybe some coder can say us what exactly happen in this situation? Why only bots are killed by opening doors and human-players not? Sorry for off-topic but there was some thread about this at MAPPING forum, but no one coder wanted to say something...:(

Re: Button code is still f*cked up...
 

well the door button code does this...
it checks if the door is being targeted by a button.
if so it'll goto the button and push it then go through the door..
but it also makes sure that the button isn't through a wall..

Re: Button code is still f*cked up...
 

Then how come I saw bots getting stuck and trying to push a button in those double sliding doors in cs_siege2k? Those doors don't have buttons and open fine without.
I got around this problem by placing the WPs in front of the door and behind of it very far from each other - if the code behaved as you say, this shouldn't stop bots from looking for a button! But it does.
Well, look at the screenshots... these bots are DEFINITELY targeting the door button on the other side of the wall, not the one that's on their side. This even happens if the WP with the button flag is WAY nearer to the correct button than to the other one (see first pic).

Re: Button code is still f*cked up...
 

oh you attached screenshots... :|

well I dunno whats wrong then..

Re: Button code is still f*cked up...
 

@sPlOrYgOn - here You have a demo (CS1.5) saved by me in no-clip mode and pwf file - if You want cs_iraq map (2 702 716 bytes created 1999.12.13 23:59), I can send You by e'mail with some needed wads files. When You 'll see this at Your computer, maybe this can help.

Re: Button code is still f*cked up...
 

this might help understand something about it:
some doors are triggered by a trigger_multiple.....meaning you walk through the invisible trigger........and the door opens.......this is done to make the door start opening before you actually touch it.....i have done this is some of my maps.....and since the door has a name...and is targeted.....the bot is stuck on the triggermultiple thinking it has to "use"...when it actually doesnt...

there are many ways to make doors work and not all of them can be flawlessly covered in one bit of button code :)

Re: Button code is still f*cked up...
 

True. However, those doors in cs_iraq don't open before you have reached them. It's the classical case there: Go there, push button, wait a sec, walk through, door closes after a short time. No invisible triggers here (wish there were!) :(

Re: Button code is still f*cked up...
 

what if the button is targeting a multi trigger and the multi trigger is targeting the door..
then the bot would be trying to push the multi trigger

Re: Button code is still f*cked up...
 

yes, this is also done in de_prodigy afaik.