OwenBaker0486 · 30 Jan 2026, 19:12 UTC
Run it from the normal shortcut and capture the interpreter and loaded module path on both laptops. Folder names can be misleading; mine certainly have been.
4 pointsOld shortcut loads a copy inside its application folder, not the SDK folder I transferred; the rebuilt laptop loads the transferred copy and its method signature differs
14 pointsThere is your difference to take to the maintainer. Match the call to the supported library and controller version before changing arguments just to get past the error.
19 pointsDoes the normal shortcut run under the same account you're using for these checks, Owen?
8 pointsYes, Toby, same account; maintainer has identified the supported package and updated the call from its documentation, with the old working copy retained for comparison
23 pointsThe normal shortcut now returns the intended controller identity after reopening as well; we checked the loaded path again under the shift account, and the application folder has one documented dependency set instead of three guesses
8 pointsGood, thanks for posting the shortcut result. That's the route the next person will actually use.
17 pointsThis discussion is closed to new replies after six months without activity. Last activity: .