Skip to content
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.

Materials do not work with Unity 5.6.0f3 #3

Closed
djohns451 opened this issue May 8, 2017 · 6 comments
Closed

Materials do not work with Unity 5.6.0f3 #3

djohns451 opened this issue May 8, 2017 · 6 comments
Labels

Comments

@djohns451
Copy link
Contributor

No description provided.

@ghost
Copy link

ghost commented Jun 2, 2017

use the unity package:
https://github.com/MicroGSD/RoadArchitect/releases

@ghost
Copy link

ghost commented Jun 2, 2017

and close the issue

@djohns451
Copy link
Contributor Author

@Tomor1 The attached Release package suffers from the same issues.

@MicroGSD MicroGSD added the bug label Jun 29, 2017
@mneilly
Copy link
Contributor

mneilly commented Jul 2, 2017

The materials do not appear when opening the project from a GitHub repo because the .meta files are not included in the repository. The .meta extension is included in the .gitignore file erroneously (or intentionally for other reasons?):

Per the Unity documentation:
(https://docs.unity3d.com/Manual/ExternalVersionControlSystemSupport.html)

Before checking your project in, you have to tell Unity to modify the project structure slightly to make it compatible with storing assets in an external version control system. This is done by selecting Edit->Project Settings->Editor in the application menu and enabling External Version Control support by selecting Visible Meta Files in the dropdown for Version Control. This will show a text file for every asset in the Assets directory containing the necessary bookkeeping information required by Unity. The files will have a .meta file extension with the first part being the full file name of the asset it is associated with. Moving and renaming assets within Unity should also update the relevant .meta files. However, if you move or rename assets from an external tool, make sure to syncronize the relevant .meta files as well.

When checking the project into a version control system, you should add the Assets and the ProjectSettings directories to the system. The Library directory should be completely ignored - when using .meta files, it’s only a local cache of imported assets.

When creating new assets, make sure both the asset itself and the associated .meta file is added to version control.

@djohns451
Copy link
Contributor Author

@mneilly Since we release as a unitypackage, adding .meta files would prove a hindrance to making sure that the items import properly as-is.

@djohns451
Copy link
Contributor Author

Trying with a fresh installation, the Materials work.

FritzsHero referenced this issue in FritzsHero/RoadArchitect Mar 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants