CallumAli0186 · 9 Dec 2025, 20:35 UTC
Have the maintainer record the interpreter and imported module path from each actual shortcut. Compare the installed versions and the failing call against their documentation before changing the script or controller settings.
16 pointsThe maintainer found the rebuilt shortcut launching a different environment from the terminal used during setup, so we're checking that first.
21 pointsDoes the old shortcut still launch its working copy, Callum? I would want that preserved while the new installation is sorted, not quietly brought into line with the broken one.
13 pointsYes, Omar, the old path and working files are preserved; no changes made there, and the maintainer has both launch configurations recorded.
12 pointsThen confirm which SDK copy the new environment is meant to use. Finding a difference narrows the investigation, but does not by itself say which version belongs in the supported setup.
7 pointsThey've identified the intended version and corrected the rebuilt shortcut to use it; the argument error is gone, but the read-only controller check has not been repeated yet.
20 pointsWill that final check use the ordinary workshop shortcut? Worth closing the same path that failed rather than only proving it works from the maintainer's terminal.
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .