Search Issue Tracker
Won't Fix
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
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
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Resolution Note:
We will be reevaluating this issue in the following 6 months. We are studying a better P4 integrations to solve this kind of problems.
Resolution Note:
We will be reevaluating this issue in the following 6 months. We are studying a better P4 integrations to solve this kind of problems.