Search Issue Tracker

By Design

Votes

0

Found in

2020.1.0a17

2020.3

2021.2

2021.2.4f1

2022.1

Issue ID

1387777

Regression

Yes

External Materials (Legacy) are not generated when Cache Server is used

Asset - Importers

-

How to reproduce:
1. Make sure you have Accelerator running on your system
2. Unzip the project ("import-test.zip") to three seperate folders: "test1", "test2", "test3"
3. Setup and enable Cache Server (Unity -> Preferences -> Asset Pipeline/Cache Server)
4. Open the "test1" project, close it
5. Open the "test2" project
6. Disable Cache Server and close the project
7. Open the "test3" project

Expected result: All three projects should have the "Assets/AfghanBush09" materials folder, the use of Cache Server should not impact the state of the project
Actual result: "test2" project does not have the generated materials while the "test3" project does have the generated materials

Reproducible with: 2020.1.0a17, 2020.3.25f1, 2021.2.6f1, 2022.1.0b2
Not reproducible with: 2019.4.34f1

  1. Resolution Note (2022.2.X):

    Using "External Materials (Legacy)" generates new Material files alongside the SpeedTree file. These Materials are now distinct assets that can be modified, renamed, copied etc. independently of the SpeedTree file. There is no difference between these Materials and Materials that are created using the "New Material" menu, other than that they've copied some settings from the SpeedTree file.

    Because they're distinct files that can be individually configured, they need to be committed to your source control system to avoid any weirdness.

    The role of the Accelerator is only to speed up the importation of assets that the asset database is already aware of, it does not provide the syncing of assets between projects.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.