trips

I can't get this working. The mod loads into CfgPatches but the CfgAISkill values are the same default values, no matter how I set the userconfig\zeu\zeu_ai.hpp file.

Ah okay. I was using setVelocity straight away. I have noticed an effect on the ballistics, but I think it's not too bad. I'm not trying to do anything precise, just make the AI miss once in a while...

Even AI with aimingAccuracy set to 0 seem to hit targets 99% of the time. Is there a way to artificially introduce aiming error? I've tried getting them to doFire at an invisible target but no dice. Can I set their aimpoint directly?

Great workaround, thanks! I can catch the RPG projectile from a 'fired' event handler, right?

Same problem here :( Seems to happen to a random box every time I open a new mission.

None of us could find anything other than change view distance.

Just had a quick try with a few of us at MAG and we couldn't figure out how to place the defending zone. Is there a minimum player limit?

Currently: Close Combat: Last Stand Arnhem Combat Mission: Shock Force Lock On FC2 Red Orchestra A little bit of IL2

It's the kind of thing people train on IRL to get faster and more reliable under stress, I thought it'd be cool to reflect that in game somehow.

Just had a new idea, how about incorporating timing minigames into player actions that would require dexterity in real life? For example instead of just hitting R to reload and waiting for the animation to finish, you can speed up the process if you tap R in time with your character doing certain things like hitting the mag release, pushing the new mag in and racking the bolt. I really want to see them up the fidelity of infantry combat in 3.

Without a doubt a DEFEND waypoint with emphasis on finding cover in the terrain & buildings. http://forums.bistudio.com/showthread.php?p=1954382#post1954382

You can't have it all, there aren't enough cycles on your CPU or bytes in your RAM. Compare BF3 to ArmA in terms of map sizes or AI versatility, for example. I'd expect more destructible subsections and stages per building but there are probably better (by that I mean have a bigger effect on gameplay) things to spend CPU time on than dynamic destruction.

Definitely, Dre. I think there's big room for improvement in the infantry combat. Giving the AI the ability to effectively use buildings & bunkers, both on map and user placed, would really up the tactics needed. At the moment the only option I know of is to weld the AI to the floor (disableAI "MOVE") and force them into the right stance to get them to fire back from inside a building. It ends up meaning that instead of using four Fs most missions played against AI really just use two, find the enemy and finish the fight by shooting them. Sometimes I feel like i'm playing a shooting gallery. They don't duck when they get shot at or otherwise use the great cover they have effectively. Maybe we need a 'defend' or 'occupy' waypoint so the AI know they're supposed to stay put and survive, not run out in the open or try to flank and attack. Not just buildings but I think the AI should be taught to use terrain cover more effectively as well, but first the cover has to be there. Has anyone fought on the cliff in southern Chernarus between Chernagorsk and Elektrozovadosk? It's in the first campaign mission but you're not so much fighting in it as picking off targets from the summit. Take a look at the terrain there, maybe give yourself a fireteam and put an enemy patrol there. When you get to the top look back west at the opposite hill face. Compare the number of pockets of cover you have up here to what it looks like basically everywhere else on the map. It's smooth hills basically everywhere else. I don't know of any place on any other map, official or user made, where the terrain is as good as on those ten hectares in Chernarus. A map shouldn't all be like that, open plains has a value, but going in a forest and having to hide behind thin trees like in a cartoon got old real fast. I imagine that it's a lot less graphically, memory and CPU intensive to use the terrain map to generate cover instead of objects. I think terrain is a lot of the time easier to use as cover too 'cause it's not fixed at waist height, you can inch forwards and pop up, take a shot and move back. On that point I think a 'cover system' wouldn't go amiss. It doesn't have to be like Gears of War or Red Orchestra (although that kind of system wouldn't be too bad), it could just be something simple like the mouse lean in the Tom Clancy games but also applied to how far your character is kneeling/squatting/raising their head above the ground. Just something that lets us use a wider range of objects as cover. Let's leave crouching behind thigh-high stone walls with your head and shoulders sticking out behind. Finally, can the suppression 'system' be made a little more accurate? I only really have two complaints with how it is at the moment but I think changing one or both of these things could have a significant impact on infantry combat: At the moment rounds passing overhead don't suppress, only rounds that hit around you/your target. AI don't stick behind cover when being suppressed, i.e. they can't be pinned. Hopefully someone reads that. At least i've finally put it in writing.

Points 1 and 3 are features you see often but they're not necessary features of a cover system, see Red Orchestra 2. If a cover system is implemented, which I hope it is, i'd also hope it wouldn't have those features.Point 2 is kind of the whole idea of cover. I think there's room for improvement with movement. Analogue stances is something that gets resuggested for the Arma series every so often; being able to hold alt and precisely adjust your stance up and down. That could be an example of a cover system, it lets you use the in-game objects as cover a lot more effectively than the current stances and their slow transition animations do. I don't think R6V makes for a good example. Compare the average engagement distances. In R6V it's practically all CQB, where being mobile is more important. Good for them, those are two titles I hope Arma never tries to emulate. They're a different genre as far as i'm concerned. (Battlefield I think could actually benefit from a cover system) We have (some) cover and stances but putting trying to use the two together isn't always happy times.

This kind of feature would be a deal breaker for me. If infantry combat isn't given a real upgrade i'm not interested.

They could still be used as cover, but only as cover is used currently, i.e. with crouch & lean. Nothing would be lost. Perhaps mission maker-placed objects could be 'compiled' when the mission is .pbo'd so that compound or oddly placed objects are given a 'cover LOD' or maybe just evaluated to see if they'd be appropriate and the cover system disabled if they're not (stacked, at an odd angle)? I think if the game's supposed to be played with tactics that reflect real-life AI need to be a lot harder to shoot.

That's be 'cool' but for me it wouldn't add anything to the gameplay. My biggest problem with the game is it plays more or less like a shooting gallery. No big need to action battle drills. Features like advanced physics should stay in games like Crysis.

I see a lot of talk about physics but is there any netcode out there that would allow it? The current netcode struggles keeping track of units as it is... On top of that I don't really see what significant impact it would have on gameplay.

I voted none of the above. I want a cover system that players and AI can use. One that lets units expose a minimum amount of flesh and lets them pop up and down quickly. Something similar to BiA: Hell's Highway or the up-coming Red Orchestra game. If units behind cover are harder to kill that puts a bigger emphasis on tactics. The lack of necessity for tactics is one of my biggest disappointments in the game. Pick the spot with the best cover and attrit; so many missions are really just shooting galleries.

For me this is the biggest gap. You can sap the AI's effectiveness but no amount of bullets will make them take that into account and stay in hard cover. They always just get up and run, usually getting shot in the process. I think if this was 'fixed' it would really change the game for the better in terms of realistic player tactics. Flanking would be a necessity, not just an occasional bonus.

Extend left/right/forward/backward are probably better names for the commands.

I doubt there's a military radar out there without an off button.

I like the concept, the mission is very action-packed. I've two suggestions though: 1. Limiting the squad size to 4-6 and maybe only one vehicle. I think some people are put off by squad management and in such a small area there's not a lot of room for huge platoon sized squads. 2. Making vehicles a lot more expensive. At the moment battles are very vehicle oriented. There's not huge room for infantry.

Also having problems with the marker blacklisting. I'm gonna try using the function with an array and a trigger to see if that works. Edit Took me a few tries before I didn't get script errors but even after no errors enemies were spawning within the area I wanted to blacklist. This is the code i've used: [bIS_ACM1, [[[1200,12300, 0, 4300]]]] call BIS_ACM_blacklistAreaFunc; I think the format is meant to be minX, maxX, minY, maxY. At least that's what the error messages were telling me. Map was Takistan. Edit2 Took out the additional BIS_ACM_1 marker and the function seems okay now. Edit3 Nope.

Click on the map to deselect everything Drag a box around your group Drag the group Should work fine.