メニュー
Runs UVS Benchmark Play Mode performance tests against Unity Registry Visual Scripting 1.9.11 in uvs-benchmark. Use when the user asks to run benchmark tests on stock 1.9.11, Registry baseline, Run A, or compare against enhanced without naming the enhanced branch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Compares UVS Benchmark Play Mode results between Registry 1.9.11 and enhanced (or two XML files). Use when the user asks to compare benchmark runs, delta, enhanced vs stock UVS, or interpret A vs C matrix results.
Runs UVS Benchmark Play Mode performance tests against the community Visual Scripting fork on the enhanced branch (Git UPM from uvs-benchmark monorepo). Use when the user asks to run benchmark tests on enhanced, Run C, the fork, or community UVS optimizations.
Reports UVS Benchmark Play Mode performance test results from TestResults XML (Registry, enhanced, or stable). Use when the user asks for a benchmark report, test results summary, performance numbers, or after running uvs-playmode-tests skills.
| name | uvs-playmode-tests-registry |
| description | Runs UVS Benchmark Play Mode performance tests against Unity Registry Visual Scripting 1.9.11 in uvs-benchmark. Use when the user asks to run benchmark tests on stock 1.9.11, Registry baseline, Run A, or compare against enhanced without naming the enhanced branch. |
| disable-model-invocation | true |
Runs matrix Run A: stock com.unity.visualscripting 1.9.11 from the Unity Registry.
From the uvs-benchmark repo root, execute:
.\tools\Run-UvsPlayModeBenchmarks.ps1 -UvsSource Registry
Do not skip package switching. Do not ask the user to switch git branches.
Projects/UvsBenchmarkHost/Packages/manifest.json has a com.unity.visualscripting entry (adds 1.9.11 if missing).Set-UvsManifestSource.ps1 -Source Registry.Miraluna.Uvs.Benchmarks.Tests.$env:UNITY_EDITOR pointing at Unity.exe (6000.4.0f1).6000.4*.If resolution fails, set UNITY_EDITOR and re-run.
.\tools\Run-UvsPlayModeBenchmarks.ps1 -UvsSource Registry -TestFilter "UvsCounter"
.\tools\Run-UvsPlayModeBenchmarks.ps1 -UvsSource Registry -UnityPath "C:\Program Files\Unity\Hub\Editor\6000.4.0f1\Editor\Unity.exe"
| Artifact | Location |
|---|---|
| NUnit XML | TestResults/playmode-Registry-<timestamp>.xml |
| Unity log | TestResults/unity-playmode-Registry-<timestamp>.log |
| Performance reports | PerformanceTestResults/ (gitignored) |
Sample groups should show UVS version 1.9.11 and source registry (via UvsPackageProbe).
UpdateOverheadTests: UvsOverhead_*, CSharpOverhead_* (100 / 1000 / 5000)CounterUpdateTests: UvsCounter_*, CSharpCounter_* (100 / 1000 / 5000).\tools\Report-UvsPlayModeResults.ps1 -Source Registry
Or skill uvs-playmode-results-report.
After this run, use skill uvs-playmode-tests-enhanced, then uvs-playmode-results-compare (or Compare-UvsPlayModeResults.ps1).
Window → General → Test Runner → PlayMode → Performance, after Set-UvsManifestSource.ps1 -Source Registry and reopening Projects/UvsBenchmarkHost.
| Issue | Action |
|---|---|
| Manifest script error | Ensure host project path is Projects/UvsBenchmarkHost |
| Unity not found | Set UNITY_EDITOR to 6000.4.0f1 Unity.exe |
| Tests missing | Confirm testables includes com.miraluna.uvs.benchmarks in host manifest |
| Long first run | UPM resolve/import; wait for batch mode to finish |
See docs/benchmarking.md.