简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

our fr5 housing wait points at the fixture that was removed

OmarBrooks0839 · 2026年2月24日 23:51 UTC

已关闭
OM
OmarBrooks0839
The FR5 package's current waiting step names the old receiving fixture even though the installed job is for its replacement; I've kept both package identities and the matched event history, and want support to explain which branch supplies that wait before another generic video request.

15 条回复

HE
HenryAdams0090

Check which configuration the normal launcher actually loads. A new job name can sit above an old fixture mapping. Have the package author compare the loaded path and active branch.

21
OM
OmarBrooks0839

Normal launcher loads the new job file but the old fixture configuration from a shared folder, according to the startup record; the maintainer has sent both resolved paths to the author

15
OS
OscarAllen0271

Old configuration, or merely an old name inside the right configuration?

17
OM
OmarBrooks0839

Old input mapping, not just the label; its expected receiving confirmation belongs to the removed fixture, and the installed fixture drawing identifies a different input

15
AN
AnikaAli0247

Ask the author to explain why the old file was found. A corrected mapping is useful, but somebody restoring the same backup can put it straight back. We need a job package which brings its intended configuration with it, not a workstation which happens to contain the right leftovers.

22
EL
EllaAli0207

Was the replacement fixture ever checked through this normal launcher?

4
OM
OmarBrooks0839

The installation check used the author's direct launch from the new package folder; the normal shortcut retained the shared configuration location, which is now part of the correction

14
HE
HenryAdams0090

That explains why it looked intermittent across users. Were all your reported stops started through that shortcut, though? I'd keep any direct-launch failures separate until checked.

15
OM
OmarBrooks0839

The retained failures in this ticket all have the normal shortcut's startup path; I've left an older unrecorded complaint outside that conclusion rather than assigning it the same cause

14
OS
OscarAllen0271

Does the revised package reject a missing configuration instead of finding the old one?

6
AN
AnikaAli0247

And reject the wrong fixture identity if somebody selects that old file deliberately. A file existing isn't enough to make its input names belong to the installed tooling.

9
OM
OmarBrooks0839

The revision requires its intended fixture identity and reports a missing or mismatched configuration instead of falling back; the maintainer is checking that plus the receiver-available and receiver-unavailable cases from the normal shortcut

22
EL
EllaAli0207

Who is updating the restore instructions?

17
OM
OmarBrooks0839

The package author updated them, and maintenance restored the package and repeated the normal-shortcut checks, including missing and wrong configuration cases; the receiver states now match the installed fixture and this ticket's mapping fault is closed

17
HE
HenryAdams0090

Thanks for reporting the restore check. Send the seller that corrected package identity with closure, so another contact doesn't offer you the old shared-folder version again.

17

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .