Metal Heart

@wgl5\addons\wgl_wep_config.pbo\cfgweapons.hpp Increase the AI dispersion values defined in the beginnig. @wgl5\addons\wgl_wep_config.pbo\cfgammo.hpp Decrease hit values of all bullets. Don't worry, there's only like ten different bullet types. I guess that'd would be it pretty much. Not quite sure what would happen if someone with the unaltered file would join in MP, guess the AI would still shoot less accurate but the player would suffer the original damage from bullet hits.

AI controlled Cobras and Apaches will fire their AGMs (not cannon or rockets) and Warthogs will drop LGBs (they won't use cannon or Mavericks) at a laser target. You don't need any waypoints, scripting or commands, the AI just needs to see the target and it will attack. Tanks won't shoot laser targets, they don't even see them. You'll need some addon invisible armored targets or invisible infantry targets and some scripting for that. If you have a player pilot using manual fire in a chopper with AI gunner, laser target can be used to guide the cannon. Player needs to lock LGBs on target or they'll just free fall. Mavericks won't lock on to laser.

AI controlled Cobras and Apaches will fire their AGMs (not cannon or rockets) and Warthogs will drop LGBs (they won't use cannon or Mavericks) at a laser target. You don't need any waypoints, scripting or commands, the AI just needs to see the target and it will attack. Tanks won't shoot laser targets, they don't even see them. You'll need some addon invisible armored targets or invisible infantry targets and some scripting for that. If you have a player pilot using manual fire in a chopper with AI gunner, laser target can be used to guide the cannon. Player needs to lock LGBs on target or they'll just free fall. Mavericks won't lock on to laser.

That's not how it works. What does the game logic do? If it's for some script, you could execute that script manually (look into the game logic's config for the path) or createVehicle the game logic on the trigger's onActivation (you'll need the class name). If it sets some global variables that are supposed to control other scripts at startup, it won't work.

Following that logic, they don't give fire fighters water to save lives either, as if putting out fire was their main objective, not protecting the lives or property it might destroy.

No, you didn't. OR only works with booleans (true or false). and distance doesn't work with groups. What you have: group OR group OR condition_that_doesn't_work What you should have: boolean As in: condition OR condition OR condition Which will return: boolean

I think the first values determine minimum and maximum magnification of a scope and the second values determine zeroing distances for those zoom values. So zooming also affects the scope's elevation to compensate for bullet drop.

Now why would anyone zero a sniper rifle, or any rifle for that matter, at 0 meters? Would you really have to aim through the scope to hit a target at 0 meters? No. According to that manual the second chevron would only hit 1100m when the "knob" is set at ten (1000m). So if it is so in ArmA, first chevron should hit at 1000m.

Have the respawn location on some distant unaccessible place for the side that is not supposed to respawn and put them into a spectator script when they die.

That would be the createUnit command: http://www.ofpec.com/COMREF/letterC.php#createUnit

Would you rather take a constant "zoomed in" view that seriously limits your field of view or a constant fisheye effect which prevents from seeing detail you would see at distance in real life then? There's no need for excuses, it's a simple mathematic fact that on an avarage monitor stuff appears way too small compared to real life and on top of that the resolution is usually too coarse to compensate this by sticking your nose right on the display surface.

With ArmA and join in progress a mission might last for days. I think it would be very unrealistic that a soldier that has fought for days without food and water would perform just as good as a well-rested and nourished soldier. Malnutrition would only add to the immersion, just like the damage effects (hands or legs hit, bleeding, losing control when hit) and exhaustion after sprinting. Also, it could make surrounding an enemy force a more effective strategy as they'd eventually run out of food (of course this wouldn't work against players as they would probably rather charge into their certain death than hold defensive positions for hours with next to no action whatsoever). Of course it shouldn't be a factor if the missions you play generally last less than say four hours. Except for water but I guess you could just use a game logic or a variable to disable dehydration if you can't be arsed to take a quick sip every now and then.

Even most sims, such as Falcon 4 have settings where any noob can just jump in, take off and blow shit up. It doesn't really make it less appealing to hardcore-sim people in my opinnion.

It's what you make of it.

I mean that line change is equal to ;. So you are basicly trying to do this: If ( _test==2 ) then; {; hint "2"; } else; {; hint "not 2"; }; ...which doesn't work.

If OFP scripting end-of-line is used to mark end of statement so you can't use them like that.

That would be awesome... ly useless, just like the trigger finger animation. Now if the MFDs and other displays could actually serve some purpose such as radar, RWR, AGM guidance, HSD and such, that would be pretty darn nice.

http://www.ofpec.com/COMREF/

Nah. You would just see if there's a chopper nearby the particles and apply force to them according to distance and angle. Just like the wind affects particles in OFP, only a bit more complicated. It could even be scripted if you can control the velocity of a particle after it's been dropped (or have short lived particles that create new particles where the previous dissappears (possible in OFP) and give it a new vector).

Uh... there was zoom in OFP too and it actually makes the game more realistic. Normally the field of view is too big to compensate the small area of display so everything appears way too small, like looking through binoculars the wrong way. Think of it as a way to focus further away at the cost of your peripheral vision.

I don't think that they "fucked up", they just weren't making a corridor shooter but a first person game about war, not flags and small confined spaces.

Distributing copyrighted material. It's simple, he didn't compose and make the pieces of music so he doesn't have the right to distribute them to any 3rd party even if it's for free.

I'm not sure but someone might consider it an unfair advantage if I were to script my self six Carl Gustavs in an A&D game.

Why have three guys doing what one could do alone? I'm not talking about doing a 20km march with that load out, just the 300m-1km walk from the transport to your tactical tank-pwnzoring position.

Vehicles with madar (Magic Detection And Ranging, aka "ofp radar" ) always see waypoints. Even tanks. You could disable the map and replace it with a picture you can view ingame but that's not a very nice solution. I'd remove the waypoints, you can use other means such as triggers to replace any special funtion they might serve in your mission. If they're there for a possible AI group leader you can replace them with doMove command.