Volw 10 Posted December 31, 2009 I seem to have problems with ACE2 overriding simple scripts written in the editor. As an example init line of Shilka: gunner this setskill ["aimingAccuracy",0.0002]; In A2 vanilla it will shoot all over the place - as it should. In ACE2, it will fire accurate bursts. It's just an example, I've noticed a lot more commands don't work with ACE2. I was wondering if it's possible to override ACE2 somehow, without disabling it completely. Would appreciate any help. Happy new year! Share this post Link to post Share on other sites
Evil_Echo 11 Posted December 31, 2009 (edited) This involves changes to AI via configuration changes. It's a scaling thing. Edited December 31, 2009 by Evil_Echo Share this post Link to post Share on other sites
sickboy 13 Posted December 31, 2009 (edited) Some useful info I hope: - ACE does not use the setSkill aimingAccuracy command (actually non of them) - ACE makes changes to AI config settings, to make them more agressive etc. It is very likely that these config changes mess up the scaling of setSkill properties etc. - On a side note; ACE uses eXtended EventHandlers, which should allow other XEH compatible addon inits to run alongside ACE. Willing to look into the problem, and resolve it, as it is not our intent to break things, especially when not required :) You could help us (and yourself) greatly, if you would do the basic leg work: - Move the ace_c_ai_*** pbo's to a temporary folder, so that the game doesn't load these addons - Start the game, verify the effects of your setSkill command - If the problem is gone, put an ace_c_ai addon back one by one, checking ingame if the effect is still working properly, or is behaving weird again - Else, if the problem is not gone, try to move more ace_c_** and ace_sys_*** addons away. Basically repeat the above until you can say if the issue is caused by a group, or best, a single addon. When it is pinpointed, we should be able to fairly quickly resolve the issues, and the next scheduled update would include the changes already. Don't forget to put the files back after you're done ;) Edited December 31, 2009 by Sickboy Share this post Link to post Share on other sites
Volw 10 Posted December 31, 2009 - Move the ace_c_ai_*** pbo's to a temporary folder, so that the game doesn't load these addons - Start the game, verify the effects of your setSkill command - If the problem is gone, put an ace_c_ai addon back one by one, checking ingame if the effect is still working properly, or is behaving weird again - Else, if the problem is not gone, try to move more ace_c_** and ace_sys_*** addons away. Right, thanks for pointing me in a right direction. I did test it and it's 'ace_c_ai_skill.pbo' that is causing the issue. FYI. With that file removed, it seems like ACE2 is much more sensitive than vanilla, it's probably due to the use of event handlers. But it works, requires little tweaking so it's not an issue. Just as an example, with "aimingAccuracy",0.0002 - vanilla would shoot in a 20-30 degree cone, with ACE2, it's more like 120 degrees. But as I've said, not a huge issue to change a few numbers around. Share this post Link to post Share on other sites
Rommel 2 Posted January 1, 2010 Lower bounds have been reset to 0, upper bounds have been changed to 0.35 instead of 0.3 to account for a changed mean AI value. Hopefully this should fix your issue. Share this post Link to post Share on other sites
Volw 10 Posted January 1, 2010 That was quick! Thanks! Share this post Link to post Share on other sites