Browse Source

Updated with new commandline options

Jorrit Rouwe 1 year ago
parent
commit
e239d4cb7a
1 changed files with 5 additions and 1 deletions
  1. 5 1
      Docs/PerformanceTest.md

+ 5 - 1
Docs/PerformanceTest.md

@@ -6,11 +6,15 @@ The performance test application contains a couple of simple scenes to test perf
 
 - -s=[scene]: This allows you to select a scene, [scene] can be;
     - Ragdoll: A scene with 16 piles of 10 ragdolls (3680 bodies) with motors active dropping on a level section.
+	- RagdollSinglePile: A single pile of 160 ragdolls (3680 bodies) with motors active dropping on a level section.
     - ConvexVsMesh: A simpler scene of 484 convex shapes (sphere, box, convex hull, capsule) falling on a 2000 triangle mesh.
+	- Pyramid: A pyramid of 1240 boxes stacked on top of each other to profile large island splitting.
+- -i=[iterations]: Number of physics steps before the test finishes.
 - -q=[quality]: This limits the motion quality types that the test will run on. By default it will test both. [quality] can be:
     - Discrete: Discrete collision detection
     - LinearCast: Linear cast continous collision detection
-- -t=[num]: This sets the amount of threads the test will run on. By default it will test 1 .. number of virtual processors.
+- -t=[num]: This sets the amount of threads the test will run on. By default it will test 1 .. number of virtual processors. Can be 'max' to run on as many thread as the CPU has.
+- -no_sleep: Disable sleeping.
 - -p: Outputs a profile snapshot every 100 iterations
 - -r: Outputs a performance_test_[tag].jor file that contains a recording to be played back with JoltViewer
 - -f: Outputs the time taken per frame to per_frame_[tag].csv