UUM-133483
Fixed in 6000.7.0b4Mentioned in 7 Unity 6 release notes.
First fixed in 6000.7.0b4 (Oct 8, 2026); relisted in 6 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.7.0b8 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.7.0b7 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.7.0b6 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.6.6f1 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.7.0b5 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.7.0b4 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. | |
| 6000.7.0b4 | Fixes Scripting | Fix | Fixed an issue where opening the Standalone Profiler could trigger a script compilation in the Profiler process, which logged "Could not find a part of the path" errors for package assemblies. |