Different paths. Our vendor folder on the old laptop, an installed package on the rebuild. I'd compared everything except the imports, apparently.

Preserve your working copy and compare the two function signatures. Recreating it in an isolated environment should answer the laptop part of the problem.

@BrunoAllen0278 Does recreating that copy really settle the laptop side? It could fix the signature mismatch while leaving a different launcher or dependency problem.

@CallumAbbott0012 You're right; I overstated it. Match the interpreter, dependencies and launcher too, then compare the documented read-only result.

@BrunoAllen0278 Found it: the rejected argument has a different signature. Both copies are intact, and our working laptop is untouched.

@HazelChen1180 My first instinct would've been to change that argument. Why not just match the installed package's signature?

It could remove the local error. You'd still need matching SDK documentation and confirmation of the controller pairing; accepting the arguments doesn't establish the rest of the behaviour.

@BrunoAllen0278 I had a terminal pointing at one environment and a shortcut at another on my setup. My triumphant fix covered exactly one way of launching it.

@JamieChan1078 Checked our launcher too. Same installed-package path as the terminal.

@BrunoAllen0278 Are the controller and SDK meant to have matching version numbers? I don't know whether those numbers belong to the same scheme.

Treat them as separate identifiers unless the documentation says otherwise. Look for a stated pairing, or send both identifiers to support for confirmation.

@BrunoAllen0278 Our maintenance record matches the controller screen. Still no identifiable release archive for that vendor folder, though.

@HazelChen1180 Checksums help compare copies. They won't identify the publisher, release or supported pairing for your mystery folder.

Any local edits? They could prevent an archive checksum match.

@CallumAbbott0012 Can't tell; there's no history. I'm leaving its origin unknown rather than giving our mystery folder a guessed release name.

Your identifiers, signature comparison and sanitized traceback should make a useful support request. Describe the vendor folder as untraced so they don't mistake it for a known release.

Once you know which copy it's, is a dependency list enough to make the next rebuild less painful?

Add SDK source, interpreter, launch instructions and controller ID. Keep a sanitized read-only result too, so you've got a baseline.

Our known paths and IDs are in the note. SDK origin stays blank. A tidy guess would make rebuilding harder.