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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #988324