Jump to content

b0s

Member
  • Content count

    97
  • Joined

  • Last visited

  • Medals

Community Reputation

16 Good

About b0s

  • Rank
    Corporal
  1. Tested the current dev build a bit. No visible errors. It didn't seem FFE was used. Only when I set to use classic VCOM arti shells started raining. "VCM_ARTYENABLE" is double in the current config so maybe this was the cause. Nice to see the new CBA menus for all settings. Also whats that build about smarter tanks? :) Would be nice to have UAV usage and smoke shells back. Also noted that AI doesn't care much about cover when advancing towards a bulletstorm. Also it seems AI never use grenades if they have ammo for primary weapon. Also rifle grenades
  2. Thank you again Genesis and Freddo! With Arma3 being the only game I still play and only VCOM making the AI interesting enough... this means a lot. This might be the best release. No errors thus far and all features seem to be working. One thing I noticed that an AI group w/o waypoints didnt want to advance in my direction when I shot at them from 500m Question. Do the CBA settings overrule the userconfig settings for the mod?
  3. The userconfig is included in every version of the mod. Here for example https://github.com/genesis92x/VcomAI-3.0/tree/master/userconfig/VCOM_AI
  4. Thank you for posting the resource leak fixes! Haven't played Arma for months because VCOM isn't really working I guess there are still problems with the gunshot hearing insta-detection and driving/transporting troops? Will test it and post an issue if it is present. edit: It seems some things have improved. Silenced weapons no longer cause instant detection, but non-silenced still result in insta-detection (VCOM_HEARINGDISTANCE) AI transports and driving in generals seem to be fundamentally broken also in vanilla Arma3
  5. Not sure if it's a problem with the current Arma version or vcom, but transports are currently broken. When AI decides to enter a vehicle they barely move and keep getting out/in. And still the insta-detection is still present. "VCOM_HEARINGDISTANCE= 500" results in 1shot < 500m and the AI gets "knowsabout 4" about the player.
  6. Hi The good old insta-detection by AI is back. If I fire something within the gunshot hearing range I am instantly detected (knowsabout 4) and fired upon. I think it started with the late august updates. Also if VCOM_VehicleUse = true then: ...x isequalto []} && {_x distance _unit < |VCOM_AIDISTANCEVEHPATH} && {!(locked _x... undefined varialbe in vcom_aidistancevehpath undefined varialbe in vcom_aiingamemenu
  7. Hi Thank you for the best AI Arma can have! With the 2.91 mod version I am getting a lot of this. I did not get this error with the script version from a week ago.
  8. Thank you for taking the time! A feature that I think is missing is that AI medics from any squad could heal any friendly unit. Including player and ACE medical compability. Currently it only seems to work inside the squad.
  9. 64-bit Executables Feedback

    Same here. When 8GB gets full, Windows keeps showing the "low memory" warning, although 8GB is still free. Windows 10 here.
  10. 64-bit Executables Feedback

    Yes my page file is set to 2GB maximum becuase it's an SSD and it's not needed for any other application. Increasing it is not a proper solution, but a workaround. Windows and Arma should be able to utilize the free RAM, instead of disk space. Just an observation to take into consideration. Also the problem might just be on my side.
  11. 64-bit Executables Feedback

    Thank you for 64bit! The performance according to YAAB did not change, but the game seems smoother under load. Getting a lot of "your computer is low on memory", although I have 8GB still free and Arma is using <3GB... guess it's a Windows issue.
  12. Thank you for the update! I think I've seen almost all the features being used and more or less effectively. But I'm not sure the skill settings work. Sniper team with all skills set to 1.0 (everywhere possible,colonel) cannot detect a moving enemy squad 350m infront. edit: no server-side settings used. Singleplayer
  13. Thank you for the new version! A lot of good fixes in this version. The godly-insta detect fix works:) Two things I observed: call vcomai_closestobject; if (|#|_ClosestFirendly distance _PlantPosition...' error undefined variable in: _closestfriendly vcomai_destroybuilding.sqf, line 126 Helicopters called in for support dropped their gunners to death and landed directly in the enemy squad (multiple times). Do i understand correctly that in VCOM_RainPercent a higher value means less skill penalty?
  14. Hi Just some more testing on the godly-insta-detect AI. If I put this setVariable ["NOAI",1,false]; on the inits of units in a group then they are not insta-detecting me. If one unit in that group is missing ["NOAI",1,false] then only that unit insta-detects&fires at me. I am also detected and shot if any other unit engages a enemy group! Eg I'm just lying still 200m from a blufor unit. When that blufor unit engages a opfor group, I am detected and shot. Hope you will return for Vcom Genesis! Thank you
  15. The difficulty/skill is set to the minimum everywhere. In the game settings, in the editor and even with F5 modules. A skill of 0.2 Tried the Pre-created difficulty setting, but same results. Btw this config is missing an }; Singleplayer only. Also "VCOM_AISkillEnabled = false;" doesnt change anything. It's like it's not skill related. https://youtu.be/iHb1zhLO45w Regards
×