Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.1f1
Issue ID
952362
Regression
No
Unity Perforce Integration does not check out Reflection Files
To reproduce:
1. Setup Perforce on your machine;
2. Open the attached project;
3. Go to Edit > Project Settings > Editor > Version Control and fill in Username, password, workspace and service used in Perforce;
4. Make sure that there are no pending files on the changelist in Perforce Client (refresh app by clicking on F5 key to make sure. Revert files if there are any);
5. In Unity, open Lighting tab, click on "Auto Generate" to check it;
6. Select the Directional Light, change it's albedo to something else, then rotate the light to have different shadows being cast;
7. Refresh the Perforce Client app.
Expected result: Lightning Data and Reflection Maps are generated and added into the Perforce changelist.
Actual result: Only Lighting Data is added to Perforce changelist.
Reproduced on versions: 5.6.3f1, 5.6.3p4, 2017.1.2f1, 2017.2.0f2, 2017.3.0b2, 2018.1.0a1.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #988324