pettka

I would recommend You to use the launcher of Arma 3 tools to create the virtual P: drive - it prepares buldozer.exe, PhysX libraries and necessary folders with data :icon_twisted:

08-09-2014 Size: ~3 MB Addon Builder: Fixed: Issues with P3Ds Fixed: Addon Builder failed to sign binarized PBOs Fixed: Addon destination filename Arma3Tools.exe Added: Check more dependencies on startup (Visual Runtime 2010 and 2012) Added: Log files handled by Arma 3 Tools\logger.xml are created on startup Added: Tooltip on moving over "Game Updater" Added: Menu item "View" containing links to important directories Added: About box Changed: Native methods rewritten Changed: Now mainly uses Log4Net instead of Common library Changed: Updated Application manifest Changed: Removed menu item "File" >> "Show License" because it was a duplicate Changed: Removed menu item "Misc" >> "Buldozer Configurator" (There is another link in Preferences) Changed: Removed menu item "Help" >> "Launcher" Changed: Removed directory links from menu item "File" Changed: Versioning convention (<Arma3 Tools Version>.<Release Number>) E.g. This is 0.75.1 Fixed: Icon of the menu item "Preferences" >> "Settings" was missing Fixed: A message box was displayed on startup of some tools Fixed: Mikero tools menu item in the notification context menu Starter Added: Ability to mount P drive Changed: Uses its own log file (Logs\Start.rpt) Changed: Improved log (relevance & readability) Changed: Versioning convention Changed: Now uses Log4net instead of Common library Changed: Reads only the 3 first parameters instead of throwing an error if more than 3 startup parameters are parsed Steam dumpAccountInfo Added: Returns if Arma 3 content has been marked as corrupted by Steam Added: Errors are stored in Steam_dumpAccountInfo.log Changed: Now uses Log4net instead of Common library installscript Changed: Incremented version to reflect the current stage (Development branch, RC 1) ImageToPAA Added: New classes of conversion (mask, prt, ambient_diffuse_shadow, detail_specular_diffuseinverse_map, AddAlphaNoise, TexRGBA4444, TexRGBA4444, TexRGBA1555, TexAI88, TexDXT1, TexDXT5) Steam configuration Fixed: Starting "Arma 3 Tools" directly from Steam with additional parameters (e.g. -config=server.cfg) may cause some of them to have an error on startup. Samples Added: Advanced Flight Model for the sample helicopter (including XML) Added: Example campaign from our Playable Content department (kudos to Zipper5 and ZoZo) Fixed: Class AnimationSources in the Tank sample

Thanks a lot for a great job with both this guide and guide to the sample models, I hope that You won't mind if I share the link to this thread with thanks to You :icon_twisted:

It seems to me like You are inheriting parameters form DefaultClutter without declaring it first. class StrBigFallenBranches_pine: DefaultClutter reads as "create class called StrBigFallenBranches_pine which inherits all parameters from class DefaultClutter". The compiler doesn't know class DefaultClutter because it has not been mentioned before and throws an error. The easiest way to fix it is to add declaration of class DefaultClutter at the beginning of class clutter in CfgClutter.hpp (the same way like it's been done for class CAWorld): class clutter { class DefaultClutter; class StrBigFallenBranches_pine: DefaultClutter{ ... }; ... };

I would dare correct You as the model is a brand new one, obviously based on A-10 as it is even described in the Field Manual, but made from scratch. Hellcat is based on the BAF model, but Mohawk is based on Take On model, which means it has been improved twice since BAF :icon_twisted:

I may be dumb, but I don't get the idea of pre-ordering the DLC. Our DLC strategy lets the players try the new vehicles in full quality and they may freely decide any time during trying them to buy them. I feel like this is better approach than any promises that may be twisted into whole different way (as seen even here) :icon_twisted:

Thanks a lot for letting us know. Could You, please, try to add *.p3d to list of files that should be copied (in Options)? Our programmers have taken a look at the issue and next version should do that by default, but the functionality has been unchanged from the beginning :icon_twisted:

I have been crossing mountain ranges during winter with heavy equipment, doing the same in hot summer, but I have never got a feeling that I am 53.48 % fatigued and walking to another point would take me to 67.29 %. The inputs my body gave me were roughly similar on both points, with some heavy breathing and hand shaking. Having a stamina bar feels somehow like gaming the game - "needing" some precise information to improve in-game performance, not for the feeling itself :icon_twisted:

01-09-2014 Size: ~136 MB Publisher Added: Filter text box Added: Search watermark added Added: Change notes field in summary window hidden when not applicable Added: Empty description of changes notes fields in summary window now displays meta text Changed: Reworked code base Fixed: Force steam_appid.txt load (prevent Publisher to read the Arma 3 Tools cloud instead of Arma 3) Fixed: Text boxes in the summary window having unnecessary vertical scroll bars Fixed: An invalid font family reference to Purista in labels and text boxes Fixed: Font and label in the published items filter text box Addon Builder Added: Author name is now written into the CfgPatches class before packing Added: New author option in options window Changed: The clear temp option now moves files to the recycle bin instead of doing a permanent deletion Fixed: Deletion of source data if an addon prefix is specified as rooted path (http://feedback.arma3.com/view.php?id=19265) DevP Changed: Use short paths (instead of searching and removing trailing white-spaces) MapDisk Changed: Use short paths (instead of searching and removing trailing white-spaces) ImageToPAA Added: Ability to handle TGA files created in 3D graphics software (using DirectX TGA) Arma3Tools.exe Changed: Now uses .net Framework 4.5.1 (instead of 4.0) Changed: Reworked method to launch some tools Changed: Updated manifest to handle "starter.exe" Changed: Reworked "Buldozer check" InstallScript Changed: Version (0.74) Steam Configuration Changed: Object Builder and Terrain Builder are now launched from starter.exe to fix the very common issue "Failed to attach viewer" Removed: Mounting P Drive directly from Steam Added: .NET framework 4.5.1 Note: Development branch is now the same as main branch (both are equally up to date).

25-08-2014 Size: ~10 MB Publisher Added: New version with skin and better functionality Game Updater Added: "Delete user data.bat" to erase all generated content (restore to default) Added: Log4net is now used for child processes (log file unchanged) Added: Support of Steam Guard code during the installation Removed: GameUpdater_files, now handled by "Delete user data.bat" Known issue: GameUpdater can crash your Steam client Arma3Tools.exe Added: Menu items in "File" to access some important directories Added: Warning message if a user tries to run Object Builder or Terrain Builder when Arma3Tools was ran from Steam (Buldozer won't work) Changed: Restore function to check for potential issues with Buldozer Fixed: Startup of Publisher when Arma3Tools is ran from Steam Arma3Tools Diagnostics Added: BinMakeRules to the report Samples Added: Inertia to the sample weapon Added: Insignia to the sample character DevP Fixed: Trailing whitespace in the Arma 3 path when defined in settings.ini In case of failure, a previous version can be found here: http://tom4897.info/?attachment_id=2574 MapDisk Fixed: Trailing whitespace in the Arma 3 path when defined in settings.ini In case of failure, a previous version can be found here: http://tom4897.info/?attachment_id=2574

There seems to be some issue with the Steam interface, we had similar in our offices and it seems like the only solution is re-installing the game :icon_evil:

We had some similar issues in our office at some stations, it appear randomly and re-installing the game seems to be the only solution. I am sorry to say that, but this is beyond our control :icon_evil:

The keyboard command has been added in the game engine just recently, our UI specialists are implementing it into the Configure part of the game. You may use action menu meanwhile as a temporary solution :icon_twisted:

We are investigating reports about desync issues, our programmers are working on that. There is a possibility to use Legacy build in case You are sure Your issues are because of 1.26 update, as it has been described in SPOTREP, however I would advise to verify local file cache first as there have been some issues with updating via Steam recently :icon_twisted:

It needs to be properly tested, TL;DR: It doesn't work at all now as it requires a new binarization with model version 60 :icon_twisted: Longer version: Our programmers have devised a new method of baking the PhysX mesh directly into the model itself, which may improve the performance. The only challenge is in the reversed models - most of moveable models are actually used reversed (flipped front to rear) in the game according to a config parameter. As the config may not be available during the time P3D is binarized, we want to add a new property into geometry lod that describes the model as being reversed (not so surprisingly reversed = 1;), while the binarization prepares the PhysX convex mesh during the process and turns it correctly. The game should take a look into the model and use the pre-created PhysX mesh if it finds it inside, which should be faster than creating it on the fly. Don't be afraid, if it is going to produce reasonable results, weľl let the community know, but we aim for backwards compatibility in models :icon_twisted:

It strongly depends on how the mods are done. There are some basic values set for various core classes (may possibly not hit the development branch yet), which means that at least some inertia should work for all the weapons if they inherit the core classes. And documentation has been already mentioned in the OPREP to be done soonTM :icon_twisted:

21-08-2014 Size: ~10 MB DevP & Mapdisk Fixed: P wasn't mounted on some Operating Systems (mainly Windows 7) Game Updater Added: Ability to close SteamCMD if it's already running Added: Temp log for unhandled exceptions (Arma 3 Tools\Logs\GameUpdater_UnhandledException.log) Changed: Installation path text box is now read-only, you need to click on [...] to browse and define the path Changed: System EventLog enabled Changed: Improved CrossThread operations Changed: CrossThread operations disabled on Windows 7 (denied by the system) Fixed: In some conditions, GU was unable to write the installation path to the registry, and occasionally, caused a CTD Fixed: Potential CTD on CrossThread operations Fixed: Event listener in case of unhandled exception wasn't killing the child processes Fixed: Kill every sub processes on exit (normal or CTD) Fixed: Systematic CTD during the update on Windows 7 Fixed: Some CrossThread operations were detected as illegal Known issue: GameUpdater can erase your parameters on closure Known issue: GameUpdater can CTD on startup A known solution is to add an existing path to the following registry entry: "HKEY_CURRENT_USER\Software\bohemia interactive\gameupdater" "path_d"

I'll add some documentation SoonTM together with updating the weapon sample :icon_twisted:

Problem solved, thanks a lot for participating, the thread could be closed, I think :icon_twisted:

20-08-2014 Size: ~5 MB Common.dll Fixed: The common library wrongly added some parameters in the registry (the next iteration will clean the wrong entries) Game Updater Added: Descriptive filename for GameUpdater_files.zip Note: Development branch is now the same as main branch, both are equally up to date :icon_twisted:

Strange, I'll investigate that, thanks a lot for letting us know :icon_twisted:

Could You, please, elaborate more on the way You have inflicted the damage? There is a difference between setting the damage, shooting to the rotor and the impact damage that has been added thanks to Dr. Hladik's personal involvement (the animation source RotorHFullyDestroyed described on wiki) - the first two ways don't make the rotor disappear, but hitting something with the rotor causes its destruction and it's not visible anymore (lets say it went somewhere else for sake of simplicity, but You know what's going on :icon_twisted:)

Yep, You are right, and as Killzone Kid has already done the documentation, there is nothing more to expect at this moment, more could possibly be done in the future, but no promises in here :icon_twisted:

Or You could use the new tool by Tom_48_97 called Game Updater - it's part of Arma 3 Tools suite in development branch of the tools :icon_twisted:

There's going to be a proper documentation soonTM :icon_twisted: