> For the complete documentation index, see [llms.txt](https://docs.lightact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightact.com/miscellaneous/launching-lightact-with-arguments.md).

# Launching LightAct with Arguments

LightAct can be launched with predefined command line arguments. Depending on the argument, LightAct will start in a different mode which may speed up your workflow or give you better insight on the program.

LightAct offers three types of arguments: standalone, advanced and custom arguments

### Standalone arguments

To launch LightAct with a standalone argument, the correct formatting would be *"C:\Program Files\Lightact\Lightact4\Lightact4.exe" -argument.*

<table><thead><tr><th width="159">Command</th><th>Description</th></tr></thead><tbody><tr><td><strong>-log</strong></td><td>Extensive logging. When you are in this mode, in the Log Window, you will notice extended messages for Iris cameras, down-sampling, up-sampling and so on.</td></tr><tr><td><strong>-developer</strong></td><td>Gives you an insight of developer information such as object IDs, down-sampled resolutions and more.</td></tr><tr><td><strong>-most_recent</strong></td><td>Opens your most recent project.</td></tr><tr><td><strong>-clear</strong></td><td>Clears the cache folder.</td></tr><tr><td><strong>-secondary</strong></td><td>Gives the machine a Secondary role in LightNet.</td></tr><tr><td><strong>-lightnet</strong></td><td>Sets the LightNet checkbox to ON.</td></tr></tbody></table>

{% hint style="info" %}
**Good to know**: For example, to launch LightAct in the extensive logging mode, you would type *"C:\Program Files\Lightact\Lightact4\Lightact4.exe" -log*.
{% endhint %}

### Advanced arguments

To launch LightAct with advanced arguments, the correct formatting would be *"C:\Program Files\Lightact\Lightact4\Lightact4.exe" -argument "\<advanced\_arguments>".*

<table><thead><tr><th width="401">Command</th><th>Description</th></tr></thead><tbody><tr><td><strong>-project "&#x3C;filepath>"</strong></td><td>Lets you decide which project to open upon launch.</td></tr><tr><td><strong>-window "&#x3C;poz.x> &#x3C;poz.y>"</strong></td><td>Gives you the liberty to determine the position of the program window upon launch.</td></tr><tr><td><strong>-window "&#x3C;poz.x> &#x3C;poz.y> &#x3C;size.x> &#x3C;size.y>"</strong></td><td>Gives you the liberty to determine the position and size of the program window upon launch.</td></tr><tr><td><strong>-nic "&#x3C;ip> &#x3C;port>"</strong></td><td>Sets the default NIC and data port for the application. If the NIC is not valid, a default NIC is set.</td></tr></tbody></table>

{% hint style="info" %}
**Good to know**: For example, to launch LightAct in *nic* mode, you would type *"C:\Program Files\Lightact\Lightact4\Lightact4.exe" -nic "192.169.0.101 12345".*
{% endhint %}

### Custom launch arguments

In LightAct, you can also create your own custom launch arguments which you can then read through the *Get Launch Argument* node. The string after the dash is considered the key, and the string in the quotation marks is considered the value.

For example, if you launch LightAct with the formatting *"C:\Program Files\Lightact\Lightact4\Lightact4.exe" -pizza "cheese", -pizza* is your *key* and *cheese* is your *value*.

<figure><img src="/files/Johm6PmDUpKgCYmZKpSf" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lightact.com/miscellaneous/launching-lightact-with-arguments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.