Search Issue Tracker
By Design
Votes
0
Found in
2019.3
2019.3.0f6
2020.1
2020.2
Issue ID
1219431
Regression
No
CustomSampler.GetReporter().elapsedNanoseconds returns 0 in code when the first frame takes longer than a second to compute
Reproduction steps:
1. Open the attached project ("case_1219431-BRep.zip")
2. Open the repro scene ("main")
3. Enter Play Mode and wait for the cubes to load
4. Inspect the GUI on the lower right corner of the Game View
Expected result: Information about loading times can be seen
Actual result: Text fields remain empty (CustomSampler.GetReporter().elapsedNanoseconds returns 0)
Reproducible with: 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Couldn't test with: 2017.4, 2018.4 (project breaking after downgrade)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.2.X):
The 0 data reported by Recorder is due to the design decision that sampler.GetRecorder() creates a new recorder.
This results in the situation where a recorder object created on stack is garbage collected disabled and disposed.
Basically Update method with usage like sampler.GetRecorder().elapsedNanoSeconds always returns 0 being a new recorder.
A workaround for this would be to use a member variable to store recorder instance in the class.