# MSet 2026 key-in evidence reference - MicroStation Status: **canonical-development evidence index** Branch: **MSet 64-bit** Target: **MSet 2026 / MicroStation 2026 unless a row says otherwise** Release: **20260919-v35** Knowledge version: **2026.09.19-v35** ## Purpose This is a compact evidence reference for MSet-relevant MicroStation command forms and promoted semantics. It combines reviewed Instruction Author evidence with current runtime reconstruction, real MSet corpus observations, Bentley documentation/support evidence and explicitly labelled GRAPHICO production practice. If an operation is not present here or in another authoritative current source, treat its exact syntax as unverified. ## Evidence labels - **runtime-verified** - exercised successfully by GRAPHICO on the stated current host/runtime. - **runtime-observed** - a specific behavior was observed; do not generalize beyond that observation. - **historical/supporting** - established by historical GRAPHICO packages/manual evidence and suitable as a candidate where the task explicitly allows verification, but not current-host proof. - **canonical normalization/rule** - an MSet authoring rule about a known form; it does not prove arbitrary commands that merely resemble it. - **unverified** - no exact current authoritative command contract yet. - **Bentley-documented** - semantics/syntax supported by Bentley Help/Support material; keep the cited scope/version in mind. - **runtime-reconstructed** - canonical syntax reconstructed from the current MicroStation runtime command table; this proves the command surface, not every semantic detail. - **corpus-observed** - observed in real historical/production MSet instruction packages; occurrence is practice evidence, not by itself semantic authority. - **GRAPHICO production-practice** - empirical recommendation from long-term MSet/MicroStation production use; keep it distinct from Bentley documentation. - **MSet-runtime-contract** - behavior established by current MSet 2026 source for MSet-specific composition/substitution; this is separate from proof that MicroStation itself accepts an arbitrary spelling. - **Bentley-documented** - semantics/syntax supported by Bentley Help/Support material; keep the cited scope/version in mind. - **runtime-reconstructed** - canonical syntax reconstructed from the current MicroStation runtime command table; this proves the command surface, not every semantic detail. - **corpus-observed** - observed in real historical/production MSet instruction packages; occurrence is practice evidence, not by itself semantic authority. - **GRAPHICO production-practice** - empirical recommendation from long-term MSet/MicroStation production use; keep it distinct from Bentley documentation. ## Current command index | Command/form | Evidence | Scope / authoring note | Canonical source | | --- | --- | --- | --- | | `co=bylevel` | runtime-verified package evidence | Evidence-backed symbology baseline used by the current verified `MSet_Polohopis` package. | module 05 | | `lc=bylevel` | runtime-verified package evidence | Evidence-backed baseline; remember MSet line-style auto-scale processing after `lc=`. | modules 03, 05 | | `wt=bylevel` | runtime-verified package evidence | Evidence-backed symbology baseline. | module 05 | | `place smartline` | historical/supporting; current-host runtime test still required; current authoring preference | Preferred general-purpose linework when no specific resulting element type is required. | modules 05, 09 | | `place line` | historical/supporting; current-host runtime test still required | Single-line/segment-oriented candidate. | module 09 | | `place lstring` | historical/supporting; corpus-observed; GRAPHICO production-practice | Situational when LineString/exact workflow intent matters; not the generic default. In 3D prefer `place smartline` unless LineString identity is required: GRAPHICO has empirically observed occasional incorrect `place lstring` behavior in 3D. | modules 05, 09 + production practice | | `place shape` | historical/supporting; current-host runtime test still required | Geometry candidate; not labelled current-host runtime-verified by the track. | module 09 | | `place cir radius ` | historical/supporting; parameterized form current-host runtime test still required | Explicit-radius circle candidate; `$S(...)` may be appropriate for a scale-sensitive numeric radius when requested. | module 09 | | `place block rotated` | runtime-verified | GRAPHICO MicroStation 2026 runtime verification, 2026-08-26. | module 09 | | `place cir` | runtime-verified | Current interactive-radius circle workflow; GRAPHICO MicroStation 2026 runtime verification, 2026-08-26. | module 09 | | `place cir edge` | runtime-observed | Observed three-point/circumference variant on 2026-08-26; do not substitute it for the interactive-radius workflow. | module 09 | | `place dialogtext above` / `place dialogtext below` | historical/supporting semantic evidence | The evidenced relation is above/below an **element**, not generically above/below a point. | modules 07, 09 | | `PLACE CELL` | runtime-reconstructed; MSet-runtime-contract | Full current command surface. Preferred for new MSet 2026 authoring; current MSet `CellScaleRule` recognizes it through the case-insensitive `place cel` prefix, so it gets the same MSet cell-scale handling as legacy `pla cel`. | MicroStation 2026 runtime reconstruction + modules 03, 08 | | `PLACE CELL RELATIVE` | runtime-reconstructed; MSet-runtime-contract | Preferred full form for new relative-cell placement. Current MSet cell-scale recognition is equivalent to legacy `pla cel rel`. | MicroStation 2026 runtime reconstruction + modules 03, 08 | | `PLACE TERMINATOR` | runtime-reconstructed; MSet-runtime-contract | Preferred full form for new terminator placement. Current MSet terminator-scale rule recognizes it through the case-insensitive `place ter` prefix, equivalent to legacy `pla ter` for MSet scale handling. | MicroStation 2026 runtime reconstruction + modules 03, 08 | | `TH=` / `TW=` / `TX=` / `LS=` | MSet-runtime-contract | Supported text scale-sensitive assignment forms. Keep them compact; do not mechanically expand them as if they were legacy word-prefix abbreviations. | module 03 | | `LC=` | MSet-runtime-contract | Current trigger for MSet line-style auto-scale. Do not substitute a guessed full-word spelling unless equivalent MSet behavior is separately verified. | module 03 | | `AC=` / `AR=` / `CM=` | MSet-runtime-contract | Current cell-related triggers used by MSet cell-scale detection. Their own values are not the scale value; the cell rule ensures/adjusts `AS=`. | module 03 | | `LT=` | MSet-runtime-contract | Current terminator-related trigger used by MSet terminator-scale detection; the terminator rule ensures/adjusts `TS=`. | module 03 | | historical `pla ...` -> new-authoring `place ...` | canonical normalization/rule | Prefer a complete established canonical command when available, not merely a half-expanded leading token. Example: `pla cel rel` -> `place cell relative`. | module 08 | | historical `act ...` -> new-authoring `active ...` | canonical normalization/rule | Normalize the known leading token; do not guess unrelated unknown abbreviations. Example: `act ang pt2` -> `active angle pt2`. | module 08 | | `ACTIVE FILLCOLOR` | corpus-observed; historical/supporting | Sets the active fill color. | MSet corpus + Bentley/supporting key-in evidence | | `ACTIVE TXJ ` | corpus-observed; Bentley/supporting semantic evidence | Sets Text justification. Use the justification suffix table below. | MSet corpus + Bentley support/archive evidence | | `ACTIVE TNJ ` | corpus-observed; Bentley/supporting semantic evidence | Sets Text Node justification. Use the same justification suffix table below. | MSet corpus + Bentley support/archive evidence | | `FILEDESIGN` | corpus-observed; Bentley-documented/supporting | Save Settings for the active design file; useful at the end of batch/reference display command sequences when the change must persist. | MSet corpus + Bentley support | | `SELVIEW ` | corpus-observed; Bentley-documented/supporting | Supplies the target view (or all views) to view-specific command sequences such as reference-level display operations. | MSet corpus + Bentley support/archive | | `LOCK FENCE INSIDE` / `LOCK FENCE CLIP` | corpus-observed; Bentley-documented/supporting | Sets Fence Selection Mode to Inside / Clip. | MSet corpus + Bentley support/archive | | `REFERENCE EXCHANGE` | corpus-observed; direct Help semantic evidence | Opens/exchanges to the selected reference as the active working model while retaining the view configuration. See DGN reference section below. | MSet corpus + Bentley Help/training | | `RASTER ATTACH FIXED` | runtime-reconstructed; Bentley-documented/supporting | Attaches a raster without interactive placement; use the raster/header attachment geometry unless another placement contract is specified. | MicroStation 2026 runtime + Bentley support | | `RASTER DETACH ALL` | runtime-reconstructed | Canonical current-runtime command surface for detaching all raster attachments. | MicroStation 2026 runtime reconstruction | | `USERCOMMAND` | corpus-observed; legacy/supporting | Legacy MicroStation User Command / UCM invocation mechanism. Do not infer modern parameters or a current recommended workflow from the bare command name. | MSet corpus + historical MicroStation evidence | ## Text and Text Node justification For natural-language authoring, map the requested justification to the suffix first, then choose Text (`TXJ`) or Text Node (`TNJ`). The justification point is the text/text-node anchor (reference point). | Suffix | Meaning | Slovak intent examples | | --- | --- | --- | | `LB` | Left Bottom | vľavo dole | | `LC` | Left Center | vľavo na stred | | `LT` | Left Top | vľavo hore | | `CB` | Center Bottom | na stred dole | | `CC` | Center | na stred / stred | | `CT` | Center Top | na stred hore | | `RB` | Right Bottom | vpravo dole | | `RC` | Right Center | vpravo na stred | | `RT` | Right Top | vpravo hore | Examples: ```text "zarovnaj text vpravo hore" -> ACTIVE TXJ RT "zarovnaj text-node vľavo dole" -> ACTIVE TNJ LB ``` Do not confuse Text with Text Node: use `TXJ` for ordinary text and `TNJ` for a text node. ## DGN / vector reference operations This is the semantic/reference section for working with attached DGN/vector references. Prefer a stable **logical name** when a project provides one; it is usually more robust for automation than a physical path/file name. Configuration-variable/relative reference paths are preferable to hard-coded machine-specific paths where the project contract supports them. ### Display, levels and view targeting - `REFERENCE DISPLAY ON|OFF|TOGGLE ` controls the whole reference attachment display. Nested references may be addressed as paths such as `Ref_1.dgn->Ref_2.dgn`; `*`/`ALL` may be used where Bentley documents wildcard use. - `REFERENCE LEVELS ON|OFF|TOGGLE ` controls **View Display** of levels in a reference. This is view-specific; follow it with `SELVIEW ` or `SELVIEW ALL` when the command sequence must explicitly target views. - `LEVEL SET DISPLAY ON|OFF file: ` controls **Global Display**, including reference levels. Do not present this as a synonym for `REFERENCE LEVELS`: View Display and Global Display are different states. - `FILEDESIGN` saves design settings. In batch/reference workflows it is commonly appended after the view-selection command when the display state must persist. Example patterns documented by Bentley support/archive material: ```text REFERENCE LEVELS OFF Preliminary REF->ISO;SELVIEW ALL;FILEDESIGN LEVEL SET DISPLAY OFF file:"testV08.dgn" Preliminary;SELVIEW ALL;FILEDESIGN ``` ### Attachment settings and nested references Bentley documents a general `REFERENCE SET` family. Useful settings include: ```text REFERENCE SET DISPLAY=ON|OFF REFERENCE SET SNAP=ON|OFF REFERENCE SET LOCATE=ON|OFF REFERENCE SET DISPLAYRASTERREFS=ON|OFF ``` `file_spec` may be a file name or logical name; nested paths may use `->`. Keep exact task-specific selectors evidence-gated rather than guessing them. ### Attach / detach / exchange Bentley documents the full attach family as: ```text REFERENCE ATTACH [configuration_variable:]filename [,model_name] [,logical_name] [,description] [,view_name] [,scale] [,nesting] [,ON|OFF] ``` Supplying enough arguments can avoid the interactive dialog. Project configuration variables and relative/reference-root paths are preferred when they are part of the project contract. `REFERENCE DETACH` is a current canonical runtime command and is heavily observed in the MSet corpus; do not guess an attachment-selector tail when it is not already established by source/task context. `REFERENCE EXCHANGE` changes the selected reference into the active working model and retains the same view configuration. Historical/practical evidence describes the operation as swapping the reference and active/master roles. GRAPHICO production experience further observes that the new active model opens at the same working location/zoom seen immediately before the exchange; keep that exact location/zoom statement labelled **GRAPHICO production-practice** rather than Bentley-documented semantics. ## Raster references Raster attachments are managed separately from DGN/vector references. Raster Manager changes attachment information in the DGN; it does not modify the original raster image data. ### Attach ```text RASTER ATTACH FIXED RASTER ATTACH INTERACTIVE ``` - **Interactive** placement lets the user define the raster extents/placement with data points. - **Fixed** is the non-interactive attachment path; unlike interactive placement, it does not ask the user to define raster extents with placement data points. Use the established attachment/file geometry and project georeferencing contract rather than inventing placement coordinates. - Historical V8i command-line batch processing may require `MDL LOAD RASTMGR` before `RASTER ATTACH FIXED`; this is legacy/supporting evidence, not a blanket MicroStation 2026 prerequisite. ### Display, clipping and detach ```text RASTER DISPLAY ON RASTER TOOLCLIP RASTER DETACH ALL ``` `RASTER DISPLAY ON` is Bentley-documented for raster display; `RASTER TOOLCLIP` is Bentley-documented as the raster clipping tool key-in; `RASTER DETACH ALL` is reconstructed from the current MicroStation 2026 runtime command table. ### Rasters carried through DGN references When the raster is attached **inside a DGN reference**, use the DGN-reference setting rather than treating it as a direct master-model raster attachment: ```text REFERENCE SET DISPLAYRASTERREFS=ON|OFF ``` This controls whether raster references belonging to the specified DGN reference are displayed. Keep this distinction explicit: ```text "vypni raster pripojený priamo v tomto modeli" -> RASTER ... "vypni rastre, ktoré prichádzajú cez referenciu PODKLAD" -> REFERENCE SET DISPLAYRASTERREFS=OFF PODKLAD ``` ## Provenance boundary for the promoted semantic sections The semantic additions above combine several evidence layers and must keep them distinct: - MicroStation 2026 runtime reconstruction: canonical command surface/existence. - Real MSet corpus: historical/production occurrence and frequency. - Bentley Help/Support/archive material: documented/supporting semantics and command patterns. - GRAPHICO production-practice: empirical recommendations such as preferring `PLACE SMARTLINE` over `PLACE LSTRING` in 3D when exact LineString identity is not required, and the observed exact working-location/zoom continuity of `REFERENCE EXCHANGE`. Do not promote a corpus occurrence or an empirical recommendation into a Bentley-documented claim. ## MSet-mediated external action The following is not a general Bentley drawing key-in entry, but it is part of the current MSet authoring evidence contract: ```text $ % "https://..." ``` Evidence: **runtime-verified** in MSet `26.11.0.4` / MicroStation 2026 for HTTP/HTTPS URL opening. See module 10. Do **not** infer from that result that these are canonical yet: ```text $ % "C:\Temp" $ % "C:\Temp\Test.pdf" $ % "" ``` Local folder/document launch, variable expansion, path quoting and missing-target behavior remain **unverified** until their exact current-runtime tests pass. ## Boundary This reference is deliberately small. It is an evidence index, not a complete MicroStation key-in manual. A missing entry must remain a documentation/runtime gap unless another authoritative current source or explicit user-supplied syntax establishes it.