URP pink textures Only in editor, different results on different PC

[Visssarion]

I have a URP Project, which renders completely fine.

However, same project on my friends PC (shared through Git), has all URP materials in Editor rendered pink

However, during the game URP textures look completely fine for him

We’re both running windows 10, I have a proper GPU and he has an integrated GPU (CPU rendering stuff). Why would the result be different only in editor? How to fix this?

[Kurt-Dekker]

@Visssarion

shared through Git

^ ^ ^ Sounds like perhaps you’re doing this wrong, such as ignoring metafiles or misconfiguring so the metafiles are hidden, which will not work.

PROPERLY CONFIGURING AND USING ENTERPRISE SOURCE CONTROL

I’m sorry you’ve had this issue. Please consider using proper industrial-grade enterprise-qualified source control in order to guard and protect your hard-earned work.

Personally I use git (completely outside of Unity) because it is free and there are tons of tutorials out there to help you set it up as well as free places to host your repo (BitBucket, Github, Gitlab, etc.).

You can also push git repositories to other drives: thumb drives, USB drives, network drives, etc., effectively putting a complete copy of the repository there.

As far as configuring Unity to play nice with git, keep this in mind:

Prefab links keep getting dumped on Git pull

There really isn’t any fix because git works perfectly with Unity when configured properly. Best practices involve saving your work and closing Unity before using git. But if you understand how Unity does and does not flush changes to disk (or at least ALWAYS do a save-project), you can get away with leaving Unity open. The only thing linking EVERYTHING together in Unity is the GUID assigned to a script or asset. Name is irrelevant. Only the GUID connects it. This GUID is in the meta file. I…

I usually make a separate repository for each game, but I have some repositories with a bunch of smaller test games.

Here is how I use git in one of my games, Jetpack Kurt:

2 steps backwards

Yeah, what Praetor said is it… Debug.Log is your friend, and also since this is animation related, you can open up the Animator window when you expect the animations to go, and actually visually see where the state machine is, see which state it thinks it is in. You can combine this with Debug.Log() output at the locations where you set the animations to be what you think they should be, and that should lead you to some intel. I highly recommend setting up git source control. It really plays ni…

Using fine-grained source control as you work to refine your engineering:

When to make a separate object or class/script? Help me think like a programmer! (Example in text.)

This is a reasonable initial approach. The problem is you have listed the parts, but you haven’t really listed how they interact, and even if you did, it’s still sorta up to you how to organize it. Only YOU will know how to organize it, and the only way you can tell is to do the work. I recommend this: first, develop ALWAYS with source control (such as git), and every time you get even the slightest thing working, commit those changes with good commit messages. Then move to the next thing, c…

Share/Sharing source code between projects:

Your techniques to share code between projects?

I have found that bundling your own code into DLLs only serves to slow down your workflow. I base this on several years of experience dealing with other teams well-intentioned packaging mishaps. With games, it is almost always useful to reach into library code, make a temporary tweak to isolate a problem, and then revert it. With DLLs this is impossible, making workflow harder and more brittle. I prefer to share source code at the C# level. That way I can reach into libraries trivially and inje…

Setting up an appropriate .gitignore file for Unity3D:

Removing IL2CPP_cache from Project

Not sure what you are “auto generating” with… I usually start from one of my other projects, or a gitignore example online, and reason about all the parts inside it, and start from there. Like any other configuration change, after you make it, pay attention for a while to make sure it is what you want. You can always clone the repo somewhere else to verify that the correct files are being tracked. Doing so to a brand-new computer is the acid test to make sure you can still build the project. …

Generally the ONLY folders you should ever source control are:

Assets/
ProjectSettings/
Packages/

NEVER source control Library/ or Temp/ or Logs/
NEVER source control anything from Visual Studio (.vs, .csproj, none of that noise)

Setting git up with Unity (includes above .gitignore concepts):

How to Git with Unity

It is only simple economics that you must expend as much effort into backing it up as you feel the work is worth in the first place. Digital storage is so unbelievably cheap today that you can buy gigabytes of flash drive storage for about the price of a cup of coffee. It’s simply ridiculous not to back up.

If you plan on joining the software industry, you will be required and expected to know how to use source control.

Source control does require learning, but there are TONS of tutorials and courses and online reference.

You should strive to use source control as confidently as you use your file/folder system.

“Use source control or you will be really sad sooner or later.” - StarManta on the Unity3D forum boards

[kdgalla]

@Visssarion

(shared through Git)

Most likely your friend for whom the materials are broken either has no URP asset set-up in their graphic settings, or the materials are somehow losing their references to either shaders or texture maps. The later could happen in a scenario like Kurt Dekker describes- if they pull certain files from the repo, but their project does not have the necessary meta files to reconcile the assets with their GUIDs. In Unity, every asset has a GUID that’s stored in a corresponding *.meta file.

[CodeSmile]

@Visssarion

However, during the game URP textures look completely fine for him

Which means it can’t be a missing GUID. But do check your git setup anyway. You should be using GitHub’s .gitignore for Unity projects. Particularly if you do not exclude the Library folder from source control all sorts of issues can occur, and it’s definitely wasting space and slowing git operations.

Question is: does the scene view continue to show the pink materials while the game view works fine? Because URP has this live shader compilation where objects are usually light blue until the shader got compiled, which happens during playmode (unless you turn off that setting and force shader compilation up front when entering playmode). But like I said, those non-compiled materials should be light or pale blue, not magenta (RGB 255,0,255).

Oh and very importantly: both of you need to be using the exact same Unity version, down to the last (third) digit!