Last reviewed 31 Jul 2026

Applies to

Unity editor errors VRChat SDK problems Creator Companion packages

Difficulty Beginner

Unity and VRChat Troubleshooting

Use the error message and the affected system to choose the next check. Unity, Creator Companion, the VPM Package Resolver, and the VRChat SDK Builder each report different parts of the project.

First Diagnostic Pass

Protect the project, capture the first useful error, and check the tool responsible for the failed operation.

Create a Creator Companion backup before removing packages or changing Unity versions.
Open Window > General > Console and inspect the earliest relevant red error.
Check the SDK Builder for upload validation or the Package Resolver for missing VPM packages.

Protect the working project

Creator Companion's Make Backup creates a project ZIP. Use it before package replacement, migration, or other repairs that affect the whole project.

Route the Problem

Symptom	Open first	What to capture
Red compile errors	Window > General > Console	First error, full message, file, line, package name
VRChat SDK menu is missing	Unity Console	Compile errors and installed Unity version
SDK build is blocked	VRChat SDK > Show Control Panel > Builder	Required validation messages and Console errors
VPM package is missing	Package Resolver or Creator Companion	Package ID, requested version, resolver message
Unity Package Manager failed	Window > Package Manager	Package name and the full Package Manager error
Materials are pink	Material Inspector	Shader name and render-pipeline compatibility
Scene opens blank	Project window under `Assets`	Saved scene path and recent migration/import steps
Unity closes or hangs	Editor log	Messages immediately before the failure

1. Make a Recoverable Copy

In Creator Companion, open the project's management screen and select Make Backup before a project-wide repair.

By default, Creator Companion stores backup ZIP files under:

%LOCALAPPDATA%\VRChatCreatorCompanion\Project Backups

To restore one, extract the ZIP into a normal project location and use Add Existing Project in Creator Companion.

If Creator Companion cannot create a backup or reports missing packages, check the project path length. Its FAQ identifies long Windows paths as a common cause and recommends a shorter location such as C:\Projects\Project Name.

2. Read the Unity Console

Open Window > General > Console. Unity uses the Console for editor messages, warnings, import failures, and script compilation errors.

For a useful report:

Disable Collapse temporarily if several errors may only look identical.
Select the earliest relevant red entry.
Read the full message and stack trace.
Record the script or package path and line number.
Fix or remove the cause, then allow Unity to compile again.

Errors lower in the list may be consequences of the first compile failure. Recheck the Console after each correction.

3. Identify Who Owns the Failing File

The path in the error usually identifies the responsible area:

Path or label	Likely owner
`Assets/...`	Imported asset, custom script, or project content
`Packages/...`	Unity, VRChat, or third-party package
`com.vrchat.base`	VRChat Base package
`com.vrchat.worlds`	VRChat Worlds package
`com.vrchat.avatars`	VRChat Avatars package
Package ID from a community repository	That package's publisher

Do not edit installed package files merely to silence an error. Confirm the package version and compatibility, then update, resolve, or remove the package through its manager.

4. Check VRChat Packages

Creator Companion manages official VRChat SDK packages. Do not import an old VRCSDK3...unitypackage into a VCC project; VRChat warns that mixing the legacy SDK with VCC-managed packages can break the project.

For package problems:

Close Unity before changing project packages in Creator Companion.
Open the project in Creator Companion and select Manage Project.
Confirm the expected project type and official packages.
Review third-party packages added shortly before the problem appeared.
Reopen Unity and allow package resolution and compilation to finish.

The official packages are:

VRChat Base for files shared by avatar and world projects;
VRChat Worlds for world creation;
VRChat Avatars for avatar creation.

5. Resolve Missing VPM Packages

VPM-compatible projects include the Package Resolver. When Unity opens a project, the Resolver compares Packages/vpm-manifest.json with the installed package folders.

If it reports missing or mismatched packages:

Select Show Me What's Missing to inspect the list; or
Select OK or Resolve All to restore the versions specified by the VPM manifest.

The Resolver may also remove legacy package folders that should not exist separately in a current VPM project. Use the package manager instead of copying SDK folders between projects.

6. Check the VRChat SDK Builder

Open VRChat SDK > Show Control Panel > Builder for build and upload problems.

The Builder reports required fixes and advisory messages. Check it for:

a missing scene descriptor in a world;
missing VRChat layers or collision settings;
invalid avatar or world components;
Audio Source, texture, or Udon problems;
platform-specific validation.

Resolve required validation messages, then read the Unity Console if the build still fails.

VRChat's SDK troubleshooting page identifies two primary checks when the build control panel is absent:

use the Unity version recommended by VRChat;
resolve compilation errors from third-party scripts or components.

7. Diagnose Visual Problems

Pink materials

A pink material normally indicates that its shader is missing, unsupported, or incompatible with the current render pipeline.

Inspect one affected material:

Select it in the Project window.
Record the shader shown in the Inspector.
Confirm that the shader package is installed and supports the project's pipeline.
Test the fix on one material before changing the rest.

VRChat uses Unity's Built-in Render Pipeline. Do not convert a VRChat project to URP or HDRP to repair pink materials.

Missing objects or references

Select the affected GameObject or prefab and inspect:

missing scripts in the Inspector;
missing object fields;
prefab overrides;
assets moved or renamed outside Unity;
deleted .meta files.

Move and rename assets inside Unity so their metadata and references remain paired.

8. Find the Logs

Unity writes Console messages to log files. From the Console menu, select Open Editor Log.

On Windows, the default locations include:

Editor:          %LOCALAPPDATA%\Unity\Editor\Editor.log
Package Manager: %LOCALAPPDATA%\Unity\Editor\upm.log

Creator Companion logs are available from its Logs tab or:

%LOCALAPPDATA%\VRChatCreatorCompanion\Logs

When requesting help, include the relevant error and surrounding log context. Remove account names, local paths, tokens, or other private information before posting a log publicly.

Common Repairs

The VRChat SDK menu or build panel is missing.

Check the Console for compile errors first, then confirm the project uses VRChat's recommended Unity version and contains the correct VCC-managed official package for its project type.

The Package Resolver says packages are missing.

Use Show Me What's Missing to review the package IDs and versions, then Resolve All to restore the packages specified by Packages/vpm-manifest.json.

Creator Companion cannot create a backup.

Check whether the full Windows project path is too long. Move or copy the project to a shorter location, add that project to Creator Companion, and try Make Backup again.

The project opens to a blank scene after migration.

Browse the Project window under Assets for the saved scene and open it. VRChat notes that a scene saved only as SampleScene or UdonExampleScene may not be copied during migration unless it was first saved under Assets.

The build fails but the SDK validation list looks clear.

Open the Unity Console and read the earliest relevant red error. If the Console view is insufficient, open Editor.log and inspect the messages immediately before the failed build.

A package update introduced compile errors.

Record the package ID and installed version, close Unity, and use Creator Companion to select a compatible version or remove the third-party package. Restore the backup if the project remains broken.