frederf 0 Posted May 10, 2007 The satchel touchoff and they know where you are is a known bug and I believe in the changelog for 1.06 Share this post Link to post Share on other sites
INNOCENT&CLUELESS 0 Posted May 10, 2007 I guess it is pretty simple to reproduce and BI can assemble the mission by themself in 2 minutes in their editor, Balschoiws description is sufficient. I browsed through all similar TTs and some similar reports here and it seems: That the bombs vitually "smell" like the one who placed them so Balschoiws "sexy perfume" comment is somehow correct. Regardless if it was an RPG fired or a bomb exploded, the killed unit was never discovered visually and in most cases the killer did not have/could not have the intelligence where the AT/RPG was coming from/who placed the satchel and where the atacker was going to. And I guess BI have much better internal trouble shooting tools where they see immediately the intelligence each AI has after each event. Fact is that the excellent shacktac guide is useless at the moment since AI has some abilities which are not considered there. Share this post Link to post Share on other sites
suma 8 Posted May 10, 2007 Quote[/b] ]I guess it is pretty simple to reproduce and BI can assemble the mission by themself in 2 minutes in their editor, Balschoiws description is sufficient. Well, if anyone can dedicate those 2 minutes in their editor to give me a repro case, it will greatly help me in investigating the problem. At least it will make sure I am investigating exactly the same problem the posted is repoting, at best it will give me something to start debugging right away. Share this post Link to post Share on other sites
suma 8 Posted May 10, 2007 The satchel touchoff and they know where you are is a known bug and I believe in the changelog for 1.06 This issue is assumed to be fixed in 1.05 already. Cf.: http://bugs.armed-assault.net/view.php?id=1614 If you have any evidence the issue persists in 1.05 or any newer version, please, post a repro in the bug tracker and reopen the issue. Share this post Link to post Share on other sites
NeMeSiS 11 Posted May 10, 2007 Quote[/b] ]AFAIK for the AI it does not matter in which way their 'knowsabout' value about you hits the critical level, once its reached they will attack, be it trough hearing, seeing or being reported. So theoratically they could hear your location trough a This is not the way it works. Each sensory channel has its own accuracy and its own precision. knowsabout is only a very rough indication of what the AI means about the target, the internal knowledge state is much more complex, including information positional precision, information age and information reliability. Interesting. Is there any change we will get something like this about the ArmA AI (and a bit more in depth)? It would be a nice read and it could clear up confusions about the AI. Share this post Link to post Share on other sites
INNOCENT&CLUELESS 0 Posted May 10, 2007 RGR, but not before weekend. Weekend? Just Saturday, on Sunday everyone needs to bring his wife into an excellent restaurant (if you have kids). I also assumed it was fixed but never tested (my fault, it is my duty) since I play mostly PvP at the moment. Share this post Link to post Share on other sites
ricnunes 0 Posted May 10, 2007 Hi ricnunesHere is the bug-tracker: http://bugs.armed-assault.net/main_page.php And Here are the instructions on how to report a bug: http://community.bistudio.com/wiki/BTS_Instructions The real advantage of the bug tracker for users is people can vote for bugs and raise their profile. So it is very important to do a search to see if your bug already exists that way the bug gets your vote and input rather than 70 different reports of the same bug. For the devs it allows them to have a measurable problem to solve. Kind Regards walker Thanks for the reply Walker! I think I've found the bug that I described in "bug tracking". It's one called in the summary "AI are too smart". Since I don't have an account I can't vote for it or else I would but for me this is by far the most annoying bug (with version 1.05). Share this post Link to post Share on other sites