Metal Heart

But it could be a server-side option like the crosshair and 3rd person view are so it's not a valid reason.

Wrong. You can adjust mass per vertex in Oxygen Light. (but of course you can't make or edit arma models with it)

How's the windowed mode anyways? Is the "windows cursor" invisible and does it get locked when the window is active? (as in cursor doesn't escape from ArmAss to desktop and no annoying extra cursor)

It's faster to edit this part of ofp\users\name\userinfo.cfg: class Notepad { inBack=1; position[]={-0.067581,0.003070,0.320000}; positionBack[]={-0.330518,-0.011716,0.400000}; }; Exit ofp, set the first two coordinates to zero and start again. (or switch user, alt+tab to edit, switch back user) I think you could fix this by shifting the origin right in the wgl model so it wouldn't go so far left. Just be sure to move all lods by the same amount if you do this by yourself

Make a mod folder with a copy of the original file res\dta\hwtl\data3d.pbo (so it's @urmod\dta\hwtl\data3d.pbo) and put the modified files in it. You can also put the textures in that data3d.pbo, like data3d\compasstextures and data3d\watchtextures folders so they're easier to make (only have to pack one pbo for in-game test) and easier to modify later. If you have a skypack that has a data3d.pbo make the modifications there. If you're only modifying the textures, I'd still do it this way because data3d.pbo is a smaller file than data.pbo where the original textures are. (change path to textures in the model.p3d to data3d\modeltxt\ with O2 and copy the modded textures there) You could also use separate pbos but then you'd have to use a modified bin\config.cpp and that might be a problem if you play on public servers since they'd have no way of knowing what you modified in it.

Since that was already easily possible in OFP with tiny bits of scripting why wouldn't it be possible in ArmA. There might not be a hard-coded UI for it but it's quite simple to make one via scripting and dialogs. And with human squad leaders it's even simpler since the lieutenant or whatever can just use the built-in voice comms or teamspeak to command squads or even platoons. And it's possible to script platoon formations, command over invidual soldiers and such.

Open the editor. Double click on the map to insert the helo you want to train on. Start the mission. Get a hang of the controls. Imagine all kinds of scenarios and practice flying them. If that doesn't work out, you could mail me a copy of ArmA and I'll make you a 72 part training mission with detailed instructions and voice overs

Also mentioned in wiki: http://community.bistudio.com/wiki/Camera.sqs

1. Place a game logic and name it server (it could be named anything, it's only local to the server anyway). 2. Have a condition either on the exec command or in the beginning of the script that checks if the gl is local. So, if you exec the script from another script such as init.sqs: ?local server : [] exec "serversidescript.sqs" that will exec the script only on the server Or if you want the condition in the script itself: ?not local server : exit will exit the script for everyone but server

Yeah, I just got the impression that you could carry about a dozen from your post because "one after another" usually refers to more than "exactly one after the first". Personally, I like how it is in WGL. There's only so much you can do with the engine, you can't easily limit the player's movements based on the stuff he's carrying etc so it's a nice compromise.

Huh? The only launchers that can be packed are rpg-22 and m72 and you can only fit two of those into a rucksack. So a maximum of two launchers can be carried by one person. Same goes for the reloadable launchers, you can have the laucher and either one or two rounds for it.

Uh, no, Matt. That would be like an austrich burying his head would prevent everyone else from seeing anything too.

Is there a reason why something simple as this wouldnt work? Player is a function that returns the local player's character so it would return true only when the local player is near _unit thus displaying titletext only to him. ~1 is a 1s delay so the script wont be checking the distance every cycle.

Well, they're the ones who disabled the feature, why would they tell? That wouldn't make any sense.

Just move the data.pbo and data3d.pbo from dta\hwtl to dta\ and it'll probably work. ...or take the originals from res\dta and put the new stuff in them from the newdata folder of SLX. Models (p3d) into data3d and textures (pac & paa) into data.

^^ Nice stuff btw and lots of unique features! Hope you keep polishing it, right now it feels quite... unpolished. Especially the sounds get a little crazy sometimes (but maybe it just takes some time to get used to the new effects).

Some random questions... -Are there any options indicating automatic downloading of addons in the menus? -How does holding breath work exactly? (how much delay, how much does it effect aiming, how long can you hold breath) -Does toggle look key give 100% steady aim? -If you run through a forest, can the AI keep up? -Are there focal blur effects when aiming with ironsights? -Do bushes move or make sound when you run through them? -Do the light cones illuminate stuff behind them if you look through them from the side as seen on some screen shots?

You can have macro-like commands in scripts with call. Like this: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">_kill = {_this setdammage 1.0;} chop call _kill or <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">_hypotenuse = {sqrt((_this select 0)^2 + (_this select 1)^2)} _a = 3 _b = 4 _c = [_a, _b] call _hypotenuse hint format ["c=%1", _c]

Well Resistance pbos didn't open with the pbo tools that worked for CWC pbos, right? They could update the format without changing the extension, like adding a new compression that would make it unreadable by the old programs. In fact, I'm quite surprised they didn't update it.

Well Resistance pbos didn't open with the pbo tools that worked for CWC pbos, right? They could update the format without changing the extension, like adding a new compression that would make it unreadable by the old programs. In fact, I'm quite surprised they didn't update it.

Well I guess they're left out from the menus because not everyone has Red Hammer.

http://www.ofpec.com/COMREF/letterS.php#setCombatMode SetCaptive might be a better solution though, that way no one will shoot at him before you set SetCaptive false. So a trigger: west present once condition: this onActivation: hostagename setCaptive false And on the hostage's init line: this setCaptive true http://www.ofpec.com/COMREF/letterS.php#setCaptive

That's not blood, it's a damage texture. No loose blood or blood on the ground. Well that is blood though? The blood on the ground in OFP was also a texture I'd say they are more like textures that portray injuries than blood. I'm sure you know what I meant. I'm quite cerain I saw a shot where there was blood on the ground though. Don't remeber seeing loose blood, except maybe some lousy 'puffs'. And yes, Chipper, hey to you too good sir. I do care and I'm sure a lot of other people do as well. If you don't, why'd you bother to post anything on a thread about it.

That's not blood, it's a damage texture. No loose blood or blood on the ground.

The only one that might not be answered by a search on this forum is number five so: The russian voices come with the Red Hammer campaign, they are located in ofp\AddOns\VoiceRH.pbo. Names are: Aleksei Andrei Boris Georgiy Ivan Nikolai Oleg Ruslan Sergey Vadim Vitaliy Vladimir You can also use these in sp and mp as your own voice but they are not selectable via the player setup so you need to set them manually in userinfo.cfg. Other players will need to have the addon too for them to hear the correct voice of course.