1nsider

Have a slight problem: radio chatter with AIs comes in incomplete chunks. Looks like it's a feature actually, but it'll be nice to have an ability to turn it back to default :) Have looked all over the code & couldn't find the proper directive. Please point to the right direction.

Guys, what were your server fps during tryouts? I've tried a mission with only one player joined, but my server fps were about minimal barrier of 15-18. Rechecked with other usual missions (incl. TFOR) - and server has shown usual performance within 30-40 fps. Tried to disable ambient civilians for 'Patrol Ops' - but server fps has gone up just a little, hitting 20fps. -- Mission's content & capabilities sounds great from the description, btw :)

Point taken.

Cannot agree, mate. ArmA's AI is a great addition to any large-scale COOP session if players know how to use them (and those who don't usually don't bother at all).

couple of minor bugs experienced with latest version (1.32) witnessed some dynamically generated objects hovering in the air, specifially - it was a camo net not far from mission area. upon respawn on FOB, one of the players have heard the siren sound (quite loud). he has been able to hear the sound continiously while he stayed at base 'blue' zone. other players at base haven't heard anything. nuke feature has been disabled in the parameters. have not been able to encounter any IED still :) -- conditions: game running at dedicated server, session lasted for about 1 hour, minor customizations were introduced to the mission setting (shouldn't had effect on game logic). cheers.

Same with me. Wanted to dedicate some proper time to research these customizations in detail. Actually, I was moving in the same direction - limiting features & resources in Dom in order to make it a bit more edgy. Though I'm not sure if limiting certain vehicles to certain classes only is a good idea. If players are cooperative - they probably will not steal & use vehicels inappropriately, while not being able to use vehicles in certain conditions (to help your own teammates for example) could ruin the experience.

that was some busy saturday night huh

The script helps to add some ambient threat to the map by randomly placing an enemy outposts all over. But nevermind, actually, I've realized that WiT generates some ambient threats near the main objective anyway + not a lot of players would like to get shot at all the way across the map. makes sense

thanks, i think other players might like some ambient sounds as well. a couple of other suggestions: to change AI recruitment dialog in a way that dialog window will not close after recruiting the AI soldier every time or to borrow the bon_recruit_units script (very handy piece of code) to change one of the UH-60s to a Little Bird with FLIR (ACE) or Venom with FLIR (comes in vanilla ArmA) in order to have not only a transport chopper, but a recon chopper as well i believe someone has asked for this one already - to have an ability to recover wrecks of own vehicles in Sim mode also, I spice WiT up a bit by adding Bon's enemy_camps script from TFORCEs And thanks for the mission, btw - it turned out to be a lot of fun, specially for low number of players (who knew, huh). I play it rather a lot recently, on my own, when there's not enough of fellow players for a proper TFORCE coop.

understood, thanks for clarification. will look up & turn it on in the code now :) rain with no sound makes it too creepy of an experience -- looks like changing enableEnvironment in init.sqf from false to true does the trick

it seems that there's some issue with an ambient sounds - like rain/wind, they are just not present. just checked with 1.32 in simulation mode & rechecked in other missions to be sure that it's WiT-related only

Start the server by arma2oaserver.exe & start the actual gaming session at the same pc and then join the server.

As far as I can tell - there are changes in big chunks of 2.60's code, comparing to 2.59.

That is some great news, looking forward to try it out this weekend. Once more - encourage everyone, looking for quality COOP sessions to give TFORCE a test. Haven't been able to find anything better, and trust me, I was trying hard. In the end - just chose to stick with TFORCE, introducing small tweaks of my own here & then (which is incredibly easy to do since the code is as clean as it gets).

Having troubles loading the mission after an update "You cannot play/edit this mission; it is dependent on downloadable content that has been deleted. acex_sm_c_sound_wep_mg" Error has been reproduced at the other, completely separate, machine as well. Before update - fine. After update - the above mentioned troubles. -- added: also, if the LandRover_CZ_special is present on the map, the following error appears "No entry 'bin\config.bin/CfgVehicles/LandRover_Special_CZ_EP1/Turrets/AnimationSources.minElev'." the error has been reproduced on a separate setup as well

Are you referring to an ability to recruit AI units as part of friendly squad ? If so - it's not that hard to do by utilizing 'bon_recruit_units' script (for example) & adding the action on Mobile HQ.

Yes, looks like this setup should work just fine as well (proven that router is forwarding ports correctly I guess). In my case the problem was (and still is) of the other sort: one particular guy can join the server & can see the lobby, but he can't receive the mission fully & it's never ending 'waiting for host' for him. I'm thinking that something messed up with network-related server configs... Would have to reinstall & reset everything to defaults.

Sry, mate, I haven't thought about making the code look properly - just was trying to illustrate the idea. By the way, those AI soldiers cannot use their backpacks, as you probably know. So I've made one more trick with them. Seems like game engine does not track the inventory slots available for AI guys and you can actually put a lot of stuff in 'em, even without a backpack. So something, like that ... {_unit addMagazine "30Rnd_556x45_Stanag"} forEach [1,2,3,4,5,6,7,8,9,11,12]; {_unit addMagazine "HandGrenade_West"} forEach [1,2,3,4,5,6]; ... would actually work (notice the amount of mags - it all gets added to the usual unit loadout & we're adding the stuff not into the backpack here, but to the main inventory). But backpack helps to keep it realistic in a visual way + it's a very useful tool for other human players in game. I've stocked AI specops guys backpacks with satchels for example, so whenever I take them on the mission with me - I can be sure that I'll have explosives easily reachable. Also this kind of a 'bug' comes very useful when you try to use AI medics with ACE WOUNDS system.

Thanks for confirming - still get my head around some of the ARMA2 specific script techniques. atm, I've made my changes like that (scripts\enemy_camps.sqf): (some tfor_ variables are changed to the constants here) ... While{true} do { _campchance = 0; While{{side _x == west} count nearestObjects[_this,["Man","LandVehicle","Helicopter","Plane"],2500] == 0} do {sleep 10}; _campchance = floor(random 2); if (_campchance == 1) then { _campstrength = floor(random 3); _campstrength = _campstrength + 4; _grp = [east,_campstrength,_this,50,"militia"] call spawnInf; }; While{{side _x == west} count nearestObjects[_this,["Man","LandVehicle","Helicopter"],3000] > 0} do {sleep 10}; if (_campchance == 1) then { {deleteVehicle _x} foreach units _grp; sleep 2; deleteGroup _grp; }; }; ... This way it's possible to encounter an empty camp & camp strength is different. Should be a little bit more interesting for the friendly forces, roaming the map. Added some random snipers appearing near the camp locations as well :)

I'm looking for a way to modify enemy camps logic a bit, could anyone experienced enough please provide advisement on the following. The file is 'scripts\enemy_camps.sqf' From line 40 there goes a code creating a camp & populating it with bad guys: ... if(count _pos > 0) then{ _camptype = ["tentcamp_1","tentcamp_2","bunkermedium_0","bunkermedium_1","bunkermedium_2","bunkersmall_0","outpost_1","guardpost_0","guardpost_1"] call getRandomElement; [_camptype,round random 360,_pos] execVM "dyno\objectMapper.sqf"; ... I'm not sure what happens from line 43: ... _pos spawn { While{true} do { While{{side _x == tfor_friendly_side} count nearestObjects[_this,["Man","LandVehicle"],1000] == 0} do {sleep 10}; _grp = [tfor_enemy_side,5,_this,50,"militia"] call spawnInf; [_grp,_this] execVM "upsmon\init.sqf"; While{{side _x == tfor_friendly_side} count nearestObjects[_this,["Man","LandVehicle"],1000] > 0} do {sleep 10}; {deleteVehicle _x} foreach units _grp; sleep 2; deleteGroup _grp; ... As I understand it - the camp stays inactive unless any man or vehicle of friendly side enters 1000 radius, then it gets populated with milita infantry. And if friendly forces leave the 1000 radius - the spawned milita groups get destroyed (to free up CPU I guess). Then if friendly forces enter the camp - it gets repopulated all over again. Am I right ? -- What I'm looking for is to extend the functionality: to introduce some chance that camp will be populated at all (or not) and to increase the chance for the camps that are further away from the friendly base (or even better - further away from the zones of high player activity).

Looks like it indeed, everything goes down to routing issues. When I was trying the following setup: INET CABLE -> HARDWARE ROUTER -> LAN (where the server with ARMA + my home PC were present) = there were routing troubles apparently. I've tried the following setup: INET CABLE -> SERVER with ARMA (+ doing the routers job with RRAS/NAT) -> LAN (including my home PC) = it worked out. Have made only a brief tests with default setup + stock missions, though. But it shouldn't be different for ACE tweaks + custom missions anyway. If it'll be - I'll update accordingly. -- btw one doesn't need a separate CDKEY for ARMA stand-alone server, right ?

I have exactly the same question - struggling with the setup of a stand-alone server, so it would accept connections from the global inet & server connections to the LAN as well.

With OA units - surely it does. Though it's not much of my script, bon made all that - I've just tweaked a very small part based on recommendations in this topic.

What about respawning an ammo crate after a certain period of time in case it's not present anymore on initital spawn location (but crate itself is still intact) ? I would like to use the ACE transport containers in a way that if players take one with them - another one will respawn on the initial location after 60 mins (for example) as a substitute.

Well, as the script itself is written very well - it's very easy to make a clean adjustment in init_newunit.sqf as suggested. Mine looks like this: //add backpacks to specific units switch (true) do { case (_unit isKindOf "US_Soldier_AAR_EP1"): // Assistant MG (M249) { removeBackpack _unit; // not needed most probably, but just in case _unit addBackpack "US_Assault_Pack_AmmoSAW_EP1"; }; ...