Have noticed several instances of the AI running away from contact IF you punch enough rounds down range to suppress them initially and then keep the rate of fire relatively high. However they tend to start calling in IDF and reinforcements a little quicker in those instances because they think you are a heavier group than them.

I watched one of our small patrols do that in our ALiVE deployment (they were a 4 man patrol) and each person dumped probably 3-5 mags or 2-3 belts of RPK ammo with the intent of forcing the AI into suppression on my requests...they were then overwhelmed by the response they recieved about 5 minutes later from the AI.

Has anyone else noticed that squad/team leaders for the AI now stay in place at the cycle point area instead of following the patrol route with their teams? I can't pin it down to VCOM but it seems that might be the culprit.

Try this

go to the directory VCOMAI\functions and delete VCOMAI_ClosestAllyWarn.sqf
rename VCOMAI_ClosestAllyWarnOLD.sqf in VCOMAI_ClosestAllyWarn.sqf

that's from the VCOM thread on the BI forums. Hopefully it makes sense

@JD_Wang Try this

that's from the VCOM thread on the BI forums. Hopefully it makes sense

I think that has to do more with the AI not responding to calls for help, though it may play into the waypoint problem. I myself haven't noticed any problems with the calls for help, but I have noticed the waypoint behavior - do they still use this behaviour after using that fix?

I haven't noticed any issues since I did that fix, but to be fair I haven't done any extensive testing.

A really big thing that is a game-breaker while using VCOM is that the OPCOM ignores all of the warning features that come from VCOM (hearing gunshots, vehicles, far off detection) and continues using stupid move and cycle waypoints in the objective. This results in other AI in the objective that aren't involved in combat to just not do anything. The group in combat doesn't use flanking maneuvers or anything, and they never get reinforced like VCOM should allow. Players end up having to seek out the remaining combatants to clear them completely out of the objective, which gets tiring. As virtualized reinforcements come in per the OPCOM's request, the same thing happens, they're just mindlessly stuck to their move waypoint. There is no cooperation, which VCOM should allow.

I'd love to get in touch with him. Any idea how that would happen? And are you suggesting that VCOM is no longer supported/compatible, or something on my mod list is messing it up? Appreciate the reply.

How would I happen to do that? Also, I noticed when using custom objectives, there are units "on reserve", meaning that they don't have any move or cycle waypoints, and can respond to things like seeing units from away or hearing gunshots. Other than that, units that are in the obj. and have cycle and move waypoints don't respond really to anything, I can get close and they won't react to me or my fire. It's odd. No HC is being run.

I haven't touched ARMA for a couple of months now, but just after the new year I think it was I put together to completely vanilla mission on Altis and I struck the issue with VCOM calling in support choppers again. This despite using the same code in my initServer.sqf I always have to disable it.

Has anyone else had this issue, or has something changed?

It was the straw that broke the camel's back for me at the time. Sometimes it gets very weary fighting this game to make it do what you want it to.

All I've ever had to do in the past was use the initServer.sqf with

[
	{
		{
			If (!isNull (driver _x) ) then {
				{
					_x setVariable ["NOAI", true, false];
				} foreach (units group (driver _x));

			};
		} Foreach (vehicles select {_x isKindOf "Helicopter"});
	},
	10,
	[]
] call CBA_fnc_addPerFrameHandler

I actually fired up ARMA for the first time in months and played around with it and couldn't get it to happen again. (and that's part of the reason I don't play much anymore haha)

@AUTigerGrad So heads up folks....VCOM in its current state will ultimately wreck an ALIVE server after the server being up for 8-12 hours. By wreck I mean.... extremely long save times (or no save at all can be done) on server save and exit, extremely long spawn times for ALiVE units causing units to spawn in on top of players after several minutes, etc. I'm assuming this is due to some bad code that causes never ending loops and spam on the server.

A VCOM user named MrLED has uploaded several fixes to VCOM's github but they have not been pushed yet to the main VCOM code. You can grab them off of github and replace the current version.

I'm going to test to see if these new updates fix the VCOM issues. But I figured I'd let folks know who are running servers.

I confirm also. Long time to save. VCOM and ALiVE compatibility looks like a marriage... Moments of peace and moments of fights!

Let's wait for future VCOM updates, it seems Genesis is working hard on the mod and is aware of the FSM Leaks and other bugs in VCOM.

Thanks AUTigerGrad, maybe I'm confused on how vCOM works. As of now I've got vCOM subscribed to on the Steam Workshop. If I clone the repository, how would I overwrite the files the vCOM download from Steam applies? Or have I been using it wrong all along?

