Note: When using your own assets changing instancing, texture size, texture config option, or material does not work. To get them working will require manual modification of the generated balsam output. You can compare the generated balsam output to the original assets in the demo if you want to do that.
Remote Controller
---------------------
-----------------
The RemoteController application is most useful with targets that either do not support command-line arguments (like Android) or do not have a file system for saving the reports on (like Integrity).
If the application is started in remote mode (`--mode remote`), you will need the RemoteController application to control it. It can be built from the RemoteController.pro -file. Android will start in remote mode by default.
...
...
@@ -156,3 +155,12 @@ If the application is started in remote mode (`--mode remote`), you will need th
When starting the BenchmarkDemo application in remote mode, it will display the IP address the RemoteController application needs to connect to. Insert the IP address into the field reserved for it in the remote controller, and click "Connect".
RemoteController has an UI for toggling the target, preset, mode, and all other settings that would normally be controlled using the command-line arguments. In benchmark mode the report that would normally be saved on the device will be received by the RemoteController application, and can be saved from there. It receives the result of each test run one-by-one, in case an error happens on the target. This way it also allows you to check the results of individual test cases as they are run.
Running meaningful tests
------------------------
In case you wish to compare different HWs with each other, or try if some changes in your HW setup affects performance, the basic tests often are not very useful. There is a collection of test scripts included in the project (under `BenchmarkUI/testscripts`) for you to use to run a more comprehensive test set. These are best run via the `Remote Controller`. Set the `Mode` to `benchmark`, `Benchmark Mode` to `testset`, and then click on the `Test Script` text box to select the script to run.
There are a lot of different scripts targeting different areas of interest. If you wish to run a test set that covers many of the most important aspects, choose the `becnhmarkset_comparison_tests_1.json` script (and once you've run that, scripts 2 and 3 as well).
After that, start your BenchmarkDemo application in remote mode, connect to it, and click `Run`. The whole script will run through one test after the other, and once it is finished, you'll have a test report which can be saved. 2 reports will be saved each time: the complete report, and a summary with average FPS of each test in the set.
