Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.27f1
2022.3.4f1
2023.1.2f1
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-17933
Regression
No
[Perforce] Lightmap meta file changes when fetched from Perforce
Reproduction steps:
1. Setup Perforce Server
2. Setup a workspace on 2 Windows PCs
3. Download the attached project "P4CSMeta.zip" and place it under the root of the Perforce workspace in both PCs
4. Add a Lightmap file in the Assets folder in PC 1
5. Submit the Lightmap file (including its meta file) to Perforce
6. Checkout the Lightmap file to Perforce
7. Get the latest version of the Lightmap file from the depot in PC 2
Expected result: The meta files are the same on both PCs
Actual result: The meta files are different in PC 1 and PC 2
Reproducible with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1, 2021.2.0b4, 2022.2.0a3
Notes:
- Lightmap file is .exr
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Add comment