gsleighter

There seems to be a lot of echo added to the small arms, it's quite distracting. Also, the bullet cracks here are louder than Hi-Fi mod's, and the tanks firing sound a bit too heavy on the high end. I do like the different explosion sounds when you hit a building, that's a nice touch. Very good overall, I think I'll probably hop between this and Hi-Fi until Chammy's is released.

Ha, even if I managed to mangle the line.

About 25 percent of the time, when I launch a JDAM, it fires like a rocket, and the plane stops in mid-air. Also, it doesn't lock onto the laser designator, so I'm dumb bombing with it. Also, and maybe this is because of the scripting associated with the weapons bays, but AI won't engage anything, even after I told a wingman to open his weapons bays. Other than that, the plane flies great, and the shilkas look great firing way off in the wrong direction.

11? Why not make 10 louder and make 10 the loudest?

Awesome timing. My wife and kids are out of town this weekend, which means the PC gets hooked up to the surround home theatre system in the living room. Looks like this will be just in time!

http://seamless.usgs.gov/ is a great source of elevation data, the US data is pretty high fidelity at 10m resolution for height maps(with 1m res satellite data in 5k tiles, to boot), and it's easy to use once you've sorted out the interface. Also gives you access to data in Geotiff format.

Crawler, do you have a tutorial or any other information about that feature?

Yes, it can. There was an addon on Armaholic somewhere, it was a demo for multiple gunner positions. I plan on getting this tank textured up and in-game with the turret and custom weapon working in-game first, and then I'll go in and get the hull MG working. Getting close, Rip's helped me out in understanding how to use the O2 UV Mapper, so (If the kids keep taking good naps) I might have this thing in next week.

Wow, that's looking sharp. If you email me your prop texture, I can set up a prop blur texture for you in photoshop. Same for the Junkers, C47, and other prop planes. Here's about as modeled as this tank's going to get, I just need to figure out the UV Mapper myself, and get some textures on it, set up models, weights, shadows, and geometry, and config it into Arma. Easy cheesy. Thanks again, Rip, the tracks are working now.

Manzilla, this is a military sim, and my argument comes from my service in the US Army. We zeroed our sights on the M-16 rifle to 30/300 meters, since that's about where the Krasnovians would be most of the time (According to military planners, anyway). The US Army is fighting a different type of war right now, so that may have changed, but as far as I know, 30/300 meters is accurate for Iron Sights. Also, when I was in most soldiers weren't issued any kind of optics, but you could customize your own rifle somewhat in my unit (I just had a bipod, hadn't bought an ACOG yet by the time I got out, since I was the 240B gunner in my section, and that was my primary weapon anyway). Keep in mind, though, this is all just for the US Army, might vary by branch or country.

@Scubaman We basically agree on all our sources, I just watch CNN, MSNBC, and CSPAN instead of Fox News. High five for not just taking it all from one source, anyway.

No, most scopes are zeroed between 150 and 300 m. Longer out you need to compensate up, closer down. That is normal. You dont need or want a scope at 25-50 m. That's not true. Because a bullet travels up, then down, you zero the scope at 30 meters. The bullet travels up to the zero point. It keeps moving up, so that at 150 meters, it's about 1.5 feet over where you're aiming, and at 300 meters, it's falling right through the point where you're aiming at. So he is correct, most sights are zeroed at 25-30 meters, because of the ballistic trajectory of the rounds.

Check to make sure your viewdistance is under 2000. Arma does not optimize terrain well at a distance, so that's a lot of triangles. I've got a 1048*10m map that has the same problem with higher visible ranges.

Now that live for windows is free for PC Gamers, what are the odds of this being a cross-platform title? It would be nice to have several thousand console players to play against.

I had this problem, turned out my terrain detail was set to low. I'm terrible with config files, but maybe it's not the config?

It's the DEM data, it's got steps in it. Just open the heightmap in photoshop or gimp and run a really light gaussian blur over the whole thing, it should get rid of some of that step effect. All I've ever managed to do in Visitor using the erosion tool is crash visitor.

I think I'd like to take a crack at that Sherman Firefly, next, as long as I'm doing all this Brit armor. Col. Faulkner, I think you'll be as pleased as anybody with how the Cromwell's shaping up. More screenshots tomorrow, need to make some major changes to the chassis and armor skirts.

I've seen groups of rowdy conservatives around me, so I'm not so sure they're as gentle-mannered as you're inferring. Also, I'm sure a CNN reporter would never take it upon themselves to deliberately antagonize a group like that.

I have another question! Is it important to make only convex corners in Arma modelling? And if not, what effect can concave geometry have when you're getting the thing in game? For example, the taper on my Cromwell's cannon is concave (Less than 180 degrees angle), as will some areas of the armor skirts.

1. Is it okay to have open objects in the Arma engine? On vehicles or men, especially. For instance - If I have an object with a face that will never be seen, like the underside of a commander's cupola, can I just delete the face? That way, I save some polys and don't have to sort through it when I'm UV mapping the model. 2. Is there a way to subdivide faces in Oxygen2? It's nice for some parts to create a primitive and modify it with subdivision and extrusion, but I can't find anything about subdivision after you create an object. This is also good for adding details and beveling edges, since it doesn't look like Arma can do that, either.

I've got a map in the works with 10m cells, and every time I up the viewdistance past 2600m, the game crashes to desktop. I've also got a 1m res satmask. which might also have something to do with it. Anyway, it looks great in game, it's just a pity that I'm limited to a 2k viewdistance, since the actual spot in Arizona I'm modeling has pretty much unlimited visibility to the horizon.

I hope that doesn't mean just spawning shells around known contacts in a mission, it would be nice to create missions where you have to silence actual artillery, firing at actual targets far out of range. This could just be marketing hyperbole that means "In mission three of the campaign, we added scripts that simulate artillery fire for more intense atmosphere." No matter how they do it, I hope the sounds and effects convey a sense of power to it.

I prefer 800m to 1km, depending on how hi-res the Imagery actually is there's areas of Europe that don't have 1m res imagery, so going that close would be pointless and time consuming. I also find taking a wide shot of the area and lining it up with grid coordinates helps a lot when you're pasting all the little pieces of imagery together. The bigger your monitor, the easier it is, too.

I would greatly simplify the wheels and add the details with normal maps, it looks like that's where all the polys went too. I mean, the wheels are probably going to be part of the model people see the least off, especially when in flight.

@Scubaman, I don't think Fox is outright lying to its audience, as much as taking generous liberties with how they present their truths. The video that started this discussion is a pretty good example, if I wanted to make a fool of protesters at the DNC, I would have thrown a fox news reporter and camera crew right into a parade path too. It seems pretty carefully calculated in order to present the story as they want it to be recieved, versus just presenting news objectively.