james mckenzie-smith

Yes, I was afraid that's what it was. No big deal, but I will have to find a work around if I wish to have my US troops in old school BDUs for any scenarios set in the tail end of the cold war. Thanks for the (VERY prompt) assistance!

First time back here for me for a few years... I am making missions (again) in ArmA2 because ArmA3, even with the otherwise beautiful Global Mobilization mod, just cannot handle what I do, viz., the creation of single player games at the company combat team level and higher. So, I am making high command missions set on Chernarus using the US Army assets from Operation Arrowhead. Out of the box, these are in desert colours, so I have retextured certain things like the M1A1, and have used the setObjectTexture command with success. However, for reasons unknown to me, using this command with the US Army soldiers does nothing whatsoever. Code << TANK1 setObjectTexture [0, "NEWH1A1hullTex.paa"] >> works fine for the M1A1, for instance, but << MAN1 setObjectTexture [0, "NEWsoldierTex.paa"] >> does nothing when used on US Army soldiers (or USMC men). This code works fine when used on say BAF expansion soldiers from Operation Arrowhead, so I am a little stumped. Anyone know what's the deal with this?

In the Initialization field of whatever tank for which you wish to set a new tactical number, place this code... this setVariable ["LIB_Numbers",235] ...with the '235' being changeable to whatever three digit code you want. Note that two digit and one digit codes are also possible. If you do not want any code at all, put this in instead: this setVariable ["LIB_Numbers",null]

Try this: _group = _this select 0; _X action ["Eject",War_Thunder]; unassignVehicle; sleep 1}foreach units _group; unassignVehicle is a command. There is no need to replace the word Vehicle with the name of the vehicle in question.

It sounds like the paratroops are not being unassigned from the C130 after ejecting. In the eject script, check your spelling for unassignVehicle; if it is spelled correctly, let us see your code.

The icons go black when casualties eliminate the group. Are the groups starting in a location that puts them immediately under fire? If not, we could use a little info. Care to upload the mission to Dropbox or somewhere?

Use the enableSentences command. Make a trigger with the On Act field containing this: enableSentences false; If you want to change back, have another trigger with: enableSentences true; Using radio activation of triggers is a simple way to turn this on and off. Finally, you may like to try out https://community.bistudio.com/wiki/fadeRadio - as a note, I must say that I have not tried this out, but it might be useful just to reduce the volume so it's more like chatter in the background.

Re. post #4. Problem is, you are creating units with names like "_c", as in... _c = _grp createUnit ["Ins_Soldier_1", [(getMarkerPos "spwn" select 0),(getMarkerPos "spwn" select 1),0], [], 20, "CANCOLLIDE"]; ...but you are applying unassignVehicle to units with names like "c". _mg1 setWaypointStatements ["true", "unassignVehicle c; unassignVehicle d; unassignVehicle e; unassignVehicle f; unassignVehicle g; unassignVehicle h"]; Replace the above line with... _mg1 setWaypointStatements ["true", "unassignVehicle _c; unassignVehicle _d; unassignVehicle _e; unassignVehicle _f; unassignVehicle _g; unassignVehicle _h"]; ...and see how you get on. It should work as per your original intent, and you will be able to have the vehicle unloading where you want it to, and not have to rely only on enemies on foot.

