Possible Bugs or Observed Issues Topic |
Possible Bugs or Observed Issues Topic |
madmax2 |
Nov 30 2018, 08:19 PM
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 |
Aug 9 2020, 09:50 PM
Post
#2
|
RCBot Guru Group: Waypointers Posts: 957 Joined: 2-March 12 From: USA, WA state Member No.: 2,162 |
Hi Poka,
Nice, how far into the HL campaign are you? Are you attempting the whole campaign? Hey Cheeseh, I was going to report bots not shooting some enemies on sc_activist (barneys, otis, & swat), but I see you fixed that, nice work . I think I tested that a month ago and the problem was there, it must of been a recent fix? ================================= But on sc_activist2, bots don't attack zord. They need to use grenades to hurt him, bullets do nothing... (they don't shoot at him, either) "Super-Mega Containment Zord" in red on hud CODE [RCBOT]25 : monster_gargantua frame=148.953857 distance = 80.819305 (x=-57.912491,y=-674.03125,z=-212.582733) visible=1,solid=3,angle.x = 0, angle.y = 180 active = 1 Also, The lift button wasn't working for either old metamod or new AS bots. The waypoints will need some rework there, because some are noclipped into the button, and I did a search and found the button wasn't exactly where I thought it was... Guess I should check the git rcwa's, not sure if there were some changes done? Lift button is centered in lift shaft on right wall about half way up, its one large button for both top & bottom. When lift is up frame=1 when down frame=0 CODE [RCBOT]282 : func_button frame=1 distance = 24.779984 (x=-88,y=-767.5,z=-75) visible=1,solid=4,angle.x = 0, angle.y = 0 active = 1 [RCBOT]282 : func_button frame=0 distance = 24.779984 (x=-88,y=-767.5,z=-75) visible=1,solid=4,angle.x = 0, angle.y = 0 active = 1 So I might be able to script it, Though the size and position might be a problem? ================================= I've been working on some fixes for crystal, but I got stuck on the HT on top of the box into the vent, for several hours, the other day... It's a very difficult HT and I have them towering under the opening to the vent, but I can't get the top bot to stand up (like the old metamod bots would do), then crouch jump into the vent. I've done a few fixes/tweaks before this point. So, for now, I will set up the HT for bots to crouch for the player, and test/fix the other parts of the waypoint, then upload it. I started work on this from the git rcwa. It might need a script, but I will see how well it works without one first... |
Poka |
Aug 10 2020, 09:54 AM
Post
#3
|
Member Group: Members Posts: 25 Joined: 28-February 08 Member No.: 1,314 |
duplicate post
|
Poka |
Aug 10 2020, 10:32 AM
Post
#4
|
Member Group: Members Posts: 25 Joined: 28-February 08 Member No.: 1,314 |
Hi Poka, Nice, how far into the HL campaign are you? Are you attempting the whole campaign? I'm doing a bit here and there when I think the bots could potentially make through the whole map. Maybe eventually I'll have something for all the maps. Also ran into a null pointer in hl_c11_a1 right when the door opens and the bots freeze. The problem seems to be with bots trying to use gauss. CODE Angelscript: Not allowed: in section 'c:/program files (x86)/steam/steamapps/common/sven co-op/svencoop/scripts/plugins/botmanager/botweapons.as', at (520, 21):Angelscript: Function Angelscript: DoWeapons: Angelscript: Message: Null pointer access ERROR: Angelscript: CASBaseCallable::Call: Execution of function 'BotManager::Think' failed! ERROR: Angelscript: CScheduler::Think: execution of function BotManager::Think failed! |
Lo-Fi Version | Time is now: 5th November 2024 - 08:49 PM |