Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.10
Issue ID
1132158
Regression
No
Scriptable Render Pipeline Component values of the Camera are not pasted when copying them from another Camera
How to reproduce:
1. Open user attached project "copyHDRP.zip"
2. Select "Main Camera" GameObject
3. Right Click on the Camera Component in the Inspector
4. Select "Copy Component"
5. Select "Main Camera_2" GameObject
6. Right Click on the Camera Component in the Inspector
7. Select "Paste Component Values"
Expected result: All Component values of the Camera are pasted
Actual result: HDRP Component values of the Camera are not pasted
Reproducible with - 2018.3.7f1, 2019.1.0b5, 2019.2.0a7
Reproducible package version - 1.1.10; 4.10
Notes:
1) Could not test with 2017.4 because Scriptable Render Pipeline is not supported by that version.
2) Could not test with earlier package versions because there were no additional Component values in the Camera.
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
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
Resolution Note:
A large refactor is required to have this fixed with plenty of others issue related to that. Work have been started on Camera. It will stay like this at least up to 2020.2.
Meanwhile, user should copy paste both component (Camera and HDAdditionalCameraData) to have full copy.
There is similar issue on Light and Reflection Probe regarding their respective AdditionalData components.