In a STEP viewer's exploded view, moving one copy of a repeated part looks right on screen. Export to STEP and every copy has moved by the same amount. The importer gives each later copy its own id that includes its parent's id. The exporter rebuilds ids from the label alone, so every copy gets the first copy's id. The viewport and the file disagree about what the assembly is, and only someone who reopens the export would notice.
Recurring agent failure issue in Loupe (imperator28)
What engineers report
A recurring agent failure problem in Loupe (imperator28) that mostly hits the mechanical designer.
Failure pattern: agent / failure
Analyst note
From the Grok pain-radar digests, Nov 11-12 2026 (Nov 11 8:41 AM ET through Nov 12 5:41 AM ET digests plus the Haitch editions). Verified live 2026-11-12: issue/PR read; title and state confirmed.
What it costs a team
Modeled annual cost
$30,000
For a team of 5
Prototype delay
3 days
Modeled schedule slip per occurrence
Time lost
240 min
Per engineer per month, about 1 incidents
How the cost is modeled
240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000
A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.
Engineering tools that address it
No engineering tool profile lists this error yet. Browse tools that connect to Loupe (imperator28).
Evidence
Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.