Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Posts posted by dnk

  1. No to jumping.

    Yes to climbing.

    We need "real life" arguments, because ArmA is supposed to be realistic. No more "because other games" etc.
    Why would we need jump? I still dont get any idea how it would be helpful. As stated it would most likely be abused by people trying to make Arma more like Cod/BF and used to bunny hop.

    I would like to see more realism in movement, like you have to drop your ruck when you receive contact so you can move. From all the vets I have spoken with they always dropped their rucks so they could move easier when under fire.

    These comments are good.

    Weight-based inertia/stamina modifiers would be nice.

  2. This is going to be your downfall if you don't do something about this.
    As much as I dislike getting into arguments with kids who in all likelihood never even heard of ArmA until a few weeks ago, there's a point to be made for the larger issue:

    Where is the community going to go exactly? CoD? BF? RO? TF? A quick read of the forums will show the fans of this series don't see any real competition for the milsim genre, just general distaste towards mainstream FPS gaming and other franchises (though many can enjoy both ArmA and mainstream, it does seem to be the general feeling). Nothing currently in alpha/beta that I have noted at least compares to OA/ACE2 as a milsim. With OFP2 being such a dud, ArmA's basically alone right now as a standalone title here. Plus, many have built up communities around the game over years, and that's a big reason they will stick with it even if there was competition, which there isn't.

    Some will eschew A3 because they can't play it, but these aren't the ones complaining about FPS oddly, since their machines are old as dust and they don't expect them to handle it, not because they're $1000+ new gaming rigs (the primary complainers, and certainly with good cause, though overblown with rhetoric/idiocy by many such as yourself). Some others will eschew it because they realize it isn't COD with bigger maps, and they were never really the target demo anyway (and despite all the complaints from the core community, it really doesn't seem like BIS is pandering to them much at all with it's current design imo).

    Personally, I have a decent-ish CPU and a crap GPU, and I'm wholly content with the performance I'm getting, given it's an alpha and all. I do plan to upgrade before launch, so I hope they fix this issue for higher-end PCs, but if not I guess I've saved myself a new GPU purchase, eh?

  3. Course they aren't as quality as Arma3 trees. The point was to demonstrate there are older trees which convey lighting much better than Arma3 trees. It's to show a contrast between lit trees and flat ones.
    No, I was talking about both the visual aesthetics AND the flatness. Neither look nice, though certainly having some shadows makes the mod trees less flat (but still, they look fairly flat to me).

  4. Eh, JSRS for ACE2 is pretty much the best crack/whiz sounds for being shot at I've heard, and the ambient noises are top-notch. I DO love the higher contrast between gunshots and all other SFX with A3, though. Guns are LOUD, and now they feel it moreso than in any mod/ArmA game I've tried yet. They just need to work on adding more reverb, which always makes guns sound better ("Heat" did this about perfectly for movies). With all these valleys and rocks around, should be a pretty reverby sort of place, imo.

  5. Currently, A3's damage is similar to the 7.62NATO in ACE2: usually 1 shot, but sometimes 2 unless in an extremity. This is with an intermediate round (the 5.56 in ACE2 is a lot weaker and takes more than 1 hit often), but with all the advanced body armor of the next 25 years... I'm not feeling it to be a good balance or even realistic, and it means we're lacking wounded/downed soldiers and a proper wounded system, as in ACE and even vanilla A2. Obviously, the devs know how to implement this, and have in the last game, so why is it missing, or am I just missing something in the editor?

    I dislike this in both iterations of the game in this respect. Wounding needs to be more common, and for A3 wounded animations for incapacitated soldiers should be included.


    Nah, I've read those studies years back. It's true: it takes time, especially with adrenaline, for a direct hit to really incapacitate someone, CNS aside. No personal experience, but the statistics are there.

    Speaking of which, generally combat casualties are hugely skewed towards non-fatal, yet in the alpha it's more like 90% fatalities from shots.

  6. Just tried mikebart's trees on Stratis. Notice how they give the impression of low angle light but the Arma3 pine trees don't.




    Eh, all of those trees look pretty unappetizing, no offense to anyone. There's just something they need to do with the mid-long LODs. Clearly, they can do it given past games, so I'm guessing these LODs weren't a priority for the alpha release. At any rate, it needs fixing.

  7. Yeah, the model textures need some serious retexturing/shading.

    the screenshots just make me wonder again whenever I read people freaking out about the advancements in graphics from A2 to A3. Takistan and Chernarus look absolutely the same as in A2.
    The lighting and dynamic PP being toned down and the improved clouds and much less Z-fighting at distance and better character textures/models and the terrain textures are much more varied and realistic/detailed looking are a few. It's not like 2x better, but it's still a collection of serious improvements, especially as it's only in alpha.

  8. so technically, its not a preorder, although the process is exatcly the same as one, it has different phrasing so you cant get your money back, thats pretty much it. but, by following that logic, the guy is right, because if you cant get your money back, because it isnt a preorder
    Fact is, there are a ton of stores that don't let you return merchandise that was on sale when you bought it. That's what this is: merchandise (a $60-70 game) that's on sale (for $35, possibly half off, or at least close) in advance. It's a preorder-on-sale. Eventually the preorder-not-on-sale will come out for maybe a bit less than the final retail price, which I would assume could be cancelled like any other merchandise you never actually got to use. But not only do you get this merchandise on sale, you also get to partially use it as well.

    It's like going into a store, buying a suit for half price, then being allowed to take it home before tailoring and wear the pants only while they fit and tailor the suitcoat, doing so, then saying they don't fit well and claiming you've been ripped off because they won't let you return the on-sale merchandise.

    And you're some sort of idiot for expecting them to fit properly when they haven't yet been fitted and tailored.

    Oh, and don't run around buying things without seeing what the deal is first. Try that in the future, you will feel less buyer's remorse, but then given that you're unwilling to wait more than two weeks for an ALPHA to become 100% optimized as much as other gold release AAA titles, well, I guess the patience required to hold off on hitting "buy" is lacking here...

    2. THIS IS NOT AN ALPHA ISSUE, LIKE SAID OVER A FUCKING HUNDRED TIMES!!! And they still haven't said they are going to fix the CPU utilization.
    Dwarden said they'd found the likely culprit and will fix it (not a 100% guarantee, but that's exactly what you're asking for here, the devs' acknowledgement, and there it is). I guess it's hard to find these needles of hope in this giant haystack of wild ranting angst, for which you have helped water down the useful posts with more of that wild ranting angst stuff.
    We don't have to do anything.
    Still, maybe try chilling tf out while it's in alpha. Could work to your benefit.

  9. I'd be really amazing if they simulated an in-game microphone for the radio so if you press the radio transmit button you can send sounds of your surroundings to receivers. Imagine being able to hear background gunfire or other noises as someone is radio-ing in their status. That would bring so much immersion to the game.
    Yeah, that'd be pretty awesome but would also make understanding other players (already can be difficult with all these Brits/Aussies around) a bit problematic. Still, I think immersion trumps it here.

  10. My 2 cents, and I'm still learning about how ArmA handles the AI scripts, so excuse any ignorance, but I want to see this improved as much as anyone.

    How hard is it to AI map a level for cover and use it in the scripting (say for an intern or other lowly programming grunt)? My idea is to take "tiles" (or square meters or some such breakdown of the map) and give them values based on the amount of cover provided in a set of directions (whether it be N, S, E, W, or N, NE, E, etc, or multiples of 60-degrees or whatever). Then further aggregating these into another map (not literal in a visual sense) for overall terrain cover quality. It then should become a lot easier to send the AI from cover to cover and to act smartly in non-desert terrains. Basically, if they know what direction they need cover from and where they're going, they can choose from available terrains that provide cover in the appropriate direction using the data from the AI map and path to it. Further mapping could include values for quality of LOS on certain directions, so if providing support/suppression/engagement is more important, they can choose a tile with both cover and good LOS instead of just cover (in the case of being suppressed).

    For example, an AI is being actively suppressed by enemies from due north. This activates a "findcover" command, which then looks for nearest tiles with moderate/good cover from the north. Then the AI gets pathed to that tile and moves out to it. Currently, AI just stand up, deer in headlights, and take it.

    Another example, an AI in a city is ordered to engage a target while not under attack. It knows the location of the target and then looks for a tile with a LOS number in that direction high enough to be at least equal to the distance between said tile and target's tile, while not being too far out of formation. It moves in and should generally be able to start engaging. Currently, AI will just sit around inside a building staring at a wall instead. If the AI can't find anything, perhaps this can be taken into consideration when choosing whether the group remains in place or moves to a new location.

    Additionally, a more aggregated map (and non-directional) can be used so the AI knows when it is covering generally "open" ground, where it should employ a base of fire element and a rapid movement element to cross.

    I think a lot could be done with this, simplifying dynamic AI scripting with some pre-"rendered" (or laboriously stitched together by an intern) mapping. Let an intelligent human go through and evaluate maps at a given resolution in "hot spots" of CQB (anything with significant amounts of settlement), and let a more generic algorithm construct all the natural terrain outside of these areas based on object placements (like, a given tree model would automatically give certain cover values in all directions in adjacent tiles). I'm sure you could literally draw/paint the map first then have another program translate the color scheme into a much (disk size) smaller numerical map(s). This gives both the intelligence of a human to the AI in the places it needs it most (evaluating terrain, LOS, and cover), while not impacting the performance much, if at all.

  11. I don't think it is so much a problem of the ai having restricted FOV, but of them simply not glancing left and right every so often, or occasionally checking their six. they just stare straight ahead. I thought this was improved upon in a OA beta but it doesn't seem to have carried over to arma 3.
    I absolutely agree. I thought I mentioned this, but I clearly forgot. It's both issues, but probably the one mentioned here is more important. "Head on a swivel, wait, scratch that, head on a pike."
    Looks like AI prioritize more newly discovered threats than previously detected threats coming again into line of sight.

    At least debugging danger.fsm shows that.

    Any info on debugging that? I would like to get more into the nuts and bolts of things here.
    True. We are somewhat able to script the units to lie down, but we are not able to consistently make them run into cover. We lack reliable commands (findCover? ForceRun?).
    This could be solved by the AI map mentioned above, giving different cover values for direction of cover in addition to quality. Then it's a simple matter of locating the nearest directional cover tile and pathing to it, then letting the typical cover usage programming take over.

    For this form of the AI map, each tile would have 4 or 6 or however many directional values you like. You can then aggregate these directional values for the overall tile value (when considering movement when not being actively suppressed).

    It should not lie down in CQB, while crouched stance may be the preferred one imho.
    Well, if they aren't going to find proper cover and they're otherwise in the open in an urban environment, it's the next-best thing to keep them alive for more than 5 seconds.

    Anyway, a final note regarding accuracy. I'm currently finding a value of 0.1 for aimingaccuracy and 0.3 for aimingshake to be fairly appropriate. They still get kills up to 250m in under a clip, but they're not all super marksmen between 75-150m anymore (under 75 is near-instant death with any reasonable setting). 0.15/0.4 for can make the mid-far range less "ammo spew"y. I wouldn't push them much higher, though, unless you like short firefights. After considerable testing, aimingspeed seems to have no noticeable impact at all right now. Also for spotting distance, they seem to be hard capped at about 200m, though they can engage from much farther if a squadmate sees someone.

  12. I'm going to post my issues with the AI here. The first part is one the stock "regular" difficulty AI in urban combat. Later parts will deal with altered AI values and situations. I think it's important to start with regular AI, as that's what most missions end up as and what most unaware players/mission makers will have to deal with ingame and in the alpha/beta/demos.

    Primary Problems

    1. The Dance of Dumbness: if you ever really pay attention to the AI, you'll see this. Basically, the guy stands up and starts walking around slowly in a tight circle, then usually walking away slowly in the direct opposite direction of the guys shooting at him (or not, they do it pretty much in any situation). An obvious broken mechanic, and a common breakage at that.
    2. The Dunce Decider: again, highly common. This is the guy that decides to aim at, watch, and try to engage a 200m+ distant target that's not firing at him currently, while totally ignoring the 3 enemies standing within 10 feet of him lighting him up. "Priorities", I guess...
    3. The Wall Watcher: pretty much that. Sit/lie in a building (or outside), watch a blank wall. I guess there's something interesting behind it... but what's wrong with using a window? Or a door? Or maybe stop being a pansy and get out there and start fighting? Nah. I guess this can be seen as BIS modeling in "morale" or something - these guys are clearly traumatized or something. But then the AI does this on a street, too. No, don't like watch down the street or scan the area or something, keep staring intently into that fence post.
    4. Standing Stupid: if you're being shot at in the open, you should just stand up straight and do nothing for 30 seconds. Deer in the headlights much? Never, ever, ever lie down or even think about crouching to reduce your silhouette. And never use anything other than the 3 basic positions (ignore all the extra ones players can use).
    5. The Dance of Dumbness pt 2: come to open ground with enemies all around. Run through open ground under fire. Stop. Turn around. Run back. Stop. Turn around. Eventually die.
    6. The Bumbling Building User: wait, there's a second floor? Wait, there are windows and doorways? Wait, we're NOT supposed to just camp inside one of the rooms and aim at a wall? I thought these things were ground-floor-only covered walkways!
    7. The Lone Loser: lots of ramboesque "I'm going it alone" tactics in urban scenarios. Too often I see guys wandering (they're certainly not in a hurry) through the streets, detaching themselves from their squads and supporting bases of fire to penetrate into enemy lines. While this makes for slightly more interesting "surprise 1-man invasion" scenarios, it definitively is not realism-enhancing.


    1. I don't really know what's up with this, but I figure the devs can find it and fix it, maybe just by shortcutting whatever's doing it with a "lie prone and wait" command instead.
    2. Really, really need to work on AI priorities, but this may also be due to broken awareness. Obviously, the closest target is not always the most important, especially if a farther one is actively engaging you, but when anything's within like 20m, it should definitely take priority over the guy 150+m away. I would suggest something like this for prioritization: [(500 x (weapon modifier))/(distance to enemy)] + [(490 if currently/recently shot at by)/(distance to enemy)]. Here is a graph showing the result (numbers can be tweaked, of course, this is a rough version - the basic thing is that it should be exponentially in favor of closer targets, with the "being shot at by" taking over in importance at medium distance):
    3. Basically, I think there are two approaches for when a target is totally out of LOS. First, if engagement is not a priority (other orders are higher priority or it would require too much repositioning to accomplish) then the target should be stored but cease to be acted upon (in place, active scanning of the "front" or whatever should take over, supporting rest of squad, etc). Second, if engagement is a high priority, then repositioning should occur.
    4. AI should react realistically to incoming suppressive fire and run for cover or GET DOWN. This should become a #1 priority in all situations.
    5. The AI should never attempt to close range with any enemy that's in close quarters (20m or less, I'd say). The AI should also generally highly prefer cover/prone to running through open ground when multiple enemy contacts are around or when under fire.
    6. This I leave to the devs to figure out.
    7. Basically, improve CQC squad tactics. They do seem to like to bunch up a lot when in cover, but then they break up into 1-man tactical units when they press forward.
    8. (ADDITIONAL TO ALL): broken awareness of open terrain. A way to handle this is to AI-map the levels, basing areas' "cover rating" on the amount of cover objects (probably needs a creative hand to accomplish) with at least a 1m2 level of resolution. It could be divided into (1) high cover [buildings, closed in yards, etc] (2) medium cover [forests, rocky areas, small streets with good cover on both sides] (3) low cover [low density forests, cargo containers, open yards, only low cover stuff like a low fence, a street with good cover on one side] (4) no cover [large streets, streets with no cover on either side, that dried up drainage thing in Agia Marina, open ground]. The AI should then be programmed to NOT go over open/low cover terrain when already in cover unless (1) very well supported by a base of fire element that can actively suppress (and DOES suppress) while they move forward, simulating proper "leapfrog" tactics, and when they do so it should be at a FAST PACE and with a preset path and destination; (2) there is no high-cover terrain between them and the enemy and they are being aggressive (due to higher numbers or a flanking operation); (3) they have very low skill; (4) they are taking up a prone covering position behind some obstacle. If the AI can cross <75m of open terrain to find more "good cover" terrain on the other side, then it should be a fast sprint to the other side's cover, and no dilly-dallying in that no-man's-land, and definitely no RUNNING BACK AND FORTH through it.



    1. (ADDITIONAL TO ALL): broken awareness seems to be an issue. The AI should be actively scanning their environment more and have a much easier time of finding nearby enemies.

    ---------- Post added at 01:11 PM ---------- Previous post was at 12:04 PM ----------

    I've played around a bit more. It seems the situational awareness is due to the AI just not looking around much and having minimal peripheral awareness. You can place an enemy basically 5ft away at 90-degrees to the AI's orientation, and he'll never see the guy. The vision cone in this game's AI is ridiculously restricted, and I think at least a couple issues might just boil down to that.I'm going to post my issues with the AI here.

    This visual problem extends into acoustic space, where nearby gunfire is impossible for AI to pinpoint or acknowledge for fairly long lengths of time, even when it's directed at them. This needs to be fixed with an almost instant reaction time to incoming, close-range gunfire, where the reaction time to income gunfire is based on a formula similar to the one above for targeting priorities, additionally modified for gun loudness.

  13. Delta Force 2 had great long-range grass drawing, though it was quite blocky up close (but then it was the 90s, I think). Basically it was drawn to infinity and near-total concealment was possible (though there was always that one pixel that would give you away), especially with a ghillie. I think they used a totally different rendering approach, though, so it's unlikely to be useful for ArmA. Still, it is possible...

  14. Yeah, that ST vid is about as good as it can get (features, not implementation, and not the behind the back one). AA had good grenades as I remember them: cookable, easy to predict, 2 firing mods (under/overhand), easy to use overall. They're definitely broken in the alpha, but I'm assuming that's a placeholder for something similar to A2's system, which was weak as could be unfortunately. It may look realistic to have the grenade coming off the hand from an outside viewpoint, but it makes it very hard to use grenades accurately and therefore effectively. I rarely use them even with ACE because of these difficulties.

  15. After an hour or two of messing around in SP...

    The Good

    1. The skies are a LOT nicer - huge improvement in that part of the environment.
    2. The AI seems a lot better at handling MOUT situations, though with big gaps still.
    3. I like the added weather controls and clarity.
    4. The lighting is gorgeous. Seems like a big improvement, and without all the 'overly dynamic PP' that A2 had.
    5. The new stances are cool.
    6. The new inventory system is more modular, which I like.

    The Bad

    1. The terrain is still fairly lacking, and the rocks look out of place - poor blending in with the surrounding terrain.
    2. There appear to be no rivers still - extremely lame for a hyper-realistic milsim to have no inland water.
    3. The AI is up to its usual stupid all the same.
    4. The new inventory system is also a bit of a headache and harder to use than the old one (scrolling?).
    5. Some bugginess with controls, but that's to be expected.
    6. The island is pretty sparse and lacking in settlement.
    7. The weaponry - I'm sure they'd still have early 21st century weaponry around, much like we still have decades-old weapons around, and certainly older models still in production. Do I really want to play with fake future weapons? No. -1 again on 'hyper-realism' when you're in scifi land.

  16. I agree this is very needed. Such bland mid-range textures were acceptable in A1, less so in A2, but they really shouldn't still be around in A3, especially since this is where a TON of action happens in these games - 150-350m away is prime firefight distance, yet that's where the engine suffers the most?

    And while we're at it, there's another thread dealing with a related mid-/far-range rendering issue, except for how models are obscured by the grass: