For all examples, we will be using/epics as the root directory for the EPICS install. Please substitute with your own directory.

• Complete EPICS documentation can be found here:https://docs.epics-controls.org/en/latest/
• Documentation about the EPICS build system:https://docs.epics-controls.org/en/latest/build-system/specifications.html
• EPICS base:https://github.com/epics-base
• EPICS modules:https://github.com/epics-modules

Hardware version: 1027

Software version: 1.3.0

make CC=clang CCC=clang++ CMPLR_CLASS=clang

make -j12 CROSS_COMPILER_TARGET_ARCHS+=windows-x64-mingw

Documents the steps taken to migrate P2CE's internal git repos to github with self-hosted LFS storage (literally just a gitlab instance lol).

This is done first because LFS is entirely separate from the git repo itself. Relying on.lfsconfig makes it a bit tricky to mirror using "standard" procedures since there's typically no working tree available.

1. Clone your repo
2. Rungit lfs fetch --all. We'll needall LFS objects here!

System that helps manage player and map specific configurations.

• Comprised of three layers: player, map and config. Think of this as a stack.
• Each layer has a different priority, map being the lowest, and player being the highest. Priority determines where and which options may be overridden.
• Since the player layer has the highest priority, it may override any map-level or config-level option, assuming that option isn't limited to a specific layer(s).
• The config layer is intended to be used by speedrun or other gameplay altering configs. For example, you'd create a config layer for hl2 to enable suit, disable health regen, enable flashlight, etc. This layer could then be activated on map load when the player selects the hl2 campaign from the start game UI.

Below is a useful list of debugging commands and console variables.They can be used to display material names, entity info and even visualize entity IO.