Try this out: if (isServer) then { truck = createVehicle ["V3S_Civ", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; trk = createGroup EAST; ridic = trk createUnit ["Ins_Woodlander1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; ridic moveInDriver truck; grp = createGroup EAST; c = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; c moveInCargo truck; d = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; d moveInCargo truck; e = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; e moveInCargo truck; f = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; f moveInCargo truck; g = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; g moveInCargo truck; h = grp createUnit ["Ins_Soldier_1", (getMarkerPos 'spwn'), [], 0, "CAN_COLLIDE"]; h moveInCargo truck; [_grp, 2] setWaypointType "HOLD"; mg1 = trk addWaypoint [getMarkerPos 'wp_1', 0]; mg1 setWaypointType "TR UNLOAD"; mg1 setWaypointCombatMode "RED"; mg1 setWaypointBehaviour "SAFE"; mg1 setWaypointSpeed "FULL"; MG1 setWaypointStatements ["true", "unassignVehicle c; unassignVehicle d; unassignVehicle e; unassignVehicle f; unassignVehicle g; unassignVehicle h"]; mg2 = grp addWaypoint [getMarkerPos 'Z1', 0]; mg2 setWaypointType "SAD"; mg2 setWaypointCombatMode "RED"; mg2 setWaypointBehaviour "COMBAT"; mg2 setWaypointSpeed "FULL"; };

The Opfor activated trigger is designed exclusively to regulate the spawning of opfor units. If you have just one trigger set to activate by 'anyone' being present, it will spawn friendly units as well as enemy, so the Opfor needs it's own trigger there. The Blufor triggers are designed merely to tell the game that the reinforcement system should be activated once the friendly units are in position, and only then. Setting it to 'anyone' would cause the reinforcements to be activated by Blufor OR the odd civilian or stray enemy. You probably don't want that. If you need to tell the enemies already on the ground to hold back while friendlies move to fall back positions, then that's a whole different issue, and frankly one that is best solved in-game with effective machinegun employment. :) You probably could do it all in one trigger or using a sqf file or whatever. I do find that separate triggers are easier to debug, and my workflow will therefore influence my suggestions to a certain degree.

Make the condition of the trigger that we are working on to be something like: OPFORACTIVATED && "MAN" countType thisList < 2 Then, make another trigger, perhaps activated by bluefor entering the area to be defended, and an On Act with this: OPFORACTIVATED = true Add a time delay for people to get into place. As an alternative, have three triggers so that all positions must be entered in order for enemy reinforcements to be activated, in which case the original trigger's condition would look something like this: OPFORACTIVATED && OPFORACTIVATED2 && OPFORACTIVATED3 && "MAN" countType thisList < 2 The conditions OPFORACTIVATED, OPFORACTIVATED2, and OPFORACTIVATED3 would each be activated by separate triggers. Finally, consider having a radio trigger as well, that the players can activate once they are in position so as to avoid any excessive down time if they enter their defensive perimeters quicker than you expect. The On Act for such a trigger would look like this: OPFORACTIVATED = true; OPFORACTIVATED2 = true; OPFORACTIVATED3 = true;

I don't use ACE. Go to the ACE forum, someone there will know what to do!

Not really sure. Removing the brackets { } in the one.sqf file seems to work, though.

To delete the warning, click on the 'Effects' tab at the bottom of the trigger's menu. On the Edit Effects menu that pops up, just delete the text in the text block at the bottom. Just as a note, when you work with triggers, it is sometimes good to put some sort of text in the block so that at least you can tell if the trigger is firing properly. The text can be deleted when you are finished. To get the new units to move to a new waypoint, use https://community.bistudio.com/wiki/addWaypoint for info. Also, replace the On Act of the aforementioned trigger with this: null=[] spawn {"TK_INS_Soldier_EP1" createUnit [getMarkerPos "ENEMYSPAWNAREA", grpNull, "_reinf = this"]; _group = createGroup east; _reinf join _group; "TK_INS_Soldier_EP1" createUnit [getMarkerPos "ENEMYSPAWNAREA", _group]; "TK_INS_Soldier_EP1" createUnit [getMarkerPos "ENEMYSPAWNAREA", _group]; "TK_INS_Soldier_EP1" createUnit [getMarkerPos "ENEMYSPAWNAREA", _group]; "TK_INS_Soldier_AR_EP1" createUnit [getMarkerPos "ENEMYSPAWNAREA", _group]; _wp1 = _group addWaypoint [getMarkerPos 'ENEMY_WAYPOINT', 25]; [_group, 0] setWaypointType "MOVE"; _wp2 = _group addWaypoint [getMarkerPos 'ENEMY_WAYPOINT2', 25]; [_group, 1] setWaypointType "MOVE";} Note a couple of things: First, I corrected the spelling of 'ENEMY_WAYPOINT'; you will have to do so on the marker in the mission. Also, place a second marker called ENEMY_WAYPOINT2 for the enemies' second waypoint. Also, observe the numbers in red above. Those are radii of the waypoints, which is an easy way of adding an element of randomization to enemy movement. Change it to what suits you. Large numbers work well in countryside, a little smaller is perhaps best in built up areas. To add another waypoint, you would need to add the line... _wp3 = _group addWaypoint [getMarkerPos 'ENEMY_WAYPOINT3', 25]; [_group, 2] setWaypointType "MOVE" ...after the last semicolon ( ; ) but before the last bracket ( } ). You will also need to add another marker somewhere, called 'ENEMY_WAYPOINT3.

Here's a mission I've just whipped up for you... https://www.dropbox.com/sh/am3mz8o6z7djx7t/AABbYp7XHSwvU2lwMoydwFp9a Drop the mission into your C:\Users\ ... \Documents\ArmA 2\(YourPlayerName)\missions folder and open it in the editor. Be sure to activate the Markers tab (shortcut F6) to see the mission triggers. For the trigger with the condition "MAN" countType thisList < 2, you can change the number to what you want. In your case, that would probably be 21. For the On Act field of the same trigger, the unit type TK_INS_Soldier_EP1 can be changed to whatever you like. Here's the OA class name list... https://community.bistudio.com/wiki/ArmA_2_OA:_Infantry#Takistan_Militia and of course Google will reveal other classname lists for ArmA2, and addons usually have a readme with class names as well. That should be enough to get you started.