I've given up on VCOM for now, even using the latest github build I can't stop it from taking over control of my support helicopters.

Still using the same code in the initServer.sqf (I even tried the init.sqf just in case that even made a difference) that I've always used with success but eventually one by one those choppers take off and go to support another unit never to return.

So we're trialling ASR AI now, which seems ok. I do miss the static weapon deployment of VCOM though :(

VCOM 3.0 is out, anybody mess with it yet?

Yeah I added it into our current mission and so far it looks really promising.

We were passing by the town of Timurkalay on Takistan. We took contact from a large group of Taliban so found a fairly secure spot in defilade and started firing back with the .50 cal on our Coyote. There was at least 3 squads so I deployed our 60mm mortar and started to drop rounds on them. They replied with a couple of rounds from their own mortars (VCOM) destroying all the wheels on the Coyote.

After we had taken out the forces on the hills we decided to pop smoke and use that for cover to get into the town. We took a few wounds getting into a compound and holed up in a house to patch up. While we were doing so 2 insurgents breached the house (VCOM) but were quickly taken out.

Later on we started taking smoke rounds and random .50cal fire. It took us a while to work out what had happened. Insurgents flanking our initial position (VCOM) had mounted up in our disabled Coyote and were using the gun on that, along with the 60mm mortar I'd abandoned to attack us with (VCOM)

So yeah, so far so good, the enemy seem smart, reactive and very capable without being super soldiers. That was with the default settings as well.

Seems great, except for the fact that I can't order other friendly groups onto their transports anymore, even when I disable VCOM for BLUFOR. They'll get in once, and then later when I try to get them back in their transports they'll all pile in only to get right back out and refuse to get in again. Bummer.

3.0 seems stunning to me. I'm fairly experienced with leading an AI group, and I've had VCOM on always but 3.0 just blew my mind off. The AI with its movement, using covers and everything seemed so brilliant. This might be my imagination but @JD_Wang seemed to enjoy it aswell, so maybe it's not lol. Really made my day and I found out leading AI to be actually fun and interesting for a change.

We were testing a new mission last night and for a hot minute though ALiVE was blatantly spawning units behind us, but once I popped into Zeus I realised the enemy squad that had "appeared" behind us, had been sent from quite a ways down the road from an OPFOR camp. Oh and their CQB seems so much better now. I don't know how much is real and how much is just the fact that from the ground you can't see what happening, but fighting in towns is scary fun right now.

Having given such a glowing report though I am having issue with rpt spam. My rpt file is now up to 15mb and it's full with the same VCOM error. I've posted in the BI VCOM 3.0 thread but no sign of an answer yet.

Did 3.0 fix taking over combat support?

3.0 doesn't effect air vehicles at all from what I know. I haven't seen it take over supports, although I do use the code to disable VCOM on my artillery supports because I believe it would assign them targets etc otherwise.

After about a week of testing it as I built our lated campaign, I can safely say this is the best AI script hands down. Genesis did an amazing job with the rewrite.

Well I made a test mission where Vcom did take over attack, transport heli and the arty. The mission starts however with enemies in sight of the said support assets. So that might be it.

@JD_Wang After about a week of testing it as I built our lated campaign, I can safely say this is the best AI script hands down. Genesis did an amazing job with the rewrite.

Totally agreed.

@RedeyeStorm are you sure you're using version 3.0 ?
There's a new thread for it on the BI forums and a new Github. I've played for hours with it and not seen it take over helos.

Even genesis said in the old thread

Vcom AI does influence vehicles, but no longer directly controls aircraft any longer.

Make sure you have 3.0

I will check soon. I have Vcom through Steam so it should update automatically.

@RedeyeStorm I will check soon. I have Vcom through Steam so it should update automatically.

There's a line of code in the wiki that you need to place in init-file, which is accessable inside the "general" tab within Eden editor. It has worked for me (or I've been lucky), haven't noticed any CAS or Transports being controlled by VCOM. Here's the code, down the page:

http://alivemod.com/wiki/index.php/FAQ#VCOM_AI:_How_can_I_stop_VCOM_taking_over_my_CAS_Units.3F

@Hedberg that will only work (and even then not well) for pre version 3.0 and there's no reason to use anything but 3.0 now. Everything before 3.0 is hot garbage compared to what we have now.

I'm not sure if steam has a 3.0 release yet, I always use the script version.

It seems that combat support is still being used by vcom. Had mine take off mid mission to go loiter over an area.

@Seagull have you updated to version 3.0 from the BI forums?
I've been running a mission for almost a week now with that and not seen a single support take off.

The new version doesn't influence aircraft at all from what genesis says