Deterministic, unique naming for copied 3D objects and their components within the Sand3D library.
Raw Developer Origin & Technical Request
GitHub Issue
Nov 12, 2026
## Question
Should verbs that make copies give each copy a unique, deterministic name by default? This is a feature investigation for a future major version, not a decision on a naming scheme.
Today `copy`, `at(ob, on=[frames])` and `split(ob, frame, keep="both")` return objects that keep the original's name, and so do the parts and joints they hold. Each exporter then makes names unique in its own way: Blender suffixes `drawer.001` in the GLB, the URDF writes `drawer_2`. The same part goes by different names in different files, and its suffix comes from export order, not from the program. A drawer cabinet built with `at(drawer, on=grid(…))`, with a joint added to each drawer, exports links `drawer`, `drawer_2`, `drawer_3`. A `follows=` that names a copied joint becomes ambiguous.
#30 lets a program name a copy explicitly (`copy(ob, name=…)`). This issue is about the default.
## Investigate
- The naming scheme: whether the first result keeps the original name, how `at` numbers its copies, and what `split(keep="both")` should call its two halves. Joints held by a copy are renamed under the same rule.
- Face and edge tags: a copy keeps tags qualified by the original's name (`drawer.top`). Decide whether they follow the new name, and what `join` does with two copies' tags.
- Consistency across exports: one name per part, given by the library, that GLB, URDF, USD and IFC all use, and how this relates to the identity question in #27.
- Impact on published programs and on file...
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from Sandflow-ai/sand3d.
Frequently Asked Questions
Market intelligence mapped to Deterministic, unique naming for copied 3D objects and their components within the Sand3D library..
What is the technical positioning of Deterministic, unique naming for copied 3D objects and their components within the Sand3D library.?
What are the foundational technologies related to Deterministic, unique naming for copied 3D objects and their components within the Sand3D library.?
Engagement Signals
Cross-Market Term Frequency
Counts stored text matches for foundational terms like at and copy in analysed public discussions. These counts do not measure adoption.
Stored text matches, not adoption or market-share measurements.
- at: 1726 records
- copy: 31 records
- split: 17 records
- join: 14 records
- USD: 6 records
- IFC: 2 records
- drawer.001: 1 records
- drawer_2: 1 records
- follows=: 1 records
- face tags: 1 records
- edge tags: 1 records
- GLB: 1 records
- URDF: 1 records
- deterministic name: 1 records
- export order: 1 records
SaaS Metrics