Skip to content

Latest commit

 

History

History

tools

README.md

Building PzGrenBtl402 from source (HEMTT)

Requirements

  • Arma 3
  • Arma 3 Tools (available on Steam)
  • Run Arma 3 and Arma 3 Tools directly from Steam once to install registry entries (and again after every update)
  • [Windows] PowerShell v5.0+

Setup and Building

Initial Setup

Execute setup.bat in tools folder.

File Patching Setup

Script

If you have Python installed, you can run following in the tools folder:

python setup_filepatching_links.py
Manuel

Create the following links manually. First, create z folder in your Arma 3 directory. If you have not already run a HEMTT dev build, you will need to create [location of the PzGrenBtl402 project]\.hemttout\dev folder first. Then run the following command as admin, replacing the text in brackets with the appropriate paths:

mklink /J "[Arma 3 installation folder]\z\PzGrenBtl402" "[location of the PzGrenBtl402 project]\.hemttout\dev"

Create a Test Build

To create a development build to test changes or to debug something, execute build.bat in the root folder. This will populate the addons folder with PBOs. These PBOs still point to the source files in their respective folders however, which allows you to use file patching. This also means that you cannot distribute this build to others.

Create a Release Build

To create a complete build that you can use without the source files, execute build_release.bat in the root folder. This will populate the release folder with binarized PBOs that you can redistribute. These handle like those of any other mod.

File Patching

File Patching allows you to change the files in an addon while the game is running, requiring only a restart of the mission. This makes it great for debugging, as it cuts down the time required between tests. Note that this only works with PBOs created using the build.bat.

To run Arma 3 with file patching add the -filePatching startup parameter.

Files must exist in the built PBOs for file patching to work. If you create a new file you must rebuild the PBO or Arma will not find it in your file paths.

Disable CBA Function Caching

By default CBA caches a compiled version of functions to reduce mission load times. This interferes with file patching. You can disable caching for a single module. To do that you need add the following line or remove the comment in the script_component.hpp file of said module:

#define DISABLE_COMPILE_CACHE

Restrictions

Configs are not patched during run time, only at load time. You do not have to rebuild a PBO to make config changes, just restart Arma.

Credit

This guide was taken from CBA and modified for internal use.