tehsleuth

According to the dev branch field manual entries, the Hatchback also has a 'sporty variant', which I would assume is the same sports car we saw previously. As for the repair truck and police car, those exist in the beta right now; just not accessible without scripting. Another interesting tidbit - the field manual also lists a 4x4 truck with 3 variants, as well as an Offroad armed with a .50 cal machinegun.

The above script would only remove the NVGs from BLUFOR soldiers, not OPFOR or Greenfor soldiers. You'll need to use NVGoggles_OPFOR and NVGoggles_INDEP for the classnames, respectively.

I don't believe this is possible via scripting; you'd need to make a config.cpp and load it into the game as a separate addon. Here is the cfgVehicles config reference: http://community.bistudio.com/wiki/CfgVehicles_Config_Reference Edit: The parameters you're looking for is displayName and displayNameShort.

It's due to the introduction of vehicle freelook in the options. Turn that off and see if that fixes the issue. (It's under Options / Game / Vehicle Freelook)

I believe that muzzle_snds_H is the 762x51mm silencer. Try muzzle_snds_L, that should work.

Here is the class names for the crew helmets: For Blufor: H_HelmetCrew_B For Opfor: H_HelmetCrew_O For Green Army: H_HelmetCrew_I

According to the ArmA 3 twitter, it will be available on Friday.

You could try putting this in the condition field of the trigger: soldier1 in thisList That will check if the unit is in the triggers radius. Also, my apologies for not clarifying about the canMove command. Glad you figured it out though :-)

For your first question, check out the canMove command. Using a trigger, put something like this in the condition field: canMove heli1 From there, you could use the new BIS_fnc_endMission command to end the mission if the heli can no longer fly. The second question is a bit different since there really is no particular way to have them land in an exact spot. Try putting down an invisible helipad (located under Empty > Objects (Signs)) and attach a transport unload waypoint there, and in the on act. field type this: heli1 land "LAND" This will essentially force the helicopter to land within 50m of the helipad. (the AI will try to land squarely on top but be careful if the landing zone is close to buildings or trees) As for the artillery modules, I'm quite certain that the modules do not currently work (though I haven't personally tested them) but you can find them under modules > support. Hope this helps out a bit. :-)

I'm afraid Altis will not be in the beta, but the devs have said it may make an appearance on the dev branch a couple of weeks before the full release.

You'll need to use the groups tool (F2 key). With this, you can drag lines from unit to unit and create groups. Also, for future reference, try using this for questions about mission editing. :-) EDIT: You can also double click when the groups tool is selected and create pre-defined groups such as fireteams, squads, etc.

I mean you no offense here, but have you not seen what every 'optimization' thread turns into? If not, take a look at the last few pages of this thread. It doesn't have anything to do with a coverup or otherwise, it simply comes down to people attacking each other, which is obviously not the intention of the thread in the first place. If you also take a look here, you'll see that the developers have replied to the ticket and have been actively working on optimization; but, it's not as if it is an overnight ordeal. Things such as this take time, and we may not see any significant improvement until the full release.

The key for laying smoke screen is G. For the speedboats, you have to be the driver to deploy smokes - same with the Ifrit. The Ka-60s flares are deployed the same way.

I believe they've stated that the dev branch will feature the beta content the day after E3.

I don't believe it's been announced that there will be any other islands included in the Beta; however, they will be at E3 from June 11th to June 13th, so I would assume we'll get an announcement then.

Check out this page. The prices of the beta / final release are listed above the system requirements.

Just as a heads up, you may want to try this topic for questions about mission editing. As for your question, try changing your picture from jpg to paa format and see if the issue persists.

The most recent update from 0.54 to 0.56 removed some scripting commands from the game. Take a look at the latest spotrep for details.

Unfortunately, you can't build mortars due to a bug; however, when it is fixed, all you would need to do is equip the static mortar bag and walk over to the Mk6 Mortar bipod bag and it would add an action to assemble the mortar.

This is due to some scripting commands being removed from the game due to a security breach. More info on that in the latest spotrep.

@OP Take a look at this thread. If that doesn't work, you may need to restart your steam client and check the beta tab again.

If you're looking for the class name of, lets say, a vest, put the following code into the units init line: hint format ["%1",vest this]; The above code will put a message in the top right of your screen displaying the class name of the vest the unit is wearing. There are several other commands you can use as well, such as uniform, goggles, headgear, and backpack. If you want to return the class name of a vehicle or soldier, use typeOf.

The only error I see in that code is that #include doesn't require a semi-colon at the end if I recall correctly. I'm not sure if that would solve the issue or not though. Also, this forum topic is for posting completed user-made missions. You will want to use this forum topic instead.

Simply place down an invisible target soldier under the independent unit tab in the editor and group him with the unit you wish to be independent.

The Steam version of the ACR DLC, for some reason, never runs the actual setup for the DLC. It just downloads the files onto your computer. The way I managed to get it working was to go to the store page for the DLC and hit the 'Play Now' button below the screenshots on the page. It should then run the setup and hopefully work as intended.