CMB:SimplifyTesting: Difference between revisions
mNo edit summary |
Lou Montana (talk | contribs) m (Text replacement - "[[Image:" to "[[File:") |
||
(25 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
=SimplifyTesting= | =SimplifyTesting= | ||
==Goals== | == Goals == | ||
* Showcase what testing is all about | * Showcase what testing is all about. | ||
* Explain how to simplify the task | * Explain how to simplify the task. | ||
* Offer tools to support and simplify testing | * Offer tools to support and simplify testing. | ||
==Preface== | == Preface == | ||
A crucial part is to have your [[CMA:DevelopmentSetup|development setup]] right and all decent [[CMA:Tools|tools]] available. | A crucial part is to have your [[CMA:DevelopmentSetup|development setup]] right and all decent [[CMA:Tools|tools]] available. | ||
Line 13: | Line 13: | ||
'''Make sure that both is true for your setup.''' | '''Make sure that both is true for your setup.''' | ||
==General tips== | == General tips == | ||
* | * Use window mode to avoid load times from ALT+Tab and therefore easily be able to switch been the game and the OS. This is also useful for game loading times to be able to do something useful meanwhile. ([[ArmA:_Startup_Parameters]]): | ||
-window | -window | ||
* Use -x and -y along with window mode to be able to have another app visible on the screen. Alternatively get a second monitor | * Use -x and -y along with window mode to be able to have another app visible on the screen. Alternatively get a second monitor. ([[ArmA:_Startup_Parameters]]): | ||
-window -x=800 -y=1024 | -window -x=800 -y=1024 | ||
* | * Alternatively you can modify the arma.cfg located in your .\profiles\Users\''STANDARD-OS-USER'' folder. You can define the start area (x & y) as well as the width and height. In other words you can leave the area left/right either/and below/above the arma screen "blank" for your text editor or any other app. | ||
// Example for 1280 x 1024 windows resolution with two line taskbar. | |||
winX=0; | |||
winY=0; | |||
winW=1280; | |||
winH=960; | |||
<br clear="all" /> | |||
[[File:CMB_SF_NoTopWindowBar.jpg|thumb|280 px|No top window bar|left]] | |||
[[File:CMB SF WindowModeWithReduceScreenSize.jpg|thumb|280 px|Window mode with reduced screen size|left]] | |||
<br clear="all" /> | |||
* Use noPause mode to keep the gaming running even without focus for non MP environment. Testing in the MP editor makes this no longer needed. Yet with the SP editor you can load a mission more easily and bit faster. ([[ArmA:_Startup_Parameters]]): | |||
-noPause | -noPause | ||
* Use noSplash to avoid the initial intro screens and therefore speed up the loading time. ([[ArmA:_Startup_Parameters]]): | |||
-noSplash | |||
* Use profiles to put the profile folder within your arma folder to access it more easily. Use name to call a specific profile for testing. ([[ArmA:_Startup_Parameters]]): | |||
-profiles=Profiles -name=test | |||
An alternative is to use an full path to avoid the profiles folder sublayer<br> | |||
and have the 'users', 'mpmissionscache' and the debug and report files<br> | |||
directly in the game folder: | |||
-profiles=g:\games\arma | |||
g:\games\arma\users\* | |||
g:\games\arma\mpmissionscache\* | |||
g:\games\arma\ArmA2Int.RPT | |||
* Modify your test.ArmAprofile to the very lowest settings to reduce low times and get most FPS: | |||
blood=0; | |||
viewDistance=1; | |||
terrainGrid=50; | |||
precision=8; | |||
sceneComplexity=1; | |||
shadingQuality=0; | |||
shadowQuality=0; | |||
soundEnableEAX=0; | |||
soundEnableHW=0; | |||
anisoFilter=-1; | |||
TexQuality=-1; | |||
postFX=0; | |||
useWBuffer=0; | |||
==Launching the game== | == Launching the game == | ||
Everything related to configs requires the game to be (re)started to parse the config files. | Everything related to configs requires the game to be (re)started to parse the config files. | ||
Line 30: | Line 67: | ||
* Load no island and intro mission on startup ([[ArmA:_Startup_Parameters]]): | * Load no island and intro mission on startup ([[ArmA:_Startup_Parameters]]): | ||
-world=empty | -world=empty | ||
* Use | * Use {{Link|https://en.wikipedia.org/wiki/RAID_0#RAID_5|RAID 5}},{{Link|https://en.wikipedia.org/wiki/RAID_0#RAID_0|RAID 0}} or a {{Link|https://en.wikipedia.org/wiki/Solid-state_drive|solid-state drive}} to speed up loading the files from the HDD. | ||
* Use the ''minimal addons setup'' (MAS). | * Use the ''minimal addons setup'' (MAS). | ||
# Move your '''.\arma\addons''' folder to '''.\arma\ | |||
# Adapt all your standard | === Minimal Addons Setup === | ||
# Create the folder structure '''.\arma\mas\addons''' | |||
# | Step-by-step setup: | ||
# Copy '''anims.pbo''' from '''.\arma\ | |||
# Adapt dev launch paths to use '''-mod=mas;''' (and more if needed) | # Move your '''.\arma\addons''' folder to '''.\arma\CA_addons\addons''' | ||
# Adapt all your standard launch paths to use '''-mod=CA_addons;''' (and more if needed) | |||
# Create the folder structure '''.\arma\x\mas\addons''' | |||
# Git clone the MAS repository to '''.\arma\x\mas''' | |||
# Copy '''anims.pbo''' from '''.\arma\CA_addons\addons''' to '''.\arma\x\mas\addons''' | |||
# Adapt dev launch paths to use '''-mod=x\mas;''' (and more if needed) | |||
MAS repository data: | MAS git repository data: | ||
URL of repository: | URL of repository: | ||
Line 45: | Line 87: | ||
PW: | PW: | ||
==Testing areas== | == Testing areas == | ||
===SP editor=== | === SP editor === | ||
* Benefits of the SP editor: | * Benefits of the SP editor: | ||
** A | ** A | ||
* Direct launch: | * Direct launch: | ||
"g:\games\arma\users\myUser\missions\myMission.intro\mission.sqm" | |||
===MP editor=== | === MP editor === | ||
* Benefits of the MP editor: | * Benefits of the MP editor: | ||
Line 61: | Line 103: | ||
-host | -host | ||
===Dedicated server=== | === Dedicated server === | ||
You can easily setup a dedicated server on your own computer. Especially with a multi core system the performance is fine. | You can easily setup a dedicated server on your own computer. Especially with a multi core system the performance is fine. | ||
Line 71: | Line 113: | ||
* Direct launch: | * Direct launch: | ||
===Buldozer=== | === Buldozer === | ||
==Debug== | == Debug == | ||
The game will write errors of configs and scripts to a file called [[arma.RPT|arma.rpt]]. Check the page for the file's location. | The game will write errors of configs and scripts to a file called [[arma.RPT|arma.rpt]].<br> | ||
Check the page for the file's location. | |||
The meaning of some errors is explained there as well as on its talk page. However most error messages are rather easy to understand from the naming and given output. | The meaning of some errors is explained there as well as on its talk page. <br> | ||
However most error messages are rather easy to understand from the naming <br> | |||
and given output. | |||
Any script error message happening during the game will be put in the arma.rpt. | Any script error message happening during the game will be put in the arma.rpt. | ||
===Dedicated server=== | === Dedicated server === | ||
Note that while testing on a dedicated server it will write an arma.rpt there<br> | |||
as well. So make sure to check both the client and the server. | |||
=== Write to arma.rpt yourself === | |||
You can use these commands to debug strings to [[arma.RPT|rpt]] file: | |||
* [[diag_log]] | |||
diag_log "test"; | |||
diag_log _test; | |||
diag_log (a + b); | |||
diag_log [test]; | |||
* [[localize]] | |||
localize 'my Debug String'; // => 'String my Debug String Not Found' | |||
* [[createVehicleLocal]] | |||
'my Debug String' createVehicleLocal [0, 0, 0]; // => 'Cannot create non-ai vehicle: my Debug String' | |||
With [[format|format['%1',_myVar]]] you can convert code to string. | |||
localize format['%1',_myVar]; | |||
format['%1',_myVar] createVehicleLocal [0, 0, 0]; | |||
== Debug console == | |||
Get a debug console. You can execute code during the mission or check variables: | |||
* {{Link|link= http://forums.bistudio.com/showthread.php?t=126249|text= DevCon - the developer console}} | |||
* {{Link|link= http://forums.bistudio.com/showthread.php?t=73356|text= Gaia's Debug Console for ARMA 2}} | |||
== Play-testing == | |||
=== Invincibility === | |||
You can make yourself invincible with | |||
player allowDamage false; | |||
(vehicle player) allowDamage false; | |||
Run it in a loop to make it always applied to matter what vehicles you enter and exit: | |||
[] spawn | |||
{ | |||
while {true} do | |||
{ | |||
player allowDamage false; | |||
(vehicle player) allowDamage false; | |||
sleep 0.1; | |||
}; | |||
}; | |||
== Unpacked files == | |||
{{GameCategory|arma2|Editing}} |
Latest revision as of 23:09, 20 November 2023
SimplifyTesting
Goals
- Showcase what testing is all about.
- Explain how to simplify the task.
- Offer tools to support and simplify testing.
Preface
A crucial part is to have your development setup right and all decent tools available.
Make sure that both is true for your setup.
General tips
- Use window mode to avoid load times from ALT+Tab and therefore easily be able to switch been the game and the OS. This is also useful for game loading times to be able to do something useful meanwhile. (ArmA:_Startup_Parameters):
-window
- Use -x and -y along with window mode to be able to have another app visible on the screen. Alternatively get a second monitor. (ArmA:_Startup_Parameters):
-window -x=800 -y=1024
- Alternatively you can modify the arma.cfg located in your .\profiles\Users\STANDARD-OS-USER folder. You can define the start area (x & y) as well as the width and height. In other words you can leave the area left/right either/and below/above the arma screen "blank" for your text editor or any other app.
// Example for 1280 x 1024 windows resolution with two line taskbar. winX=0; winY=0; winW=1280; winH=960;
- Use noPause mode to keep the gaming running even without focus for non MP environment. Testing in the MP editor makes this no longer needed. Yet with the SP editor you can load a mission more easily and bit faster. (ArmA:_Startup_Parameters):
-noPause
- Use noSplash to avoid the initial intro screens and therefore speed up the loading time. (ArmA:_Startup_Parameters):
-noSplash
- Use profiles to put the profile folder within your arma folder to access it more easily. Use name to call a specific profile for testing. (ArmA:_Startup_Parameters):
-profiles=Profiles -name=test
An alternative is to use an full path to avoid the profiles folder sublayer
and have the 'users', 'mpmissionscache' and the debug and report files
directly in the game folder:
-profiles=g:\games\arma g:\games\arma\users\* g:\games\arma\mpmissionscache\* g:\games\arma\ArmA2Int.RPT
- Modify your test.ArmAprofile to the very lowest settings to reduce low times and get most FPS:
blood=0; viewDistance=1; terrainGrid=50; precision=8; sceneComplexity=1; shadingQuality=0; shadowQuality=0; soundEnableEAX=0; soundEnableHW=0; anisoFilter=-1; TexQuality=-1; postFX=0; useWBuffer=0;
Launching the game
Everything related to configs requires the game to be (re)started to parse the config files.
To reduce the A1 startup time you can utilize the following tweaks:
- Load no island and intro mission on startup (ArmA:_Startup_Parameters):
-world=empty
- Use RAID 5,RAID 0 or a solid-state drive to speed up loading the files from the HDD.
- Use the minimal addons setup (MAS).
Minimal Addons Setup
Step-by-step setup:
- Move your .\arma\addons folder to .\arma\CA_addons\addons
- Adapt all your standard launch paths to use -mod=CA_addons; (and more if needed)
- Create the folder structure .\arma\x\mas\addons
- Git clone the MAS repository to .\arma\x\mas
- Copy anims.pbo from .\arma\CA_addons\addons to .\arma\x\mas\addons
- Adapt dev launch paths to use -mod=x\mas; (and more if needed)
MAS git repository data:
URL of repository: User: PW:
Testing areas
SP editor
- Benefits of the SP editor:
- A
- Direct launch:
"g:\games\arma\users\myUser\missions\myMission.intro\mission.sqm"
MP editor
- Benefits of the MP editor:
- A
- Direct launch:
-host
Dedicated server
You can easily setup a dedicated server on your own computer. Especially with a multi core system the performance is fine.
- Benefits of the dedicated editor:
- Only way to properly test a MP mission for locality and performance.
- DS configuration:
- Direct launch:
Buldozer
Debug
The game will write errors of configs and scripts to a file called arma.rpt.
Check the page for the file's location.
The meaning of some errors is explained there as well as on its talk page.
However most error messages are rather easy to understand from the naming
and given output.
Any script error message happening during the game will be put in the arma.rpt.
Dedicated server
Note that while testing on a dedicated server it will write an arma.rpt there
as well. So make sure to check both the client and the server.
Write to arma.rpt yourself
You can use these commands to debug strings to rpt file:
diag_log "test"; diag_log _test; diag_log (a + b); diag_log [test];
localize 'my Debug String'; // => 'String my Debug String Not Found'
'my Debug String' createVehicleLocal [0, 0, 0]; // => 'Cannot create non-ai vehicle: my Debug String'
With format['%1',_myVar] you can convert code to string.
localize format['%1',_myVar]; format['%1',_myVar] createVehicleLocal [0, 0, 0];
Debug console
Get a debug console. You can execute code during the mission or check variables:
Play-testing
Invincibility
You can make yourself invincible with
player allowDamage false; (vehicle player) allowDamage false;
Run it in a loop to make it always applied to matter what vehicles you enter and exit:
[] spawn { while {true} do { player allowDamage false; (vehicle player) allowDamage false; sleep 0.1; }; };