Closed feature request

Coordinate component hero home view with long-axis MPN orientation

John Lauer · ·closed by Colby Knox

Environment: public Wiki embedded Babylon9 viewer bundle /static/vendor/adom-3d-viewer-babylon9/adom-3d-viewer-babylon9.esm.js?v=20260923a; Chrome for Testing153.0.8010.12 on Linux with SwiftShader; adom-wiki1.7.69. No desktop Bridge involved. Exact deployed viewer package revision is not exposed by this page.

Default home view makes the long-axis virtual MPNs on two published component heroes read upside down. Top and underside views retain correct lead/pad alignment, so rotating the reusable physical library to compensate would be the wrong fix. Please review whether the shared home orientation should consume author-supplied presentation orientation, coordinated with the marking planner and component-hero authoring contract. The caller is the Wiki viewer template; transfer to adom/wiki if ownership belongs there.

Reproduce on https://wiki.adom.inc/adom/opa189idbvr and https://wiki.adom.inc/adom/lm339bidr : Load 3D model, then Home. The default camera is alpha0.7853981633974483,beta0.9553166181245092. The attached home screenshots show inverted text; top screenshots show the long-axis mark and pin labels. This is reproducible with ?animate=0 at /viewer/3d/adom/component/<slug> and window.__viewerDrive.camera('home'); it is not an animation transient. No exception is raised.

Expected: the first hero view should present the virtual MPN legibly while preserving physical pin numbering, seating, hero pad alignment and board-use coordinates. A presentation-only solution needs verification with both five-pin and fourteen-pin packages and a square QFP. Do not alter every physical model or merely redefine pin1 to fit a camera.

Observed during electronic-load component review on2026-10-11. No earlier known-good deployment identified. Source fix, package release and deployed availability are not claimed.

opa189idbvr-home

opa189idbvr-top

lm339bidr-home

1 Reply

Colby Knox ·

Shipped on prod: adom-3d-viewer 0.9.1, vendored in git-wiki 1f0e134 (bundle 20261012a).

The fix is presentation only, as you asked: no physical model, pin 1 or board coordinate changes. A page already sets its opening view with component.viewer_3d.camera ({ "alpha", "beta", "radiusScale"? } in radians, the ?camera= contract). Before this, Home (the view cube's Home and __viewerDrive.camera('home')) ignored it and jumped to the generic top-front-right corner. The viewer now has setHomeView(), and the wiki passes the page's authored view to it, so Home returns to the author's view. Pages without one keep the corner.

For opa189idbvr, the opposite corner reads the marking right side up with pads, leads and seating unchanged. Default home vs ?camera=3.9269908,0.9553166:

To apply it, set this in each page's package.json and republish (or push page.json); Home then lands there too:

"component": { "viewer_3d": { "camera": { "alpha": 3.9269908, "beta": 0.9553166 } } }

I verified opa189idbvr (5-pin) only. lm339bidr (14-pin) should take the same value, since its marking runs the same way on the long axis. A square QFP has no long axis: pick the alpha whose side the marking reads from (the four corners are 0.785, 2.356, 3.927 and 5.498). Those three page edits are yours, so I have not touched the pages.

2026-10-12T15-26-14

2026-10-12T15-26-35

Colby Knox closed this ·

Log in to reply.