Fixing Build Problems
This page will guide you through the steps of figuring out why the changes you've made to your VRChat world might not be appearing after building or why you are getting "Last built VRChat Scene could not be found. Please Test/Compile Full Scene (Slow)." when trying to build.
The Console can be either opened from the Unity Menu Bar inside the Window menu category in the General submenu or using the Ctrl + Shift + C shortcut.
- Ensure Error Pause is disabled and enable Collapse to have fewer logs to go through.
- The logs you are looking for usually will be red Errors. Yellow Warnings will not matter in almost every case except for things listed below Rare Problems.
- You can disable showing Messages and Warnings and only have Errors enabled to find what you are looking for quickly.
Start by clearing the console once and building again after making sure the build errors are visible in the console.
- While working with SDK2, you will see "Trigger on x was not initialized in time!" in your Console. These do not matter and normally happen with the SDK.
- The Errors you are looking for will usually be above an Error, "Error building Player because scripts had compiler errors".
Once you've located the errors stopping the new build from happening, you can inspect them better by selecting them and seeing the full message in the window at the bottom. If the errors are caused by 3rd party script not related to the SDK, and you aren't using them, you can delete them.
If you are using the asset with the problem script:
- Make sure the asset hasn't been depreciated and is supported on the current Unity version
- Update to the latest version of the asset
- Report the bug to the asset author so they can fix it
If the problem is a script inside the SDK:
- Follow the up to date instructions to reimport the SDK you are using from https://docs.vrchat.com/docs/updating-the-sdk
If the problem persists after these steps ask for help! Post a proper screenshot of your errors to make the life of the person helping you easier.
Problems where the cause of the problem isn't always clear.
Warning: No AssetBundle has been set for this build.
Unity can't include the current scene in the build. One example cause for this is when you have your scene file outside of the Assets folder.
List of assets known to cause problems with solutions for each case included.
Error: Assets\AllSkyFree\AllSkyFree_Menu.cs(10,4): error CS0246: The type or namespace name 'MenuItem' could not be found (are you missing a using directive or an assembly reference?)
Includes a script that causes build errors delete Assets/AllSkyFree/AllSkyFree_Menu.cs to fix the issue.
Error: Assets\SimpleLightProbePlacer\Scripts\LightProbeGroupControl.cs(34,13): error CS0200: Property or indexer 'LightProbeGroup.probePositions' cannot be assigned to -- it is read only
The asset is not compatible with Unity 2018 and above either apply the patch as described here or remove the asset after setting up your light probes.
Error: Cannot mark assets and scenes in one AssetBundle. AssetBundle name is "coconut_palm_tree".
The asset contains a Scene file with an asset bundle name set in its meta file, causing it always to get included in builds causing builds to error out. Either erase it from the meta file or delete the scene: Assets/Coconut Palm Tree Pack/Coconut Palm Tree Pack.unity