-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCOM AI sniper engage #149
Comments
I'm using 3.3.3-develop branch script version downloaded from github, I got more detailed information about sniper engage bug. The First error I encounter:
VcomAI-3.0/Vcom/Functions/VCM_Functions/fn_SniperEngage.sqf Lines 52 to 54 in 6bd9aae
This error was caused by Magical Value _x, the first and the second _x are all entities of "VCM_AIDIFA" instead of first "_x"=="_Snipers" and second "_x"=="VCM_AIDIFA". You cannot use _x in multiple forEach like this. So I use solid values
to replace the original one
and the error solved. You might have a better solution. After I overided above function to make it correct, the next error shows up:
I'm not sure what caused the second error, so I just deleted that line. Then I start a mission and during init process, this error pops up:
I dont know about this at all... So I submit the reply tohelp you developers have a more detailed information about sniper engage issue than the issue poster's. The development of sniper engage function is still in a very early stage, I suggest users who read this issue to disable that function until further changes. |
Describe the bug
Receiving an error message when the special ai setting for marksmen/snipers is enabled; the error message "Error undefined variable in expression: vcm_fnc_sniperengage" is shown
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Well i supposed the specific ai setting for sniper ai would mean they would stay where they are and engage from a long distance rather than do what regular ai do and flank/assault the enemy position
Screenshots
https://steamcommunity.com/sharedfiles/filedetails/?id=1850860673
VCOM Version:
current updated steam version
Additional mods used:
bug was able to be replicated on vanilla arma 3 (only vcom installed)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: