Search the Community

In this thread we'll try to describe updates happening in the Development branch of Arma 3. This changelog is not complete, nor confirmed to be working as advertised. Again, Development branch does not pass internal QA before publication. Stick with main branch if you do not want to deal with the (big) potential issues and frequent data transfers. Feel free to discuss the updates to this branch in the relevant thread. 12-03-2013 Cross-joining default and Development branch disabled in MP Ifrit config class names changed to O_Ifrit_F and similar Various artwork fixes and tweaks in materials, textures and passenger animations Active Development branch is now indicated in the main menu Showcase: Helicopters - little optimization and conversation timings Various other showcase fixes Multiple crash opportunities fixed First tests of shadow improvements

In this thread we'll try to describe updates happening in the Development Branch of Arma 3 Tools. This changelog is not complete, nor confirmed to be working as advertised. Again, Development branch does not pass internal QA before publication. Stick with main branch if you do not want to deal with the (big) potential issues and frequent data transfers. Feel free to discuss the updates to this branch in the relevant thread. The changes are not going to be done daily like the Arma 3 development branch does, but rather in irregular intervals according to needs and additions by our team. 20-06-2014 Fixed: Broken Addon Builder UI Fixed: Copying of files to the target destination in Addon Builder Fixed: "External" feature of Tools Launcher was disabled by error

Sometimes it's useful to discuss updates to the Steam Development branch in one centralized place. Let's use this thread for that. The changelog thread can stay clean and do its thing. It mainly serves for our team to rapidly see if a daily update is very broken or very epic :ph34r: Actual issue reporting should still happen via the Feedback Tracker of course. Thank you!

In this thread we'll post announcements about Release Candidates (RC) of future main branch updates. That includes the opening of the RC-Branch ahead of an update, possible change logs between RC updates and details on (multiplayer) stress tests. This thread itself will remain closed to allow for a clear overview of announcements, please feel free to discuss this branch here.

WORK IN PROGRESS https://www.youtube.com/watch?v=K6LDXK1URr8 I've decided to openly release a very basic version of iBuild for testing. The main reason for this is to test the underlying foundations and iron out any kinks before I start piling new features and content on top. It's very basic and rough, but it has enough content to give you an idea of where it's heading. The mod has evolved from the first conceptual prototype I put together, and I've lost count the amount of times I've started over, so I hope you guys enjoy what I've settled with. I'm still in the process of writing most of the documentation, which I suck at doing, but you can find what has been written so far organised into a drop-down menu under 'iBuild'. More info can be found in the description on Steam. >| Download Pre-Alpha |< About time! ;)

Hi, there When it's possible/useful, we will try to post brief descriptions of recent AI changes done on the development branch. We hope this will help demonstrate the tweaks that we're making and generate useful feedback to help us validate and polish our work. For now, the first batch of notes to kick things off: It wasn't supposed to fix rotation speed of AI soldiers, but is letting them use "aiming deadzone" as specified in the unit config (minGunTurnAI, maxGunTurnAI) which is typically 60 degrees cone. Therefore currently AI should be able to follow targets better without moving whole body. RPG and NLAW are supposed to be unguided, but AI was still able to use them as guided weapons. This was corrected. Quite big change, now AI is able to calculate and predict accurate ballistic of bullet, therefore is able to aim and engage targets on all ranges, both static and moving. Also, this improves AI ability to hit moving targets by more precise time of leading calculation. Good way to check this change is try to fight AI sniper on 1km+ range. Of course it still depends on his skill. AI was considering animals as friendly, therefore denied to shot in theirs direction. Example: put yours character, enemy soldier and snake animal between you. After this fix AI won't bother with friendly fire against animals.

Next to already revealed an known https://community.bistudio.com/wiki/Category:Arma_3:_New_Scripting_Commands_List There are more script commands now :) + fixed http://feedback.arma3.com/view.php?id=12324 + only discussion related to new or changed Arma 3 Beta/Dev Scripting allowed

Please use this thread for discussion specific to the Release Candidate (RC) branch on Steam, when it's available in the weeks leading up to a release. The preferred method of reporting issues in that build is the Feedback Tracker. Thanks!

Hi there, in the recent update of development branch you will find the new version of announced (http://dev.arma3.com/sitrep-00030) fatigue mechanics improvement which we prepared for you. As the design of such an important feature is inevitably burdened by many subjective feelings and opinions we decided to inform and discuss it's implementation with you. Therefore I would like to gladly ask you for a valuable, constructive and civilized feedback upon the issue. Hopefully, it will help me a lot to tune that feature according to your sound objections, good suggestions and overall gameplay feelings. So, this update will affects three main issues: 1) Animation slowdown. The more you are fatigued, the more sluggish and cumbersome all your movement becomes. Simple as that. However, not every animation could be slowed down by the same degree without odd side effects. Thus it's quite tricky to set up the values for every respective animation correctly. If you find out some unexpected motion that goes simply "too slow", please, let me know. Also I would like to hear from you if the current overall slowing isn't too much, or if you generally feel that it could be even more severe. As I said, it's very subjective issue and many different opinions will arise for sure. 2) Fatigue gain from inventory load. The more you are loaded, the sooner you get exhausted by doing exhaustive actions. I've made the progress of fatigue gain from inventory load much steeper to force you to consider your carried equipment with greater care. Let me know if it's not too punitive, or, if you feel that it could be even more severe. 3) Weapon sway. Believe it or not, weapon sway behavior is inevitably connected to fatigue. Thus the recent changes will certainly have an impact on it. We wish to improve the sway mechanics even further, so every feedback regarding this issue, regardless if it's just personal opinion or shooting range testing video, will be also much appreciated. Thanks in advance for your feedback and stay tuned.

Sometimes it's useful to discuss updates to the Arma 3 Tools Development branch in one centralized place. Let's use this thread for that. The changelog thread can stay clean and do its thing. It mainly serves for our team to rapidly see if an update is very broken or very epic. Actual issue reporting should still happen via the Feedback Tracker of course. Thank you!

I've very nice news about headless client (HC) which is variant of dedicated client for server use we will be rolling out soon (days) new test version for both linux and windows - no more steamclient nor steam account with game ownership needed for HC - HC needs only steam dedicated server binary and set of commandline params - auto-connection recognize & detection of HC by server (server needs some config to allow that) - multiple HC per server are supported - HC can be primary used to offload AI work and secondary for some script jobs - logic for mission & scripting operations with HC introduced - HC are autoassigned to slots - HC are not visible to players - HC are visible to admins - HC isn't counted against playercount in server list - BattlEye supported (1.36 RC2 released 28.11.2014 18:00 CET) today's DEV: •Added: Enable new headless client implementation - see https://community.bistudio.com/wiki/Arma_3_Headless_Client for more details note: known limitation, none (except some AI bugs, need repro/confirm) note: what needs to be somewhat tested/determined/improved/changed is disconnect & reconnect of HC and all related to that post bugs, feedback and ideas below

We'd like to try using this thread to track clear updates about changes to the AI. But first, some all important disclaimers! Not all the changes made to the AI can be logged as and when they happen Sometimes the changes made by the programmers require other departments to update or pack their data Sometimes that's not always possible right away (i.e. changes to AI Costmaps for terrain, tweaking of new/refined values in configs) Sometimes the changes must be put on hold while we make sure/prevent them from entirely annihilating the rest of the game Sometimes the changes must be reverted because they destroy more than they heal. Sometimes our programmers have to work, rather than talk about working. We hope it helps shine some light on the ongoing refinements/fixes being made to the AI, and can help to frame/promote some useful feedback/discussion/understanding about the current state/future direction and progress. You can discuss the changes across in the AI Dev Branch Discussion thread. Best, RiE First set of notes follows: It wasn't supposed to fix rotation speed of AI soldiers, but is letting them use "aiming deadzone" as specified in the unit config (minGunTurnAI, maxGunTurnAI) which is typically 60 degrees cone. Therefore currently AI should be able to follow targets better without moving whole body. RPG and NLAW are supposed to be unguided, but AI was still able to use them as guided weapons. This was corrected. Quite big change, now AI is able to calculate and predict accurate ballistic of bullet, therefore is able to aim and engage targets on all ranges, both static and moving. Also, this improves AI ability to hit moving targets by more precise time of leading calculation. Good way to check this change is try to fight AI sniper on 1km+ range. Of course it still depends on his skill. AI was considering animals as friendly, therefore denied to shot in theirs direction. Example: put yours character, enemy soldier and snake animal between you. After this fix AI won't bother with friendly fire against animals. N.b. Sometimes I'll quote one one of our Programmer's comments, but reserve the right to make splendid editorial adjustments! :cool:

First: all credits belong to Snake2200 the author of the big and excellent XAM1.06b-modifikation for ArmA1. you can download the hole addon for ArmA1 here: http://www.armaholic.com/page.php?id=1756 -this mod is not from me, it is only a part of the Xam1.06b-mod from Snake2200 -I have only edited the mod a little bit (logic,sound balancing)that it works with ArmA3. Thanks to kju for pushing me into the right direction and also to (Snake2200 wherever he is)! -This addon gives you: -excellent nature ambient-sounds -churchbells with different distances -different windsounds on hills ..etc. -mornigbirds (excellent for europe) -at night wulfs, owls ..beware ..sometimes scary ! -on the field sparrows, larks, robins..etc. -multiplayer not tested -no bi-signs included and i am not able to create some -first shot error included ! ...and not yet repairable for me Installation: -note: CBA is needed for this. 1.copy "@xam_environment.pbo" to your ArmA3 root directoy 2.edit your shortcut for ArmA3 or use a Launcher you like to start. ps:enjoy it or leave it... for me me its a musthave... at least the file http://www.file-upload.net/download-9091901/Xam.rar.html

This is the place to find latest info about suppression mechanic in Arma 3 and also the place to post feedback about it (mainly about features already implemented in the game). Suppression mechanics in the game Mechanics, rules and outcomes implemented in Arma 3 up to date AI looses good aim when under fire Basic info: AI gets suppressed by bullets flying by, nearby bullet impacts, explosions and by direct hits. Every single such "event" increases the AI suppression by small increments from 0.0 to 1.0. (it is possible to fully suppress the AI with about 5-10 bullets) The suppression continuously decreases in time. AI with higher skill recovers faster (at avg. skill it takes several seconds while @ skill 1.0 the recovery from suppression 1.0 is almost instant) The more powerful ammunition the bigger the beaten zone. (the more powerful ammo the slower the suppressive effect decreases with distance from the target when compared to a weaker ammo) The suppression doesn't have any immediate effect on units in vehicle turrets (incl. static weapons). But it still has an effect on units that are firing from the vehicle with personal weapons or units that have disembarked the vehicle. Configuration and script commands - AI prioritizes cover that is not suppressed Basic info: When selecting a new cover position the AI prefers a position that is "under control" of its own side It hasn't been under enemy fire recently It is not in the fire sector of a superior enemy force Feedback tracker: AI Suppression Player Suppression Known issues: Suppressive fire command doesn't work

The VhC is the new system responsible for the customization of vehicles, either, defined or randomized. It consists of a set of config properties and classes and a set of functions. It has been introduced in order to replace the old system which consisted in a set of scripts. [vehicle player, ["blu",1], ["AddBenches", 0, "AddTread", 0, "AddHoldingFrame", 1, "AddTread_Short", 1]] call BIS_fnc_initVehicle; More information available here: http://dev.arma3.com/post/oprep-vehicle-customization Usage for designers Mission designers will find what they need with the following examples, which cover most of the cases of use of the system. In addition, an example mission has been published in dev branch of Arma 3 Tools. Parameters: 0: vehicle to customize 1: Variant (textures) BOOL - true to restore default texture source ; false to skip texture source change VOID - Nil to skip the texture source change ARRAY - Array of texture sources with their given probability: ["textureSource1", 0.5, "textureSource2", 0.5] STRING - Variant class name(from the configFile >> cfgVehicles or from the missionConfigfile >> cfgVehicleTemplate) SCALAR - index of the texture source (same as the old system) 2: Animations BOOL - true to restore init phase of every animation sources VOID - Nil to skip change of the animation sources ARRAY - Array of animation sources and probability: ["AnimationSource1", 0.5, "animationSource2", 0.5] STRING - Variant class name(from the configFile >> cfgVehicles or from the missionConfigfile >> cfgVehicleTemplate) Examples: Do nothing because default VAR texture and VAR animation are "false" result = [this] call bis_fnc_initVehicle; Restore default texture and animation sources (reset) result = [this, true, true] call bis_fnc_initVehicle; Randomize everything according to the config file result = [this, "", []] call bis_fnc_initVehicle; //<-- Prefered result = [this, "", ""] call bis_fnc_initVehicle; Skip everything result = [this, nil, nil] call bis_fnc_initVehicle; //<-- Prefered result = [this, false, false] call bis_fnc_initVehicle; Apply the given texture and ignore the animations Priority is given to [missionConfigFile, "CfgVehicleTemplates"] result = [this, "TemplateName", nil] call bis_fnc_initVehicle; random weighted on the given texture sources and their probability, then randomize the animation sources according to the config file result = [this, ["MyTextureSource1", 0.5, "MyTextureSource2", 0.6], []] call bis_fnc_initVehicle; MyAnimationSource1 phase has a 50% chance to be set to 1 and MyAnimationSource2 has a 70% chance to be set to 1 result = [this, nil, ["MyAnimationSource1", 0.5, "MyAnimationSource2", 0.7]] call bis_fnc_initVehicle; MyAnimationSource1 phase will be 1 whereas MyAnimationSource2 will be set to 0 result = [this, nil, ["MyAnimationSource1", 1, "MyAnimationSource2", 0]] call bis_fnc_initVehicle; Change animation sources with a given template result = [this, nil, "MyTemplate"] call bis_fnc_initVehicle; Usage for Modders On the other hand, in addition to the documentation (still wip), modders will find examples of implementation in the samples (car and boat) of Arma 3 Tools (dev branch only for now) As per usual, issues, feedback and suggestions are very much welcome :cool: This feature is still actively developed, meaning it will be adjusted and extended during the upcoming weeks. To be 'extended'...

Hi all - just a quick question, I'm not sure if it's feasible - but... I was wondering if one can force a vehicle to move along the road despite a unit being on it. Essentially, I want to disable whatever it is that forces the object to stop, because it detects it will collide with another object. Ordinarily, I'd just use the unitCapture function, but as we all know, it doesn't work well on land based vehicles. The problem I'm trying to resolve, is to have a vehicle stop at a checkpoint when the AI's driving. Unfortunately, because there are units at the checkpoint, it is causing some odd behaviour and the vehicle does not stop very close to them. Either that, or the vehicle goes off the road, or veers to one side. Any ideas? :D Thanks as always, in advance guys!

***If you do not have a way to view this video in 3D you can turn 3D off and watch it in normal 2D in the settings below the video. For those of you that have 3D glasses, 3DTV or 3D monitor.....prepare for bombs and bullets to fly out of your screen

Greetings! I'm currently building a Mod Database app and I'd like to collect feedback as to the attributes that I am assigning to each mod. So far I have: Category Tags Requirements (Tags) Author Images 1/2/3 Featured Image Youtube Link Version License License URL Code Repo URL (Bitbucket/Github/Other) Mod Website Overview Features Changelog Credits Excerpt BIS Forum Link Any missing or not needed/redundant? Second question, should I allow anyone to add to the database any mod/mission or should only the author be able to?

This is a small units addon I'm using for my gaming team needs so I've decided to also puplish it for anyone else might find it useful. It is based on simple retexture presenting some ISIS warriors (Islamic State). These units are using default A3 weapons and there is no other mod or addon dependency ... you can find all classnames into the txt file included (also a server key is included). Nothing fancy ... just some units. Note : into classnames txt file I forgot to mention some backpacks classnames ... so here they are ... Download Link : REMOVED THIS ADDON NO LONGER SUPPORTED AS IT SEEMS THAT MANKIND STUPIDITY HAS GONE TOO FAR (see quote below) Aplion

Hello everyone! I know it has been some time since we updated the main branch, and there is a good reason for it: Multiplayer. Yes, that's right, in case you have not been following things on the forums or the development build, Take On Mars now features multiplayer. At the moment this includes a cooperative mode where players can build bases and vehicles together. As I am sure many questions will come up surrounding this, I'll try to answer a few straight away: Q) What is currently possible in multiplayer? A: Everything that is possible in single player with the Mars Astronaut. That includes the following: * Building habitats from individual pieces * Printing building pieces and vehicles via the 3D Printer * Mining materials from the location, however the materials themselves are not used yet * Driving vehicles, including with friends * Full physics simulation over the net * Having fun! Q) Who can start a server? A: Anyone can start a server, simply select Multiplayer in the main menu and select Create Game. There, choose a scenario and begin! In case you are wondering who will be able to see your server, the answer is anyone! Q) I built an awesome base with a friend, but don't want to lose it, can we save the game somehow? A: Yes, the multiplayer implementation features a unique saving system. Connected players may vote for a save or the server may initiate a save directly. The server saves the game to his hard drive and sends the save file to all connected players. This means that any one of those players may then re-host that save in their own server. Q) Are our characters and their last known positions stored in the save? A: Yes, each player that joins has his character stored exactly where he left it. This can be on a hill, in a base, or falling off a cliff. In all situations, the character is stored with his health and everything intact. We will be adding an inventory soon, so the storage of your items will also be guaranteed. Q) When can we load a saved game? A: When you start to host a server you can select to start the server from stored save games on your hard disk. Information about the save is displayed when you select it. Once you start the server anew or from a save, you can load the game at any time via player vote or directly by the server. The interruption in play is very short. Q) Will future builds render my save incompatible? A: No, the save files have been written to save in a format which ensures compatibility between builds. They are in fact stored almost identically to a scenario file. Q) Take On Mars has very detailed physics simulation... Is that present in multiplayer? A: Yes, everything in multiplayer and single player is fully physically simulated, which includes vehicles, characters and so on. Yes, this does mean vehicles can be smashed in multiplayer :) Q) Did you say save similar to a scenario? Does that mean we could adjust a save into a scenario? A: Yes, a save is similar to a scenario, so with some minor editing a scenario may be derived from the save. We intend to add an option to Export Save To Scenario soon. Q) It crashed... What do I do with the crash info? A: If you started in Developer mode (the yellow Play Game button in the loader), then it could help us track down the bug. When you see the crash window appear, press Ctrl + C and then paste it into a new thread or post on the forums, along with as detailed as possible set of steps as to how the crash occurred. We do not expect you to test the game for us of course, but will appreciate feedback and bug reports :) Q) What can I expect in the next update? A: Survival elements, including oxygen simulation, using mined resources to fill habitats with air, a flatbed-truck-like vehicle for transporting larger cargoes, and an inventory for objects such as soil samples, food and water, etc. Q) When can we expect another update? A: I am heading on a 3 week vacation as of the 30th of August and will return on the 18th of September, so expect full-speed development to continue then, with an update following within two weeks. Q) Just tried the multiplayer, love it! How can I help? A: Thank you! We always appreciate when our games are enjoyed :) You can help us by giving us feedback, posting screenshots, sharing videos and spreading the word if you like it! Q) I recall the expected release date being at the end of August... Is this still true? A: In short, no. We have pushed the final release date back to allow for proper and full implementation of the multiplayer features as well as the entire Expedition One addition, both in terms of single player (Space Program) and multiplayer (survival elements, base management, additional game modes, etc). This is good news as you get highly refined content, and more of it! Q) What has changed in the game? Any chance of a change log? A: There is a change log directly accessible through the main menu, top right corner as Change Log. Alternatively, check here: mars.takeonthegame.com/changelog/mainbranch Q) I'm enjoying the game, but want to finish my in-progress Space Program. Can I go back to a previous build? A: Yes, we have added a build titled 'Legacy', which is the previous Main Branch build. Switch to this if you want to continue using the older build for now. To switch to the build, select Take On Mars in your steam library, right-click, select Properties. Switch to the BETAS tab, and select 'Legacy' in the list, ignoring password input. Q) Sounds great... Screenshots or it didn't happen!!! A: Of course, screenshots are mandatory :) There have been plenty released over the past few weeks as we have been testing the builds. Here are some highlights: Collaborative building with the 3D Printer: http://steamcommunity.com/sharedfiles/filedetails/?id=306547495 Base interior, under construction: http://steamcommunity.com/sharedfiles/filedetails/?id=305677900 Physics... Forklift lifting Scout Buggy: http://steamcommunity.com/sharedfiles/filedetails/?id=304590734 After over 5 hours of printing and building, and composed of over 800 individual pieces, a bridge coming together on Mars, across Victoria Crater: http://steamcommunity.com/sharedfiles/filedetails/?id=304790952 A player standing on the edge of the bridge: http://steamcommunity.com/sharedfiles/filedetails/?id=304790913 We really hope you enjoy the newest update! Please keep in mind this is an Early Access game, and bugs are to be expected. We are sorting them as fast as we can, and apologize for frustration some bugs may cause! Kind and sincere regards, Martin Melicharek (Project Lead)

I am wanting to re-texture Hunters for use in a PMC clan but cant seem to find any psd templates anywhere..are these available anywhere or even possible to get? I did a search and only came up with Infantry templates no vehicles..any help would be appreciated. Diesel

Hello everyone. First off, we apologize for the lack of updates, we are hard at work on the Global Objectives system, the Technology Tree, Mars 3 as a vehicle, and the landing systems overhaul. These changes are quite vast and certainly game breaking until completed, hence the lack of updates. By the end of the week these things will be completed and normal daily updates to the development branch will resume. The main branch will also be updated by the end of the week or early next week. Admittedly we should have kept more in touch with you guys during this process, but there was so much to do that we needed to keep our minds set on the goal. Here on out, we'll make sure to let you guys know what is happening so that noone feels either left out or worried about where the project is headed. I look forward to feedback from you guys about the changes, a lot to look forward to!

Why is setovercast still not working? This is really some kind of joke. Instead of tweaking uniform patches and colors, this seems to be more important...

Hi, What happened to "Seek & Destroy" behavior, I can't find it anymore ?? Regards, Alain

I am using the latest arma 2 combined operations beta patch (build 107882) along with these command lines -nosplash -maxMem=2047 -cpuCount=4 -exThreads=7 Just recently got a new SSD. Idk why it stopped me in middle of game. Did a google search and nothing came up for Battleye Corrupted Memory #55 I knew that battleye had a update recently.