Tom_48_97

What are your buldozer options in Terrain Builder?

12-04-2017 Size: ~1.7 MB TOOLS Buldozer Configurator Added: Enabled log in retail Changed: Now uses the project drive path from the tools settings when the path isn't specified or mounted Fixed: The error BCFG0001 was sometimes thrown for incorrect reasons Work Drive Fixed: The install of Buldozer was incorrect Arma 3 Tools Launcher Added: Automatic patch of the Buldozer install when necessary Diagnostics script Added: A message Box on startup of the diagnostic containing the destination file Fixed: The destination file mentioned in the console was incorrect DevP Fixed: It was blocking the end of the diagnostic script Steam configuration Changed: Incremented version to reflect the current stage (1.091) NOTE If you experience issues with Buldozer, you may need to reinstall it (Arma 3 Launcher >> Project Drive Management >> Install Buldozer). KNOWN ISSUE The patch of Buldozer may trigger an error about the license not being agreed to.

Can you, please, provide the minidump mentioned in the log? C:\Users\FSUco\AppData\Local\Arma 3\buldozer_2017-04-09_17-26-59.mdmp

What is it? Introduction... Some of you may already know I was working on such project. It was delayed, postponed because of lack of time, it has required more analysis and conception than planned... but, today, here we are. First, if you're wondering if it's the same tool released yesterday in the dev branch of Poseidon Tools: Yes, it is! The Community Tools Updater is a very simple application able to check if the supported tools need to be updated/installed. If an update is needed, it downloads the new version from a depot maintained by the tool author(s) and install the newer version without asking a single question. The main purpose is to provide to the modding community a simple method to install/update the tools they need without being forced to hunt news on all over the web and take the risk to download an outdated version (I saw this many times with Poseidon Tools). More, the risk of installing an outdated version is avoided by a simple fact: It's the tool maker that update the depot with his work, not a random person. You may recognize some tools made by the community veteran Mikero and some other made by me. For users... Usage is very simple, just download it, extract where you want and use it :) In short-term, the updater will update itself when needed, but for the moment, you just need to take a look at this topic or the depot. It downloads the depot manifest at startup, then checks for updates. Once it's started, you can: Explore the local depot (place where all downloads are stored, including installers and zip tools) Clear local depot (delete the entire depot, just to be sure to do not have unnecessary files) Populate local depot (this synchronizes your local depot with the server depot) Update / Install (obviously, install or update the tools that need it and are checked) * yes, pretty basic UI for now but it's working like a charm! For tools developers... For now, only Poseidon Tools and Mikero tools "packages" are included, but I'm looking for more developers to join us. If you're interested, just let me a message here or a PM! In the best case, your tools need an installer that can take one of the following startup parameters: /s -silent -noUI And one of the following if there are some configuration to do during the installation: /d -default or way to define the configuration in command line If your tool supports this kind of options but not these ones, it's just a matter of exception, not a big deal here. By the way, if you don't have an installer, note that NSIS does the job perfectly (used by Mikero Tools) and is very user friendly. If you have questions What tools are supported? ArmA3p (1) Rapify (1) SteamToolCheck (2) MoveFolder (1) IsRap (1) DeWss (1) ExtractPbo (1) DeWrp (1) DeRtm (1) MoveObject (1) GetDePboVersion (1) DePew (1) DeRap (1) DeTex (1) LintCheckRapV (2) DeP3d (1) texConverters (2) Poseidon Tools (*) TM4 Indenter (*) MakePbo (1) SetVersion (1) DePbo (1) QueryAddons (1) pboProject (1) Eliteness (1) ConvertWrp (1) DeKey (1) DeOgg (1) DePac (1) (1) Fully supported (check version, install/update) (2) Partial support (check version, tool available in the local depot when populated) (*) Will be supported soon (this tool is supported by the updater but the tool is not yet ready to be used with it) How it works? The concept is simple, the updater retrieve a XML file live generated from a depot including what is inside the depot, compares local installations and what's in the depot, then, update if needed. Note that it can install if the tool is missing from your workstation. Advanced and curious users can have a look at the application parameters in the registry: "HKEY_CURRENT_USER\Software\bohemia interactive\Poseidon Tools\Updater" Get the Community Tools Updater: Community updater Beta 0.14.10.0 Note: I developed this tool to allow the modding community to get tools in the simplest way as possible, it was firstly designed for Poseidon Tools, then, Mikero tools have arrived and there are more to come! This is an unofficial tool and provided as it is; you bear the risk!

I'll try to reproduce the issue locally and see what I can do about it. By diagnostic, I think @Cosmo_D41 wanted to mean the debug available from the launcher >> Project Drive Management >> Show Debug Regarding the diagnostic, it apparently is stuck at the test of DevP, I will fix that soon.

Full changelog and TECHREP

29-03-2017 Size: ~3.7 MB TOOLS Work Drive Added: Support for Arma 3 Apex PBO files Added: The 32-bit executable of Buldozer is now available on 64-bit systems (buldozer_x86.exe) Fixed: An '0xFFFFFFF' error on extraction of the game data Fixed: It wasn't possible to run '/extractGameData' Fixed: Incorrect install of Buldozer on 32-bit systems Publisher Fixed: Flags for extensions in metadata were not set Arma 3 Tools Launcher Fixed: Launching Object Builder or Terrain builder was throwing an incorrect warning about a missing file Fixed: The Launcher sometimes was populating an incorrect log file Tweaked: Various small adjustments and optimizations Buldozer Configurator Fixed: Crash on config generation when the project drive wasn't mounted

You will need to switch to the development branch. You just have to subscribe to it from the properties of Arma 3 Tools (Steam Library) as described here.

21-03-2017 Size: ~2.0 MB TOOLS: Publisher Fixed: The flags for extensions in the metadata were not set

We've found the cause and it should be fixed. We are now waiting for a final confirmation from the QA department. Thank you for the report.

And it now is available in the development branch of the tools. Regarding the PxFoundation issue, it's a failure of the PhysX initialization which could be caused by a missing DLL, the above fix could help.

The fix is available on the Dev-branch, it would be perfect if you could give it a try to see if that's fixed for you.

21-03-2017 Size: ~1.7 MB TOOLS: Work Drive Added: Support for Arma 3 Apex PBO files Added: The x86 executable of Buldozer is now available on x64 systems (buldozer_x86.exe) Fixed: 0xFFFFFFF on extraction of the game data Fixed: It wasn't possible to run /extractGameData Fixed: Incorrect install of Buldozer on x86 systems Arma 3 Tools Launcher Fixed: Launching Object Builder or Terrain builder was throwing an incorrect warning about a missing file Buldozer Configurator Fixed: Crash on config generation when the project drive wasn't mounted Steam Configuration Changed: Incremented version to reflect the current stage (1.081)

The 3 mentioned issues are now fixed and should appear soon in the development branch. Thank you for the reports and ping in PM.

I have been able to find the cause and fix the issue. This should be available on the development branch soon. Thank you for the report

Full changelog and TECHREP

13-03-2017 Size: ~2.6 MB TOOLS: Terrain Builder Fixed: Some connection issues with Buldozer Steam Configuration Changed: Incremented version to reflect the current stage (1.073)

This is a known issue, introduced in the last patch. The fix is already available in the development branch and will be part of the next update of the main branch.

03-03-2017 Size: ~4.2 MB TOOLS: Publisher Added: Support for 64-bit game extensions; reworked checks for game extensions and signatures Added: When publishing is terminated with validation error(s), a severity of the error (error/warning/info) is listed with the message (the publishing is stopped only because of an error, but warnings are also listed, though they didn't caused it to stop) (command line publisher only) Tweaked: Updated User Interface Work Drive Added: Ability to extract a single PBO and unbinarize relevant content (/extract "U:\Path\to my file") Added: WorkDrive will refuse to process PurgeGameData and ExtractGameData if the target is under SVN versioning Added: Support for Arma 3 x64 Fixed: WorkDrive couldn't locate the DLL folder (development branch of the game) Tweaked: Some error messages have been improved a little FSM Editor Changed: SQF definitions updated to Arma 3 1.69+ Fixed: The shortcuts of FSM Editor were not usable on some computers Addon Builder Maintenance update Steam Configuration Changed: Incremented version to reflect the current stage (1.072)

Change log: Added: SQF definitions for Arma 3 1.69+ Download First post of this topic Poseidon Tools @ tom4897.info - 0.994.205, 03/03/2017 Enjoy

2 days, yes, but over the weekend ;) Can you share your logs? They are located in the install directory of the tool, the relevant logs are named publisher*.

Here is the first update of the year :) Change log: Added: SQF definitions for Arma 3 1.67+ Tweaked: Various things Download First post of this topic Poseidon Tools @ tom4897.info - 0.993.193, 16/01/2017 Enjoy

Just a quick notification to mention that a sample of Combat Patrol scenario is available here. Currently, the saves aren't available in Combat Patrol scenarios (deactivated on initialization).

20-12-2016 Size: ~6 KB SAMPLES Scenario Design Added: Sample of a Combat Patrol scenario

13-12-2016 Size: ~5.2 MB TOOLS: Publisher Added: Detection of extensions, and marking mods as 64 bit or 32 bit according to the architecture of the DLL Changed: The UI has been sightly revisited Changed: Detection and checks for signatures Steam Configuration Changed: Incremented version to reflect the current stage (1.071)