Feature/more args

[wCATw]

Description

Added fields and checkboxes for additional arguments

I can't imagine why a server might need an extra thread for loading textures, but whatever.

Motivation and Context

Parameter settings for hugePages, bePath, and exThreads

How Has This Been Tested?

I poked the checkboxes, the values changed correctly.

Screenshots:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• hugePages
• exThreads=<number>
• loadMissionToMemory
• bePath=<customPath>
• limitFPS=<number>
• enableSteamLogs
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.

[OverlordZorn]

overall a nice addition!

The textures is indeed a bit awkward but since its part of the exThreads command guess thats fine.
https://community.bistudio.com/wiki/Arma_3:_Startup_Parameters#exThreads

While you're at it though, would you like to add these?

simple checkboxes:

• -hugepages
• -enableSteamLogs
• -loadMissionToMemory

Numberange:

• -lmitFPS#### https://community.bistudio.com/wiki/Arma_3:_Startup_Parameters#limitFPS

Also: Force CPUCount
https://community.bistudio.com/wiki/Arma_3:_Startup_Parameters#CPUCount
with 2.20, the CPUCount will have a new low limit of 2, maybe you can prep that for 2.20 as well? :D 😬

[wCATw]

While you're at it though, would you like to add these?

simple checkboxes:

* ~`-hugepages`~

* `-enableSteamLogs`

* `-loadMissionToMemory`

Numberange:

* `-lmitFPS####` https://community.bistudio.com/wiki/Arma_3:_Startup_Parameters#limitFPS

I've already added the 'loadMissionToMemory' argument, but thanks for the suggestion! I’ll work on implementing 'limitFPS' and 'enableSteamLogs' soon.

[wCATw]

Also: Force CPUCount https://community.bistudio.com/wiki/Arma_3:_Startup_Parameters#CPUCount with 2.20, the CPUCount will have a new low limit of 2, maybe you can prep that for 2.20 as well? :D 😬

I don't believe a minimum limit below 2 would cause serious issues, so I’ll hold off on changing this until the update is released to stable.