Skip to content
Document Version v2026.08.31.0
Download PDF

Capability Boundaries

Goal

Clarify how current capabilities are meant to be used and which behaviors are product boundaries rather than regression bugs.

Current Capability Boundaries

1. Board-level 3D display scope

  • 3D supports design inputs that form a board session and shows board surfaces, pads, vias, silkscreen, and component bodies
  • imported 3D component models are preferred when available in a renderable format
  • missing, unsupported, or failed component models fall back to proxy bodies or issue records rather than blocking the whole 3D view

2. Export starts from 2D

  • the export button is unavailable in 3D and Data
  • 3D and Data remain review views; return to 2D before export to confirm visibility, camera, and export scope

3. Export and delivery are unlocked by Plus

  • if export access has not been unlocked yet, the workspace does not start export directly
  • tapping export opens the purchase center first
  • after purchase or restore succeeds, export becomes available again

4. There is currently no SES import entry

  • the file picker does not list SES as an importable document
  • the document menu offers no SES entry for new documents or appended revisions

5. iOS Photos is the PNG destination

  • PNG saves only to Photos; it is not handed off to Files or other apps
  • PDF, original-source export, and converted export are delivered only through Other Apps and do not save to Photos

6. macOS export uses file destinations

  • macOS uses the save dialog to choose the destination path

7. Original-source export depends on the current revision being library-managed

  • the original-source export option only appears when the currently open revision is managed by the library
  • original-source export does not read directly back from a temporary external path

8. AI capability depends on external AI service setup

  • the settings page can configure multiple AI services
  • actual usability depends on AI credentials, network access, and AI service response

9. The language page is not an in-app instant language switcher

  • it mainly explains the system-level language path
  • after changing it, the app may need to be relaunched

10. Directory-style manufacturing inputs go through recognition

  • folders and archives go through app recognition before entering the matching manufacturing import path

11. Schematics support viewing and targeting

  • The schematic Workbench supports sheet navigation, object search, details, locate, highlight, and canvas pick
  • Schematic editing, ERC fixes, and property writeback stay in dedicated EDA tools
  • Symbols, pins, footprints, pads, and nets with an exact object identity in the same KiCad project support bidirectional cross-probing. Dual canvases link automatically; a single canvas provides an explicit jump and one-level return.
  • BOM-only components, symbols without a footprint, board footprints without an associated schematic, and missing or ambiguous relationships do not guess a target. Use details to inspect them instead.

How to Use This Page

  1. Before filing a bug, check whether the case falls inside one of these boundaries.
  2. If product behavior conflicts with this page, report it as a documentation-vs-version mismatch first.
  3. If a capability boundary changes, update the handbook and QA pages together.

Cases to File as Bugs

  • reproducible crashes
  • blocking failures in a clearly supported path
  • regressions from previously stable behavior