Search Issue Tracker
Fixed
Votes
0
Found in [Package]
13.1.1
Issue ID
1376269
Regression
Yes
[URP]"FrameTiming' does not contain a definition for 'cpuMainThreadFrameTime" error in the Console using latest URP Core package
Steps to reproduce:
1) Download and open attached project
2) Import Master URP packages to your project : com.unity.render-pipelines.core >> com.unity.shadergraph >> com.unity.render-pipelines.universal
https://github.com/Unity-Technologies/Graphics
3) Observe errors in the Console:
/Graphics/com.unity.render-pipelines.core/Runtime/Debugging/DebugFrameTiming.cs(46,75): error CS1061: 'FrameTiming' does not contain a definition for 'cpuMainThreadFrameTime' and no accessible extension method 'cpuMainThreadFrameTime' accepting a first argument of type 'FrameTiming' could be found (are you missing a using directive or an assembly reference?)
Reproduced with:
2022.1.0a12 - URP 13.1.1
Not reproduced with:
2022.1.0a12 - 13.0.0
2021.2.0b16
Regression since:
URP 13.1.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment