![]() |
![]() |
madmax2 |
![]()
Post
#1
|
RCBot Guru ![]() ![]() ![]() ![]() ![]() Group: Waypointers Posts: 957 Joined: 2-March 12 From: USA, WA state Member No.: 2,162 ![]() |
Possible Bugs or Observed Issues Topic
Thought I should start a topic to report observed issues or bugs, not strictly related to waypointing... This first item has been resolved with some hacky waypointing, but I don't think bots were seeing or able to reach the buttons in the wall. Distance was reported by debug to be 76, perhaps that is to far? I have not tried latest build yet, the wpt is nearly done, but needs a bit of polish though... 11-28 build I finally got something to work on the first closed locked door on murks. I've put hours overall to make it work. It was the same problem with the old rcbots at these doors. So I started out with the wpt config I had with the old bots, noclipped wpt into the button, but that wasn't working. I almost gave up when I just stumbled on a config that works, after moving wpts around and using combinations of normal, important, wait and staynear flags. But just like with the old bots its a forced configuration. I don't think Bots are seeing the func_button in the panel. Before I got this working they would just run up against the door pressing use a few times, then go over to the important wpt, but not press use, then go back to unopened door & repeat. If I added an openslater on other side of door they would go over to the button/panel, but would not press it, with any of a dozen different configurations... Well this is actually working well now, but as you can see the path is through the wall. In fact I used this config at the 2nd problem door and it works there too. I have also been able to remove the important flag & it still works. ![]() ![]() Config is wait---important or wait---normal, but path must go through wall from the wait wpt. It won't work from the important wpt. Never did try path from wait thru the door? That probably won't work unless it is close to the button? I did a rcbot.search while right up against the panel, and button distance is about 76, perhaps that is the reason? CODE ] as_command rcbot.search [RCBOT]player frame=232.552887 distance = 0 [RCBOT]func_button frame=0 distance = 76.595879 [RCBOT]func_door LOCKED!! [RCBOT]func_door frame=0 distance = 120.178703 [RCBOT]func_door LOCKED!! [RCBOT]func_door frame=0 distance = 134.249481 [RCBOT]func_illusionary frame=0 distance = 168.824387 [RCBOT]multi_manager frame=0 distance = 43.174778 [RCBOT]weapon_crowbar frame=0 distance = 8 [RCBOT]weapon_9mmhandgun frame=0 distance = 8 [RCBOT]weapon_medkit frame=0 distance = 8 So for a test I removed the path thru the wall to make them fail to press the button again. Also placed openslater on other side of door to make them go to the button. Same failure is present without openslater, just easier to find it in in console this way... Ran debug task on a bot, and get this... I think maybe they are not facing correct direction, looks like they attempt once to press it? CODE ] as_command rcbot.debug_bot [m00]wh3y [RCBOT]Finding player [m00]wh3y [RCBOT]UTIL_FindPlayer MadMax2 [RCBOT]UTIL_FindPlayer [m00]wh3y [RCBOT]iBestMatch == 9 [RCBOT]Debug '[m00]wh3y' (if bot) [RCBOT][DEBUG - TASK] COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] CFindPathTask COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] func_button <--- button task [RCBOT][DEBUG - TASK] CFindButtonTask COMPLETE <--- button task complete [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) <--- slew of these in console, removed some [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) [RCBOT][DEBUG - TASK] CUseButtonTask FAILED <--- button task failed [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED L 28/11/2018 - 12:56:22: "MadMax2<1><STEAM_ID_LAN><players>" stats: frags="0.00" deaths="0" health="100" [RCBOT][DEBUG - TASK] CFindPathTask FAILED L 28/11/2018 - 12:56:24: "[m00]wh3y<3><BOT><players>" stats: frags="0.00" deaths="0" health="100" [RCBOT][DEBUG - TASK] COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] CFindPathTask COMPLETE [RCBOT][DEBUG - TASK] m_pTasks.length() == 0 [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask FAILED [RCBOT][DEBUG - TASK] CFindPathTask COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] func_button <--- button task repeats [RCBOT][DEBUG - TASK] CFindButtonTask COMPLETE [RCBOT][DEBUG - TASK] m_pCurrentTask.m_bComplete [RCBOT][DEBUG - TASK] bot.setMove(m_pCharger.pev.origin) Other observe issues (have not tried latest build yet, maybe "bots avoid last failed path" fixed #2?) : #1 Saw bot stuck on turret, not sure how it happened & only saw once? Tried placing another wpt nearby, but he wouldn't use it or suicide, seem pretty stuck... ![]() #2 This happened after removing a staynear flag from other side of the door. He was constantly pressing use in the corner & wouldn't go to the button. So I put the staynear back on the same wpt, I had to restart the map, but haven't seen it happen again. ![]() Both of these may be rare occurance, but I haven't tried many different maps, so not sure? |
![]() ![]() |
madmax2 |
![]()
Post
#2
|
RCBot Guru ![]() ![]() ![]() ![]() ![]() Group: Waypointers Posts: 957 Joined: 2-March 12 From: USA, WA state Member No.: 2,162 ![]() |
Build tested: d3ec0c131d96959c890dced23e7a7939518ed08c (1-19-19)
Possible Bug with Barney waypoints? (Not scripted barney/important wpts) While working on the first Last map bots were initially moving fine. At some point bots began to sort of freeze and stop moving, and refused to press the button to activate the teleporter. After some confusion, I discovered it started when I put important givetypes on the 2 barney wpts that were already in the rcwa. After Removing the important givetypes bots began functioning & moving normal again. Bots would seem to move normally at the beginning of the map, but as they got closer to the teleport room, they would move in a stop & go fashion. Move a few wpts, then stop for a minute or longer, then move again. When they got to the teleporter button they refused to press it most of the time, and they were very reluctant to step into the teleporter. I'm not sure if they would step into the teleporter, because I had been teleporting bots to the other side and working on that area of the map. I ran debug on the bots while in this state, and speed would be 100% but they were not moving, also task was null. Sometimes both bots would not be moving, other times one bot would freeze but the other was moving. So a bot could freeze or start moving independently of another bot... The 2 barney wpts are fairly close in proximity, located at these security doors, one behind the other. This is the first and only map I've tried to use barney wpts... Oh, I also tested this on sc5.17 (XP), not sc5.18... 1st barney wpt ![]() 2nd barney wpt ![]() debug - teleport room ![]() debug - teleport button - bots refuse to press it! (or were extremely slow?) ![]() debug - teleport destination, near the barney wpts ![]() |
Cheeseh |
![]()
Post
#3
|
![]() Admin ![]() ![]() ![]() ![]() ![]() Group: Admin Posts: 3,066 Joined: 11-September 03 From: uk Member No.: 1 ![]() |
Hey madmax, will have a look later. Will let you know how the barney waypoints work just in case you might see what they are doing, don't know why their tasks are null though, maybe need to debug the task in the console to get a history of how they go into that state.
Btw Barney waypoints must also be important waypoints 1. Bot wants to go to an important waypoint which is also a barney waypoint 2. Bot has recently seen a barney/otis 2.1 bot goes to barney/otis 2.2 bot uses barney/otis 2.3 bot goes to barney waypoint 2.4 bot waits for barney to arrive 2.5 bot finishes task I was thinking maybe point 2.4 that the bots might be getting stuck. But their task should still be WaitForEntity or something. |
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 15th August 2024 - 02:21 AM |