Reproduction steps:
1. Open the attached “IN-125177.zip” project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the PlayMode tab
4. Click “Run All” and wait for the tests to finish
5. Fully expand the “ProfileTest (2 tests)” tests dropdown
6. Click on and observe values under “TargetFramerateSetTest” and “TargetFramerateUnsetTest”
Expected result: Both tests record non-zero values for draw calls and vertex count
Actual result: Only the second test (“TargetFramerateUnsetTest”), where the target framerate property is unset, records any values
Reproducible with: 2023.1.0b1, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Workarounds:
- Add the following ProfilerRecorder option: ProfilerRecorderOptions.StartImmediately
- Force ProfilerDriver.enabled to True; however, this causes the editor to crash when trying to close it
Notes:
- This issue appears to specifically affect the ProfilerCategory.Render category. Running the same tests with Memory and Internal recorders works as expected
- The Test Runner script contains two tests, both of which start a ProfilerRecorder in the Render category. One test sets Application.tagetFramerate to 60 before running the recorder. The other test unsets it back to -1 (the default value) before running the recorder
- The issue also happens when profiling Play mode in the Editor via, for example, an in-scene script that starts a ProfilerRecorder