Talk:AI: Difference between revisions
m (Iritscen moved page Talk:Tricks behind Oni A.I. to Talk:AI without leaving a redirect: Consistency with Graphics and Physics.) |
m (using Image: consistently to make it easier to find all image refs on a page) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 5: | Line 5: | ||
[[User:EdT|EdT]] | [[User:EdT|EdT]] | ||
[[ | [[Image:Ai2_showastar.png|384px]] | ||
| Line 14: | Line 14: | ||
Couple more screenshots | Couple more screenshots | ||
[[ | [[Image:Ai2_showastar2.png|384px]] | ||
Sometimes the AI ignores the path | Sometimes the AI ignores the path | ||
[[ | [[Image:Ignorepath.png|384px]] | ||
Cookies for anyone who can explain this grid. It appeared while ai2_showastar=1. I have never seen this before. | Cookies for anyone who can explain this grid. It appeared while ai2_showastar=1. I have never seen this before. | ||
[[ | [[Image:Mysterygrid.png|384px]] | ||
I asked Neo to look into the vision bug :) | I asked Neo to look into the vision bug :) | ||
| Line 32: | Line 32: | ||
Thanks for all your work, Loser. "'''Minimal shooting distance (MinShootingDistance) - [..] for some unknown reason, value from this field is divided by 2.'''" Could it be that the engine considers this setting to be a diameter and not a radius? The AI would be at the center of a circle of diameter MinShootingDistance, so it would take effect if an enemy gets less than 0.5*MinShootingDistance in any direction from them. Of course, if the other "distance" variables don't work that way, then this could still count as a bug, I suppose. --[[User:Iritscen|Iritscen]] 21:51, 25 September 2011 (CEST) | Thanks for all your work, Loser. "'''Minimal shooting distance (MinShootingDistance) - [..] for some unknown reason, value from this field is divided by 2.'''" Could it be that the engine considers this setting to be a diameter and not a radius? The AI would be at the center of a circle of diameter MinShootingDistance, so it would take effect if an enemy gets less than 0.5*MinShootingDistance in any direction from them. Of course, if the other "distance" variables don't work that way, then this could still count as a bug, I suppose. --[[User:Iritscen|Iritscen]] 21:51, 25 September 2011 (CEST) | ||
:All other fields related to distances (be it in ONCC, CMBT, MELE, EINO, other values in ONWC and so on) use radius as a value. So my assumption is that Minimal shooting distance field is somehow bugged when processed and is taken as a diameter.--[[User:Loser|Loser]] 17:21, 28 September 2011 (CEST) | :All other fields related to distances (be it in ONCC, CMBT, MELE, EINO, other values in ONWC and so on) use radius as a value. So my assumption is that Minimal shooting distance field is somehow bugged when processed and is taken as a diameter.--[[User:Loser|Loser]] 17:21, 28 September 2011 (CEST) | ||
[[Category:Engine docs]] | |||
Latest revision as of 14:15, 13 May 2022
Thanks for the thorough explanation of Oni's AI. I learned a lot.
If you want here is a screenshot of ai2_showastar, this command was enabled in the Mac Intel.
Thank you, picture of A* will come in handy. However, can I ask for a bit different picture? I would like to see longer route being evaluated (possibly with some obstacles or corners in A.I.'s way) with camera positioned above the scene. That would serve better as demo picture.
Also, as you can see, there are numerous glitches in A.I. with the most annoying one being that "vision breaks pursuit mode". Can you please look into it? Thank you in advance.--Loser 14:29, 21 September 2011 (CEST)
Couple more screenshots
Sometimes the AI ignores the path
Cookies for anyone who can explain this grid. It appeared while ai2_showastar=1. I have never seen this before.
I asked Neo to look into the vision bug :)
Thanks for all your work, Loser. "Minimal shooting distance (MinShootingDistance) - [..] for some unknown reason, value from this field is divided by 2." Could it be that the engine considers this setting to be a diameter and not a radius? The AI would be at the center of a circle of diameter MinShootingDistance, so it would take effect if an enemy gets less than 0.5*MinShootingDistance in any direction from them. Of course, if the other "distance" variables don't work that way, then this could still count as a bug, I suppose. --Iritscen 21:51, 25 September 2011 (CEST)
- All other fields related to distances (be it in ONCC, CMBT, MELE, EINO, other values in ONWC and so on) use radius as a value. So my assumption is that Minimal shooting distance field is somehow bugged when processed and is taken as a diameter.--Loser 17:21, 28 September 2011 (CEST)