Unity 2019.4.31f1项目脚本加载无报错但所有带脚本GameObject失效，如何查看错误及.NET编译器输出？

Hey there, let's tackle this head-scratcher you're dealing with in Unity 2019.4.31f1. Silent script failures with only vague warnings are the worst, but there are ways to dig up the actual errors and get to the bottom of it.

1. Dig into Unity's Editor Log for Hidden Details #

Unity's main console often filters out low-level compilation errors, but the full editor log will have them. Here's how to access it:

• From the Unity Editor, open the Console window, click the three-dot menu in the top-right corner, and select Open Editor Log.
• Alternatively, navigate directly to the log file on your system:
  • Windows: C:\Users\[YourUsername]\AppData\Local\Unity\Editor\Editor.log
  • Mac: ~/Library/Logs/Unity/Editor.log
  • Linux: ~/.config/unity3d/Editor.log
• Search the log for keywords like error, compilation failed, or CS followed by a number (e.g., CS0246). These are the actual compiler errors that aren't showing up in the main console.

2. Force a Full Recompilation & Capture .NET Compiler Output #

Unity's caching can sometimes mask underlying issues. Forcing a full rebuild and capturing compiler output directly will help:

• First, trigger a full reimport: Go to Assets > Reimport All. This will make Unity reprocess every asset, including scripts and NuGet dependencies, which might surface hidden errors.
• To get detailed .NET compiler output, launch Unity via the command line with logging enabled:
  1. Open a command prompt/terminal and navigate to your Unity 2019.4.31f1 installation folder (e.g., C:\Program Files\Unity\Hub\Editor\2019.4.31f1\Editor on Windows).
  2. Run this command (replace the paths with your project and desired log file location):

     Unity.exe -batchmode -projectPath "C:\Path\To\Your\Unity\Project" -quit -logFile "C:\Path\To\Save\Compiler_Details.log"
     

  This will launch Unity in batch mode, recompile your project, then quit. Open the generated log file and look for sections starting with Microsoft (R) Visual C# Compiler – this is where you'll find the raw compiler output with any hidden errors.

3. Debug NuGet Dependency Conflicts #

Since removing the NuGet package brings back expected errors, the issue is almost certainly a dependency conflict or broken assembly reference:

• Check your Packages/manifest.json and Packages/packages-lock.json files for conflicting versions of transitive dependencies. Sometimes NuGet packages pull in libraries that clash with Unity's built-in .NET assemblies.
• Use Assembly Definition Files (.asmdef) to isolate your scripts. Create one in your main script folder, then in its inspector, explicitly reference only the NuGet assemblies and Unity packages you need. This can help narrow down which dependency is causing the silent failure.
• Try rolling back or updating the problematic NuGet package to a different version. Unity 2019 uses .NET Framework 4.x or .NET Standard 2.0 by default, so newer NuGet packages might have compatibility issues with this older runtime.

4. Check for Silent Assembly Loading Failures #

Even if compilation succeeds, assemblies might fail to load at runtime without triggering a console warning. Add this simple script to log loaded assemblies:

using UnityEngine;
using System.Reflection;
using System;

public class AssemblyLoaderChecker : MonoBehaviour
{
    void Start()
    {
        foreach (Assembly assembly in AppDomain.CurrentDomain.GetAssemblies())
        {
            Debug.Log($"Loaded Assembly: {assembly.FullName}");
        }
    }
}

Attach this to a GameObject in your startup scene, enter Play Mode, and check the console. If any of your NuGet-related assemblies are missing or listed with load errors, that's the source of your problem.

内容的提问来源于stack exchange，提问作者Jared