# VectorPaint three-step paired views: map plan treads to side-view heights
Language: en
Canonical: [VectorPaint three-step paired views: map plan treads to side-view heights]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-05T00:00:00+08:00
Modified: 2026-11-05T09:38:59+08:00
Author: Bison
Construct plan and side views of three invented-unit steps, checking shared horizontal boundaries, three rises and direction without construction claims.
English translation of the [Chinese original](), translated on 2026-11-05. Original publication dates, attribution, code and version notes are retained.
A staircase plan shows treads while its side view shows successive rises; the two cannot be arranged independently by eye. Build corresponding views of three equal-width teaching steps in invented units. This is no building, accessibility or construction guidance and assumes no automatic conversion from 2D views to a 3D model.
## Define three rises and three treads
Create a 1200 by 900 pixel canvas with movement and ascent left to right. Each step has one-unit going and rise and two-unit width. Treads A, B and C sit at heights 1, 2 and 3. Total horizontal extent and rise are both 3; verify this manually without counting ground as a fourth tread. Use 80 pixels per unit solely for layout, not real stair dimensions. Place plan above side view with title/unit space. Define scope before adding an unspecified top landing or material thickness.
## Use shared horizontal boundaries for both views
Establish four vertical references at x=0,1,2,3 so corresponding horizontal positions align across both views. Hand-drawn references remain artwork you may keep lightly or hide; inspect native-guide export separately. The plan’s two-unit width is not height. Measure the side view upward from ground 0 to 3 and separate the views so connecting references are not mistaken for material. Inspect shared left/right extents and equal scale before shapes, rather than distorting a finished view to force alignment.
## Draw three equal adjacent treads in plan
Draw a plan rectangle 3 units long and 2 wide, divided into three one-unit goings labelled A, B, C. Areas are equal; C is not wider because it is higher. Boundaries at 1 and 2 match references. This is not perspective foreshortening, so do not taper the plan. Three pale colours may help, but retain labels for monochrome recognition. Count three treads and annotate heights 1,2,3 separately; the plan’s transverse width is not the height coordinate.
## Close the side profile through alternating runs and rises
Start the side profile at ground, rise 1 and run right 1, then repeat twice. After the third run at height 3, descend at the far right and close along ground. There are three horizontal treads at heights 1,2,3 and three unit rises. Inspect corners without heavy strokes, whose extents are not additional dimensions. Show only this simplified solid outline, without unspecified hollow spaces or beams. Check every segment, especially the third one-unit run; reaching the highest rise is not a reason to descend immediately and omit it.
## Use IDs and direction to connect the views
Label the side treads A, B and C in the same sequence and use left-to-right ascending-direction cues in both views. A plan arrow shows travel, not an imaginary drawn slope; side text can explain height. Avoid many crossing leaders where shared boundaries and IDs suffice. Hide colour and retrieve plan B’s counterpart at height 2. If labels crowd risers, use clear short leaders rather than pointing to another step. Establish pairing before adding restrained material colour.
## Change going in both views while preserving height
In a copy, make B’s going 2 units while keeping its height 2. Recalculate total horizontal extent as 4, shift C’s start right, lengthen B in both views and update C/right endpoints. Total rise remains 3; do not widen and heighten the whole side view together. Update common references because the original 0–3 boundaries no longer all apply. Name this going-change revision separately from the equal-going version. Ordinary paths do not understand paired views, so inspect every dependent object and retain independent sources.
## Inspect numbers and proportions in the actual file
Save both views, references and model explanation. In output, read total extents before checking every tread/height. At actual size, keep numbers clear of edges and subdivisions lighter than the outline. Name three-step teaching views, units and revision rather than construction stairs. Check consistent backgrounds in transparent output so one view is not white-backed while the other loses lines. Retain the nonphysical-dimension scope; actual stair safety, materials and standards need their professional process. Reopen the file to exclude going-change test remnants.
## Count boundaries and treads when views disagree
For four apparent steps, check whether ground or the far vertical edge was counted as a tread; return to the three horizontal segments. For misalignment, inspect shared positions and unequal scaling. Find counterparts through ID and height, not colour guesses. If a going change alters total height, inspect selection and the saved source to isolate the intended variable. Recount three treads, three rises and shared boundaries after repairs. The pair should explain one object across directions rather than present two unrelated staircase pictures.
## Related tutorials and sources
[VectorPaint wireframe boxes: distinguish visible edges, hidden edges and shared vertices](), [VectorPaint grids and guides: composition references for icons and posters]().
Sources checked on November 5, 2026: VectorPaint 1.0.8, requiring iOS / iPadOS 17 or later. Capability scope follows the [official App Store description]() and [Apple public version lookup](). These are exercises and checks you can perform, without a claim of step-by-step physical-device testing or verification in every target environment. Example content is instructional; follow the controls in your installed version.