Testers wanted: run playcal on your own Unity project (10 minutes)

[RizgarOzan]

I've only run playcal against my own projects on one Windows machine, so I can't tell yet what breaks on yours. If you have a Unity project and ten minutes, this would help a lot.

You need Unity's CLI working (unity status should list your open Editor) and Python 3.10 or newer.

pipx install git+https://github.com/RizgarOzan/playcal
playcal doctor --project PATH/TO/YourGame
playcal loop settle --project-path PATH/TO/YourGame
playcal observe --project-path PATH/TO/YourGame --seconds 3

observe presses Play and stops it again afterwards, so save your scene first. It doesn't write anything into the project except a screenshot under .playcal/observe/ when the run goes red.

Then reply here with:

• OS, Unity version and Pipeline package version;
• what each command printed (cut out paths if you like);
• roughly how long observe took;
• anything that looked wrong, even if you're not sure it's playcal's fault.

A reply that says "doctor said fail and I don't know why" is exactly what I'm after. If you're on macOS or Linux, the live benchmark in #6 is the next step up.

[RizgarOzan]

playcal has grown since the first call. Besides the Unity loop it now has:

• a Godot backend (headless, nothing installed in the project)
• playtest, which runs a scene several times and separates a flaky failure from a real one
• audio check and assets check, which read import settings and flag things like a streamed UI click or a UI texture with mipmaps
• calibrate --targets, which fails CI when a level's predicted pass rate leaves the band you designed for

What I need is someone with a real project, Unity 6 or Godot 4, to run three commands and tell me where the output was wrong or confusing:

pipx install playcal
playcal doctor
playcal assets check --project-path .

If you use an AI agent on that project, playcal skill --project . writes a SKILL.md for it, and I'd love to know whether the agent actually picked it up. Reply here or open an issue with the output. Nothing gets sent anywhere; every command runs locally.