VCom and ALiVE

  1. ‹ Older
  2. 3 years ago

    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.

  3. Edited 3 years ago by HeroesandvillainsOS

    I’d encourage you to reach out to Genesis. Aside from some edge cases (which included VCOM at one point because Genesis was actively talking with the ALiVE devs), ALiVE simply doesn’t have the manpower to ensure compatibility with outside mods.

  4. 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.

  5. Edited 3 years ago by HeroesandvillainsOS

    @Carmine39 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.

    I have no idea, I don’t use it. You made it sound like there was a problem. :) He has a VCOM thread on BI forums and Steam Workshop too I think.

    @AUTigerGrad uses it a lot though. Any opinions on what Carmine is seeing?

  6. Friznit

    18 Feb 2018 Administrator
    Edited 3 years ago by Friznit

    VCOM works fine with ALiVE. Since VCOM only applies to units typically within less than 1km, and the ALiVE spawn range is 1500m by default, VCOM kicks in after the units have spawned and carries on as normal.

    What's more likely happening is the ALiVE HC autobalancer breaking the unit KnowsAbout, which VCOM relies on for 'sharing' info on enemy units. Try turning it off and see if you have better luck with VCOM.

  7. 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.

  8. I use VCOM in just about every mission I run, with a HC on our server. From time to time, I'll notice enemy AI not being as "aware" as I would like, but overall..it's very few and far between. Not enough to be considered an issue. VCOM adds so much to the game it's hard to find fault with it. AI seem to be reacting very well on our server, and the enemy are definitely aggressive in sending QRF forces when engaged.

  9. 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.

  10. did you put it in the pilots' INIT?

  11. 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)

  12. 2 years ago

    @JD_Wang 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.

    I hear ya there!!

    The wiki link says this is needed.. perhaps the info is outdated?

    [{{Driver _x setvariable ["NOAI",true];} foreach (vehicles select {_x isKindOf 'air'});}, 1, []] call CBA_fnc_addPerFrameHandler;
  13. 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.

  14. @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.

  15. How exactly do you replace the existing vCOM files with the updated ones from the github? my vcom is packed into a pbo, do i need to replace and repack it all or is there a pbo avail?

  16. Get Github for Desktop..then add the VCOM github to your repository. Choose the branch that has the fixes and select to clone that repository.

  17. 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?

  18. You could use the script version of vCOM (I assume it still exists and is updated) and just add it to your mission(s) instead of loading the mod.

  19. 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 :(

  20. VCOM 3.0 is out, anybody mess with it yet?

  21. 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.

  22. Newer ›
 

or Sign Up to reply!